Books for you

What? Describe domain terms from the system environment.
How? Describe the terms in text form in the style of a lexicon. Long explanations and
formal defi nitions do not belong to a glossary.
Where? A standardized project language that doesn ??™ t leave much room for all sorts
of interpretations forms the basis for effective working and successful modeling.
Guiding questions
?–  What domain terms will be used in the project?
?–  Do all project participants have the same understanding of a term?
?–  Does every project participant have quick and easy access to the glossary?
SysML elements
None.
Create
glossary
Glossary
Requirements
108 CHAPTER 2 The Pragmatic SYSMOD Approach
clearly so that any project participant will understand the term unambiguously.
It surely happened to you too during your daily project work that unnerving discussions
or system errors emerged due to petty misunderstandings.
Our glossary should contain two types of terms: ??? real ??? domain terms that
not everybody necessarily knows, and domain terms that everybody thinks they
know.


Pages:
219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243