Figure 4-1, Products of requirements elicitation and
analysis.
problem
statement
Requirements
elicitation
Requirements
Specification
nonfunctional
requirements
functional
model
Analysis
Analysis Model
dynamic model
analysis object
model
Bernd Bruegge & Allen H. Dutoit
Object-Oriented Software Engineering: Using UML, Patterns, and Java
1
Figure 4-4, Actors for the SatWatch system.
WatchOwner moves the watch (possibly across time
zones) and consults it to know what time it is.
SatWatch interacts with GPS to compute its position.
WebifyWatch upgrades the data contained in the
watch to reflect changes in time policy (e.g., changes
in daylight savings time start and end dates).
GPS
WatchOwner
SatWatch
WebifyWatch
Bernd Bruegge & Allen H. Dutoit
Object-Oriented Software Engineering: Using UML, Patterns, and Java
2
Figure 4-5, Actors of the FRIEND system.
FieldOfficers not only have access to different
functionality, they use different computers to access
the system.
FieldOfficer
Bernd Bruegge & Allen H. Dutoit
FRIEND
Dispatcher
Object-Oriented Software Engineering: Using UML, Patterns, and Java
3
Figure 4-11, Example of communication relationships
among actors and use cases in FRIEND.
<<initiate>>
FieldOfficer
Dispatcher
ReportEmergency
Bernd Bruegge & Allen H. Dutoit
OpenIncident
AllocateResources
Object-Oriented Software Engineering: Using UML, Patterns, and Java
4
Figure 4-12, Example of use of extend relationship.
ConnectionDown
FieldOfficer
ReportEmergency
Bernd Bruegge & Allen H. Dutoit
<<extend>>
Object-Oriented Software Engineering: Using UML, Patterns, and Java
5
Figure 4-13, Example of include relationships among
use cases.
<<include>>
OpenIncident
ViewMap
<<include>>
AllocateResources
Bernd Bruegge & Allen H. Dutoit
Object-Oriented Software Engineering: Using UML, Patterns, and Java
6
Project
definition
Management
definition guide
Research
Preliminary specification
Session agenda
Preparation
Session script
Working document
Figure 4-15,
Activities of JAD
Scribe forms
Final document
preparation
Bernd Bruegge & Allen H. Dutoit
Session
Object-Oriented Software Engineering: Using UML, Patterns, and Java
Final document
7
Figure 4-20, High-level scenarios identified for
ARENA.
defineKnockOutStyle
alice:Operator
installTicTacToeGame
joe:LeagueOwner
mary:Player
organizeTicTacToeTournament
bill:Spectator
analyzeTicTacToeTournament
sponsorTicTacToeBeginnersLeague
Bernd Bruegge & Allen H. Dutoit
Object-Oriented Software Engineering: Using UML, Patterns, and Java
zoe:Advertiser
8
Figure 4-21, High-level use cases identified for
ARENA.
«initiate»
ManageUserAccounts
Operator«initiate»
ManageComponents
«initiate»
«initiate»
DefineLeague
«participate»
«initiate»
LeagueOwner
OrganizeTournament
Register
Anonymous
«initiate»
ManageOwnProfile
Player
«initiate»
«initiate»
«participate»
Advertiser
Manage Advertisements
Bernd Bruegge & Allen H. Dutoit
Spectator
BrowseTournamentHistory
Object-Oriented Software Engineering: Using UML, Patterns, and Java
9
Figure 4-23, Detailed use
cases refining the
OrganizeTournament
high-level use case
LeagueOwner
«initiate»
«include»
OrganizeTournament
«include»
«include»
«include»
AnnounceTournament
ArchiveTournament
«include»
ProcessApplications
ApplyForTournament
PlayMatch
KickoffTournament
«participate»
«participate»
Player
Advertiser
Spectator
Bernd Bruegge & Allen H. Dutoit
Object-Oriented Software Engineering: Using UML, Patterns, and Java
10
Figure 4-25, Exceptions occurring in
AnnounceTournament represented as extending use
cases.
«extend»
«extend»
AnnounceTournament
InvalidDate
«extend»
AdvertiserCreditExceeded
«extend»
«extend»
NoMatchingSponsorFound
NameInUse
MaxNumberOfTournamentsExceeded
Bernd Bruegge & Allen H. Dutoit
Object-Oriented Software Engineering: Using UML, Patterns, and Java
11