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.

Slides:



Advertisements
Similar presentations
Data Flow Diagram (DFD) Overview
Advertisements

CAPE INFORMATION TECHNOLOGY – Unit 2
Johnb DFDs and Design John Bell The DeMarco notation.
Software Engineering-II
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.
Data Flow Diagram Purpose – visually depict how data moves and changes through a top-down, logical model Logical model – requirements and the relationship.
How to : Data Flow Diagrams (DFDs)
DATA FLOW DIAGRAM (PART 2)
1 Introduction to Data Flow Modelling The data flow approach to requirements determination in building a system for business use. This type of computer.
Review Questions The four symbols on a data flow diagram are: Rounded rectangles (processes) Squares (external agents) Open-ended boxes (data stores) Arrows.
Dataflow modelling: Context and Data Flow Diagrams
Jump to first page Chapter 2 System Analysis - Process Modeling.
DT211 Stage 2 Software Engineering
Modern Systems Analysis and Design
Tutorial 2 DT228/3 Database Technology. Joe’s Yard Take the following documents: –The script as prepared –The docket –The diary in the yard –The list.
Spreadsheets in Finance and Forecasting Project Session 3b(ii) Data Flow Diagrams.
DT211 Stage 2 Software Engineering
Process Modelling Using Data Flow Diagrams - Building and Levelling Them; Process Modelling Using Function Decomposition CSE Information Systems.
Current Physical Diagram Document this in Select SSADM.
System Analysis and Design
DATA FLOW DIAGRAMS IT 155.
Data Flow Diagrams BCA Sem IV K.I.R.A.S.
National Diploma in Systems Analysis and Design Data Flow Modelling.
staffs.ac.uk Process Model. staffs.ac.uk Contents Provide definitions Explain the components and representations Introduce a step.
1 Structured Analysis Techniques. 2 Data Flow Diagrams.
Data Flow Diagrams (DFDs)
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.
Data Flow Diagrams Objectives:
Data Flow Diagrams.
1 Lecture 3: Introducing Data Flow Diagrams (DFDs) Section 1 - The Concept of Diagrams Why use Diagrams? Diagrams as Working Documents Systems Analysis.
DATA FLOW DIAGRAMS Learning Units
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.
 During systems development both processes and data must be modeled ◦ Data modeling describes data used by system ◦ Process modeling describes processes.
System Analysis System Analysis - Mr. Ahmad Al-Ghoul System Analysis and Design.
1 Ref: Prof Sarda Process Modeling…… Lecture Outline Data flow diagram (DFD)
AN INTRODUCTION BUSINESS PROCESS DOCUMENTATION WITH DATA FLOW DIAGRAMS.
Sequence Diagrams.
Software Engineering INTRODUCTION TO SOFTWARE ENGINEERING.
University of Sunderland ISIC 1 Data Flow Diagrams - Part 2 Hierarchical DFDs.
1 DATA FLOW DIAGRAM. 2 Outline Process decomposition diagrams Data flow diagram (DFD)
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.
Data Flow Diagrams (DFDs)
Modern Systems Analysis and Design Fifth Edition
Joe’s Yard Case study done through SSADM. Joe’s Yard Joe’s builders’ suppliers has a shop and a yard. His system is entirely manual. He has a stock list.
1Lecture 8 Introduction to Systems Analysis l Objectives –Explain how systems analysis relates to business needs, problems, and opportunities –List and.
Information Modelling Process Technique- DFD 5C Sybase_PowerDesigner_ html.
Btec National - IT SYSTEMS ANALYSIS AND DESIGN 1 IT Systems Analysis and Design SSADM – Design.
C HAPTER 8 STRUCTURED APPROACH WITH THE DATA & PROCESS MODELING.
Systems Analysis & Design
Data Flow Diagram, Data Dictionary, and Process Specification PART I
Software Analysis 1 PROCESS MODELING: Data Flow Diagrams (DFDs)
SYSTEMS ANALYSIS AND DESIGN ITDB 2101 HAND OUT # 3 1.
Software Specification Models
C_ITIP211 LECTURER: E.DONDO. Unit 3 : PROCESS MODELING.
Copyright © 2011 Pearson Education, Inc. Publishing as Prentice Hall Using Dataflow Diagrams Systems Analysis and Design, 8e Kendall & Kendall 7.
© 2006 Prentice Hall Business Publishing Accounting Information Systems, 10/e Romney/Steinbart1 of 37 C System Process Modeling DATA Flow Diagrams.
Software Development Lifecycle- SDLC Design- using DFDs.
Software Specification Models
DFD(Data Flow Diagram)
Data Flow Diagrams.
G063 - Data flow diagrams.
System Process Modeling
DATA FLOW DIAGRAM (PART 2)
DATA FLOW DIAGRAM PART 2.
Data Flow Diagrams.
Process & Logic Modeling
Software design and architecture
Presentation transcript:

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 the system do to the data?  A DFD is a graphic representation of the flow of data or information through a system

