Word has long since gotten around that in systems engineering we should not just start writing. Instead, we should control the language. The vocabulary to be used is an important aspect that can be easily controlled.<\/p>\n\n\n\n
I recently came across a study that deals with exactly this topic, the effects of controlled vocabulary in requirements management. More importantly, the effects are quantified. In the following, I will first answer the question of what forms of vocabulary there are. I will then list a few interesting figures from the study that quantify the added value of controlled vocabulary.<\/p>\n\n\n\n\n\n\n\n
The use of controlled vocabulary (CVs) aims to increase the quality of the specifications of the software requirements. So far so good: the quality of the written documentation is better. Controlled vocabulary also helps to avoid ambiguities and Complexity<\/a> to reduce. <\/p>\n\n\n\n The authors of the study were surprised that very little had been published on the effects of controlled vocabulary. They therefore carried out a meta-study in which they examined 90 papers in detail from 2348 published papers on the topic. The paper published in 2020 can be downloaded here: <\/p>\n\n\n\n The Impact of Controlled Vocabularies on Requirements Engineering Activities: A Systematic Mapping Study <\/a><\/p>\n\n\n\n The most commonly known controlled vocabulary is probably the Glossary<\/a>. This is not even mentioned in the paper. Instead, the authors only identify the two groups Ontology<\/a> and taxonomy.<\/p>\n\n\nThe study<\/h2>\n\n\n\n
What is controlled vocabulary?<\/h2>\n\n\n\n