What? Describe the domain intention for the use case in the form of essential steps
that don ??™ t consider technical details and concrete fl ows.
How? Think of the steps involved in the standard fl ow of a use case and remove the
technical details that are contained in the standard fl ow so that they will no longer be
present in the result.
Where? The essential steps give you the structure for the next level of details. The
description is stable and can be reused for subsequent or similar systems, e.g., in a
product family.
Guiding questions
?– What is the domain intention for the use case?
?– Does the essential description contain technical solutions?
?– Is the name of an essential step identical with that of the use case?
?– Is the essential description easy to understand for a domain person who doesn ??™ t
know anything about the project?
?– Does the use case have 2??“8 essential steps?
SysML elements
Use case diagram, use case, comment.
Describe use
case essences
Use cases
[essential]
Use cases
Requirements
77
A helpful path toward our essential description leads across a pragmatic process.
Pages:
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188