Page 12 - Software and Systems Requirements Engineering in Practice

C o n t e n t s xi

Analyzing Product Features and Creating
a Use Case Model . . . . . . . . . . . . . . . . . . . . 92
Extracting Requirements from the Model . . . 94
Starting an MDRE Effort . . . . . . . . . . . . . . . . . 96
Managing Elicitation and Analysis Sessions 96
Improved Productivity Through Distributed
Modeling . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
Conducting Model Reviews . . . . . . . . . . . . . . 98
Elicitation and Analysis Model Heuristics . . . . . . . . 99
The Model Should Have a Single
Entry Point . . . . . . . . . . . . . . . . . . . . . . . . . . 99
All Actors Associated with the System Being
Analyzed Should Appear on the Context
Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
The Early Modeling Effort Should Cover
the Entire Breadth of the Domain . . . . . . . 100
Identify “Out-of-Scope” Use Cases
as Early as Possible . . . . . . . . . . . . . . . . . . . 100
Every Diagram Should Have an Associated
Description and Status . . . . . . . . . . . . . . . . 100
Avoid the Early Use of Packages . . . . . . . . . . 101
Do Not Substitute Packages for Abstract
Use Cases . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
Every Artifact in a Model Should
Be Visible on a Diagram . . . . . . . . . . . . . . . 101
Every Symbol Should Have a Bidirectional
Hyperlink to the Diagrams
That Define It . . . . . . . . . . . . . . . . . . . . . . . . 102
Package Dependencies Should Be Based
on Content . . . . . . . . . . . . . . . . . . . . . . . . . . 102
Every Concrete Use Case Must
Be Defined . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
Use an Activity Diagram to Show All Possible
Scenarios Associated with a Use Case . . . 105
Use Sequence Rather Than Collaboration
Diagrams to Define One Thread/Path
for a Process . . . . . . . . . . . . . . . . . . . . . . . . . 105
Abstract Use Cases Must Be Realized
with Included or Inherited Concrete
Use Cases . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
Extending Use Case Relationships Can
Only Exist Between Like Use Cases . . . . . 108
A Concrete Use Case Cannot Include
an Abstract Use Case . . . . . . . . . . . . . . . . . . 108
Avoid Realization Relationships and Artifacts
in the Analysis Model . . . . . . . . . . . . . . . . . 108