FUNCTIONAL MODELING Alajas, Sophiya Ann Allego, Keefer Lloyd Maningo, Patrick Sage Pleños, John Enrick CPE 51ASATURDAY 7:30 – 10:30ENGR. ARNOLD ROSO.

Slides:



Advertisements
Similar presentations
Software Processes Coherent sets of activities for specifying, designing, implementing and testing software systems.
Advertisements

Chapter 7 Structuring System Process Requirements
© 2005 by Prentice Hall 7-1 Chapter 7 Structuring System Process Requirements Modern Systems Analysis and Design Fourth Edition Jeffrey A. Hoffer Joey.
PowerPoint Presentation for Dennis & Haley Wixom, Systems Analysis and Design, 2 nd Edition Copyright 2003 © John Wiley & Sons, Inc. All rights reserved.
Chapter 4 Enterprise Modeling.
Chapter 4.
Systems Analysis and Design 9th Edition
Concepts of Systems Theory
Lecture 13 Revision IMS Systems Analysis and Design.
PROCESS MODELING Transform Description. A model is a representation of reality. Just as a picture is worth a thousand words, most models are pictorial.
Systems Development Life Cycle
© Copyright 2011 John Wiley & Sons, Inc.
Systems Analysis and Design in a Changing World, 6th Edition
9 1 Chapter 9 Database Design Database Systems: Design, Implementation, and Management, Seventh Edition, Rob and Coronel.
Chapter 4.
IS Terms and Introductory Concepts. Contemplative Questions What is an information system? What is an information system? What is data, information and.
DATA FLOW DIAGRAMS IT 155.
Chapter 7 Structuring System Process Requirements
Software Design Description (SDD) Diagram Samples
6 Systems Analysis and Design in a Changing World, Fourth Edition.
Chapter 6: The Traditional Approach to Requirements
System Analysis Overview Document functional requirements by creating models Two concepts help identify functional requirements in the traditional approach.
1 Structured Analysis Techniques. 2 Data Flow Diagrams.
Systems Analysis and Design in a Changing World, Fifth Edition
Chapter 6 The Traditional Approach to Requirements
The Software Development Life Cycle: An Overview
Data and Process Modeling
Systems Analysis and Design in a Changing World, Fifth Edition
Systems Analysis – Analyzing Requirements.  Analyzing requirement stage identifies user information needs and new systems requirements  IS dev team.
Modelling information systems
Business Process Management. Key Definitions Process model A formal way of representing how a business operates Illustrates the activities that are performed.
Phase 2: Systems Analysis
Data Flow Diagram A method used to analyze a system in a structured way Used during: Analysis stage: to describe the current system Design stage: to describe.
Chapter 7 Structuring System Process Requirements
ITEC 3220M Using and Designing Database Systems
Chapter 14 Information System Development
Chapter 9 Moving to Design
Analysis Modeling. Function Modeling & Information Flow  Information is transformed as it flows through a computer-based system. The system accepts input.
Requirements Capture. Four Steps of requirements capture List candidate requirements Understand system context Capture functional requirements Capture.
Design Concepts By Deepika Chaudhary.
Chapter 4 enterprise modeling
Architecture View Models A model is a complete, simplified description of a system from a particular perspective or viewpoint. There is no single view.
Chapter 7 Structuring System Process Requirements Modern Systems Analysis and Design Fourth Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich.
Systems Analysis and Design 8th Edition
CS223: Software Engineering
6 Systems Analysis and Design in a Changing World, Fourth Edition.
UTA/ARRI. Enterprise Engineering for The Agile Enterprise Don Liles The University of Texas at Arlington.
From Use Cases to Implementation 1. Structural and Behavioral Aspects of Collaborations  Two aspects of Collaborations Structural – specifies the static.
© 2005 by Prentice Hall Chapter 7 Structuring System Process Requirements Modern Systems Analysis and Design Fourth Edition Jeffrey A. Hoffer Joey F. George.
SOFTWARE DESIGN & SOFTWARE ENGINEERING Software design is a process in which data, program structure, interface and their details are represented by well.
From Use Cases to Implementation 1. Mapping Requirements Directly to Design and Code  For many, if not most, of our requirements it is relatively easy.
7-1 Chapter 7 Structuring System Process Requirements Modern Systems Analysis and Design Fourth Edition.
© 2012 Cengage Learning. All Rights Reserved. This edition is intended for use outside of the U.S. only, with content that may be different from the U.S.
1 Team Skill 3 Defining the System Part 1: Use Case Modeling Noureddine Abbadeni Al-Ain University of Science and Technology College of Engineering and.
Systems Development Life Cycle
Business System Development
DATA FLOW DIAGRAMS Budi Arifitama.
Chapter 6 The Traditional Approach to Requirements.
Object-Oriented Analysis and Design
DATA MODELS.
SYSTEMS ANALYSIS Chapter-2.
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
Public Management Information Systems System Analysis & Design Tuesday, December 04, 2018 Hun Myoung Park, Ph.D. Public Management & Policy Analysis.
Requirement Analysis using
Chapter 7: Data Flow Diagram Structuring System Process Requirements
Systems Development Life Cycle
UNIT No- III- Leverging Information System ( Investing strategy )
Public Management Information Systems System Design Monday, July 01, 2019 Hun Myoung Park, Ph.D. Public Management & Policy Analysis Program Graduate.
Presentation transcript:

