[Note: The following template is provided for use with the Rational Unified Process. Text enclosed in square brackets and displayed in blue italics (style=InfoBlue) is included to provide guidance to the author and should be deleted before publishing the document. A paragraph entered following this style will automatically be set to normal (style=BodyText).]
[To customize automatic fields in Microsoft Word (which display a gray background when selected), select File>Properties and replace the Title, Subject and Company fields with the appropriate information for this document. After closing the dialog, automatic fields may be updated throughout the document by selecting Edit>Select All (or Ctrl-A) and pressing F9, or simply click onthe field and press F9. This must be done separately for Headers and Footers. Alt-F9 will toggle between displaying the field names and the field contents. See Word help for more information on working with fields.]
|Date |Version |Description |Author |
|| | | |
| | | | |
| | | | |
|| | | |
Table of Contents
1. Use-Case Name 2
1.1 Brief Description 2
2. Flow of Events 2
2.1 Basic Flow 2
2.2 Alternative Flows 2
2.2.1 < First Alternative Flow > 2
2.2.2 < Second Alternative Flow > 2
3. Special Requirements 2
3.1 < FirstSpecial Requirement > 2
4. Preconditions 2
4.1 < Precondition One > 2
5. Postconditions 2
5.1 < Postcondition One > 2
6. Extension Points 2
[The following template is provided for a Use-Case Specification, which contains the textual properties of the use case. This document is used with a requirements management tool, such as RationalRequisitePro, for specifying and marking the requirements within the use-case properties.
The use-case diagrams can be developed in a visual modeling tool, such as Rational Rose. A use-case report, with all properties, may be generated with Rational SoDA. For more information, see the tool mentors in the Rational Unified Process.]
1 Brief Description
[Thedescription briefly conveys the role and purpose of the use case. A single paragraph will suffice for this description.]
Flow of Events
1 Basic Flow
[This use case starts when the actor does something. An actor always initiates use cases. The use case describes what the actor does and what the system does in response. It is phrased in the form of a dialog between the actor and thesystem.
The use case describes what happens inside the system, but not how or why. If information is exchanged, be specific about what is passed back and forth. For example, it is not very illuminating to say that the actor enters customer information. It is better to say the actor enters the customer’s name and address. A Glossary of Terms is often useful to keep the complexity of the usecase manageable(you may want to define things like customer information there to keep the use case from drowning in details.
Simple alternatives may be presented within the text of the use case. If it only takes a few sentences to describe what happens when there is an alternative, do it directly within the Flow of Events section. If the alternative flow is more complex, use a separate...