<Project Name>

Use-Case Modeling Guidelines

 

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.       General Use-Case-Modeling Guidelines     

3.       How to Describe a Use Case

4.       UML Stereotypes

Use-Case-Modeling Guidelines

1.                  Introduction

[The introduction of the Use-Case-Modeling Guidelines should provide an overview of the entire document. It should include the purpose, scope, definitions, acronyms, abbreviations, references and overview of this Use-Case-Modeling Guidelines.]

1.1               Purpose

[Specify the purpose of this Use-Case-Modeling Guidelines.]

1.2               Scope

[A brief description of the scope of this Use-Case-Modeling Guidelines; what Project(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 Use-Case-Modeling Guidelines.  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 Use-Case-Modeling Guidelines.  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 Use-Case-Modeling Guidelines contains and explain how the document is organized.]

2.                  General Use-Case-Modeling Guidelines

[The section describes which notation to use in the use-case model. For example, you may have decided not to use extends-relationships between use cases.]

3.                  How to Describe a Use Case

[This section gives rules, recommendations, and style issues, and how you should describe each use case.]

4.                  UML Stereotypes

[This section contains or references specifications of Unified Modeling Language (UML) stereotypes and their semantic implications-a textual description of the meaning and significance of the stereotype and any limitations on its use-stereotypes already known or discovered to be useful for the construction of Use-Case models. The use of these stereotypes may be simply recommended or perhaps even made mandatory; for example, when their use is required by an imposed standard, when it is felt that their use makes models significantly easier to understand, or when it ensures that common types of entities, roles, relationships, or patterns are uniformly modeled and understood. This section may be empty if no additional stereotypes, other than those predefined by the UML and the Rational Unified Process, are considered necessary.]