This wiki has undergone a migration to Confluence found Here
<meta name="googlebot" content="noindex">

SAEAF Constraint Pattern

From HL7Wiki
Revision as of 22:22, 13 March 2009 by Ocasiw01 (talk | contribs)
Jump to navigation Jump to search

Detail of the Specification Constraint Pattern

Choose a square or three, then document it.

the author is to the left of the /, the reviewer to the right.

SpecificationEnterprise / Business ViewpointInformation ViewpointComputational ViewpointEngineering Viewpoint
Reference Reference - Business JaneReference - Informational PatrickReference - ComputationalJohnN/A
Analysis Analysis - Business JaneAnalysis - Informational AMS/WendellAnalysis - Computational AMS/JohnN/A
Logical Logical - Business JaneLogical - Informational Cecil/WendellLogical - Computational JohnN/A
ImplementableImplementable - Business JaneImplementable - Informational WendellImplementable - Computational DaleImplementable - Engineering
  • There are relationships between the various cells. The primary relationship between cells on the same row is one of "consistency". In other words, artifacts for the same "topic" must be consistent with each other across the row. This applies primarily from the Analysis level, through the Logical and Implementation levels. Some reference artifacts do need to have a consistency relationship with each other, but they are not topic specific.
  • Relationships between cells in the same column is one of "traceability". Artifacts from the Analysis row must be traceable to equivalent reference artifacts, Logical artifacts must be traceable to their associated Analysis artifacts and Implementable designs must be traceable to their logical equivalents. The term "traceability" is used to mean the ability to confirm that the source of the semantics expressed at one level is derived from the level above. In some cases, artifacts at a lower are algorithmically transformed from equivalent artifacts from the row above. Therefore, the term "traceability" also implies "transformed from" where such algorithmic conversions are possible. Model driven design gains it's productivity and re-usability from such transformations.