<Project Name>
Business Use-Case Specification: <Business Use-Case Name>
Version <1.0>
[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=Body Text).]
Revision History
|
Date |
Version |
Description |
Author |
|
<dd/mmm/yy> |
<x.x> |
<details> |
<name> |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Table of Contents
1.3 Definitions, Acronyms and Abbreviations
4.1 <name of performance goal>
12.1 <name of special requirement>
13.1 <name of extension point>
Business Use-Case Specification: <Business Use-Case Name>
[The introduction of the Business Use-Case Specification should provide an overview of the entire document. It should include the purpose, scope, definitions, acronyms, abbreviations, references, and overview of this Business Use-Case Specification.]
[Note: If you are not using Rational Requisite Pro, then this document template should be used to capture the actual Business Use Case including the workflow, special requirements, and performance goals of the Business Use Case. This file should be linked to the corresponding business use case in the Rose model.
If you use SoDA then this document is used as input to the business use-case report that combines this content with use-case diagrams from Rose.]
[Specify the purpose of this Business Use-Case Specification]
[A brief description of the scope of this Business Use-Case Specification; what Use-Case model(s) it is associated with, and anything else that is affected or influenced by this document.]
[This subsection should provide the definitions of all terms, acronyms, and abbreviations required to properly interpret the Business Use-Case Specification. This information may be provided by reference to the project Glossary.]
[This subsection should provide a complete list of all documents referenced elsewhere in the Business Use-Case Specification. Each document should be identified by title, report number (if applicable), date, and publishing organization. Specify the sources from which the references can be obtained. This information may be provided by reference to an appendix or to another document.]
[This subsection should describe what the rest of the Business Use-Case Specification contains and explain how the document is organized.]
[The description should briefly convey the purpose of the business use case. A single paragraph should suffice for this description.]
[A specification of the measurable goals or objectives of the business use case.]
[A specification of the metrics relevant to the business use case and a definition of the goals of using those metrics.]
[A brief description of the performance goal.]
[A textual description of the workflow the business use case represents. The workflow should describe what the business does to deliver value to a business actor, not how the business solves its problems.
Only one level of workflow steps is indicated in the subsections below, but you may add more levels if necessary.]
[A brief description of the workflow step.]
[A brief description of the workflow step.]
[Whether the business use case is of the category 'core', 'supporting', or 'management'.]
[A specification of the risks of executing and/or implementing the business use case.]
[A description of the estimated improvement potential of the business use case.]
[A definition of who the owner of the business process is, the person who manages the changes and plans for changes.]
[A precondition of a business use case is a condition that must be true before performing the business use case.]
[A postcondition of a business use case is a condition that will be true after performing the business use case.]
[The special requirements of the business use case are included here. These are requirements not covered by the workflow as it has been described in the sections above.]
[A brief description of the special requirement.]
[Extension points of the business use case.]
[Definition of the location of the extension point in the flow of events.]