Professional Documents
Culture Documents
The
Thepurpose
purposeof
ofRequirements
Requirementsis
isto:
to:
Establish
Establishand
andmaintain
maintainagreement
agreement
with
withthe
thecustomers
customersand
andother
other
stakeholders
stakeholdersononwhat
whatthe
thesystem
system
should
shoulddo.
do.
Give
Givesystem
systemdevelopers
developersaabetter
better
understanding
understandingofofthe
therequirements
requirements
of the system.
of the system.
Delimit
Delimitthe
thesystem.
system.
Provide
Provideaabasis
basisfor
forplanning
planningthethe
technical
technicalcontents
contentsofofthe
theiterations.
iterations.
Provide
Provideaabasis
basisfor
forestimating
estimatingcost
cost
and
andtime
timeto
todevelop
developthe
thesystem.
system.
Define
Defineaauser
userinterface
interfaceof
ofthe
the
system.
system.
Use-Case Model
Glossary
Actors
Use Cases
...
Supplementary
Specification
Use-Case Specifications
Course Registration
Requirements Document
Actor
UseCase
Student
Login
Identification
Users
End User Domain Expert
Course Catalog
Maintain Professor
Register for Courses Information
Student
Registrar
Select Courses to
Teach Close Registration
Professor
Submit Grades
Billing System
Flow of Events
This use case starts when the Registrar requests that the
system close registration.
Activity2
1. The system checks to see if registration is in progress. If it
is, then a message is displayed to the Registrar and the use
case terminates. The Close Registration processing cannot
be performed if registration is in progress.
Activity1 Activity3
2. For each course offering, the system checks if a professor
has signed up to teach the course offering and at least three
students have registered. If so, the system commits the
course offering for each schedule that contains it.
Synchronization
Bar (Fork)
Check Check
Guard Schedule Pre-requisites
Condition
Synchronization
Bar (Join)
[ checks completed ] [ checks failed ]
Assign to Resolve
Course Conflicts
Transition
Update
Schedule
Glossary
Supplementary
Specification
Mastering Object Oriented Analysis and Design with UML
Copyright © 2003 Rational Software, all rights reserved 24
Requirements Overview Topics
Introduction
Key Concepts
Use-Case Model
Glossary
Supplementary Specifications
Checkpoints