<Project Name>

Business Use-Case Realization 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.       Introduction         

1.1     Purpose     

1.2     Scope     

1.3     Definitions, Acronyms and Abbreviations     

1.4     References     

1.5     Overview     

2.       Workflow Realization    

3.       Derived Requirements

Business Use-Case Realization Specification: <Business Use-Case Name>

1.                  Introduction

[The introduction of the Business Use-Case Realization 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 Realization Specification.]

[Note: This document template assumes that the business use-case realization is partly described within a Rational Rose model; this means that the business use case’s name and brief description is within the Rose model, and that this document should be linked as an external file to the business use case. This document should contain additional properties of the business use-case realization that are not in the Rose model.]

1.1               Purpose

[Specify the purpose of this Business Use-Case Realization Specification]

1.2               Scope

[A brief description of the scope of this Business Use-Case Realization 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 should provide the definitions of all terms, acronyms, and abbreviations required to properly interpret the Business Use-Case Realization Specification.  This information may be provided by reference to the project Glossary.]

1.4               References

[This subsection should provide a complete list of all documents referenced elsewhere in the Business Use-Case Realization 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.]

1.5               Overview

[This subsection should describe what the rest of the Business Use-Case Realization Specification contains and explain how the document is organized.]

2.                  Workflow Realization

[A textual description of how the business use case is realized in terms of collaborating objects. Its main purpose is to summarize the diagrams connected to the business use case and to explain how they are related.]

3.                  Derived Requirements

[A textual description that collects all requirements, such as automation requirements, on the business use-case realization that are not considered in the business use-case model but need to be taken care of when building the system.]