4 Main Elements  external entity - people or organisations that send data into the system or receive data from the system  process - models what happens to the data i.e. transforms incoming data into outgoing data  data store - represents permanent data that is used by the system  data flow - models the actual flow of the data between the other elements

Notation Process box DData Store External Entity Data Flow Process External Entity Data Store

4 Levelled DFDs  Even a small system could have many processes and data flows and DFD could be large and messy use levelled DFDs - view system at different levels of detail one overview and many progressively greater detailed views

 Level 0 or context diagram shows a system as a single process with inputs and outputs flowing to or from external entities.  Level 1 DFD will split up that single process into subsystems and show more detail about the data flows and data stores.  Level 2 DFD may decompose a single subsystem even further.

Level 0 - Context Diagram  models system as one process box which represents scope of the system  identifies external entities and related inputs and outputs  Additional notation - system box

Level 1 - overview diagram  gives overview of full system  identifies major processes and data flows between them  identifies data stores that are used by the major processes  boundary of level 1 is the context diagram

Level 2 - detailed diagram  level 1 process is expanded into more detail  each process in level 1 is decomposed to show its constituent processes  boundary of level 2 is the level 1 process

Other Notation  Duplicates marked by diagonal line in corner  System Boundary  Elementary Processes - star in corner  Process that is levelled - dots on top

5 Rules for DFDs  Numbering  Labelling  Balancing

Numbering  On level 1 processes are numbered 1,2,3…  On level 2 processes are numbered x.1, x.2, x.3… where x is the number of the parent level 1 process  Number is used to uniquely identify process not to represent any order of processing  Data store numbers usually D1, D2, D3...

Labelling  Process label - short description of what the process does, e.G. Price order  Data flow label - noun representing the data flowing through it e.G. Customer payment  Data store label - describes the type of data stored  Make labels as meaningful as possible

Balancing and data stores  Balancing any data flows entering or leaving a parent level must by equivalent to those on the child level  Data stores data stores that are local to a process need not be included until the process is expanded

Data Flows  Allowed to combine several data flows from lower level diagrams at a higher level under one data flow to reduce clutter  Flows should be labelled except when data to or from a data store consists of all items in the data store

Context Diagram  Find the people who send data into the system Often data is part of a PHYSICAL transaction When handing a bar of chocolate to a shopkeeper, you are handing him/her a barcode.  Find the people who get data out of the system. The only data you need is data that is transformed or sent completely out of the system – not data that is handled by an operator within the system.

Context diagrams a top-level DFD shows the least amount of detail and is known as a Level 0 DFD or context diagram. Customer Order Invoice Process order Out-of-stock notice Picking List Warehouse Order rejection notice

Context diagram

Remove passive verbs and queries  Passive: has stock list  Buy supplies Picks stock items (views list) Writes orders Pays joe Stamps docket  Customer then Takes docket to yard Hands it to foreman  Gets items Gives them to builder Builder signs docket Takes copy as receipt  Joe then Looks around yard and reorders Records order in order book  Foreman takes delivery – checks Foreman pays supplier Staples receipt to order book  Joe Produces financial report

Level 1 current physical

Buy Supplies

Get Items

Reorder supplies

Restock