The Traditional Approach to Requirements: Using Dataflow Diagrams Spring 2014 1.

Slides:



Advertisements
Similar presentations
CAPE COMPUTER SCIENCE UNIT 2
Advertisements

Process Models: Data Flow Diagrams
CAPE INFORMATION TECHNOLOGY – Unit 2
SYSTEMS ANALYSIS AND DESIGN TOOLS
IFS310: Week 3 BIS310: Structured Analysis and Design 5/4/2015 Process Modeling and Data Flow Diagrams.
Using Data Flow Diagrams
Using Dataflow Diagrams
Chapter 4 Enterprise Modeling.
How to : Data Flow Diagrams (DFDs)
DATA FLOW DIAGRAM (PART 2)
Dataflow modelling: Context and Data Flow Diagrams
Chapter 7 Using Data Flow Diagrams
Using Dataflow Diagrams
Chapter 7 Using Data Flow Diagrams
Topics Creating DFD Physical and logical DFD Event driven modeling
Data and Process Modeling
Chapter 9 Using Data Flow Diagrams
Chapter 7 Using Data Flow Diagrams
Modeling the Processes and Logic
L ECTURE 9 – PROCESS MODELLING PART 1 Data Flow Diagrams for Process Modelling Multi-level Data Flow Diagrams Logical Vs Physical DFDs Steps to Construct.
Chapter 4.
System Analysis and Design
DATA FLOW DIAGRAMS IT 155.
Structured Analysis Infsy 570 Dr. R. Ocker. What is structured analysis? n It focuses on specifying what the system or application is required to do.
Phase 2 – Systems Analysis
Traditional Approach to Requirements Data Flow Diagram (DFD)
Data Flow Diagrams (DFDs)
2 Approaches to Requierements Engineering Reference: Systems Analysis and Design in a Changing World, 3 rd Edition, chapter 2 and chapter 6.
Lecture Note 7 Using Data Flow Diagrams
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.
Systems Analysis – Analyzing Requirements.  Analyzing requirement stage identifies user information needs and new systems requirements  IS dev team.
SDLC Phase II: Structuring System Requirements IS 582 Dr. Dania Bilal Spring 2008.
Business Process Management. Key Definitions Process model A formal way of representing how a business operates Illustrates the activities that are performed.
Systems Analysis & Design Data Flow Diagrams. End Home Data Flow Diagrams – Definition  A data flow diagram is a pictorial model that shows the flow.
Phase 2: Systems Analysis
Lecture 6 Data Flow Modeling
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
Data Flow Diagrams (DFD). ScenarioCriteriaTasks Data flow diagram(DFD) is a diagram of the movement of data between external entities.
Chapter 7 Using Data Flow Diagrams
PHASE 2: SYSTEMS ANALYSIS
Software Engineering INTRODUCTION TO SOFTWARE ENGINEERING.
SYSTEMS ANALYSIS AND DESIGN TOOLS DATA FLOW DIAGRAMS.
DFDs (Data Flow Diagrams). Data Flow Diagrams DFDs are a system modeling tool, the most popular and important representation in data flow modeling. DFDs.
System Decomposition Overview. Data Flow Diagrams Despite the name “Data Flow Diagrams”, DFD have a process, rather than a data, focus We represent all.
3/5/2009Computer systems1 Using Data flow Diagrams Computer System: 1. Input 2. Data Processing 3. Output.
Information Systems Architecture (ISA) Conceptual blueprint for organization’s desired information systems structure Consists of:  Data (e.g. Enterprise.
Information Systems Architecture (ISA)
Using Dataflow Diagrams – Part 1 Systems Analysis and Design, 7e Kendall & Kendall 7 © 2008 Pearson Prentice Hall.
IS3320 Developing and Using Management Information Systems Lecture 16: Data-Flow Diagrams 1 (Intro to Context-Level diagrams) Rob Gleasure
Systems Analysis and Design 8th Edition
Structuring User Requirements IS 592 Dr. Dania Bilal Spring 2005.
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.
CS223: Software Engineering
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.
McGraw-Hill/Irwin Copyright © 2006 by The McGraw-Hill Companies, Inc. All rights reserved. Chapter 5 Modeling the Processes and Logic.
DATA FLOW DIAGRAMS.
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.
MIS 360: System Analysis and Design Dr. Qasem Al-Radaideh Department of Computer Information Systems Faculty of Information Technology Yarmouk University.
Lab 3 Data Flow Diagram CPIT 250 System Analysis and Design.
Data Flow Diagrams 1. What is a Data Flow Diagram?  A data flow diagram (DFD) is a graphical representation of the movement of data between external.
IS 334 information systems analysis and design
Ch 7: using Data Flow Diagrams
Process & Logic Modeling
Welcome to my presentation
Chapter 4: documenting information systems
Presentation transcript:

The Traditional Approach to Requirements: Using Dataflow Diagrams Spring

Traditional versus Object-Oriented Approaches 2

Traditional Approach -Requirements Models 3

Data Flow Diagrams (DFDs)  Graphical system model that shows all main requirements for an IS in one diagram › Inputs/outputs › Processes › Data storage  Easy to read and understand with minimal training 4

Advantages of the Data Flow Approach Freedom from committing to the technical implementation too early Understanding of the interrelatedness of systems and subsystems Communicating current system knowledge to users Analysis of the proposed system 5

Basic Symbols A double square for an external entity An arrow for movement of data from one point to another A rectangle with rounded corners for the occurrence of a transforming process An open-ended rectangle for a data store 6

The Four Basic Symbols Used in Data Flow Diagrams, Their Meanings, and Examples (Figure 7.1) 7

External Entities Represent another department, a business, a person, or a machine A source or destination of data, outside the boundaries of the system Should be named with a noun 8

Data Flow Shows movement of data from one point to another Described with a noun Arrowhead indicates the flow direction Represents data about a person, place, or thing 9

Process Denotes a change in or transformation of data Represents work being performed in the system Naming convention: – Assign the name of the whole system when naming a high- level process. – To name a major subsystem attach the word subsystem to the name. – Use the form verb-adjective-noun for detailed processes. 10

Data Store A depository for data that allows examination, addition, and retrieval of data Named with a noun, describing the data Data stores are usually given a unique reference number, such as D1, D2, D3 Represents a: – Database – Computerized file – Filing cabinet 11

Steps in Developing Data Flow Diagrams (Figure 7.2) 12

Creating the Context Diagram The highest level in a data flow diagram Contains only one process, representing the entire system The process is given the number 0 All external entities, as well as major data flows are shown 13

Basic Rules The data flow diagram must have one process. Must not be any freestanding objects A process must have both an input and output data flow. A data store must be connected to at least one process. External entities should not be connected to one another. 14

Context Diagram (Figure 7.3) 15

Drawing Diagram 0 The explosion of the context diagram. May include up to nine processes. Each process is numbered. Major data stores and all external entities are included. 16

Drawing Diagram 0 (Continued) Start with the data flow from an entity on the input side. Work backwards from an output data flow. Examine the data flow to or from a data store. Analyze a well-defined process. Take note of any fuzzy areas. 17

Data Flow Diagram Levels Data flow diagrams are built in layers. The top level is the context level. Each process may explode to a lower level. The lower level diagram number is the same as the parent process number. Processes that do not create a child diagram are called primitive. 18

Creating Child Diagrams Each process on diagram 0 may be exploded to create a child diagram. A child diagram cannot produce output or receive input that the parent process does not also produce or receive. The child process is given the same number as the parent process. – Process 3 would explode to Diagram 3. 19

Creating Child Diagrams (Continued) Entities are usually not shown on the child diagrams below Diagram 0. If the parent process has data flow connecting to a data store, the child diagram may include the data store as well. When a process is not exploded, it is called a primitive process. 20

Differences between the Parent Diagram (above) and the Child Diagram (below) (Figure 7.4) 21

Checking the Diagrams for Errors (Figure 7.5) Forgetting to include a data flow or pointing an arrow in the wrong direction 22

23 Context Analysis Diagram (CAD)

24 DFD - LEVEL 0

Checking the Diagrams for Errors (Continued Figure 7.5) Connecting data stores and external entities directly to each other 25

Checking the Diagrams for Errors (Continued) Incorrectly labeling processes or data flow Including more than nine processes on a data flow diagram 26

Checking the Diagrams for Errors (Continued) Omitting data flow Creating unbalanced decomposition (or explosion) in child diagrams 27

Typical Errors that Can Occur in a Data Flow Diagram (Payroll Example) (Figure 7.5) 28

Data Flow Example 29

Layers of DFD Abstraction for Course Registratio n System 30

Ref Systems Analysis and Design, Kendall & Kendall, 2014 Object-Oriented Systems Analysis and Design Using UML by Bennett, McRobb, Farmer,