Activity Diagram.

Slides:



Advertisements
Similar presentations
OOAD – Dr. A. Alghamdi Mastering Object-Oriented Analysis and Design with UML Module 3: Requirements Overview Module 3 - Requirements Overview.
Advertisements

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.
Software Design Process A Process is a set of related and (sequenced) tasks that transforms a set of input to a set of output. Inputs Outputs Design Process.
Information System Design IT60105
® IBM Software Group © 2006 IBM Corporation Rational Software France Object-Oriented Analysis and Design with UML2 and Rational Software Modeler 04. Other.
7M701 1 Activity Diagram. 7M701 2 Example 7M701 3 Activity Diagram: what is it? Describes activities and flows of data or decisions between activities.
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.
Introduction to UML Part 2 Behavioral Modeling. Sequence (event) diagram Describes object interaction Typically captures behavior of a single use case.
THE OBJECT-ORIENTED DESIGN WORKFLOW Activity Diagrams.
Ch5: Software Specification. 1 Dynamic modeling using UML  Static models:  Dynamic models:
1 CS 501 Spring 2005 CS 501: Software Engineering Lecture 8 Requirements II.
1 CS 691z/791z Topics in Software Engineering Chapter 13: Activity Diagrams & Chapter 19: Basic Statecharts [Arlow and Neustadt, 2002] March 8, 2007.
L06-2-S1 Activity Diagrams 2003 SJSU -- CmpE Software Engineering II Dr. M.E. Fayad, Professor Computer Engineering Department, Room #283I College of Engineering.
7M822 UML Activity Diagrams 6 October 2008.
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.
Activity Diagrams Derived from several techniques: Event diagrams of Jim Odell SDL state modeling techniques Workflow modeling Petri nets Especially useful.
IS550: Software requirements engineering Dr. Azeddine Chikh 4. Validation and management.
Use Case Diagrams. Use Case Use case A view to system seen from outside(user) User’s requirements on system A set of scenario for an actor to achieve.
COMP1007 Intro to Requirements Analysis © Copyright De Montfort University 2002 All Rights Reserved COMP1007 Introduction to Requirements Analysis Lecture.
SE-565 Software System Requirements More UML Diagrams.
1 Business Models Modeling. 2 Why Model the Business Business modeling is a technique to help answer critical questions, such as: What do the workers.
Software Design Processes and Management
Financial Information Management Managing Financial Information Critical Thinking Business Process Modeling WINIT Control Structures Homework.
Software Engineering EKT 420. What is Activity Diagram Activity diagrams are graphical representations of workflows of stepwise activities and actions.
Free Mini Course: Applying SysML with MagicDraw
Object-Oriented Software Engineering Practical Software Development using UML and Java Chapter 8: Modelling Interactions and Behaviour.
Use Case Diagrams. Use cases modeling Overview Motivation Communication between developers and users Users don’t know system, developers don’t know users’
SOFTWARE DESIGN AND ARCHITECTURE LECTURE 21. Review ANALYSIS PHASE (OBJECT ORIENTED DESIGN) Functional Modeling – Use case Diagram Description.
Prepared by Afra`a Sayah. Introduction. Weekly Tasks. Plane Phase. Analysis Phase. Design Phase. Report Rules. Conclusion. 2.
Functional Modeling Question How do you know if you have enough information to compute the necessary output values? How do you know if you have.
Chapter 4 – Requirements Engineering Lecture 3 1Chapter 4 Requirements engineering.
Requirements Artifacts Precursor to A & D. Objectives: Requirements Overview  Understand the basic Requirements concepts and how they affect Analysis.
© 2001 Business & Information Systems 2/e1 Chapter 8 Personal Productivity and Problem Solving.
Lead Black Slide Powered by DeSiaMore1. 2 Chapter 8 Personal Productivity and Problem Solving.
Activity diagrams. Introduction ● Activity diagrams are a behavioural model that represent the dynamics of the system. ● An activity diagram is essentially.
© 2008 Prentice Hall, Ovidiu Noran Lecture 7b 1 Modelling OO Logic Requirements: Sequence Diagrams and Activity Diagrams (Textbook Chapter 8, Appendix)
12/2/2015 2:45 AM 1 PROJECT TIME PLANNING Process and Bar Chart Technique.
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.
State Modeling. Events An event is an occurrence at a point in time, such as user depresses left button or.
Information Systems Engineering Activity Diagram 1.
University of Southern California Center for Systems and Software Engineering 9/20/2010© USC-CSSE Activity Diagrams for Business Workflows and.
1 Activity Diagram. Activity Diagrams 1.Activity diagrams are the object-oriented equivalent of flow charts and data-flow diagrams from structured development.
Activity Diagramming by Andrzej Rosolski Stanisław Gliniewicz.
Activity Diagrams IST 420 Dr. Ocker. BPM With Activity Diagrams Business processes consist of a number of activities Activity diagrams depict the sequence.
Software Engineering: Models David Millard
Business Process and Functional Modeling
UML Chapter 17.
Identifying & Creating Use Cases – Part 2
ACTIVITY DIAGRAMS 《UML面向对象建模基础》.
Activity Diagrams.
Chapter 1 Introduction to Computerized Medical Office Procedures
Chapter 4: Business Process and Functional Modeling, continued
Unified Modeling Language
Business Models Modeling.
Activity and State Transition Diagram
Activity Diagram.
Software Engineering Chapter 5 (Part 3) System Modeling Dr.Doaa Sami.
Activity Diagrams.
UML Activity Diagrams.
Software Engineering Chapter 5 (Part 3) System Modeling Dr.Doaa Sami.
Object Oriented Analysis and Design
Software Engineering Chapter 5 (Part 3) System Modeling Dr.Doaa Sami.
Process Modeling: Activity/Swimlane Diagrams
Week 12: Activity & Sequence Diagrams
Activity Diagrams for Business Workflows and Scenarios
Information Systems Engineering
Presentation transcript:

Activity Diagram

UML : ACTIVITY DIAGRAM Activity diagrams are the object-oriented equivalent of flow charts and data-flow diagrams from structured development Activity diagrams describe the workflow behavior of a system The process flows in the system are captured in the activity diagram

UML : ACTIVITY DIAGRAM When to Use Activity Diagrams ? to explore the logic of a complex operation a single use case several use cases a business process software processes Useful for showing workflow and parallel rocessing

UML : ACTIVITY DIAGRAM Elements of activity diagram

UML : ACTIVITY DIAGRAM Elements of activity diagram

UML : ACTIVITY DIAGRAM Example : creating document Open the word processing package Create a file Save the file under a unique name within its directory Type the document If graphics are necessary, open the graphics package, create the graphics, and paste the graphics into the document If a spreadsheet is necessary, open the spreadsheet package, create the spreadsheet, and paste the spreadsheet into the document Save the file Print a hard copy of the document Exit the word processing package

UML : ACTIVITY DIAGRAM

UML : ACTIVITY DIAGRAM Example 2: processing an order Once the order is received the activities split into two parallel sets of activities One side fills and sends the order while the other handles the billing On the Fill Order side, the method of delivery is decided conditionally Depending on the condition either the Overnight Delivery activity or the Regular Delivery activity is performed Finally the parallel activities combine to close the order

UML : ACTIVITY DIAGRAM

UML : ACTIVITY DIAGRAM Guards A guard is a condition that must be true in order to traverse a transition Each Transition Leaving a Decision Point Must Have a Guard This ensures that you have thought through all possibilities for that decision point Guards Should Not Overlap For example guards such as x <0, x = 0, and x >0 are consistent whereas guard such as x<=0 and x >=0 are not consistent because they overlap – it isn’t clear what should happen when x is 0 Guards on Decision Points Must Form a Complete Set For example, guards such as x < 0 and x >0 are not complete because it isn’t clear what happens when x is 0 Apply a [Otherwise] Guard for “Fall Through” Logic.

UML : ACTIVITY DIAGRAM Parallel Activities guidelines It is possible to show that activities can occur in parallel, the fork, it has one transition entering it and two or more transitions leaving it The other bar is a join, with two or more transitions entering it and only one leaving it A Fork Should Have a Corresponding Join In general, for every start (fork) there is an end (join) In UML ) it is not required to have a join, but it usually makes sense Forks Have One Entry Transition Joins Have One Exit Transition Avoid Superfluous Forks

UML : ACTIVITY DIAGRAM Swimlane Guidelines A swimlane is a way To group activities Performed by the Same actor on an Activity diagram or to group activities in a single thread

UML : ACTIVITY DIAGRAM Swimlane Guidelines Order Swimlanes in a Logical Manner Apply SwimLanes To Linear (sequential) Have Less Than Five Swimlanes Consider Swimareas For Complex Diagrams SwimLane Suggest The Need to Reorganize Into Smaller Activity Diagrams Consider Horizontal Swimlanes for Business Processes Left to right

UML : ACTIVITY DIAGRAM Example 0: business process of meeting a new client A salesperson calls the client and sets up an appointment If the appointment is onsite (in the consulting firm's office), corporate technicians prepare conference room for a presentation If the appointment is offsite (at the client's office), a consultant prepares a presentation on a laptop The consultant and the salesperson meet with the client at the agreed-upon location and time The salesperson follows up with a letter If the meeting has resulted in a statement of a problem, the consultant create a proposal and sends it to the client

UML : ACTIVITY DIAGRAM

UML : ACTIVITY DIAGRAM

UML : ACTIVITY DIAGRAM Homework Draw an activity diagram for the following problem: Appointment system for doctor office A patient came to office, the scheduler get patient info If the patient is new the scheduler make new patient record The scheduler display list of possible appointments to patient Patient choose new appointments , modify appointments or cancel his appointments Patient make payment

UML : ACTIVITY DIAGRAM References: Systems Analysis & Design with UML, )2nd Edition Elements of UML )E style Software Engineering - Sams - Teach Yourself Uml In 24 Hours