1 / 26

INFO2005 Requirements Analysis Activity Diagrams

INFO2005 Requirements Analysis Activity Diagrams. Department of Information Systems. Learning Objectives. Identify the need for activity modelling UML notation for activity diagrams Examine the use of activity diagrams in the Rational Unified Process. Activity Modelling.

Download Presentation

INFO2005 Requirements Analysis Activity Diagrams

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. INFO2005Requirements AnalysisActivity Diagrams Department of Information Systems

  2. Learning Objectives • Identify the need for activity modelling • UML notation for activity diagrams • Examine the use of activity diagrams in the Rational Unified Process.

  3. Activity Modelling • Computer systems and the commercial / work environments in which they are used comprise may activities • business activities performed by people • activities performed with the information system by software • activities performed by machines under computer control

  4. Activity Modelling • Business processes are typically captured in use cases • Computer procedures are embodied in operations (analysis) and the methods (design and construction) that implement them. (Note that objects collaborate to realize a use case).

  5. Dynamic Modelling • Activity diagrams are one of the five modelling techniques in UML that capture the dynamics of the system • The others are

  6. Activity Diagrams • An activity diagram represents the a series of actions in sequence. • Activity diagrams are essentially flowcharts, rather similar in format to system flowcharts though used in a somewhat different way.

  7. Activity Diagram - notation Activity diagram for calculateBonus() operation Bennett, McRobb, Farmer 1999

  8. Notation • An action state is normally used to model a step in the execution of an algorithm or procedure • When an action state ends the next action state (depending upon guard conditions) executes.

  9. Notation • Transitions show the sequence of the actions. These transitions are completion transitions. • Guard conditions are used represent conditional paths of execution.

  10. Notation • A thread of execution with a guard condition is only executed if the condition is satisfied. • Decisions and guard conditions are used to show alternate threads.

  11. Activity Diagram - nested decisions Nested decisions can be used to represent complex conditions Bennett, McRobb, Farmer 1999

  12. Concurrent threads • Concurrent threads can be shown by using synchronization bars. • A synchronization bar shows the start (fork) or end (join) of a group of parallel subflows.

  13. Fill kettle with Find tea bag Find cup water Boil water in Place tea bag kettle in cup [milk required] Add water to Add milk cup [no milk required] Bennett, McRobb, Farmer 1999

  14. * Example: Enrolment • Prepare an activity diagram for student enrolment • Typical activities might be • Prepare registration documentation • Arrange enrolment session • Enrol student at the beginning of the academic year • Complete enrolment form • Send joining instructions to student

  15. Object flows • Object flows are used to show how objects involved in a workflow, procedure or algorithm. • An object may be the output of an activity and the input activities. • Object flow is a kind of control flow which it replaces. • The object flow symbol shows an object in a particular state.

  16. Swimlanes Object flow Note that the object changes state Bennett, McRobb, Farmer 1999

  17. Swimlanes • An activity diagram may be partitioned into swimlanes. • Each swimlanes represents a particular responsibility for some of the action states. • The responsibilities may be allocated to a person, a part of an organisation, or a set of classes.

  18. * Example: Enrolment • Redraw the activity diagram with swimlanes. • possible participants with responsibilities could be Registry, Faculty and Student.

  19. Registry Faculty Student *

  20. Where are activity diagrams used? • Activity diagrams can be used for a number of different purposes: • to model a human task • to describe a system function that is represented by a use case; • to describe the logic of an operation. Bennett, McRobb, Farmer 1999

  21. Activity diagram & BOM • Describes the ordering of activities or tasks that accomplish business goals. • Activity diagrams help

  22. Business Use Case Model • A business use case typically involves a workflow that produces some benefit for the business actor. • Activity diagrams are used to describe the structure of workflows

  23. Activity diagrams & Use Cases • The flow of events of a use case describes the sequence of activities that together produce the value for an actor. • An activity diagram can be used to describe the flow of events of a use case.

  24. Summary • Identify the need for activity modelling • UML notation for activity diagrams • Examine the use of activity diagrams in the Rational Unified Process

  25. References • Bennett, S. et. al. (2002)“Object-Oriented Systems Analysis & Design using UML” McGraw-Hill, Maidenhead. • OMG (1999) “Unified Modeling Language Specification,version 1.3” • Rational Unified Process 2000

More Related