Process Analysis and Modeling Using IDEF0

Slides:



Advertisements
Similar presentations
CAPE INFORMATION TECHNOLOGY – Unit 2
Advertisements

Software Engineering-II Sir Zubair Sajid. 3 Data Flow Diagrams (DFD)  DFDs describe the flow of data or information into and out of a system what does.
1 FUNCTION MODELING USING IDEF-0 IE 590 INTEGRATED MANUFACTURING SYSTEMS Lecture 7.
Systems Analysis Requirements structuring Process Modeling
Practice data flow diagramming as a tool for structured system programming (process modelling) DATA FLOW DIAGRAMs.
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.
ACG 4401 Data Modeling: Data Flow Diagrams Flow Charts.
How to : Data Flow Diagrams (DFDs)
1.  Integrated Computer-Aided Manufacturing (ICAM) Definition Languages  Comprehensive, formal syntax for describing a process  Better analysis and.
Dataflow modelling: Context and Data Flow Diagrams
Jump to first page Chapter 2 System Analysis - Process Modeling.
DT211 Stage 2 Software Engineering
Lecture 1 CS171: Game Design Studio 1I UC Santa Cruz School of Engineering 5 January 2010.
Modern Systems Analysis and Design
Structuring System Process Requirements -- Process Modeling --
Chapter 9 Using Data Flow Diagrams
Chapter 3 : Software Process and Other Models Juthawut Chantharamalee Curriculum of Computer Science Faculty of Science and Technology, Suan Dusit University.
System analysis and design
Chapter 7 Structuring System Process Requirements
National Diploma in Systems Analysis and Design Data Flow Modelling.
Data Flow Diagrams (DFDs)
Chapter 1: Data Flow Diagram Structuring System Process Requirements
Data Flow Diagrams (DFDs). Data flow diagram (DFD) is a picture of the movement of data between external entities and the processes and data stores within.
Structuring System Process Requirements. Learning Objectives Understand the logical modeling of processes by studying examples of data flow diagrams (DFDs).
Copyright © 2012 Pearson Education, Inc. Publishing as Prentice Hall 6.1.
1 iSee Player Tutorial Using the Forest Biomass Accumulation Model as an Example ( Tutorial Developed by: (
PROF. ANNA MORENO ENERGY EFFICIENCY UNIT TRAINING AND INFORMATION SERVICE.
Business Process Management. Key Definitions Process model A formal way of representing how a business operates Illustrates the activities that are performed.
Data Flow Diagrams.
程建群 博士(Dr. Jason Cheng) 年03月
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.
Computer System Analysis Chapter 8 Structuring System Requirements: Process Modeling Dr. Sana’a Wafa Al-Sayegh 1 st quadmaster University of Palestine.
Chapter 7 Structuring System Process Requirements
SAD - DFD Context Diagrams
1 FUNCTION MODELING USING IDEF-0 IE 469 Manufacturing Systems 469 صنع نظم التصنيع.
IDEF0 Modelling techniques
© Minder Chen, IDEF 85 - Methods and Tools for BPR An Integrated Framework for Methods and Tools for BPR Process Modeling Methods and Tools –IDEF0.
DFDs (Data Flow Diagrams). Data Flow Diagrams DFDs are a system modeling tool, the most popular and important representation in data flow modeling. DFDs.
Drawing System Sequence Diagrams
System Decomposition Overview. Data Flow Diagrams Despite the name “Data Flow Diagrams”, DFD have a process, rather than a data, focus We represent all.
Modern Systems Analysis and Design Fifth Edition
Chapter 7 Structuring System Process Requirements Modern Systems Analysis and Design Fourth Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich.
1Lecture 8 Introduction to Systems Analysis l Objectives –Explain how systems analysis relates to business needs, problems, and opportunities –List and.
C HAPTER 8 STRUCTURED APPROACH WITH THE DATA & PROCESS MODELING.
Enterprise Engineering How to read an IDEF0 model
© 2005 by Prentice Hall Chapter 7 Structuring System Process Requirements Modern Systems Analysis and Design Fourth Edition Jeffrey A. Hoffer Joey F. George.
DATA FLOW DIAGRAMS.
C_ITIP211 LECTURER: E.DONDO. Unit 3 : PROCESS MODELING.
7-1 Chapter 7 Structuring System Process Requirements Modern Systems Analysis and Design Fourth Edition.
School of Mechanical, Industrial, & Manufacturing Engineering Process Analysis and Modeling Using IDEF0.
Failure Modes and Effects Analysis. 2 Failure Modes and Effects Analysis (FMEA) ● Purpose – Systematically, prospectively, identify ways in which a process.
School of Mechanical, Industrial, & Manufacturing Engineering Process Analysis and Modeling Using IDEF0.
School of Mechanical, Industrial, & Manufacturing Engineering Process Analysis and Modeling Using IDEF0.
Process Analysis and Modeling Using IDEF0
Analysis Classes Unit 5.
Process Analysis and Modeling Using IDEF0
Chapter 6 Structuring System Requirements: Process Modeling
Business System Development
Structured Analysis and Design Technique
Process Analysis and Modeling Using IDEF0
IS 334 information systems analysis and design
Process & Logic Modeling
Chapter 6 Structuring System Requirements: Process Modeling
Representing Structure and Behavior with Trees
IDEF0/Activity Model – Functional Decomposition
Functions Guided Notes Review
Chapter 7: Data Flow Diagram Structuring System Process Requirements
Presentation transcript:

Process Analysis and Modeling Using IDEF0 … continued

Tunneled Arrows Arrows that provide information at one level of decomposition but are not needed at another (parent, child) level. does not appear on parent ( ) does not appear on parent ( ) ( ) does not appear on child ( ) does not appear on child

Call Arrows Special case of mechanism arrow. Caller box does not have its own child diagram. Detailed by another box in same or other model. Example: same “Fly aircraft” model called by “Fly aircraft in climb” “Fly aircraft in cruise” “Fly aircraft in descent”

Box Numbers and Node Numbers Single box in context (A-0) diagram numbered A0 (“Activity” 0). Boxes in context diagram’s child numbered A1, A2, A3, … [A6]. Boxes in A1’s child diagram numbered A11, A12, … Boxes in A2’s child diagram numbered A21, A22, … Boxes in A21’s child diagram numbered A211, A212, … and so on … Node – for our purposes, another name for an activity/process Node numbers Context diagram is node A-0 A-0’s child node is node A0 A0’s children are nodes A1, A2, … In general, a node bears the same number as the box in the parent node it details.

Node A-0 (Context)

Node A0

Node A3

Node List, Node Tree Node List Node tree (horizontal) A-0: Assemble widgets A0: Assemble widgets A1: Restock parts A2: Get widget parts A3: Assemble parts A31: Hold widget base A32: Position parts in place A33: Secure parts to base A34: Release assembled widget A4: Inspect widgets Node tree (horizontal)

Node List, Node Tree Node tree (vertical – AI0Win) Node tree (vertical – Visio)

Reading IDEF0 Diagrams Scan boxes of diagram to gain impression of what is being described. Refer to parent diagram. Note arrow connections to parent box. Try to identify “most important” input, control, output. Consider arrows of current diagram. Try to determine if there is a main path linking “most important” input or control and "most important" output. Mentally walk through the diagram, from upper left to lower right. Note how arrows interact with each box. Determine if there are secondary paths. Check story being told by diagram by considering how familiar situations are handled. Check to see if a related FEO diagram exists. Read text and glossary, if provided.

Creating IDEF0 Diagrams Select Context, Viewpoint, Purpose. Create Context (A-0) Diagram. Create topmost (A0) diagram. 3-6 subprocess boxes. May be necessary to switch back and forth between A0 and A-0 several times to get a good start. Create child diagrams Detail each A0 process box into 3-6 subprocess boxes. May be necessary to redraw several times. Split and cluster boxes until satisfied. Create supporting materials: text, glossary, FEOs.

Detailing Boxes Select a box: Gather data. Select the hardest part. Select the box whose detail will give the most information. Gather data. Structure: draw and re-draw. Write text carefully. Draw boxes. Make process box names verbs or verb phrases. Lay out diagonally, upper left to lower right. Place boxes that “dominate” in the upper left. All boxes should have a consistent “flavor”.

Drawing interface arrows. Think control and constraint, not flow. Don’t worry about sequence. All boxes may be active simultaneously. Bundle groups of arrows, when possible. Don’t clutter with arrows. All boxes must have control arrows, but they don’t require input arrows. Give arrows noun or noun phrase names.

WSE Project Assignment IDEF0 A-0 diagram (using AI0Win) IDEF0 A0 diagram (using AI0Win) At least 3 more IDEF0 diagrams (e.g., A1 & A2 & A3, A2 & A21 & A213, etc., using AI0Win) IDEF0 glossary (using AI0Win) Requirements Version 2 Progress Report 2 Cover: Memo Evaluation Form (provided by instructor) Memo (see syllabus) Separator page: Work Products Evaluation Form (provided by instructor) Copies of work products (see above)