Data Flow Diagrams.

Slides:



Advertisements
Similar presentations
Systems Analysis Requirements structuring Process Modeling
Advertisements

Data Flow Diagram (DFD) Review
Irwin/McGraw-Hill Copyright © 2004 The McGraw-Hill Companies. All Rights reserved Whitten Bentley DittmanSYSTEMS ANALYSIS AND DESIGN METHODS6th Edition.
Irwin/McGraw-Hill Copyright © 2004 The McGraw-Hill Companies. All Rights reserved Whitten Bentley DittmanSYSTEMS ANALYSIS AND DESIGN METHODS6th Edition.
1 Software Design Introduction  The chapter will address the following questions:  How do you factor a program into manageable program modules that can.
Chapter 3 Systems Documentation Techniques Copyright © 2012 Pearson Education 3-1.
Chapter 4 Enterprise Modeling.
What is Software Design?  Introduction  Software design consists of two components, modular design and packaging.  Modular design is the decomposition.
Copyright Irwin/McGraw-Hill Software Design Prepared by Kevin C. Dittman for Systems Analysis & Design Methods 4ed by J. L. Whitten & L. D. Bentley.
Software Design Deriving a solution which satisfies software requirements.
Chapter 4.
Systems Analysis and Design 9th Edition
Sylnovie Merchant, Ph.D. MIS 160 Section 2 Spring 2004 Lecture 9: Structured Systems Development MIS 160 Systems Development Life Cycle I.
© Copyright 2011 John Wiley & Sons, Inc.
Modeling the Processes and Logic
 A data flow diagram ( DFD ) is a graphical representation of the "flow" of data through an information system.  A data flow diagram can also be used.
Algebra Problems… Solutions
Chapter 3 Systems Documentation Techniques Copyright © 2012 Pearson Education, Inc. publishing as Prentice Hall 3-1.
Traditional Approach to Requirements Data Flow Diagram (DFD)
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.
PROCESS MODELING Chapter 8 - Process 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 3 Systems Documentation Techniques Copyright © 2012 Pearson Education, Inc. publishing as Prentice Hall 3-1.
Analysis Modeling. Function Modeling & Information Flow  Information is transformed as it flows through a computer-based system. The system accepts input.
Structured Analysis.
Chapter 3 Systems Documentation Techniques Copyright © 2012 Pearson Education, Inc. publishing as Prentice Hall 3-1.
Chapter 12: Design Phase n 12.1 Design and Abstraction n 12.2 Action-Oriented Design n 12.3 Data Flow Analysis n Data Flow Analysis Example n
PowerPoint Presentation for Dennis, Wixom, & Roth Systems Analysis and Design, 3rd Edition Copyright 2006 © John Wiley & Sons, Inc. All rights reserved.
1 6 Systems Analysis and Design in a Changing World, 2 nd Edition, Satzinger, Jackson, & Burd Chapter 6 The Traditional Approach to Requirements.
PROGRAM DEVELOPMENT CYCLE. Problem Statement: Problem Statement help diagnose the situation so that your focus is on the problem, helpful tools at this.
Systems Analysis and Design 8th Edition
Context Process0. student Data Flow Diagram Progression.
Systems Analysis and Design 8th Edition
McGraw-Hill/Irwin Copyright © 2006 by The McGraw-Hill Companies, Inc. All rights reserved. Chapter 5 Modeling the Processes and Logic.
Business Process Modeling What is a process model? – A formal way of representing how a business system operates. – Illustrates the activities that are.
© 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.
Tools Of Structured Analysis
Chapter 6 Structuring System Requirements: Process Modeling
DFD(Data Flow Diagram)
Business Process Modeling
Chapter 8 Structuring System Requirements: Process Modeling
Systems Analysis and Design
Chapter 6 The Traditional Approach to Requirements.
Problem Solving How do we attack a large problem?
System Design and Modeling
Copyright © Cengage Learning. All rights reserved.
Systems Analysis and Design
Chapter 1: Data Flow Diagram Structuring System Process Requirements
Data Flow Diagram (DFD) Review
CHAPTER 4 Test Design Techniques
Chapter 6 Structuring System Requirements: Process Modeling
Sequential circuit design
Model-View-Controller Patterns and Frameworks
Chapter 9 Structuring System Requirements: Logic Modeling
Accounting Systems & Business Processes Chapter 4
Sequential circuit design
Week 12: Activity & Sequence Diagrams
Sequential circuit design
Accounting Systems & Business Processes Chapter 4
Accounting Systems & Business Processes Chapter 4
Requirement Analysis using
Chapter 7: Data Flow Diagram Structuring System Process Requirements
Chapter 11 Describing Process Specifications and Structured Decisions
Chapter 9 Structuring System Requirements: Logic Modeling
Chapter 5.
Copyright © Cengage Learning. All rights reserved.
Scatter Diagrams Slide 1 of 4
DFD Process & Examples.
Presentation transcript:

Data Flow Diagrams

Revision Two-dimensional summary. Completeness. DFDs summarize the data flow characteristics of a process; provide a useful and concise summary of system-related (e.g., data-driven) process attributes. Completeness.  DFDs offer a way to check the completeness of your process model, particularly as regards your understanding of the data that would be required by an information system Processing, not processes.  DFDs refer to "process" steps. It might be more useful to think of DFD "processes" as processing steps rather than process activities

Advantages Data flows and process consequences Understand the processing steps that we need to take to complete the relevant transaction(s). Data inputs and outputs.  The DFD also makes it possible to understand what data are needed to provide appropriate inputs to any processing step Simplifying complexity by isolating process components.  Note how the DFD would make it easier to capture the detail of such data flows.

Testing the DFD/SF: DFDs look easy on the surface - after all, what's hard about writing down a few bubbles and arrows? In practice the techniques proves to be somewhat more difficult than one might initially anticipate. Obtaining appropriate names for both processing steps and data flows can require careful thought. As one rule of thumb, imagine that you are producing a diagram that must pass this test: you will finish the DFD, then hand it to someone who will then proceed to describe the process back to you based upon what he or she sees in your diagram.

Illegal data flows One of the patterns of data flow analysis is that all flows must begin with or end at a processing step. This makes sense, since presumably data cannot simply metastasize on its own without being processed

Diagramming Mistakes A processing step may have input flows but no output flows. This situation is sometimes called a black hole. A processing step may have output flows but now input flows. This situation is sometimes called a miracle. A processing step may have outputs that are greater than the sum of its inputs - e.g., its inputs could not produce the output shown. This situation is sometimes referred to as a grey hole.

Processing steps that do not change data: DFD’s are NOT flow charts: A last class of DFD mistakes are somewhat more difficult to identify. Flow chart diagrams can be useful for describing programming logic or understanding a single sequence of process activities. It is important to recognize, however, that DFDs are not flow charts. Flow charts often show both processing steps and data "transfer" steps (e.g., steps that do not "process" data);

Processing Activities? Display Print Endorse a cheque Write Log events

Preparation for test Know and Understand the notes: Chapter 2 DFD Mistakes with DFD