System Analysis and Design

Slides:



Advertisements
Similar presentations
Identifying Data Flows
Advertisements

CAPE INFORMATION TECHNOLOGY – Unit 2
Johnb DFDs and Design John Bell The DeMarco notation.
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.
Chapter 4 Enterprise Modeling.
How to : Data Flow Diagrams (DFDs)
DATA FLOW DIAGRAM (PART 2)
Chapter 4.
Systems Analysis and Design 9th Edition
Jump to first page Chapter 2 System Analysis - Process Modeling.
Data Flow Diagrams Mechanics.
Modern Systems Analysis and Design
Structuring System Requirements: Process Modeling
MIS 461: Structured System Analysis and Design Dr. A.T. Jarmoszko
Data and Process Modeling
Copyright 2002 Prentice-Hall, Inc. Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich Chapter 8 Structuring.
TCS2411 Software Engineering1 Functional and Behavioural Modeling “What is the software supposed to do?”
Chapter 4.
DATA FLOW DIAGRAMS IT 155.
Process Modeling SYSTEMS ANALYSIS AND DESIGN, 6 TH EDITION DENNIS, WIXOM, AND ROTH © 2015 JOHN WILEY & SONS. ALL RIGHTS RESERVED. 1 Roberta M. Roth.
Data and Process Modeling.  Describe data and process modeling, and name the main data and process modeling techniques.
Chapter 7 Structuring System Process Requirements
Chapter 8 Structuring System Requirements: Process Modeling
Copyright © 2012 Pearson Education, Inc. Publishing as Prentice Hall 6.1.
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.
Copyright © 2012 Pearson Education, Inc. Publishing as Prentice Hall 6.1.
PowerPoint Presentation for Dennis & Haley Wixom, Systems Analysis and Design Copyright 2000 © John Wiley & Sons, Inc. All rights reserved. Slide 1 Process.
Phase 2: Systems Analysis
Copyright © 2009 Pearson Education, Inc. Publishing as Prentice Hall Essentials of Systems Analysis and Design Fourth Edition Joseph S. Valacich Joey F.
Computer System Analysis Chapter 8 Structuring System Requirements: Process Modeling Dr. Sana’a Wafa Al-Sayegh 1 st quadmaster University of Palestine.
Copyright 2002 Prentice-Hall, Inc. Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich Chapter 8 Structuring.
Chapter 7 Structuring System Process Requirements
PHASE 2: SYSTEMS ANALYSIS
AN INTRODUCTION BUSINESS PROCESS DOCUMENTATION WITH DATA FLOW 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.
Data Flow Diagrams (DFDs) 1Information Systems Engineering.
Copyright 2001 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Chapter 5 Structuring.
Copyright 2002 Prentice-Hall, Inc. Chapter 7 Structuring System Requirements: Process Modeling.
Data Flow Diagrams (DFDs)
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.
Systems Analysis and Design 8th Edition
Systems Analysis and Design 8th Edition
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.
Data Flow Diagram, Data Dictionary, and Process Specification PART I
Software Analysis 1 PROCESS MODELING: Data Flow Diagrams (DFDs)
© 2005 by Prentice Hall Chapter 7 Structuring System Process Requirements Modern Systems Analysis and Design Fourth Edition Jeffrey A. Hoffer Joey F. George.
SYSTEMS ANALYSIS AND DESIGN ITDB 2101 HAND OUT # 3 1.
DATA FLOW DIAGRAMS.
C_ITIP211 LECTURER: E.DONDO. Unit 3 : PROCESS MODELING.
MIS 360: System Analysis and Design Dr. Qasem Al-Radaideh Department of Computer Information Systems Faculty of Information Technology Yarmouk University.
- 1 - SW 분석 기법 개론 ( 구조적 분석 기법 ) 정 인 상정 인 Data Flow Diagram (DFD)  Graphical representation of functional modeling  In analysis, provide representation.
© 2006 Prentice Hall Business Publishing Accounting Information Systems, 10/e Romney/Steinbart1 of 37 C System Process Modeling DATA Flow Diagrams.
7-1 Chapter 7 Structuring System Process Requirements Modern Systems Analysis and Design Fourth Edition.
Chapter 8 Structuring System Requirements: Process Modeling
Process Modeling Graphically represent the processes that capture, manipulate, store, and distribute data between a system and its environment Models DFDs.
Identifying Data Flows
Business System Development
System Process Modeling
Structuring System Requirements: Process Modeling
Chapter 1: Data Flow Diagram Structuring System Process Requirements
Process & Logic Modeling
Data Flow Diagrams Mechanics. Outline DFD symbols External entities (sources and sinks) Data Stores Data Flows Processes Types of diagrams Step by step.
Chapter 6 Structuring System Requirements: Process Modeling
MBI 630: Week 4 Process Modeling
System Design By Kustanto.
Presentation transcript:

System Analysis and Design Data Flow Diagram

Data Flow diagram The dataflow diagram is a modeling tool that allows us to picture a system as a network of functional processes, connected to one another by “pipelines” and “holding tanks” of data

Data Flow Diagrams Context Diagrams Top-level view of an information system that shows the system’s boundaries and scope Do not show any data stores in a context diagram because data stores are internal to the system. Begin by reviewing the system requirements to identify all external data sources and destinations

