Process Analysis I: Flow Charts, Decision Tables, Decision Trees

Slides:



Advertisements
Similar presentations
Chapter 10: The Traditional Approach to Design
Advertisements

Systems Analysis and Design in a Changing World, Fifth Edition
Chapter 11 Describing Process Specifications and Structured Decisions
Systems Analysis Requirements structuring Process Modeling
CSC 123 Systems Analysis & Design
Describing Process Specifications and Structured Decisions Systems Analysis and Design, 7e Kendall & Kendall 9 © 2008 Pearson Prentice Hall.
Copyright © 2015 Pearson Education, Inc. Systems Documentation Techniques Chapter
Chapter 6: Documenting Accounting Information Systems
L ECTURE 12 – P ROCESS S PECIFICATION Definition, Motivation and Elements Structured English Decision Tables Decision trees Software Project Management.
Chapter 4.
Systems Analysis and Design 9th Edition
Copyright © 2011 Pearson Education, Inc. Publishing as Prentice Hall Process Specifications and Structured Decisions Systems Analysis and Design, 8e Kendall.
Chapter 9 Describing Process Specifications and Structured Decisions
Chapter 9 Describing Process Specifications and Structured Decisions Systems Analysis and Design Kendall & Kendall Sixth Edition © 2005 Pearson Prentice.
Chapter 9 Describing Process Specifications and Structured Decisions
PROCESS MODELING Transform Description. A model is a representation of reality. Just as a picture is worth a thousand words, most models are pictorial.
Data and Process Modeling
Jump to first page Chapter 2c System Analysis - Logic Modeling.
Kendall & KendallCopyright © 2014 Pearson Education, Inc. Publishing as Prentice Hall 9 Kendall & Kendall Systems Analysis and Design, 9e Process Specifications.
Chapter 4.
© 2005 by Prentice Hall Chapter 9 Structuring System Requirements: Logic Modeling Modern Systems Analysis and Design Fourth Edition.
Chapter 3 Planning Your Solution
Kendall & KendallCopyright © 2014 Pearson Education, Inc. Publishing as Prentice Hall 9 Kendall & Kendall Systems Analysis and Design, 9e Process Specifications.
Chapter 9 Structuring System Requirements: Logic Modeling
© 2005 by Prentice Hall Chapter 8 Structuring System Logical Requirements Modern Systems Analysis and Design Fourth Edition Jeffrey A. Hoffer Joey F. George.
PROCESS MODELING Chapter 8 - Process Modeling
Information Systems System Analysis 421 Class Eight.
Data and Process Modeling
MBI 630: Class 6 Logic Modeling 9/7/2015. Class 6: Logic Modeling Logic Modeling Broadway Entertainment Co. Inc., Case –Group Discussion (Handout) –Logic.
Accounting systems design & evaluation 9434SB 12 April 2002.
Modelling information systems
Chapter 9 Describing Process Specifications and Structured Decisions
Phase 2: Systems Analysis
Chapter 7 Structuring System Process Requirements
Chapter 11 Describing Process Specifications and Structured Decisions Systems Analysis and Design Kendall and Kendall Fifth Edition.
© 2006 ITT Educational Services Inc. SE350 System Analysis for Software Engineers: Unit 8 Slide 1 Chapter 8 Structuring System Logical Requirements.
Describing Process Specifications and Structured Decisions Systems Analysis and Design, 7e Kendall & Kendall 9 © 2008 Pearson Prentice Hall.
Chapter 8 Structuring System Logical Requirements.
Structured Analysis.
© 2006 Prentice Hall Business Publishing Accounting Information Systems, 10/e Romney/Steinbart1 of 138 FLOWCHARTS A flowchart is an analytical technique.
Irwin/McGraw-Hill Copyright © 2000 The McGraw-Hill Companies. All Rights reserved Whitten Bentley DittmanSYSTEMS ANALYSIS AND DESIGN METHODS5th Edition.
Chapter 4 enterprise modeling
PROGRAM DEVELOPMENT CYCLE. Problem Statement: Problem Statement help diagnose the situation so that your focus is on the problem, helpful tools at this.
Engineering H192 - Computer Programming Gateway Engineering Education Coalition Lect 3P. 1Winter Quarter Structured Engineering Problem Solving and Logic.
Systems Analysis and Design 8th Edition
© 2005 by Prentice Hall Chapter 9 Structuring System Requirements: Logic Modeling Modern Systems Analysis and Design Fourth Edition Jeffrey A. Hoffer Joey.
FLOWCHARTING AND ALGORITHMS
1 Information System Analysis Topic-3. 2 Entity Relationship Diagram \ Definition An entity-relationship (ER) diagram is a specialized graphic that illustrates.
Copyright © 2011 Pearson Education Process Specifications and Structured Decisions Systems Analysis and Design, 8e Kendall & Kendall Global Edition 9.
Modern Systems Analysis and Design Fourth Edition Chapter 8 Structuring System Logical Requirements (process description)
 Problem Analysis  Coding  Debugging  Testing.
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
Business Process Modeling
Chapter 8 Structuring System Logical Requirements
Business System Development
Process Specifications and Structured Decisions
Chapter 9 Structuring System Requirements: Logic Modeling
Introduction to Transaction Processing
Process Analysis I: Flow Charts, Decision Tables, Decision Trees
CIS 210 Systems Analysis and Development
Chapter 9 Structuring System Requirements: Logic Modeling
Chapter 9 Structuring System Requirements: Logic Modeling
Chapter 8 Structuring System Logical Requirements
Chapter 11 Describing Process Specifications and Structured Decisions
Chapter 9 Structuring System Requirements: Logic Modeling
Chapter 9 Structuring System Requirements: Logic Modeling
Documenting Accounting Information Systems
Information system analysis and design
Presentation transcript:

