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
(Created page with "<noinclude> Generic requirements for SAIF Information models. intended to appear under: == Requirements, Relationships and Content == </noinclude> # Include the set of Reference ...") |
|||
| Line 1: | Line 1: | ||
| − | <noinclude> | + | <noinclude><span style="color:#0000FF">Generic requirements for SAIF Information models. '''Only the content in </span>black font<span style="color:#0000FF"> will appear in the inclusion.''' These elements are intended to appear under the following section:</span> |
| − | Generic requirements for SAIF Information models. intended to appear under: | + | ==<span style="color:#0000FF"> Requirements, Relationships and Content </span>== |
| − | == Requirements, Relationships and Content == | ||
</noinclude> | </noinclude> | ||
# Include the set of Reference Information Model (RIM) classes, attributes and associations that '''represent the information needed to support interoperability in''' the domain or project that this model will support. | # Include the set of Reference Information Model (RIM) classes, attributes and associations that '''represent the information needed to support interoperability in''' the domain or project that this model will support. | ||
Revision as of 18:45, 9 April 2011
Generic requirements for SAIF Information models. Only the content in black font will appear in the inclusion. These elements are intended to appear under the following section:
Requirements, Relationships and Content
- Include the set of Reference Information Model (RIM) classes, attributes and associations that represent the information needed to support interoperability in the domain or project that this model will support.
- RationaleRIM-derived Models must use the RIM content needed to support the interoperability project in question.
- 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.
