Books for you

FIGURE 2-100
Example for a model view.
bdd [package] Customer request view [requirements/use cases]
?«viewpoint?»
stakeholder???Customer,
requirements engineer, project manager???
concerns???Which requirements does the system satisfy????
purpose???Show the requirements including their relationships
that are of primary interest for the customer.???
methods???The model view includes all use cases...???
languages???SysML???
?«viewpoint?»
CustomerRequirementViewpoint
?«conform?»
?«view?»
Customer view
Requirements Use cases
141 2.8 Marginal Notes
Another way to emphasize different aspects of a model is the diagrams themselves.
Each diagram always shows only a section of the model, i.e., the section
that represents certain aspects, rather than all information stored in the model
( repository ). You can see in Figure 2.101 that a customer appears in three diagrams
in a different context each. However, this customer is present in the model
only once as a model element; see also Section 3.2.
FIGURE 2-101
The diagrams/model relation.


Pages:
274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298