Books for you

This also includes the introduction of requirement
categories (e.g., usability requirements). Section 5.3 describes the extensions for
requirements in the SYSMOD profi le.
Since requirements are pure specifi cation elements, it wouldn ??™ t make sense to
create instances of requirements. For this reason, requirements are always abstract.
Requirements must not be generalized. And it wouldn ??™ t make much sense,
because they have neither operations nor attributes to inherit.
The stereotype ?«requirement?» is defi ned without a notation of its own. This
means that the standard notation for stereotypes applies ( Figure 4.4 ).
The term feature is often used synonymously for requirement. Unfortunately,
there is no uniform defi nition of this term. It is one of those unfortunate words that
are used in almost all projects without having clear defi nitions of its meaning. This
causes many minor misunderstandings that, in total, can lead to serious problems.
4.3.2 The Derive Requirement Relationship
FIGURE 4-5
Example for a derive requirement.


Pages:
407 408 409 410 411 412 413 414 415 416 417 418 419 420 421 422 423 424 425 426 427 428 429 430 431