SYSTEMS ANALYSIS AND DESIGN ITDB 2101 HAND OUT # 3 1.

Slides:



Advertisements
Similar presentations
CAPE INFORMATION TECHNOLOGY – Unit 2
Advertisements

Systems Analysis Requirements structuring Process Modeling
Data Flow Diagram (DFD) Review
SYSTEMS ANALYSIS AND DESIGN TOOLS
Using Data Flow Diagrams
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.
ACG 4401 Data Modeling: Data Flow Diagrams Flow Charts.
Chapter 4 – Documenting Information Systems
Chapter 4.
Systems Analysis and Design 9th Edition
Jump to first page Chapter 2 System Analysis - Process Modeling.
Using Dataflow Diagrams
Chapter 7 Using Data Flow Diagrams
Topics Creating DFD Physical and logical DFD Event driven modeling
Modern Systems Analysis and Design
Structuring System Requirements: Process Modeling
MIS 461: Structured System Analysis and Design Dr. A.T. Jarmoszko
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 9 Using Data Flow Diagrams
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.
The Traditional Approach to Requirements: Using Dataflow Diagrams Spring
System Analysis and Design
DATA FLOW DIAGRAMS IT 155.
Chapter 7 Structuring System Process Requirements
Chapter 8 Structuring System Requirements: Process Modeling
Chapter 1: Data Flow Diagram Structuring System Process Requirements
PowerPoint Presentation for Dennis & Haley Wixom, Systems Analysis and Design Copyright 2000 © John Wiley & Sons, Inc. All rights reserved. Slide 1 Process.
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.
1 Chapter 2 Revision: Documentation DFD System FC.
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 Learning Units
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.
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
Data Flow Diagrams (DFD). ScenarioCriteriaTasks Data flow diagram(DFD) is a diagram of the movement of data between external entities.
Chapter 3 Systems Documentation Techniques Copyright © 2012 Pearson Education, Inc. publishing as Prentice Hall 3-1.
Chapter 7 Using 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.
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
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.
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.
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.
Software Development Lifecycle- SDLC Design- using DFDs.
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.
Process Modeling Graphically represent the processes that capture, manipulate, store, and distribute data between a system and its environment Models DFDs.
Business System Development
IS 334 information systems analysis and design
System Process Modeling
SDLC Phase III: Structuring System Requirements
Chapter 1: Data Flow Diagram Structuring System Process Requirements
Process & Logic Modeling
Welcome to my presentation
MBI 630: Week 4 Process Modeling
Chapter 7: Data Flow Diagram Structuring System Process Requirements
Chapter 4: documenting information systems
Presentation transcript:

SYSTEMS ANALYSIS AND DESIGN ITDB 2101 HAND OUT # 3 1

2 MAINTENANCE CONVERSION CONSTRUCTION TESTING PROBLEM RECOGNITION FEASIBILITY STUDY ANALYSIS DESIGN THE SYSTEMS DEVELOPMENT LIFE CYCLE (SDLC), also known as the WATERFALL MODEL

STEP 1: PROBLEM RECOGNITION STEP Name Problem Recognition Major Function To establish that a problem exists in the system. Output PROBLEMS TO BE SOLVED; WHY DO WE NEED A BETTER SYSTEM.– Permission to conduct feasibility Study WHO ARE INVOLVED? Systems Analyst, Users (Staff) and Managers of the Company Usually known as the PLANNING STEP.

STEP 2: FEASIBILITY STUDY STEP NameFeasibility Study Major Function ??? OUTPUT Feasibility Report and Risk Analysis WHO ARE INVOLVED? Systems Analyst

STEP 3: ANALYSIS STEP Name ANALYSIS Major Function To study the present system very carefully, study the requirements of the new computerized system, and to create models of the old and the new system. The objective is to clearly understand the present system, learn what is needed, and discover the shortcomings or faults that must be corrected or modified

DATA FLOW DIAGRAM (DFD) DATA FLOW DIAGRAMS (DFD) – graphical representation to show the flow of data within the system. - shows the processes in the system

DATA FLOW DIAGRAM (DFD) Purpose/Objective The purpose of data flow diagrams is to provide a bridge between users and systems developers. Graphical: Eliminating need of thousands of words. Logical Representations: Modeling WHAT a system does, rather than physical model showing HOW it does it.

2 CATEGORIES OF DFD 1.LOGICAL DATA FLOW DIAGRAM 2.PHYSICAL DATA FLOW DIAGRAM

2 CATEGORIES OF DFD 1.LOGICAL DATA FLOW DIAGRAM- Focuses on the business and how the business operates. It describes the events that happens and the data required and produced in each event. 2. PHYSICAL DATA FLOW DIAGRAM- Shows how the system will be implemented.

SYMBOLS OF DFD 1.ENTITY- represents either the SOURCE or the DESTINATION of data. Example: A person, another system or an organization who send or receive data to and from the system SYMBOL:

SYMBOLS OF DFD 2.DATA FLOW- represents movement or the flow of data. SYMBOL:

SYMBOLS OF DFD 3.PROCESS- represents an activity or a process that transforms or manipulates the data. Note: A process transforms incoming data flow into outgoing data flow). SYMBOL:

SYMBOLS OF DFD 4.DATA STORE- represents data that is saved on some file or in a table. Represents the STORAGE of data. SYMBOL:

RULES IN CONSTRUCTING DFDs ENTITY RULE # 1: Data cannot move directly from an entity to another entity. It must be moved by a PROCESS. RULE # 2: An entity should have a NOUN phrase level.

RULES IN CONSTRUCTING DFDs PROCESS RULE # 1: A process should have at least one input and at least one output. RULE # 2: A process should have a VERB phrase level.

RULES IN CONSTRUCTING DFDs DATA FLOW RULE # 1: A data flow should only have one direction of flow between symbols. RULE # 2: A fork in a data means that exactly the same data goes from a common location to two or more different processes, data stores, or sources (this usually indicates different copies of the same data going to different locations)..

RULES IN CONSTRUCTING DFDs DATA FLOW RULE # 3: A data flow cannot go directly back to the same process it leaves.. RULE # 4: A data flow to a data store means update (delete or change). RULE # 5: A data flow from a data store means retrieve or use. RULE # 6: A data flow has a noun phrase label. More than one data flow noun phrase can appear on a single arrow as long as all of the flows on the same arrow move together as one package.

RULES IN CONSTRUCTING DFDs DATA STORE RULE # 1: Data cannot move directly from one data store to another data store. Data must be moved by a process. RULE # 2: Data cannot move directly from an entity to a data store. Data must be moved by a process. RULE # 3: Data cannot move directly from a data store to an entity. Data must be moved by a process. RULE # 4: A data store has a noun phrase level.

STEPS IN CONSTRUCTING DFDs 1.Start with the Context Diagram 2. Identify the functions to be performed 3. Show the information flow between functions and identify data stores and external entities 4. Repeatedly elaborate on the DFD ( bottom up and top down )

CONTEXT DIAGRAMS A context diagram provides the most general view of an information system. Emphasis is on the relationship between the system and its environment. Consist of a single process symbol representing the whole system, entities and data flow.

STEPS IN CONSTRUCTING CONTEXT DIAGRAMS 1. Start by placing a single process symbol at the center of the page. The symbol represents the entire information system, and you identify it as process Then place the external entities around the process and use data flows to connect the entities to the central process. 3. Do not show any data stores in a context diagram because data stores are internal to the system.

END OF CLASS FOR TODAY 22