Cis339 Modern Systems Analysis and Design Fifth Edition Chapter 8 Structuring System Logic Requirements: 8.1.

Slides:



Advertisements
Similar presentations
Decision Tables.
Advertisements

Chapter 9 Structuring System Requirements: Logic Modeling
Chapter 8 Logic Requirements
Chapter 5 Structuring System Requirements: Process Modeling
Systems Analysis Requirements structuring Process Modeling
Chapter 8 Structuring Requirements Logic Modeling.
Chapter 7 Structuring System Process Requirements
Copyright 2006 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Third Edition Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Chapter.
Structured English. From user-speak to programming User Structured English Analyst Programs Programmer Plain English Pseudocode.
Logic Modeling. Learning Objectives Use Structured English as a tool for representing steps in logical processes in data flow diagrams Use Structured.
Decision Trees. Modeling Logic with Decision Trees A graphical representation of a decision situation Decision situation points are connected together.
Structuring System Requirements: Process Modeling
Copyright 2004 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Second Edition Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Chapter.
CHAPTER 9: Structuring System Requirements: Logic Modeling
Logic Modeling Data flow diagrams do not show the logic inside the processes Logic modeling involves representing internal structure and functionality.
Jump to first page Chapter 2c System Analysis - Logic Modeling.
Process Descriptions: Logic Modeling
Modeling the Processes and Logic
© 2005 by Prentice Hall Chapter 9 Structuring System Requirements: Logic Modeling Modern Systems Analysis and Design Fourth Edition.
Logic Modeling MIS 322. Why do we need Logic Modeling? Lets look at the following DFD.
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.
Copyright © 2012 Pearson Education, Inc. Publishing as Prentice Hall 6.1.
Chapter 7 Structuring System Process Requirements Modern Systems Analysis and Design Sixth Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich.
Copyright © 2012 Pearson Education, Inc. Publishing as Prentice Hall 6.1.
Copyright © 2009 Pearson Education, Inc. Publishing as Prentice Hall Chapter 6 Structuring System Requirements: Process Modeling 6.1.
Information Systems System Analysis 421 Class Eight.
MBI 630: Class 6 Logic Modeling 9/7/2015. Class 6: Logic Modeling Logic Modeling Broadway Entertainment Co. Inc., Case –Group Discussion (Handout) –Logic.
Chapter 8 Structuring System Requirements: Logic Modeling
© 2008 Prentice Hall, Ovidiu Noran Lecture 7a 1 Modelling Logic Requirements (Textbook Chapter 8)
Copyright © 2009 Pearson Education, Inc. Publishing as Prentice Hall Essentials of Systems Analysis and Design Fourth Edition Joseph S. Valacich Joey F.
© 2006 ITT Educational Services Inc. SE350 System Analysis for Software Engineers: Unit 8 Slide 1 Chapter 8 Structuring System Logical Requirements.
Chapter 8 Structuring System Logical Requirements.
Systems Analysis and Design for the Small Enterprise section III Process design.
Business Analysis Information determination Information specification Alternative generation and selection.
9-1 © Prentice Hall, 2007 Chapter 9: Analysis Classes Object-Oriented Systems Analysis and Design Joey F. George, Dinesh Batra, Joseph S. Valacich, Jeffrey.
Copyright 2001 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Chapter 5 Structuring.
Modern Systems Analysis and Design Fifth Edition
7-1 © Prentice Hall, 2007 Topic 7: Analysis Classes Object-Oriented Systems Analysis and Design Joey F. George, Dinesh Batra, Joseph S. Valacich, Jeffrey.
Seg3430A Tutorial 8 Decision Table. Logic Modeling Data flow diagrams do not show the logic inside the processes Logic modeling involves representing.
© 2005 by Prentice Hall Chapter 9 Structuring System Requirements: Logic Modeling Modern Systems Analysis and Design Fourth Edition Jeffrey A. Hoffer Joey.
1 Information System Analysis Topic-3. 2 Entity Relationship Diagram \ Definition An entity-relationship (ER) diagram is a specialized graphic that illustrates.
Chapter 7 Structuring System Process Requirements Modern Systems Analysis and Design Sixth Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich.
Modern Systems Analysis and Design Fourth Edition Chapter 8 Structuring System Logical Requirements (process description)
McGraw-Hill/Irwin Copyright © 2006 by The McGraw-Hill Companies, Inc. All rights reserved. Chapter 5 Modeling the Processes and Logic.
Copyright 2002 Prentice-Hall, Inc. Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich Chapter 9 Structuring.
6 - 1 Systems Analysis and Design, 2 nd Edition Alan Dennis and Barbara Haley Wixom John Wiley & Sons, Inc. Slides by Roberta M. Roth University of Northern.
MIS 360: System Analysis and Design Dr. Qasem Al-Radaideh Department of Computer Information Systems Faculty of Information Technology Yarmouk University.
Analysis Classes Unit 5.
Chapter 6 Structuring System Requirements: Process Modeling
Chapter 6 Structuring System Requirements: Process Modeling
Chapter 8 Structuring System Logical Requirements
Business System Development
Chapter 9 Structuring System Requirements: Logic Modeling
Chapter 2 : Data Flow Diagram
Process & Logic Modeling
Chapter 6 Structuring System Requirements: Process Modeling
Chapter 9 Structuring System Requirements: Logic Modeling
Chapter 9 Structuring System Requirements: Logic Modeling
CIS 210 Systems Analysis and Development
Chapter 8 Logic Requirements
Chapter 9 Structuring System Requirements: Logic Modeling
Chapter 9 Structuring System Requirements: Logic Modeling
Chapter 9 Structuring System Requirements: Logic Modeling
Information Systems Development MIS331
Chapter 7: Data Flow Diagram Structuring System Process Requirements
Chapter 8 Structuring System Logical Requirements
Chapter 9 Structuring System Requirements: Logic Modeling
Chapter 9 Structuring System Requirements: Logic Modeling
Presentation transcript:

Cis339 Modern Systems Analysis and Design Fifth Edition Chapter 8 Structuring System Logic Requirements: 8.1

Cis339 Learning Objectives Use Structured English as a tool for representing steps in logical processes in data flow diagrams Use decision tables and decision trees to represent the logic of choice in conditional statements Select among Structured English, decision tables, and decision trees for representing processing logic 8.2

Cis339 Logic Modeling Data flow diagrams do not show the logic inside the processes Logic modeling involves representing internal structure and functionality of processes depicted on a DFD Logic modeling can also be used to show when processes on a DFD occur 8.3

Cis339 Modeling a System’s Logic

Cis339 Logic Modeling Deliverables and Outcomes Structured English representation of process logic. Decision Tables representation. Sequence diagram. Activity diagram Structured English Decision Tables Decision Trees State-transition diagrams Sequence diagrams Activity diagrams 8.5

Cis339 Modeling Logic with Structured English Structured English: modified form of English language used to specify the logic of information system processes. No single standard. Typically relies on action verbs and noun phrases and contains no adjectives or No specific standards. Uses a subset of English Action verbs Noun phrases No adjectives or adverbs No specific standards 8.6

Cis339 Modeling Logic with Structured English

Cis339 Modeling Logic with Structured English

Cis339 Modeling Logic with Decision Tables A matrix representation of the logic of a decision which Specifies the possible conditions and the resulting actions Best used for complicated decision logic 8.9

Cis339 Figure 9-4 Complete decision table for payroll system example

Cis339 Modeling Logic with Decision Tables Consists of three parts Condition stubs: that part of a decision table that lists the conditions relevant to the decision. Action stubs: that part of a decision table that lists the actions that result for a given set of conditions. Rules: that part of a decision table that specifies which actions are to be followed for a given set of condition. 8.11

Cis339 Modeling Logic with Decision Tables Indifferent Condition Indifferent condition: in a decision table, a condition whose value does not affect which actions are taken for two or more rules. Procedure for Creating Decision Tables Name the condition and values each condition can assume Name all possible actions that can occur List all rules Define the actions for each rule Simplify the table( remove any rules which has no actions) 8.12

Cis339 Figure 9-4 simplify decision table for payroll system example 8.13

Cis339 Decision Table for Hoosier Burger’s Inventory reordering

Cis339 Simplified Decision Table for Hoosier Burger’s Inventory reordering

Cis339 Modeling Logic with Decision Trees A graphical representation of a decision situation Decision situation points (nodes) are connected together by arcs and terminate in ovals Two main components Decision points represented by nodes Actions represented by ovals Read from left to right Each node corresponds to a numbered choice on a legend All possible actions are listed on the far right 8.16

Cis339 Figure 9-9 Decision tree representation of the decision logic in the decision tables in Figures 9-4 and 9-5, with only two choices per decision point 8.17

Cis339 Deciding Among Structured English, Decision Tables and Decision Trees CriteriaStructured English Decision Tables Decision Trees Determining Conditions and Actions Second BestThird BestBest Transforming Conditions and Actions into Sequence BestThird BestBest Checking Consistency and Completeness Third BestBest 8.18

Cis339 Deciding Between Table and Tree CriteriaDecision Table Decision Tree Portraying complex logic Best Worst Portraying simple problemWorst Best Making decisionWorstBest More compactBestWorst Easier to manipulateBestWorst