art for chapter 4, requirements elicitation
Post on 01-Jan-2016
45 Views
Preview:
DESCRIPTION
TRANSCRIPT
Usi
ng U
ML
, Pat
tern
s, a
nd J
ava
Ob
ject
-Ori
ente
d S
oftw
are
En
gin
eeri
ng
Art for Chapter 4,Requirements Elicitation
Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 2
Figure 4-1, Products of requirements elicitation and analysis.
Analysis
problemstatement
functionalmodel
nonfunctionalrequirements
analysis objectmodel
Requirementselicitation
dynamic model
Analysis Model
RequirementsSpecification
Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 3
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).
WatchOwner
GPS
WebifyWatch
SatWatch
Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 4
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 DispatcherFRIEND
Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 5
Figure 4-11, Example of communication relationships among actors and use cases in FRIEND.
ReportEmergency
FieldOfficer Dispatcher OpenIncident
AllocateResources
<<initiate>>
Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 6
Figure 4-12, Example of use of extend relationship.
ReportEmergency
FieldOfficerConnectionDown
<<extend>>
Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 7
Figure 4-13, Example of include relationships among use cases.
ViewMapOpenIncident
AllocateResources
<<include>>
<<include>>
Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 8
Figure 4-15, Activities of JAD
Managementdefinition guide
Projectdefinition
Research
Preparation
Session
Session agendaPreliminary specification
Working document
Session script
Scribe forms
Final documentpreparation
Final document
Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 9
Figure 4-20, High-level scenarios identified for ARENA.
installTicTacToeGamealice:Operator
defineKnockOutStyle
organizeTicTacToeTournament
sponsorTicTacToeBeginnersLeague
joe:LeagueOwner
zoe:Advertiser
bill:Spectator
mary:Player
analyzeTicTacToeTournament
Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 10
Figure 4-21, High-level use cases identified for ARENA.
ManageComponentsOperator
ManageUserAccounts
OrganizeTournamentLeagueOwner
DefineLeague
PlayerManageOwnProfile
Manage Advertisements SpectatorBrowseTournamentHistory
Advertiser
Anonymous Register
«participate»
«initiate»
«initiate»
«initiate»
«initiate»
«initiate» «initiate»
«initiate»
«initiate»
«participate»
Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 11
Figure 4-23, Detailed usecases refining theOrganizeTournamenthigh-level use case
ApplyForTournament
AnnounceTournament
OrganizeTournament
LeagueOwner
ProcessApplications
Player
ArchiveTournament
KickoffTournament
Spectator
PlayMatch
«initiate»
«include»
Advertiser
«participate»
«participate»
«include»
«include»
«include»
«include»
Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 12
Figure 4-25, Exceptions occurring in AnnounceTournament represented as extending use cases.
MaxNumberOfTournamentsExceeded
AnnounceTournamentInvalidDate
NameInUse
NoMatchingSponsorFound
AdvertiserCreditExceeded
«extend»
«extend»
«extend»
«extend»«extend»
top related