Interaction Models (2): Activity Diagrams

Slides:



Advertisements
Similar presentations
© 2005 by Prentice Hall Appendix 3 Object-Oriented Analysis and Design Modern Systems Analysis and Design Fourth Edition Jeffrey A. Hoffer Joey F. George.
Advertisements

Nested state diagrams:Problems with flat state diagram
UML State chart/machine diagram State machine diagram is a behavior diagram which shows discrete behavior of a part of designed system through finite state.
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.
UNIT 2. Introduction to Computer Programming
© 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
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.
SE 555 Software Requirements & Specification 1 Activity Diagrams.
L06-2-S1 Activity Diagrams 2003 SJSU -- CmpE Software Engineering II Dr. M.E. Fayad, Professor Computer Engineering Department, Room #283I College of Engineering.
Activity Diagrams. What is Activity Diagrams?  Activity diagrams are a technique to describe procedural logic, business process, and work flow.  An.
1999 – 2006 M.E. Fayad SJSU -- CmpE Software Engineering Management Dr. M.E. Fayad, Professor Computer Engineering Department, Room #283I College of Engineering.
Software Engineering Design & modelling
SE-565 Software System Requirements More UML Diagrams.
Game city International Starting on the road to programming. This project is all about learning how to program using scratch and other languages. The aim.
Software Design Processes and Management
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.
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.
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.
February 20, 2012  Present Fayad KSU – SWE Process and Modeling Software Process and Modeling Dr. M.E. Fayad, Professor Software Engineering Department,
11 Software Engineering Dr. K. T. Tsang Lecture 6 Interaction 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, 2004 Chapter 9: Analysis Classes Object-Oriented Systems Analysis and Design Joey F. George, Dinesh Batra, Joseph S. Valacich, Jeffrey.
Information System Design IT60105
© 2007 Pearson Education, Inc. Publishing as Pearson Addison-Wesley 1 UML Activity Diagrams.
UNIFIED MODELING LANGUAGE(UML) BY Touseef Tahir Lecturer CS COMSATS Institute of Information Technology, Lahore.
Chapter 11 Activity Diagrams. 2 “Activity diagrams are a technique to describe procedural logic, business processes, and work flows” - M. Fowler An activity.
Object Oriented Analysis & Design & UML (Unified Modeling Language)1 Part VI: Design Continuous Activity Diagams State Diagrams.
CS212: Object Oriented Analysis and Design Lecture 34: UML Activity and Collaboration diagram.
UML: The Unified Modeling Language Excertos do livro: The Unified Modelling Language User Guide by Grady Booch, James Rumbaugh and Ivar Jacobson.
UML Activity Diagrams.
University of Southern California Center for Systems and Software Engineering 9/20/2010© USC-CSSE Activity Diagrams for Business Workflows and.
 Activity diagram is basically a flow chart to represent the flow from one activity to another activity.
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.
Activity Diagrams. Notation Activity1()cActivity2() 1. Activities 2. Transition.
© 2007 Pearson Education, Inc. Publishing as Pearson Addison-Wesley 1 UML Activity Diagrams.
© 2007 Pearson Education, Inc. Publishing as Pearson Addison-Wesley 1 Advanced UML State Diagrams.
Activity Diagram.
Business Process and Functional Modeling
UML Chapter 17.
Chapter 3 DOCUMENTING ACCOUNTING SYSTEMS
Analysis Classes Unit 5.
ACTIVITY DIAGRAMS 《UML面向对象建模基础》.
Activity Diagrams.
Information Delivery Manuals: Process Mapping
Unified Modeling Language
Activity Diagram.
Activity and State Transition Diagram
Visit for more Learning Resources
State Machine Diagrams
Activity Diagrams Activity diagrams describe the workflow behavior of a system.  The diagrams describe the state of activities by showing the sequence.
Activity Diagrams.
Business System Development
UML Activity Diagrams.
Process Modeling: Activity/Swimlane Diagrams
States.
Software System Engineering
Activity Diagrams.
Sequence Diagrams Getting the Message.
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.
States.
Activity Diagrams for Business Workflows and Scenarios
Appendix 3 Object-Oriented Analysis and Design
Object-Oriented Analysis & Design
Presentation transcript:

Interaction Models (2): Activity Diagrams

An activity diagram shows the sequence of steps that make up a complex process such an algorithm or a workflow. An activity diagram shows flow of control. It is like a traditional flowchart in that it shows the flow of control fro step to step. However, unlike a traditional flowchart, activity diagrams can show both sequential and concurrent flow of control. Activity diagrams are most useful during the early stages of designing algorithms and workflows.

Activity (1) The steps of an activity diagrams are operations, specifically activities from the state model. The purpose of an activity diagram is to show the steps within a complex activity and the sequencing constraints among them. Some activities run forever until an outside event interrupt them. But most activities eventually complete their work and terminate by themselves. The completion of an activity indicates that the next activity can be star ted

Activity (2) An activity may be decomposed into finer activities. It is important that the activities on an activity diagram be at the same level of details (level of abstraction).

Branches (1) If there is more than one successor to an activity, ach arrow ay be modeled with a condition in square brackets, for example: [failure] All subsequent conditions are tested when an activity completes: If one condition is satisfied its arrow indicates the next activity to perform. If no condition is satisfied, the diagram is badly formed and the system will hang unless it is interrupted at some higher level If multiple conditions are satisfied , only one successor executes but no guarantee which one it will be.

Branches (2) A diamond shows a branch into multiple successors but it means the same thing as arrows leaving an activity symbol directly: One incoming arrows, two or more outgoing arrows :Decision node Several incoming arrows, one outgoing arrow: Merge node

Initiation/Termination A solid circle with an outgoing arrow shows the starting point of an activity diagram. When an activity diagram is activated , control starts at the solid circle and proceeds via the outgoing arrow towards the first activity. Termination: A solid circle surrounded by a hallow circle shows the termination point. It only has incoming arrows. When control reaches this symbol, the overall activity is complete and execution of the activity diagrams ends.

Concurrent Activities Organizations and computer systems can perform more than one activity at the same time. Example: one activity may be followed by another activity then split into several concurrent activities (a fork of control), and finally be combined into a single activity (a merge control) A fork or merge is shown by a synchronization bar: On a synchronization, control must be present on all the incoming activities, and control passes to all of the outgoing activities.