Functional Hierarchical Model

Slides:



Advertisements
Similar presentations
Database Systems: Design, Implementation, and Management Tenth Edition
Advertisements

DFD Rules and Guidelines Yong Choi BPA CSUB. 2 DFD example - Hoosier Burger’s food ordering system I * One process (level 0 - the whole system) * No data.
Chapters 7 & 9 System Scope
Chapter 7 Structuring System Process Requirements
Data Flow Diagrams Levelling Them; Process Modelling Using Function Decomposition CSE Information Systems 1.
Elisati Hulu. Definition  “a deliverable-oriented hierarchical decomposition of the work to be executed by the project team to accomplish the project.
Overview of GIS projects Geog 463 March 29, 2006.
Concepts of Systems Theory
Knowledge Acquisitioning. Definition The transfer and transformation of potential problem solving expertise from some knowledge source to a program.
System Engineering Instructor: Dr. Jerry Gao. System Engineering Jerry Gao, Ph.D. Jan System Engineering Hierarchy - System Modeling - Information.
Process Modelling Using Data Flow Diagrams - Building and Levelling Them; Process Modelling Using Function Decomposition CSE Information Systems.
PROJECT SCOPE, SCHEDULE, AND RESOURCE MANAGEMENT
Chapter 7 Structuring System Process Requirements
Chapter 7 Structuring System Process Requirements
CSC350: Learning Management Systems
Copyright 2002 Prentice-Hall, Inc. Chapter 2 Succeeding as a Systems Analyst 2.1 Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer Joey.
1 ER Modeling BUAD/American University Entity Relationship (ER) Modeling.
DATABASEMODELSDATABASEMODELS  A database model ◦ defines the logical design of data. ◦ Describes the relationships between different parts of data.
Systems Analysis and Design in a Changing World, 6th Edition 1 Chapter 4 - Domain Classes.
Systems Analysis and Design in a Changing World, 6th Edition 1 Chapter 4 Domain Classes.
Work Breakdown Structure Use and Demo
5 - 1 Copyright © 2006, The McGraw-Hill Companies, Inc. All rights reserved.
UML Use Case Diagramming Guidelines. What is UML? The Unified Modeling Language (UML) is a standard language for specifying, visualizing, constructing,
Kal Bugrara, Ph.DSoftware Engineering Northeastern University Fundamentals Of Software Engineering Lecture V.
Chapter 7 Structuring System Process Requirements Modern Systems Analysis and Design Fourth Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich.
Context Process0. student Data Flow Diagram Progression.
Domain Model A representation of real-world conceptual classes in a problem domain. The core of object-oriented analysis They are NOT software objects.
Information Modelling Process Technique- DFD 5C Sybase_PowerDesigner_ html.
© 2005 by Prentice Hall Chapter 7 Structuring System Process Requirements Modern Systems Analysis and Design Fourth Edition Jeffrey A. Hoffer Joey F. George.
© 2008 Prentice Hall6-1 Introduction to Project Management Chapter 6 Managing Project Scheduling Information Systems Project Management: A Process and.
Chapter 4 Identifying and Selecting Systems Development Projects
Fundamentals of Object Oriented Modeling
Teaching Reading in Science
West, Ford & Ibrahim: Strategic Marketing
Data Modeling Using the ERD
Software Design.
Topic 1: Strategic Marketing
Marketing Implementation and Evaluation
CGS 2545: Database Concepts Fall 2010
Problem Solving How do we attack a large problem?
Use Case Model.
Chapter 2 Succeeding as a Systems Analyst
Class diagram Description
Functional Hierarchical Model
Information Technology Project Management – Fifth Edition
Entity-Relationship Modeling
DFD Rules and Guidelines
CV-1: Vision The overall vision for transformational endeavors, which provides a strategic context for the capabilities described and a high-level scope.
Chapter 1: Data Flow Diagram Structuring System Process Requirements
Process & Logic Modeling
Abstract descriptions of systems whose requirements are being analysed
Data Flow Diagram (DFD) Review
USING TECHNOLOGY FOR IMPROVEMENT
Chapter 9 Achieving Operational Excellence and Customer Intimacy: Enterprise Applications.
UML Class Diagram.
Entity – Relationship Model
What is a Relationship Map?
SYS466 Domain Classes – Part 1.
Chapter 4 Identifying and Selecting Systems Development Projects
Welcome W 15 Introduction to Engineering Design II (IE 202)
Thinking Thinking or cognition refers to a process that involves knowing, understanding, remembering and communicating. Thinking involves a number of mental.
Four Main Components for Effective Outlines
Chapter 1 Database Concepts.
Database Design Hacettepe University
Why Study Databases? Databases have incredible value to businesses.
Chapter 4 Identifying and Selecting Systems Development Projects
Copyright © 2005 Prentice Hall, Inc. All rights reserved.
The Database Environment
Chapter 8 - Design Strategies
Jim Fawcett CSE687 – Object Oriented Design Spring 2015
Presentation transcript:

Functional Hierarchical Model

Functional Hierarchy Most Abstract Level of detail Describes basic concepts present in a business Usually done Enterprise-wide Usually a component of an Information Systems Strategic Plan (ISP) or other multi-project effort Organizationally, technologically, and time independent

Functions An activity performed in the enterprise that occur at all times. They do not have an identifiable start or stop. Functions are expressed as nouns (Sales Management, Human Resource Mgt) Functions have a label and a definition (Order Management: The activities involved in taking orders, confirming stock quantities, and fulfilling orders.) Functions are shown as boxes in the Function Hierarchy.

General Modelling Standards An object has one and only one meaning An object is defined immediately upon creation Logical objects are defined independently of organizational constraints, implementation targets, and technology issues Abbreviations are standardized

Definitions Describe what activities are being done, not who uses it or when, why, where, or how it’s used. Generally have the format of The activities involved in … Describe the meaning of the object, not the term used to label that object.

Function Standards All UPPERCASE names Noun-based names Unique names, Unique meanings No special characters Minimize abbreviations Reusable across projects

Functions Examples: HUMAN RESOURCE MANAGEMENT, CUSTOMER RELATION MANAGEMENT, etc. Functions go on as long as the business goes on. Functions can be decomposed into other Functions or into Processes

Functions Functions are organizationally independent, but they may share the name of a division or department. A box with the same name on a Functional Hierarchy does not have the same meaning as a box on an Organization Chart with the same name.

Functions vs. Organizational Titles Is not the same as …..

Functions vs. Organizational Titles Organization roles DO come in to play when mapping responsibilities to Functions and Processes.

Sample Functional Hierarchy Model

Sample Functional Hierarchy Model with rocesses

Decomposition Each break down of a Function into other functions is called decomposition. Each decomposition is a parent/child(ren) relationship. A decomposition should completely exhaust the parent.