Process Analysis I: Flow Charts, Decision Tables, Decision Trees Yale Braunstein School of Information Management & Systems

Processes These lectures all relate to processes: Describing, analyzing, developing, modifying, documenting,… Types of processes include: Decision processes Data flow & manipulation processes, … Specific approaches depend on internal needs & practices, standards “A process model is a formal way of representing how a business operates”

Flow charts There are several standards – just be consistent Manual methods vs. automated tools Visio, PowerPoint, etc. Waves of fashion / variety of uses Programming Documenting processes Multi-user settings General documentation of all sorts

Flow chart techniques Basic symbols Terminator Process Decision Predefined process On-page connector Connector

Flowchart guidelines Top to bottom, left to right on the page Activity being flowcharted should be defined carefully and made clear to reader Identity start and end Use “one-verb” (verb-noun) descriptions Examples: “prepare statement,” “file record” Keep steps in proper sequence Observe scope & range of activity; branches should be on separate pages Use standard symbols; lines should NOT cross Use cross-overs only if necessary; keep lines straight No blind alleys or endless loops

Samples (with comments) Dining room table (again) Only partially complete, has potentially endless loop Still partially complete, but with additional steps Flow of logic in an SPSS session No terminators, no decision points Flow of information in a survey No terminators, no decision points, but clear distinction betweens types of processes How to obtain your FBI file (or Elvis’s) Why you might want to do this (if time permits)

Common problems Distinguish between “do it” and “schedule it” Avoid endless loops Account for & follow-up on holds / pauses / “unable to process” conditions, etc. Make clear whether data flows and telecom links are one-way or two-way Do NOT link to processes – use connectors

Other uses for Visio Document spreadsheets Functional decomposition diagrams Network & wiring diagrams E-R diagrams for databases Organization charts Statistical documentation & output Crime scene documentation, time lines, etc. Links to some of these are on the course download page

Decision tables & Decision trees Sometimes DFDs and E-R diagrams do not work adequately or the nature of the problem is more “analytic” First, a slight digression: It may help to specify the underlying logic in “structured English” Structured programming + natural English = Structured English

Examples of Structured English - 1 For each customer number in the customer table For each loan in the loans table that matches the above customer number Keep a running total of loans Keep a running total of the original loan principal Keep a running total of the current loan balance Keep a running total of the amounts past due

Examples of Structured English - 2 Sequence of Actions approach: Action 1: Go to inventory area Action 2: present ID to guard Action 3: Pick items from stock Action 4: Wand the items

Action Conditions can be simple or complex Simple Condition Actions: If item is on shelf Then sequence of actions Else sequence of actions Complex Condition Actions Do the following based on the customer order Case 1: Construct turkey sandwich Case 2: Assemble taco salad Case 3: Construct pastrami sandwich

Decision tables May be a better alternative to characterize the actions taken in a given task Tabular form of presentation that specifies a set of conditions and their corresponding actions Sometimes used for guidance in decision-making, especially if trying to routinize a process.

Example: Should we cash the check? Awful pun may go here We can document the process with a flow chart or with a decision table (or both) Which one is better? Depends on common practice in organization May depend on the specifics of the process The policy (decision rule): “A customer with check-cashing privileges is entitled to cash personal checks up to $75 and payroll checks from pre-approved local employers.”

Construction of the decision table Four main parts: Conditions vs. Actions Stub vs. Entry Conditions: think of a series of if statements Actions: think of a series of then statements

General format

The “cash a check” table

Decision trees A decision tree is an alternate approach to representing decision situation More graphical Easier to change (sometimes) Shows conceptually what is going on—you step through the decision-making process Legend: Salaried? Hours worked < 40? Hours worked = 40?