Prev | Current Page 236 | Next

Tim Weilkiens

"Systems Engineering with SysML/UML: Modeling, Analysis, Design"

You can see the glossary
entries in Table 2.17 .
I ??™ m giving a few rules for glossary entries that, when observed, will help you
create them in an easy-to-understand way to avoid misunderstandings:
1. Write down entire sentences rather than headwords. This helps you avoid
that important information will eventually be missing. For example, compare
the entry in Table 2.17 with the following description of ??? usage right ??? .
?–  Customer
?–  Booking period
?–  Emergency driving
2. Try to write active sentences rather than passive ones. This helps you prevent
that you inadvertently omit information. For example, use a style similar to the
one in Table 2.17 instead of the following description of ??? disposal right. ???
A customer is granted the disposal right if he or she has entered a correct
customer PIN at the beginning of the usage period.
3. Write short, communicative sentences. Somebody who tries to look something
up in a glossary doesn ??™ t expect long essays. Think of entries in a lexicon.
110 CHAPTER 2 The Pragmatic SYSMOD Approach
2.


Pages:
224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248
pozycjonowanie strony multihack do metina 2 wentylacja Wiadomosci firmowe K10