On this page
12. Glossary
Content
The most important domain and technical terms that your stakeholders use when discussing the system.
You can also see the glossary as source for translations if you work in a multi-language environment (i.e. in offshore development models).
Motivation
You should clearly define your terms, so that all stakeholders
- have an identical understanding of these termes
- do not use synonyms and homonyms
Form
- A simple table with columns <Term> and <Definition>
- Potentially more columns for translations
| Term | Definition |
|---|---|
| <Term-1> | <definition-1> |
| <Term-2> | <definition-2> |
Examples
<insert glossary (and optionally translation) table >
Practical Tips
- Tip 12-1: Take the glossary seriously!
- Tip 12-2: Document the glossary as a table!
- Tip 12-3: Amend the glossary by a (graphical) model!
- Tip 12-4: Include translations in the glossary!
- Tip 12-5: Keep the glossary compact! Avoid trivia.
- Tip 12-6: Make your 'product owner' or 'project manager' responsible for the glossary