Artifact:  Business Glossary

Business Glossary	The Business Glossary defines important terms used in the business modeling portion of the project.
Role:	Business-Process Analyst
Optionality:	This document is developed only if you need to keep separate the terms necessary to understand during business modeling from the terms used during the following software engineering effort. Otherwise it can be excluded.
Template:	Word Template HTML Template
More Information:	Checkpoints:Business Glossary
Purpose Brief Outline Timing Responsibility Tailoring Annotated Outline (hyperlinks into HTML template in a new window)

Input to Activities: Detail a Business Use Case Find Business Workers and Entities Define Automation Requirements Review the Business Object Model Structure the Business Use-Case Model Define the Business Architecture Maintain Business Rules

Output from Activities: Capture a Common Business Vocabulary

Purpose

There is one Business Glossary for the project. This document is important to many developers, especially when they need to understand and use the terms that are specific to the project.

Brief Outline

(hyperlinks into HTML template in a new window)

1.       Introduction         

    1.1     Purpose     

    1.2     Scope     

    1.3     References     

    1.4     Overview     

2.       Definitions

    2.1     <aTerm>     

    2.2     <anotherTerm>     

    2.3     <aGroupofTerms>     

    2.3.1         <aGroupTerm>           

    2.3.2         <anotherGroupTerm>           

    2.3.3         <yetAnotherGroupTerm>           

    2.3.4         <andAnotherGroupTerm>           

Timing

The Business Glossary is primarily developed during the inception phase, because it is important to agree on a common business terminology early in the project.

Responsibility

A Role: Business-Process Analyst is responsible for the integrity of the Business Glossary, ensuring that:

• The Business Glossary is produced in a timely manner.
• The Business Glossary is kept consistent with and not overlaps the Glossary. 
• It continuously is kept consistent with the results of development.

Tailoring

If some situations, the context and scope of the business modeling effort has a large degree of similarity to the context and scope of the software engineering effort. Where this is true, the terms identified and defined during business modeling and requirements activities can be included in a single glossary to improve consistency and reduce duplicate change management.

Copyright  © 1987 - 2001 Rational Software Corporation

Rational Unified Process