Asper School of Business University of Manitoba Systems Analysis & Design Instructor: Bob Travica Analyzing systems process: Activity diagram Updated 2014.

Slides:



Advertisements
Similar presentations
Class 4 Process Diagramming MIS 2000 Information Systems for Management Instructor: Bob Travica Updated September 2012.
Advertisements

Data Flow Diagram (DFD) Review
Describing Process Specifications and Structured Decisions Systems Analysis and Design, 7e Kendall & Kendall 9 © 2008 Pearson Prentice Hall.
Activity Diagrams in UML. Definition Activity diagrams represent the dynamics of the system. They are flow charts that are used to show the workflow of.
© 2006 ITT Educational Services Inc. SE350 System Analysis for Software Engineers: Unit 9 Slide 1 Appendix 3 Object-Oriented Analysis and Design.
Class 8 Process Analysis & Diagramming MIS 2000 Information Systems for Management Instructor: Bob Travica Updated Jan
Extending the Requirements Model - techniques for detailing use cases
Information System Engineering
Interaction Diagrams Activity Diagram State Machine Diagram
Asper School of Business University of Manitoba Systems Analysis & Design Instructor: Bob Travica Analyzing system processes: Use Case Diagram Updated.
Systems development life cycle & development methodologies
Summary Class responsibility cards can be used to help allocate responsibilities between different classes. The use of stereotype classes, such as entity,
Asper School of Business University of Manitoba Systems Analysis & Design Instructor: Bob Travica Analyzing systems process: Use Case Diagram.
9-1 Chapter 9 (part I): Analysis Classes (Adapted) Object-Oriented Systems Analysis and Design Joey F. George, Dinesh Batra, Joseph S. Valacich, Jeffrey.
Asper School of Business University of Manitoba Systems Analysis & Design Instructor: Bob Travica Use Case description Updated: October 2014.
Fundamental System Concepts Asper School of Business University of Manitoba Systems Analysis & Design Instructor: Bob Travica Updated: September 2014.
Asper School of Business University of Manitoba Systems Analysis & Design Instructor: Bob Travica System sequence diagram Updated: 2014.
Activity Diagrams. What is Activity Diagrams?  Activity diagrams are a technique to describe procedural logic, business process, and work flow.  An.
Visual Basic Introduction IDS 306 from Shelly, Cashman & Repede Microsoft Visual Basic 5: Complete Concepts and Techniques.
Modeling the Processes and Logic
SE-565 Software System Requirements More UML Diagrams.
Asper School of Business University of Manitoba Systems Analysis & Design Instructor: Bob Travica System implementation and deployment Updated: November.
Karolina Muszyńska Based on: S. Wrycza, B. Marcinkowski, K. Wyrzykowski „Język UML 2.0 w modelowaniu SI”
Software Engineering EKT 420. What is Activity Diagram Activity diagrams are graphical representations of workflows of stepwise activities and actions.
Interaction Modeling. Sequence Models  There are two kinds of sequence models: scenarios and sequence diagrams  A scenario is a sequence of events that.
Network Modeling - Not Just For Computer Networks  Computer Networks  The need for network modeling is being driven by a technical trend – distributed.
Chapter 7 Structuring System Process Requirements
1 Object-Oriented Modeling Using UML (2) CS 3331 Fall 2009.
Describing Process Specifications and Structured Decisions Systems Analysis and Design, 7e Kendall & Kendall 9 © 2008 Pearson Prentice Hall.
SOFTWARE DESIGN AND ARCHITECTURE LECTURE 20. Review Software Requirements Requirements Engineering Process.
Interaction Models (2): Sequence Diagrams Extracted from textbook: Object Oriented Modeling and Design with UML M. Blaha, J. Rumbaugh 1.
Use Case Driven Analysis Requirements Use Case Use Case Description System Sequence Diagram Chapter 5.
Lecture 4 :Use cases III (UC description) 1. Outline CT 1414 * Nouf Aljaffan2  Concept of Use Case Description  Levels of Use Case Description  Reading.
1 Graph Coverage (6). Reading Assignment P. Ammann and J. Offutt “Introduction to Software Testing” ◦ Section
CS212: Object Oriented Analysis and Design Lecture 34: UML Activity and Collaboration diagram.
The College Of Applied Studies And Community Services Lecture 3 :Use cases II (UC description) Systems Analysis & Design Instructor: Nouf Aljaffan CT 1414.
A Student Guide to Object-Oriented Development
Information Systems Engineering Activity Diagram 1.
Copyright © 2011 Pearson Education, Inc. Publishing as Prentice Hall Object-Oriented Systems Analysis and Design Using UML Systems Analysis and Design,
7-1 © Prentice Hall, 2007 Topic 7: Analysis Classes Object-Oriented Systems Analysis and Design Joey F. George, Dinesh Batra, Joseph S. Valacich, Jeffrey.
Systems Design.  Application Design  User Interface Design  Database Design.
Use Case Model Use case description.
Asper School of Business University of Manitoba Systems Analysis & Design Instructor: Bob Travica User interface II Updated: November 2014.
Activity Diagramming by Andrzej Rosolski Stanisław Gliniewicz.
Interaction Models (2): Activity Diagrams Extracted from textbook: Object Oriented Modeling and Design with UML M. Blaha, J. Rumbaugh.
Interstage BPM v11.2 1Copyright © 2010 FUJITSU LIMITED CREATING A SIMPLE PROCESS.
6 Class 6 Organization in Process View MIS 2000 Information Systems for Management Bob Travica Updated Jan
McGraw-Hill/Irwin Copyright © 2006 by The McGraw-Hill Companies, Inc. All rights reserved. Chapter 5 Modeling the Processes and Logic.
Systems Analysis and Design in a Changing World, Fourth Edition
Asper School of Business University of Manitoba Systems Analysis & Design Instructor: Bob Travica Analyzing system processes: Use Case Diagram Updated.
Systems Analysis and Design in a Changing World, Fourth Edition
Analysis Classes Unit 5.
Analyzing system processes: Use Case Diagram 2/2
Activity and State Transition Diagram
Data Flow Diagram (DFD) Review
Activity Diagrams.
Analyzing systems process: Activity Diagram
Use Case Modeling - techniques for detailing use cases
Process Modeling: Activity/Swimlane Diagrams
Process Step (Activity)
Week 12: Activity & Sequence Diagrams
Object Oriented Analysis and Design
Activity Diagrams.
Structure Charts Agenda: What are Structure Charts
SYSTEM ANALYSIS & DESIGN PHASE
Requirement Analysis using
Process Modeling System Analysis & Design Course
Information Systems Engineering
Analyzing systems process: Activity diagram
Structure Charts.
Presentation transcript:

Asper School of Business University of Manitoba Systems Analysis & Design Instructor: Bob Travica Analyzing systems process: Activity diagram Updated 2014

3510 Systems Analysis & Design * Bob Travica2 of 12 Outline Activity diagram concept Elements of activity diagram Reading activity diagrams Process logic in activity diagram Creating activity diagrams

3510 Systems Analysis & Design * Bob Travica3 of 12 Activity Diagram (AD) concept A diagram used for showing systems requirements; results from process analysis AD depicts: business processes (workflow) – manual & automated (carried by a system) process logic – time order of process steps (activities) & decision points actors (touch system), business event sources (initiate actors to work) AD resembles old flow charts and data flow diagram

3510 Systems Analysis & Design * Bob Travica4 of 12 AD components – Quote Process Who/What performs activity Swimlane (column) Activity, Process step Decision point; yes/no branching Process flow (control) Start End Loop, one technique: decision + flow back Time approxi- mation Page 146 * * System=information system; sometimes called just “computer”

3510 Systems Analysis & Design * Bob Travica5 of 12 AD components – Parallel Steps Parallel steps, run at the same time Provide Technical Details Synchronization Bars, indicate parallel processes

3510 Systems Analysis & Design * Bob Travica6 of 12 AD for Customer Ordering by Telephone – more components Loop -One method -Note: 1. loop bars 2. enter & exit condition Page 227 (bit modified) Decision shown as Activity: - N outflows - Outflows named Pasting activities to save space

3510 Systems Analysis & Design * Bob Travica7 of 12 Process logic Sequential (step 1, step 2, step 3…) Conditional: If-Then (decision points: if condition A, then step n); binary or N-ary choices as outflows Iteration/loop: Control back to a previous step while a certain condition persists) Slide 4, feedback from the “Change required?” decision point Slide 6, loop between bars For each item to End of each

3510 Systems Analysis & Design * Bob Travica8 of 12 What AD does not show? Data passed between steps (Data flow diagram shows it) Objects (But can be inferred; e.g., Customer, Order, Clerk) User interface (Clerk--System connection)

3510 Systems Analysis & Design * Bob Travica9 of 12 How to create AD 1. Identify activities (steps) of a process 2. Identify who/what performs activities (process steps) 3. Draw swimlanes 4. Identify decision points (if-then) 5. Determine if a step is in loop (For each…, or if-then loop) 6. Determine if step is parallel with some other 7. Identify order of activities, decision points Continues…

3510 Systems Analysis & Design * Bob Travica10 of 12 How to create AD (cont.) 8. Draw the start point of the process in the swimlane of the first activity (step) 9. Draw the oval of the first activity (step) 10. Draw an arrow to the location of the second step 11. Draw subsequent steps, while inserting decision points and synchronization/loop bars where appropriate 12. Draw the end point after the last step. You can tabulate these data (see next slide).

3510 Systems Analysis & Design * Bob Travica11 of 12 How to create AD (cont.) Step ID Process Activity or Decision Who/What Performs Parallel Activity LoopPreceding Step 1Request quoteCustomerNo - 2Develop requirement notes SalespersonNoYes1 3Decision: Help?Salesperson-Yes2 4Salesperson enters data SalespersonNoYes3 5Check requirements Technical Expert NoYes3 6Tech. expert enters data Technical Expert NoYes5 7Calculate quoteSystemNoYes4, 6 8Review quoteCustomerNoYes7 9Decision: Changes? CustomerNoYes8 10Accept quote as order CustomerNo