FUNCTIONAL MODELING Alajas, Sophiya Ann Allego, Keefer Lloyd Maningo, Patrick Sage Pleños, John Enrick CPE 51ASATURDAY 7:30 – 10:30ENGR. ARNOLD ROSO

What is functional modeling and what does it do?

 is a tool that allows a team or an individual to produce a behavioral/operational model of an existing or planned system  The resulting model shows the system functionality and the logical interconnections between that functionality.  In essence, it describes how the system functionality has to cooperate to deliver the Operational Requirements of the system. Functional Modeling

By constructing the model it is possible to:  Functional perspective -Symbols: Process, Store, Flow, External Entity  Functional decomposition

Functional Modeling uses three sub-tools to construct a model of the system of interest 1. Function Flow Diagram (FFD) 2. Flow Dictionary (FD) 3. Function Specification (FS)

Function Flow Diagram (FFD)  is a network representation of the system.  It portrays the system in terms of its component functions and the logical interdependencies or “flows” between the functions.  It uses simple diagramming conventions.  This minimum set enables the team to concentrate on discovering and understanding the system rather than the modeling technique.

Function Flow Diagram Modeling Conventions  FUNCTION - transforms input flows into output flows that is internal to the System of Interest  TERMINATOR - described as a function or object that is a source or destination of flows external to the System of Interest  FLOW - an input or output quantity (information, control, material or energy) FUNCTION TERMINATOR FLOW

Flow Dictionary (FD)  complements the Functional Flow Diagrams by documenting the flows found on any of the diagrams.  It is a set of definitions which declare the component elements of each flow, and the relationships that apply among them.  The flows represent the logical interfaces of the system some of which some will become real interfaces.

Function Specification (FS)  specifies the component functions by defining the transformation that converts inputs to outputs..

Why do functional modeling?

 provides a way of logically exploring such requirements in order to address their deficiencies  helps build a complete and consistent set of measurable system design requirements  This exploration leads to generation of new requirements and the clarification of existing requirements.  The result is a model of the system requirements that emphasizes the functional operation of the system. Functional Modeling…

What are the benefits of Functional Modeling?

 It helps the modelling team logically work through the functionality of the proposed or existing system  it identifies the potential interfaces of a system and encourages their clear definition  it encourages the team to consider not only the system of interest but also the wider system.  it can help to gain more understanding about the system of interest and what all the customers’ expect  models that can help in showing the customer that you understand what they are after  when used within a team context, it allows the whole team to share information and agree at a common understanding Functional Modeling Benefits…

Where and when to use Functional Modeling?

 limited information from the customer such as an operational requirement or idea of a potential operational requirement.  The need to check for completeness and consistency of requirement. Functional Modeling is used to help understand and engineer a set of requirements. It is particularly useful when we have: Functional Modeling can be used in three situations:  Analysis and modeling of an existing system  Analysis of an existing system together with the development of modifications to that system  Analysis and modeling of an entirely new system.

How to do Functional Modeling?

DIAGRAMMING : Modeling Concepts

INFORMATION HIDING: Modeling Concepts  Hide design decisions within modules especially when changes are expected  Access to internal modules is only provided via well defined interfaces which reveal only that information which is required to use the module  Emphasizes communication through controlled interfaces

ABSTRACTION: Modeling Concepts  refers to the diagramming conventions whereby a single convention is used to represent different real world items.  For example: the single diagramming convention of an arrow to represent an input or output flow is used represent material, energy, information and control type flows.

Process of Function Modeling

1.Collect and generate information about the system of interest Process of Function Modeling The first step is to collect information about the system of interest. This is achieved via a variety of means that include:  Viewpoint Analysis  Customer Requirements documents  Textual Analysis  Use Cases  Involving customers and users  Involving experienced staff

2.A. Draw functional Flow Diagrams Process of Function Modeling  The role of the FFD is to present a description of the system in terms of its component functions and how those functions have to interact (the flows)to deliver the intended system outcome (the operational requirement).

2.B. Compile Flow Dictionary Process of Function Modeling  The Flow Dictionary is used to specify precisely what is meant by every flow on every Functional Flow Diagram.  In particular it specifies the elements which are contained in each flow. The flows can represent different input/output quantities of:  Materials  Energy  Information/data  Control

2.C. Generate Functional Specifications Process of Function Modeling  to describe in more detail what has to happen inside a particular function on a Functional Flow Diagram.  It defines the policy governing transformation (what has to be done) but not the method of implementing it (how it is to be done).

FUNCTIONAL MODELING EXAMPLE PURCHASER 1 CREATE ORDER APRROVE ORDER PURCHASING OFFICER PURCHASER 2 EXPEDITE ORDER VENDOR ORDER approval Purchase request Purchasing data Purchase order status verification Delivery agenda approval