1. Use Case Description
Information
The following defines information that pertains to this particular use case. Each piece of information is important in understanding the purpose behind the use case.
The following defines information that pertains to this particular use case. Each piece of information is important in understanding the purpose behind the use case.
1.1.
Name:
1.3.
Use Case Team Leader/Members:
1.4.
Pre-condition:
1.5.
Post-condition:
1.6.
Constraints/Issues/Risks:
1.7.
Trigger Event(s):
1.8.
Primary Actor:
1.9.
Secondary Actor(s):
2.
Use Case Pathway Names:
2.1.
Primary Path (Happy Path):
2.2.
Alternative Path(s):
2.3.
Exception Path(s):
3.
Category: Use Case Detail:
3.1.
Pathway Name:
3.2.
Trigger Event:
3.3.
Main Sequence of Steps:
> relationship>
Step Step Description
optionally, for an <> relationship, underline the step
Step Step Description
optionally, for an <
3.4.
Variations (optional):
Step Step Description
Step Step Description
step #>
3.5.
Extensions (optional):
on the use case diagram with an
<> relationship to the extended use case.>
3.6.
Business Rules (optional):
3.7.
Constraints/Issues/Risks (optional):
4.
Use Case Tactical Information:
These items are usually not known early in the use
case inception phase, but are uncovered later during elaboration
.>
4.1.
Priority:
4.2.
Performance Target:
< this information contains specific performance expectations of the use case. . It is also possible to attach these to individual pathways.>
< this information contains specific performance expectations of the use case. . It is also possible to attach these to individual pathways.>
4.3.
Frequency:
4.4.
User Interface:
4.5.
Location of Source:
No comments:
Post a Comment