bdd [package] Domain knowledge [circle]
?«domain?»
Customer
?«domain?»
Car
?«domain?»
Usage data
107 2.6 Create Glossary
PROJECT DIARY
Project Time 7939
Similar to other diagrams used earlier, we can coordinate the domain knowledge
model also directly with our stakeholders. They can read the diagram and reproduce
the structures. That ??™ s great since it saves us the error-prone translation of our
principal ??™ s wishes to our model.
2.6 Create Glossary
Creating a glossary is shown in Table 2.16 .
Creating and maintaining a glossary are activities that continue during the
entire project time. The glossary describes all domain terms from the project
environment. Rather than defi ning terms, the glossary explains them briefl y and
Table 2.16 Summary: Creating a glossary.
Reference card: Create glossary.
Incoming and outgoing data
Requirements:
General requirements to the system.
Glossary:
Description of domain terms for the
project.
Motivation/description
Why? A glossary restricts the playground for free interpretations so typical of natural
languages to avoid misunderstandings in the project.
Pages:
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242