<Project Name>
Supplementary Business Specification
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
Supplementary Business Specification
[The introduction of the Supplementary Business Specification should provide an overview of the entire document. It should include the purpose, scope, definitions, acronyms, abbreviations, references, and overview of this Supplementary Business Specification.]
[Specify the purpose of this Supplementary Business Specification]
[A brief description of the scope of this Supplementary Business 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 Supplementary Business 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 Supplementary Business 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 Supplementary Business Specification contains and explain how the document is organized.]
[This section expresses general objectives for the behavior of the organization that are not specific to a particular business use case.]
[This section should include all of those requirements that affect usability from the perspective of a business actor. Examples follow]:
- Specify the required training time for a normal users and power users of the organization to become productive at particular operations.
- Specify measurable task times for typical tasks.
[Requirements for reliability (from a business actor perspective) of the organization should be specified here. Suggestions are as follows]:
- Availability - specify percentage of time available ( xx.xx%), anticipated hours of use, etc.
- Accuracy - specify precision (resolution) and accuracy (by some known standard) that is required in the output.
[The performance characteristics should be outlined in this section. Include specific response times. Where applicable, reference related business use cases by name.]
- Response time for a transaction(average, maximum)
- Throughput (e.g., transactions per second)
- Capacity (e.g., the number of customers or transactions the business can accommodate)
- Resource utilization: number of employees, memory capacity of systems, etc.
[List and briefly describe any information about how you expect the organization to change size in the future, and what limitations or precautions need to be considered to meet that change.]