This wiki has undergone a migration to Confluence found Here
Difference between revisions of "Template:SAIF Generic IM Requirements"
Jump to navigation
Jump to search
| Line 6: | Line 6: | ||
==<span style="color:#0000FF"> Requirements, Relationships and Content </span>== | ==<span style="color:#0000FF"> Requirements, Relationships and Content </span>== | ||
</noinclude> | </noinclude> | ||
| − | # | + | # This type of model MUST include the set of classes, attributes and associations from the parent (derived from) model that '''represent the information needed to support interoperability in''' the domain or project that this model will support. |
## <i>Rationale</i>Derived Models must use the RIM-derived model content needed to support the interoperability project in question. | ## <i>Rationale</i>Derived Models must use the RIM-derived model content needed to support the interoperability project in question. | ||
| − | # | + | # This model MUST maintain a degree of '''abstraction''' appropriate to the level of the model, remembering that models derived from this model can be more specific. |
## <i>Rationale</i> Large models with myriad classes may obscure the core patterns and concepts that need to be represented in a particular DIM, SIM or other model. | ## <i>Rationale</i> Large models with myriad classes may obscure the core patterns and concepts that need to be represented in a particular DIM, SIM or other model. | ||
Revision as of 21:52, 11 April 2011
Generic requirements for SAIF Information models.
Only the content appearing below in black font will appear in the inclusion.
These elements are intended to appear under the following section:
goto to SAIF artifact definitions
Requirements, Relationships and Content
- This type of model MUST include the set of classes, attributes and associations from the parent (derived from) model that represent the information needed to support interoperability in the domain or project that this model will support.
- RationaleDerived Models must use the RIM-derived model content needed to support the interoperability project in question.
- This model MUST maintain a degree of abstraction appropriate to the level of the model, remembering that models derived from this model can be more specific.
- Rationale Large models with myriad classes may obscure the core patterns and concepts that need to be represented in a particular DIM, SIM or other model.
