Artifacts > Requirements Artifact Set > Glossary
|The Glossary defines important terms used by the project.|
|Input to Activities:||Output from Activities:|
There is one Glossary for the system that provides a consistent set of definitions to help avoid misunderstandings. Project members initially use the Glossary to understand the terms that are specific to the project. This document is also important to people performing these roles:
The Glossary is primarily developed during the inception and elaboration phases, because it's important to agree on a common terminology early in the project.
The System Analyst role is responsible for the integrity of the Glossary, ensuring that:
In some projects where business modeling and domain modeling are not performed, the Glossary is the primary artifact used to capture information about the project's business domain.
If the context and scope of the business modeling effort is much broader than that of the software engineering effort, you may need to produce a separate Glossary, specifically for business modeling. That Glossary would then be the responsibility of the Business-Process Analyst.
Rational Unified Process