ACG 4401 Data Modeling: Data Flow Diagrams Flow Charts.

Slides:



Advertisements
Similar presentations
CAPE INFORMATION TECHNOLOGY – Unit 2
Advertisements

Documenting an AIS II Flowcharts Documenting AIS II.
Systems Analysis Requirements structuring Process Modeling
Data Flow Diagram (DFD) Review
Reading System Documentation Using Flowchart Pertemuan Matakuliah: F0204 / Sistem Akuntansi Tahun: 2007.
SYSTEMS ANALYSIS AND DESIGN TOOLS
Chapter 7 Structuring System Process Requirements
Using Dataflow Diagrams
© 2005 by Prentice Hall 7-1 Chapter 7 Structuring System Process Requirements Modern Systems Analysis and Design Fourth Edition Jeffrey A. Hoffer Joey.
Documenting Information Systems
PowerPoint Presentation for Dennis & Haley Wixom, Systems Analysis and Design, 2 nd Edition Copyright 2003 © John Wiley & Sons, Inc. All rights reserved.
Copyright © 2015 Pearson Education, Inc. Systems Documentation Techniques Chapter
Documenting Information Systems
PowerPoint Presentation by Charlie Cook Copyright © 2004 South-Western. All rights reserved. Chapter 2 Documenting Business Processes and Information Systems.
© 2006 Prentice Hall Business Publishing Accounting Information Systems, 10/e Romney/Steinbart1 of 138 DOCUMENT FLOWCHARTS A document flowchart shows the.
Chapter 6: Documenting Accounting Information Systems
Systems Documentation Techniques
Documenting Information Systems. Learning Objectives To read and evaluate data flow diagrams To read and evaluate systems flowcharts. To prepare data.
Chapter 4 – Documenting Information Systems
PowerPoint Presentation by Charlie Cook Copyright © 2004 South-Western. All rights reserved. Chapter 2 Documenting Business Processes and Information Systems.
Jump to first page Chapter 2 System Analysis - Process Modeling.
Chapter 7 Using Data Flow Diagrams
Structuring System Requirements: Process Modeling
Advanced Accounting Information Systems
Systems Analysis I Data Flow Diagrams
System analysis and design
DATA FLOW DIAGRAMS IT 155.
Copyright © 2015 Pearson Education, Inc. Systems Documentation Techniques Chapter
Systems Documentation Techniques
Chapter 7 Structuring System Process Requirements
staffs.ac.uk Process Model. staffs.ac.uk Contents Provide definitions Explain the components and representations Introduce a step.
Data Flow Diagrams (DFDs)
Chapter 1: Data Flow Diagram Structuring System Process Requirements
Structuring System Process Requirements. Learning Objectives Understand the logical modeling of processes by studying examples of data flow diagrams (DFDs).
Data and Process Modeling
1 Chapter 2 Revision: Documentation DFD System FC.
ACG 6415 Data Modeling: Data Flow Diagrams Flow Charts.
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.
Data-Flow Diagrams Week 10 Lecture 1. Data Flow Diagrams (DFDs) One of most important modelling tools used by system analysts In use since late 1970’s.
Documentation Why do auditors pay such close attention to system documentation? l It helps to understand the system - how it works. l The auditor’s documentation.
The Structured Specification. Why a Structured Specification? System analyst communicates the user requirements to the designer with a document called.
Chapter 7 Structuring System Process Requirements
Chapter 3 Systems Documentation Techniques Copyright © 2012 Pearson Education, Inc. publishing as Prentice Hall 3-1.
DATA FLOW DIAGRAMS We’re going to go into a partial example of how the first level of detail was created. But before we do, let’s step through some guidelines.
Documenting Information Systems. Learning Objectives To read and evaluate data flow diagrams To read and evaluate systems flowcharts. To prepare data.
Judi Prajetno Sugiono ©2009 Management Information System Additional note for DFD.
DON’T DO IT! IT’S NOT HOPELESS. Documentation Flowcharting Due to thier complexity (when looking at them), flowcharts intimidate many people. However,
Process Models: Data Flow Diagrams Chapter 2. Process Modeling Objective: Understand the concept of business processes Understand and create Data Flow.
SYSTEMS ANALYSIS AND DESIGN TOOLS 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.
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.
Chapter 3 Systems Documentation Techniques Copyright © 2012 Pearson Education, Inc. publishing as Prentice Hall 3-1.
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.
C_ITIP211 LECTURER: E.DONDO. Unit 3 : PROCESS MODELING.
© 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.
PowerPoint Presentation by Charlie Cook Copyright © 2004 South-Western. All rights reserved. Lecture 3 Documenting Business Processes and Information Systems.
Business Process Modeling What is a process model? – A formal way of representing how a business system operates. – Illustrates the activities that are.
Systems Documentation Techniques
Business System Development
System Process Modeling
Chapter 1: Data Flow Diagram Structuring System Process Requirements
تحلیل سیستم‌ها مدل‌سازی پردازشی.
DON’T DO IT! IT’S NOT HOPELESS.
Chapter 7: Data Flow Diagram Structuring System Process Requirements
Chapter 4: documenting information systems
Presentation transcript:

ACG 4401 Data Modeling: Data Flow Diagrams Flow Charts

Benefits of DFD’s Uncover misunderstandings of system processes Help communicate analyst system understanding to management/end users Helps to take the system out of context Eases the problem of thinking outside of the box 4

Fed Ex Process (Physical DFD) 3

DFD Guidelines Choose meaningful names for processes, flows, stores, and terminators. Number the processes. Redraw the DFD as many times as necessary for esthetics. Avoid overly complex DFDs. Make sure the DFD is internally consistent and consistent with any associated DFDs (ie Balanced). 14

Preparing Data Flow Diagrams Read narrative carefully - number lines and paragraphs in text Prepare table of entities and activities Draw context diagram - use DFD guidelines 35

Steps for Creating E&A Table Read Narrative Identify all Verb phrases (circle them) Identify all Noun phrases (rectangles or data store) Line by line insert noun as Entity and Verb as Activity along with data flow noun if present Identify External Entities Identify Internal Entities 36

Entities and Activities Table 7

DFD Guidelines 1. Include on the systems documentation all (and only) activities and entities described in the systems narrative - no more, no less. 2. When multiple entities operate identically, depict only one to represent all. 37

DFD Guidelines (Level-0 and higher) 5. Group activities if they occur in the same place and at the same time. 6. Group activities if they occur at the same time but in different places. 7. Group activities that seem to be logically related. 8. To make the DFD readable, use between five and seven bubbles. 9. On a logical DFD, data flows cannot go from higher- to lower-numbered bubbles. 40

Preparing Systems Flowcharts 1. Divide the flowchart into columns; one column for each internal entity and one for each external entity. Label each column. 2. Flowchart columns should be laid out so that the flowchart activities flow from left to right, but you should locate columns so as to minimize crossed lines and connectors. 50

System flowcharting guidelines (cont.) 3. Flowchart logic should flow from top to bottom and from left to right. For clarity, put arrows on all flow lines. 4. Keep the flowchart on one page. If you can’t, use multiple pages and connect the pages with off-page connectors. Computerized flowcharting packages will print your flowcharts only on paper that will fit in your printer! 51

52

System flowcharting guidelines (cont.) 5. Within each column, there must be at least one manual process, keying operation, or data store between documents. That is, do not directly connect documents within the same column. 6. When crossing organizational lines (one column to another), show a document at both ends of the flow line unless the connection is so short that the intent is unambiguous. 53

System flowcharting guidelines (cont.) 7. Documents or reports printed in a computer facility should be shown in that facility’s column first. You can then show the document or report going to the destination unit. 8. Documents or reports printed by a centralized computer facility on equipment located in another organizational unit ( warehouse, shipping dept.) should not be shown within the computer facility. 54

System flowcharting guidelines (cont.) 9. Processing within an organizational unit on devices such as a PC or computerized cash register should be shown within the unit or as a separate column next to that unit, but not in the central computer facility column. 10. Sequential processing steps (computerized or manual) with no delay between them (and resulting from the same input) can be shown as one process or as a sequence of processes. 55

System flowcharting guidelines (cont.) 11. The only way into a computer data storage unit is through a computer processing rectangle. 12. A manual process is not needed to show the sending of a document. The sending of the document should be apparent from the movement of the document itself. 13. Do not use a manual process to file a document. Just show the document going in to a file. 56