To specify additional
information about model elements,
add different types of annotations with semantics (like a constraint
or requirement) or annotations that are simply informative, like a
documentation note or comment.
Note: None of
the annotation types generate code; they are used to improve the readability
and comprehension of your model.
- Constraint for
a condition or restriction
expressed in text. It is generally a Boolean expression that must
be true for an associated model element for the model to be considered
well-formed. A constraint is an assertion rather than an executable
mechanism. It indicates a restriction that must be enforced by the
correct design of a system. Constraints are part of the model and
are, therefore, displayed in the browser.
- Comment for
a textual annotation that does
not add semantics, but contains information that might be useful to
the reader and is displayed in the browser.
- Note for
a textual annotation that does
not add semantics, but contains information that might be useful to
the reader. Notes are not displayed in the browser.
- Requirement for a textual annotation that
describes the intent of the element. Note that a requirement modeled
inside IBM® Rational® Rhapsody® does
not replace the usage of a dedicated requirement traceability tool,
such as IBM Rational DOORS®.
Instead, a modeled requirement complements the usage of such a tool
because the hierarchical modeling of requirements enables you to easily
correlate each requirement to the element that addresses it.
Requirements are part of the model and are therefore displayed in
the browser.