A view supports all kinds of various interests by providing a view of the entire
model especially for a target group. More specifi cally, a view describes a set of
model elements that can be represented in various diagrams. This is a fi ltered
view of the model. It is denoted as an UML package with stereotype ?«view?»
( Figure 4.60 ).
Each view realizes exactly one viewpoint. A viewpoint describes the stakeholders
and their concerns, the view ??™ s purpose, rules as to how the view should
be created (methods) as well as languages used to create the view. A viewpoint is
denoted as a class with stereotype ?«viewpoint?» ( Figure 4.60 ).
269
FIGURE 4-60
Example for a view.
bdd [package] Customer requirement view [requirements/use cases]
?«view?»
Customer view
Requirements Use cases
?«conform?»
?«viewpoint?»
CustomerRequirementViewpoint
?«viewpoint?»
stakeholder???Customer, requirements engineer, projectmanager???
concerns???Which requirements does the system satisfy????
purpose???Show the requirements, including their relationships, that are of
primary interest for the customer.
Pages:
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489