Enrol student in class.
This is better than nothing... and the start for
drafting more complete descriptions of the use case.
Brief Format
Name + Terse one paragraph description of who does what to get what.
Enrol student in class
. . . . . . . . . ( end of section Casual Format) <<Contents | End>>
Fully Dressed
. . . . . . . . . ( end of section Extensions) <<Contents | End>>
Special Requirements
| Name | Start with a verb, numbering optional |
| Scope | The System under Design |
| Level | User-goal or subfunction |
| Primary Actor | Asks the SUD to deliver service to meet goals |
| Stakeholders and Interests | (stakeholder1): what they want. |
| Preconditions | State what special and interesting things must be true for this particular case to work. |
| Postconditions | List the interesting things that are true after a scenario is completed |
| Main Success Scenario | actor does something or system responds
|
| Extensions | (steps letter): condition steps |
| Special Requirements | desired qualities or technological limitations |
| Variations in Technology and Data | step number: possible change in technology or data format |
| Frequency of Occurrence | How often |
| Miscellaneous | Open issues to research |
. . . . . . . . . ( end of section Fully Dressed) <<Contents | End>>
. . . . . . . . . ( end of section Use Case Templates) <<Contents | End>>