Activity Diagrams.

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.
Solutions to Review Questions
© 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
Activity Diagrams [Arlow and Neustadt, 2005] CS 425 / 625 Seminar on Software Engineering University of Nevada, Reno Department of Computer Science & Engineering.
UML Activity Diagrams In UML an activity diagram is used to display the sequence of actions They show the workflow from start to finish Detail the many.
SE 555 Software Requirements & Specification 1 Activity Diagrams.
THE OBJECT-ORIENTED DESIGN WORKFLOW Activity Diagrams.
Ch5: Software Specification. 1 Dynamic modeling using UML  Static models:  Dynamic models:
1 CS 426 Senior Projects Chapter 14: Activity Diagrams [Arlow and Neustadt, 2005] February 17, 2009.
03/12/2001 © Bennett, McRobb and Farmer Activity Diagrams Based on Chapter 5 of Bennett, McRobb and Farmer: Object Oriented Systems Analysis and.
Activity Diagrams. What is Activity Diagrams?  Activity diagrams are a technique to describe procedural logic, business process, and work flow.  An.
Requirements Analysis Activity Diagrams b511.ppt © Copyright De Montfort University 2000 All Rights Reserved INFO2005 Requirements Analysis.
UML Activity Diagram. Activity Diagram  The main reason to use activity diagrams is to model the workflow behind the system being designed.  Activity.
COMP1007 Intro to Requirements Analysis © Copyright De Montfort University 2002 All Rights Reserved COMP1007 Introduction to Requirements Analysis Lecture.
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.
Object-Oriented Software Engineering Practical Software Development using UML and Java Chapter 8: Modelling Interactions and Behaviour.
UML A CTIVITY D IAGRAMS 1 Dr. Hoang Huu Hanh, OST – Hue University hanh-at-hueuni.edu.vn.
© 2005 course technology1 1 1 University Of Palestine UML for The IT Business Analyst A practical guide to Object Oriented Requirement Gathering Hoard.
SOFTWARE DESIGN AND ARCHITECTURE LECTURE 21. Review ANALYSIS PHASE (OBJECT ORIENTED DESIGN) Functional Modeling – Use case Diagram Description.
Interaction Models (2): Sequence Diagrams Extracted from textbook: Object Oriented Modeling and Design with UML M. Blaha, J. Rumbaugh 1.
1 Devon M. Simmonds University of North Carolina, Wilmington CSC450 Software Engineering WorkFlow Modeling with Activity Diagrams.
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, 2007 Chapter 9: Analysis Classes Object-Oriented Systems Analysis and Design Joey F. George, Dinesh Batra, Joseph S. Valacich, Jeffrey.
© 2007 Pearson Education, Inc. Publishing as Pearson Addison-Wesley 1 UML Activity Diagrams.
Chapter 11 Activity Diagrams. 2 “Activity diagrams are a technique to describe procedural logic, business processes, and work flows” - M. Fowler An activity.
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
Activity diagrams M Taimoor Khan
Chapter 14: Activity Diagrams November 2015 [Arlow and Neustadt, 2005] CS 425/625 Senior Projects University of Nevada, Reno Department of Computer Science.
7-1 © Prentice Hall, 2007 Topic 7: Analysis Classes Object-Oriented Systems Analysis and Design Joey F. George, Dinesh Batra, Joseph S. Valacich, Jeffrey.
UML Activity Diagrams.
Chapter 3: Introducing the UML
University of Southern California Center for Systems and Software Engineering 9/20/2010© USC-CSSE Activity Diagrams for Business Workflows and.
Interaction Models (2): Activity Diagrams Extracted from textbook: Object Oriented Modeling and Design with UML M. Blaha, J. Rumbaugh.
Activity Diagrams IST 420 Dr. Ocker. BPM With Activity Diagrams Business processes consist of a number of activities Activity diagrams depict the sequence.
© 2007 Pearson Education, Inc. Publishing as Pearson Addison-Wesley 1 UML Activity Diagrams.
Elaboration: Iteration 3. Elaboration: Iteration 3 Basics Inception and iteration-1 explored many basic OOA/D modeling basics. Iteration-2 narrowly emphasized.
Business Process and Functional Modeling
Chapter 3 DOCUMENTING ACCOUNTING SYSTEMS
Analysis Classes Unit 5.
Activity Diagrams.
Chapter 4: Business Process and Functional Modeling, continued
ACTIVITY DIAGRAMS Pertemuan 20
Activity Diagram.
Activity and State Transition Diagram
Activity Diagram.
Visit for more Learning Resources
Chapter 8: Modelling Interactions and Behaviour UML Activity Diagram
Business System Development
UML Activity Diagrams.
Software Engineering Chapter 5 (Part 3) System Modeling Dr.Doaa Sami.
UML Activity Diagrams & State Charts
Process Modeling: Activity/Swimlane Diagrams
Week 12: Activity & Sequence Diagrams
Chapter 14: Activity Diagrams
Object-Oriented Analysis and Design: Activity Diagrams
Activity Diagrams.
Activity diagram It supports visual representation of sequences of actions that target a certain result. May be built for one or many use cases or for.
Chapter 14: Activity Diagrams
Chapter 14: Activity Diagrams
Activity Diagrams for Business Workflows and Scenarios
Appendix 3 Object-Oriented Analysis and Design
Object-Oriented Analysis & Design
Interaction Models (2): Activity Diagrams
Object-Oriented Analysis and Design: Activity Diagrams
Presentation transcript:

Activity Diagrams

Notation

Elements (Activity without partitions) Initial node: Indicates where the workflow begins. Control flow: An arrow showing the direction of the workflow. Activity: Indicates a step in the process. Decision: A diamond symbol, indicating a choice. Workflow will proceed along one of a number of possible paths, according to the guard conditions. Merge: Use this symbol if you wish to adhere to strictly to the UML standard when modeling a number of alternative flows that lead to the same activity. Rather than terminating them at the same activity, terminate them at a merge, and draw a flow from the merge to the activity.

Fork and join: Bars used to document parallel activities Fork and join: Bars used to document parallel activities. In the UML, parallel activities are those that may begin in any sequence—either at the same time or one before the other. A fork indicates the point after which a number of activities may begin in any order. A join indicates that workflow may commence only once the parallel activities that flow into it have all been completed. Final node: Indicates the end of the process.

A control flow labeled with an event

Activities nested within an activity symbol.

Activity Diagram with Partitions (Swimlanes) The elements in an activity diagram can be grouped by using partitions. The purpose of a partition is to indicate where the responsibility lies for performing specific activities. In a business model, the partitions may be business units, divisions, or organizations. For systems, the partitions may be other systems or subsystems. In application modeling, the partitions may be objects in the application. Each partition may be named to indicate the responsible party. To indicate who performs each activity, you add partitions (commonly referred to as swimlanes) to the activity diagram. A partition is depicted as a column (or row) on an activity diagram. Allocate one partition for each object that takes an active part in the process flow. Each partition represents a stakeholder (business actor or worker) who carries out some activity. Although you shouldn’t spend too much time focusing on technology at this time, you may also show a computer system as a partition.