<Note: everything surrounded by <> is either a placeholder to
be filled in or a comment to be deleted. All tables contain fictional
example entries which should be removed.>
|
Item |
Value |
|
Use-case name |
<name> |
|
Brief description |
<A short description of the use
case.> |
|
Actor(s) involved |
<A list of all actors related to
this use case.> |
| Object(s) involved |
<A list of all objects
(all their classes) employed in this use case.> |
|
Basic flow of events |
<An algorithmic explanation of
how the detailed use
case normally works from a design point-of-view, referencing objects
listed in the previous section where appropriate .> |
|
Alternate flow(s) of events |
<A list of all common
alternatives to the basic flow, along with what the flow would be for
each alternative.> |
|
Pre-conditions to use case |
<Conditions - if any � that are assumed by the use case to be true
immediately before the it begins.> |
|
Post-conditions of use case |
<Conditions which should be true
immediately after the use case terminates.> |
|
Special requirements |
<Non-functional requirements
related only to this use case e.g. performance requirements for this
use case. Any special requirements related
to the entire software should go into the supplemental specifications
artifact.> |
<List of items to be completed in THIS artifact.>
|
# |
Who |
Due |
What |
|
1 |
|
|
|
|
2 |
|
|
|
|
Date |
Who |
Revision |
|
|
|
|