Académique Documents
Professionnel Documents
Culture Documents
Unified Process
Basics
UML
Actors, Use cases
Example 1:
The system shall allow users to withdraw cash. [What?]
Example 2:
A sale item’s name and other attributes will be stored in a hash table
and updated each time any attribute changes. [How?]
Release:
Non-functional requirements
Performance
The blood pressure monitor will complete a
reading within 10 seconds.
Reliability
The blood pressure monitor must have a failure
probability of less than 0.01 during the first 500
readings.
Error conditions
State what happens in case of an error. How
should the implementation react in case of an
error condition?
Example:
R1.2: The speed of the vehicle will never exceed 250 mph.
R5.4: When the vehicle is cruising at a speed greater than 300 mph, a
special “watchdog” safety mechanism will be automatically
activated.
Book
______
title
print()
Player Die
_____
1 Rolls 2 ____
name facevalue
1 2
the requirements
1: r1:=roll()
:Player d1:Die
2: r2:= roll()
d2:Die
1 initialize() 1
Use
Case
View
Logical
View
Use
Case
View
Component Logical
View View
Use
Case
View
Component Logical
View View
Use
Case
View
Concurrency
View
Component Logical
View View
Use
Case
View
Deployment
View Concurrency
View
handle payments
Customer
participate in.
Method 2 - Event based
Identify the external events that a system must respond to
Relate the events to actors and use cases
Choosing actors:
Identify system boundary
Identify entities, human or otherwise, that will interact with the system, from outside the boundary.
Customer
Buy items
Return items
Handle payment
Payment
Authorization
Cashier Handle returns
service
Manage
System administrator <<actor>>
security
Accounting
Manage users
system
POST example:
Buy Items - High
Refund Items - Medium (Why?)
Shut Down POST terminal - Low
Type Primary
enterItem(itemID, quantity)
Description, total
makePayment(amount)
change due, receipt
cycle requirements
create initial conceptual model
Identify attributes
1
1
Store
Sale
Captured- address
date 1 name
time on
Attributes
1
Houses
1..*
1
Register
(POST)
….
deleting instances of things they describe (for
example, Item) results in a loss of information
that needs to be maintained.
it reduces redundant or duplicated information
Item
Serial Number
description
Price
itemID
comprehension-only associations
Records-current
POST Sale
1 1
Association
Other associations
A uses or manages or controls B (Pilot -airplane)
name
multiplicity expression
navigability
Records-current
POST Sale
1 1
Store
1
Contains
1..*
Records-current Paid-by
POST Sale payment
1 1 1 1
flies-from
0..1
*
Flight Airport
* 0..1
flies-to
Destination a
Complex concept
Flight
destination
UML notation -
Operation(arg:ArgType=defaultvalue,,,):ReturnType(s)
Postconditions:
A salesLineItem instance, sli, was created.
sli was associated with the current Sale.
sli.qty becomes quantity (attribute modification).
sli was associated with ProductSpecification based on
itemID match.