<Project Name>
Business Use-Case Specification: <Business Use-Case Name>
<o:p> </o:p>
Version <1.0><o:p></o:p>
<o:p> </o:p>
[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).]
[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 on the 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.]
[Note: If you are not using Rational RequisitePro, 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 Rational Rose model.
If you use Rational SoDA, then this document is used as input to the business use-case report that combines this content with use-case diagrams from Rose.]
Revision History
Date<o:p></o:p> |
Version<o:p></o:p> |
Description<o:p></o:p> |
Author<o:p></o:p> |
<dd/mmm/yy> |
<x.x> |
<details> |
<name> |
<o:p> </o:p> |
<o:p> </o:p> |
<o:p> </o:p> |
<o:p> </o:p> |
<o:p> </o:p> |
<o:p> </o:p> |
<o:p> </o:p> |
<o:p> </o:p> |
<o:p> </o:p> |
<o:p> </o:p> |
<o:p> </o:p> |
<o:p> </o:p> |
<o:p> </o:p>
Table of Contents
1. Introduction 2<o:p></o:p>
1.1 Purpose 2<o:p></o:p>
1.2 Scope 2<o:p></o:p>
1.3 Definitions, Acronyms, and Abbreviations 2<o:p></o:p>
1.4 References 2<o:p></o:p>
1.5 Overview 2<o:p></o:p>
2. Business Use-Case Name 2<o:p></o:p>
2.1 Brief Description 2<o:p></o:p>
3. Goals 2<o:p></o:p>
4. Performance Goals 2<o:p></o:p>
4.1 <name of performance goal> 2<o:p></o:p>
5. Workflow 2<o:p></o:p>
5.1 Basic Workflow 2<o:p></o:p>
5.1.1 <name of workflow step> 2<o:p></o:p>
5.2 Alternative Workflows 2<o:p></o:p>
5.2.1 <name of workflow step> 2<o:p></o:p>
6. Category 2<o:p></o:p>
7. Risk 2<o:p></o:p>
8. Possibilities 2<o:p></o:p>
9. Process Owner 2<o:p></o:p>
10. Special Requirements 2<o:p></o:p>
10.1 <Name of Special Requirement> 2<o:p></o:p>
11. Extension Points 2<o:p></o:p>
11.1 <Name of Extension Point> 2<o:p></o:p>
Business Use-Case Specification: <Business Use-Case Name>
1. Introduction
[The introduction of the Business Use-Case Specification provides an overview of the entire document. It includes the purpose, scope, definitions, acronyms, abbreviations, references, and overview of this Business Use-Case Specification.
Note: If you are not using Rational RequisitePro, 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 Rational Rose model.
If you use Rational SoDA, then this document is used as input to the business use-case report that combines this content with use-case diagrams from Rational Rose.]
1.1 Purpose
[Specify the purpose of this Business Use-Case Specification.]
1.2 Scope
[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.]
1.3 Definitions, Acronyms, and Abbreviations
[This subsection provides 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’s Glossary.]
1.4 References
[This subsection provides a complete list of all documents referenced elsewhere in the Business Use-Case Specification. Identify each document 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.]
1.5 Overview
[This subsection describes what the rest of the Business Use-Case Specification contains and explains how the document is organized.]
2. Business Use-Case Name
2.1 Brief Description
[The description briefly conveys the role and purpose of the business use case. A single paragraph will suffice for this description.]
3. Goals
[A specification of the measurable goals or objectives of the business use case.]
4. Performance Goals
[A specification of the metrics relevant to the business use case and a definition of the goals you want to achieve by using those metrics.]
4.1 <name of performance goal>
[A brief description of the performance goal.]
5. Workflow
[A textual description of the workflow the business use case represents. The workflow describes 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.]