9-1 Chapter 9 (part I): Analysis Classes (Adapted) Object-Oriented Systems Analysis and Design Joey F. George, Dinesh Batra, Joseph S. Valacich, Jeffrey.

Slides:



Advertisements
Similar presentations
Object-Oriented Analysis and Design: Activity Diagrams
Advertisements

© 2005 by Prentice Hall Appendix 3 Object-Oriented Analysis and Design Modern Systems Analysis and Design Fourth Edition Jeffrey A. Hoffer Joey F. George.
Chapter 9 Structuring System Requirements: Logic Modeling
Describing Process Specifications and Structured Decisions Systems Analysis and Design, 7e Kendall & Kendall 9 © 2008 Pearson Prentice Hall.
© 2005 by Prentice Hall 7-1 Chapter 7 Structuring System Process Requirements Modern Systems Analysis and Design Fourth Edition Jeffrey A. Hoffer Joey.
Chapter 7 Structuring System Process Requirements
Lecture Set 3E Introduction Basic Software Development Issues 1. Notes on Software Development 2. Intro to Software Development Tools 7/31/2008 2:43PM.
ALGORITHMS THIRD YEAR BANHA UNIVERSITY FACULTY OF COMPUTERS AND INFORMATIC Lecture two Dr. Hamdy M. Mousa.
© 2006 ITT Educational Services Inc. SE350 System Analysis for Software Engineers: Unit 9 Slide 1 Appendix 3 Object-Oriented Analysis and Design.
Information System Design IT60105
Interaction Diagrams Activity Diagram State Machine Diagram
Asper School of Business University of Manitoba Systems Analysis & Design Instructor: Bob Travica Analyzing systems process: Activity diagram Updated 2014.
Chapter 2- Visual Basic Schneider
2-1 © Prentice Hall, 2007 Chapter 2: Introduction to Object Orientation Object-Oriented Systems Analysis and Design Joey F. George, Dinesh Batra, Joseph.
Chapter 9 Describing Process Specifications and Structured Decisions
9-1 © Prentice Hall, 2004 Chapter 9, Part II: System Behavior - Interactions (Adapted) Object-Oriented Systems Analysis and Design Joey F. George, Dinesh.
Modern Systems Analysis and Design Fifth Edition Jeffrey A
Object-Oriented Analysis and Design: Sequence Diagrams
Chapter 1 Program Design
2-1 © Prentice Hall, 2004 Chapter 2: Introduction to Object Orientation (Adapted) Object-Oriented Systems Analysis and Design Joey F. George, Dinesh Batra,
SE-565 Software System Requirements More UML Diagrams.
The Program Design Phases
© 2005 by Prentice Hall Chapter 8 Structuring System Logical Requirements Modern Systems Analysis and Design Fourth Edition Jeffrey A. Hoffer Joey F. George.
System Implementation System Implementation - Mr. Ahmad Al-Ghoul System Analysis and Design.
Chapter 9 Designing Databases Modern Systems Analysis and Design Sixth Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich.
Copyright 2002 Prentice-Hall, Inc. Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich Chapter 20 Object-Oriented.
Activity/Workflow Diagrams Chapter 7 Appendix B. © 2011 Pearson Education, Inc. Publishing as Prentice Hall Process Modeling: Activity/Workflow Diagrams.
1 Introduction to Flowcharting. 2 Writing a program Defining the problem –Write down what the program will do Planning –Write down the steps, draw a flowchart.
Activity diagrams. Introduction ● Activity diagrams are a behavioural model that represent the dynamics of the system. ● An activity diagram is essentially.
9-1 © Prentice Hall, 2004 Chapter 9: Analysis Classes Object-Oriented Systems Analysis and Design Joey F. George, Dinesh Batra, Joseph S. Valacich, Jeffrey.
9-1 © Prentice Hall, 2007 Chapter 9: Analysis Classes Object-Oriented Systems Analysis and Design Joey F. George, Dinesh Batra, Joseph S. Valacich, Jeffrey.
Dale Roberts 1 Program Control - Algorithms Department of Computer and Information Science, School of Science, IUPUI CSCI N305.
© 2008 Prentice Hall, Ovidiu Noran Lecture 7b 1 Modelling OO Logic Requirements: Sequence Diagrams and Activity Diagrams (Textbook Chapter 8, Appendix)
Structured Program Development Angela Chih-Wei Tang ( 唐 之 瑋 ) Department of Communication Engineering National Central University JhongLi, Taiwan 2010.
Chapter 7 Appendix C Object-Oriented Analysis and Design: Sequence Diagrams Modern Systems Analysis and Design Sixth Edition Jeffrey A. Hoffer Joey F.
CS212: Object Oriented Analysis and Design Lecture 34: UML Activity and Collaboration diagram.
Chapter 7 Appendix B Object-Oriented Analysis and Design: Activity Diagrams Modern Systems Analysis and Design Seventh Edition Jeffrey A. Hoffer Joey F.
A Student Guide to Object-Oriented Development
Chapter 7 Structuring System Process Requirements Modern Systems Analysis and Design Fourth Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich.
7-1 © Prentice Hall, 2007 Topic 7: Analysis Classes Object-Oriented Systems Analysis and Design Joey F. George, Dinesh Batra, Joseph S. Valacich, Jeffrey.
13-1 © Prentice Hall, 2004 Chapter 13: Designing the Human Interface Object-Oriented Systems Analysis and Design Joey F. George, Dinesh Batra, Joseph S.
Some of these slides were excerpted from: Object-Oriented Systems Analysis and Design Joey F. George, Dinesh Batra, Joseph S. Valacich, Jeffrey A. Hoffer.
© 2005 by Prentice Hall Chapter 9 Structuring System Requirements: Logic Modeling Modern Systems Analysis and Design Fourth Edition Jeffrey A. Hoffer Joey.
Analysis Classes. What Is an Analysis Class?  A class that represents initial data and behavior requirements, and whose software and hardware-oriented.
STEP 3- DEVELOP AN ALGORITHM At this stage we break down the problem into simple manageable steps so that they can be handled easily.
© 2005 by Prentice Hall Chapter 7 Structuring System Process Requirements Modern Systems Analysis and Design Fourth Edition Jeffrey A. Hoffer Joey F. George.
Appendix Object-Oriented Analysis and Design: Use Cases and Sequence Diagrams Modern Systems Analysis and Design Fifth Edition Jeffrey A. Hoffer Joey F.
Copyright 2002 Prentice-Hall, Inc. Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich Chapter 9 Structuring.
Business Process and Functional Modeling
Appendix 3 Object-Oriented Analysis and Design
Analysis Classes Unit 5.
Chapter 8 Structuring System Logical Requirements
Activity and State Transition Diagram
Programming Fundamentals
Business System Development
Chapter 5 Structures.
Analyzing systems process: Activity Diagram
Use Case Modeling - techniques for detailing use cases
Chapter 9 Structuring System Requirements: Logic Modeling
Chapter 9 Structuring System Requirements: Logic Modeling
Process Modeling: Activity/Swimlane Diagrams
MSIS 655 Advanced Business Applications Programming
Structured Program
Object-Oriented Analysis and Design: Activity Diagrams
Chapter 2- Visual Basic Schneider
Chapter 7: Data Flow Diagram Structuring System Process Requirements
Chapter 8 Structuring System Logical Requirements
Appendix 3 Object-Oriented Analysis and Design
Object-Oriented Analysis and Design: Activity Diagrams
Presentation transcript:

9-1 Chapter 9 (part I): Analysis Classes (Adapted) Object-Oriented Systems Analysis and Design Joey F. George, Dinesh Batra, Joseph S. Valacich, Jeffrey A. Hoffer

9-2 Outline System Logic Activity Diagram Decision Tables Business Rules

9-3 System Logic Aspect of system’s behavior showing flow of control among processes (activities). Depicted in Activity Diagram, Decision Tables, etc. Different types of logic.

9-4 Activity Diagram A diagram that emphasizes the flow of control over processes or object activities by using decision points and other flowchart symbols. Similar to the traditional program flowchart

9-5 Elements of Activity Diagrams Activity – a behavior that an object carries out while in a particular state; an oval shape. Transition, Flow of control – a movement from one activity or state to another; an arrow shape. Decision point – condition(s) that shift control to different paths of activities; a diamond shape. Merge point – point that merges different paths after decision point; a diamond shape. Synchronization bar – bars denoting parallel paths of activities

9-6 Activity diagram with a decision point One of the two possible paths will be selected for each execution of Online Store Sales System

9-7 Activity diagram with synchronization bars Top synchronization bar is a fork. Bottom synchronization bar is a join. in a Sales Management System

9-8 1)Sequential logic – processes run one after another Types of Logic Create Order Check Order Status Place Order Process Invoice to Order Activity Diagram for Purchasing Management System 2) Parallel logic – processes run at the same time (Fig. 9.12); uses synchronizations bars.

9-9 3) Conditional logic – process runs if certain conditions met. Also called IF-THEN logic. - Example: See Fig Example of counter-based decision point: Courses <= 5 Register Student Print “Limit Reached” Yes No Decision point in Course Registration System allowing 5 courses/semester

9-10 Create Special Order 4) Case logic – expanded version of IF-THEN logic. Product in Inventory ? Create Standing Order Create New Order Never procured At min. level At zero level Enter Create Order Module Resembles decision tree. Used also for logic of user interface. Activity Diagram of Create Order Process in Purchasing Management System Merge point Conditions

9-11 5) Loop logic – circular flow (repetition, iteration); variant of IF-THEN logic. Two forms: (a) test a condition, then run a process (while a condition is true, do process) (b) run a process, then test a condition (do process, until a condition is false) Hungry ? Eat Y N Hungry ? Y N Used in lower level diagrams; communicates well to programmers. Activity diagrams may use other symbols for repetition. Also, see Fig Or: 1.Get Login Data 2.Decision: Data Correct? 3.If No at 2, go to 1

9-12 Decision Tables Legend: S=Salaried Employee, K=Hourly Employee; X means that a particular action is chosen.

9-13 Legend: S=Salaried Employee, K=Hourly Employee; X means that a particular action is chosen.

9-14 Business Rules A directive that is intended to influence or guide business behavior. In information systems, business rules are implemented as inferences (decisions), constraints, and program code.

9-15 Types of Business Rules Inferences – Decision points (in activity diagrams; in decision tables that result in attribute values and actions being set). Constraints – Restrictions, mainly in the form of multiplicities (data modeling, implemented as metadata statements), permissible data (type, range), and validation rules (in user interface). Program Code – Calculations and small programs (triggers) that produce some value. This lecture DBMS DBMS; much used in the past