Documenting Requirements - Glossary
4 important questions on Documenting Requirements - Glossary
Why using a glossary?
- Conflicts in requirements engineering often caused by participants having different interpretations of terms;
- Avoid conflicts and increase understandability;
- Glossaries can be reused within the same domain.
Rules for using a glossary
- Creating a glossary is mandatory;
- Start development of the glossary as early as possible;
- Using the glossary must be obligatory.
A glossary is a collection of term definitions for?
- context-specific technical terms
- abbreviations and acronyms
- everyday concepts that have a special meaning in the given context
- synonyms, i.e., different terms with the same meaning
- homonyms, i.e., identical terms with different meanings
- Higher grades + faster learning
- Never study anything twice
- 100% sure, 100% understanding
The following rules should be observed when working with a glossary?
- The glossary must be managed centrally
- The responsibilities for maintaining the glossary must be defined
- The glossary must be maintained over the course of the project
- The glossary must be commonly accessible
- Use of the glossary must be obligatory
- The glossary should contain the sources of the terms
- The stakeholders should agree upon the glossary
- The entries in the glossary should have a consistent structure
The question on the page originate from the summary of the following study material:
- A unique study and practice tool
- Never study anything twice again
- Get the grades you hope for
- 100% sure, 100% understanding
![Trustpilot Logo](/images/design_2020/lp/clp-trustpilot-en.png)