Nothing going on here, move along…

Posts tagged ‘Use case relationships’

Models and diagrams

RUP – Rational Unified Process


Analysis, design and implementation


Waterfall, semistructured, structured, RAD, BOEHMS spiral, incremental and iterative (this is a real model not a prototype.)

Phases for UML/RUP

Inceptions – Identity

Elaboration – Design

Construction – Build

Transaction – Roll out

Diagrams and their contents

Use case diagram – ID system boundry, fuctions and events, how the user sees the system,not behind the scenes

Activity diagram – Use case diagram details

Sequence diagram – Use case timing

Class diagram – Developed from the use case

State transition diagram – Models the behaviours of subsystems


These are users which affect the system eg. In a bank system there would be a ‘banker’ actor and a ‘customer’ actor.

In diagrams actorsare shown as stick figures

Primary elements are actors processes are use cases.

Titles are used but not names

Use cases

A use case diagram is a visual representation of a distinct business functionality

Each business fuction can be classified as a use case but some may be sub cases

A use case is represented by an oval

The system boundry is an oblong that surrounds the use cases but not the actors

Each use case has a limit defined by the boundry

Use cases share different kinds of relationships:

Association – communicates a relationship. Shown with a line __________

Include – Used to indicate a use case needs another use case to work. Shown with a broken line arrow and <<include>> sign on the line ———>. Goes from child to parent

Extend – The child case add to the functionality of the parent case the same as the include funtion, this functio is not always needed to complete a transaction, has <<extend>> sign instead of include

Genralizations – Inheritance of an object in UML, an enhancement of the parent case. Uses a closed arrowhead with an unbroken line     |>

Tag Cloud