Artifact: Business Glossary

	The Business Glossary defines important terms used in the business modeling portion of the project.
Role:	Business-Process Analyst
Optionality/Occurrence:	This document is developed only if you need to keep the terms necessary to understand business modeling separate from those terms used during the consequent software engineering effort. Otherwise it can be excluded.
Templates and Reports:	Template: Business Glossary
Examples:
UML Representation:	Not applicable.
More Information:	Checklist: Business Glossary

Purpose Timing Responsibility Tailoring

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

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.

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 Business-Process Analyst is responsible for the integrity of the Business Glossary, ensuring that it is:

• produced in a timely manner
• kept consistent with and not overlaps the Glossary
• kept consistent continuously with the results of development

Tailoring

In 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.

Rational Unified Process