Glossary

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).]

[To customize automatic fields (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.]

Revision History

Date	Version	Description	Author
<dd/mmm/yy>	<x.x>	<details>	<name>

Table of Contents

2.3.2 <anotherGroupTerm>

2.4 <aSecondGroupOfTerms>

2.4.1 <yetAnotherGroupTerm>

2.4.2 <andAnotherGroupTerm>

Glossary

1. Introduction

[The introduction of the Glossary should provide an overview of the entire document. Present any information the reader might need to understand the document in this section. This document is used to define terminology specific to the problem domain, explaining terms which may be unfamiliar to the reader of the use-case descriptions or other project documents. Often, this document can be used as an informal data dictionary, capturing data definitions so that use-case descriptions and other project documents can focus on what the system must do with the information. This document should be saved in a file called Glossary.]

1.1 Purpose

[Specify the purpose of this Glossary.]

1.2 Scope

[A brief description of the scope of this Glossary; what Project(s) it is associated with, and anything else that is affected or influenced by this document.]

1.3 References

[This subsection should provide a complete list of all documents referenced elsewhere in the Glossary. 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.4 Overview

[This subsection should describe what the rest of the Glossary contains and explain how the document is organized.]

2. Definitions

[The terms defined here form the essential substance of the document. They can be defined in any order desired, but generally alphabetic order provides the greatest accessibility.]

2.1 <aTerm>

[The definition for <aTerm> is presented here. As much information as the reader needs to understand the concept should be presented.]

2.2 <anotherTerm>

The definition for <anotherTerm> is presented here. As much information as the reader needs to understand the concept should be presented

2.3 <aGroupofTerms>

[Sometimes it is useful to organize terms into groups to improve readability. For example, if the problem domain contains terms related to both accounting and building construction (as would be the case if we were developing a system to manage construction projects), presenting the terms from the two different sub-domains might prove confusing to the reader. To solve this problem, we use groupings of terms. In presenting the grouping of terms, provide a short description that helps the reader understand what <aGroupOfTerms> represents. Terms presented within the group should be organized alphabetically for easy access.]