Context Diagrams Record the name of the entities and the name and content of the data flows, and the direction of the data flows. What makes one system more complex than another is the number of components, the number of levels, and the degree of interaction among its processes, entities, data stores, and data flows

Context Diagrams Shows the overall business process as just one process. The process is given the number zero. Shows all the outside entities that receive information from or contribute information to the system

Context Diagrams Each context diagram must fit on one page. The process name in the context diagram should be the name of the information system. Use unique names within each set of symbols. Do not cross lines. Use a unique reference number for each process symbol.

Developing DFDs 1. Context Diagram for Pizza Hut food ordering system CUSTOMER KITCHEN Food Order Customer Order Receipt Management Reports RESTAURANT MANAGER

Creating a Set of DFDs Create a graphical model of the information system based on your fact-finding results Performing three main tasks Step 1: Draw a context diagram Step 2: Draw a diagram 0 DFD Step 3: Draw the lower-level diagrams

Creating a Set of DFDs Draw a Diagram 0 DFD Diagram 0 Zooms in on the context diagram and shows major processes, data flows, and data stores Must retain all the connections that flow into and out of process 0 Each process has a reference number Diverging data flow

Draw the Lower-Level Diagrams Creating a Set of DFDs Draw the Lower-Level Diagrams Must use leveling and balancing techniques Leveling Uses a series of increasingly detailed DFDs to describe an information system Exploding, partitioning, or decomposing

Data Flow Diagrams Lower-Level Diagrams Balancing Ensures that the input and output data flows of the parent DFD are maintained on the child DFD

Developing DFDs 1. Context Diagram for Pizza Hut food ordering system CUSTOMER KITCHEN Food Order Customer Order Receipt Management Reports RESTAURANT MANAGER

Developing DFDs 2. Level-0 Diagram for Pizza Hut food ordering system 1.0 Receive & Transform Customer Food Order CUSTOMER KITCHEN Customer Order Food Order Receipt 2.0 Update Goods Sold File 3.0 Update Inventory File Inventory Data Goods Sold Formatted Goods Sold Data Formatted Inventory Data D2 D1 Goods Sold File Inventory File 4.0 Produce Management Report Daily Inventory Depletion Amounts Daily Goods Sold Amounts manager Management Reports

Developing DFDs 2. Level-1 Diagram for Pizza Hut food ordering system 1.1 Receive Customer Order 1.3 Transform Order to Kitchen Format Customer Order Customer Order Food Order Customer Order 1.5 Generate Inventory Decrements Customer Order Inventory Data Customer Order 1.2 Generate Customer Receipt 1.4 Generate Goods Sold Increments Receipt Goods Sold Data

Rules Governing Data Flow Diagramming

Rules Governing Data Flow Diagramming Process Process cannot have outputs only. It means it is making data from nothing Only a source should have outputs without inputs

Rules Governing Data Flow Diagramming Process No Process can have only inputs If an object has only inputs, then it must be a sink.

Rules Governing Data Flow Diagramming Process A Process should have a verb phrase label Generate Orders

Rules Governing Data Flow Diagramming Process Data cannot move directly from one data store to another data store. Data must be moved by a process Generate Orders

Rules Governing Data Flow Diagramming Process Data cannot move directly from an outside source to a data store Data must be moved by a process which receives data from the source and places the data into the data store Generate Orders Source Source

Rules Governing Data Flow Diagramming Process Data cannot move directly to an outside sink from a data store Data must be moved by a process Generate Orders Sink Sink

Rules Governing Data Flow Diagramming Process A data store has a noun phrase label Inventory

Rules Governing Data Flow Diagramming Process A data store A data store must have at least one incoming and one outgoing data flow. Inventory

Rules Governing Data Flow Diagramming Process Source/Sink Rule 9: Data cannot move directly from a source to a sink It must be moved by a process Generate Orders Source Sink Source Sink

Rules Governing Data Flow Diagramming Process Source/Sink Rule 10: A source/sink has a noun phrase Supplier

Rules Governing Data Flow Diagramming Process A data flow has only one direction of flow between symbols It may have both direction flows between a process and a data store to show a read before an update Later it is indicated by two separate arrows Generate Orders Generate Orders

Rules Governing Data Flow Diagramming Process A fork in a data flow means that exactly the same data goes from a common location to two or more different processes, data stores, or sources/sinks. There should not be a variation in duplication A A B A

Rules Governing Data Flow Diagramming Process A joint in a data flow means that exactly the same data comes from any of two or more different processes, data stores, or sources/sink to a common location Only similar data flows can be joined A A B A

Rules Governing Data Flow Diagramming Process A data flow cannot go directly to the same process it leaves. There must be at least one other process which handles the data flow, produces some other data flow, and returns the original data flow to the beginning process B A A A C

Rules Governing Data Flow Diagramming Process A data flow to a data store means update (delete or change) Generate Orders Delete or changed data

Rules Governing Data Flow Diagramming Process A data flow from a data store means retrieve or use Generate Orders Retrieve/Use

Rules Governing Data Flow Diagramming Process A data flow must have a noun phase label Updated stock

DFDs Exercises

Data Flow Diagrams Examples of correct uses of data store symbols in a data flow diagram. [1]

Data Flow Diagrams

Data Flow Diagrams Entity can be connected with a process only Examples of correct uses of external entities in a data flow diagram.[1]

Data Flow Diagrams

Data Flow Diagrams

DFD Errors

DFD Errors