05a - UML Diagrams Part 1

7/23/2019 05a - UML Diagrams Part 1

1/36

UML Diagrams Part I

Systems Analysis and Design

IFSY361

Summer School 2015

Reymon Rotikan


2/36

Outline

Use Case Diagram

Activity Diagram


3/36

Use Case Diagram

A use case is a case (or situation) where your system is used to fulf

more of your users requirements; a use case captures a piece of fu

that the system provides.


4/36

Use Case Diagram contd)

Actors

External thingsthat interact with the system.

Use an actor name that can be understood by both the customer a

analyst.


5/36


Use Case

Cases where the system is being used to complete a specific job fo


6/36


Communication Lines

Connects an actor and a use case to show the actor participating in

case.


7/36


System Boundaries

Implicit separation between actors (external of the system) and us

(internal to the system).

System Name


8/36


Use Case Descriptions

Text-based description of the use case (each use case should have)

No standardize format to create the description


9/36


Use Case Descriptions

Figure source: Russ Miles, Kim Hamilton. Learning UML 2.0: A Pragmatic Introduction to UML. 2006. OReilly.


10/36


Use Case Relationships

reuse all the steps from the use case being included


11/36


Use Case Relationships

opt on lly reused of a use case

Figure source: Russ Miles, Kim Hamilton. Learning UML 2.0: A Pragmatic Introduction to UML. 2006. OReilly.


12/36

Example


13/36

Example

Content Management Syste

Requirement A 1

The content management system shall allow an administrator to c

blog account, provided the personal details of the new blogger are ve

the Author Credentials Database.


14/36

Figure source:Russ Miles, Kim Hamilton. Learning UML 2.0: A Pragmatic Introduction to UML. 2006. OReilly.


15/36



16/36



17/36



18/36

Example Content Management Syste

contd)

Requirement A 2

The content management system shall allow an administrator to c

personal Wiki, provided the personal details of the applying author

using the Author Credentials Database.


19/36



20/36

Figure source:

Russ Miles, Kim Hamilton. Learning UML 2.0:

A Pragmatic Introduction to UML. 2006. OReilly.


21/36



22/36



23/36



24/36

Exercise


25/36

Activity Diagram

Specify how the system will accomplish its goals. Activity diagram

high-level actions chained together to represent a process occurri

system.

Notations: initial node, final node, edge, action, decision, merge.


26/36

Figure source:

Russ Miles, Kim Hamilton. Learning UML 2.0: A Pragmatic Introduction

to UML. 2006. OReilly.


27/36

Activity Diagram contd)

Activities and Actions

Activity = the process being modeled, e.g., washing a car

Action = step in the overall activity, e.g., lather, rinse, and dry.


28/36


Activities and Actions



29/36


Decisions



30/36


Merged



31/36


Join and Fork

Present parallel actions in activity diagrams.



32/36



33/36

Exercise


34/36

Any questio


35/36

References

Russ Miles, Kim Hamilton. Learning UML 2.0: A Pragmatic Introdu

UML. 2006. OReilly.


36/36

See u next class

Documents

05a - UML Diagrams Part 1