Difference between revisions of "Saeaf specification stack"
m |
|||
| (6 intermediate revisions by 3 users not shown) | |||
| Line 1: | Line 1: | ||
| + | {{Arb work in progress}} | ||
''' Detail of the Specification Specification Stack and Constraint Pattern''' | ''' Detail of the Specification Specification Stack and Constraint Pattern''' | ||
Choose a square or three, then document it. | Choose a square or three, then document it. | ||
| − | the author is to the left of the /, the reviewer to the right. | + | ''Use the content of the "Conceptual - Computational" cell as a template/guideline for content.'' |
| + | |||
| + | The author is to the left of the /, the reviewer to the right. | ||
<table border=1> | <table border=1> | ||
<tr><td>[[Specification - Topic | Specification]]</td><td>Enterprise / Business Viewpoint</td><td>Information Viewpoint</td><td>Computational Viewpoint</td><td>Engineering Viewpoint</td></tr> | <tr><td>[[Specification - Topic | Specification]]</td><td>Enterprise / Business Viewpoint</td><td>Information Viewpoint</td><td>Computational Viewpoint</td><td>Engineering Viewpoint</td></tr> | ||
| − | <tr><td>[[Specification - Reference | Reference]]</td><td>[[Reference - Business]] ''Jane''</td><td>[[Reference - Informational]] ''Patrick''</td><td>[[Reference - Computational]]''John''</td><td>[[N/A]]</td></tr> | + | <tr><td>[[Specification - Reference | Reference]]</td><td>[[Reference - Business]] ''Jane''</td><td>[[Reference - Informational]] ''Patrick''</td><td>[[Reference - Computational]]''John''/''Dale''</td><td>[[N/A]]</td></tr> |
| − | <tr><td>[[Specification - Conceptual | Conceptual ]]</td><td>[[ | + | <tr><td>[[Specification - Conceptual | Conceptual ]]</td><td>[[Conceptual - Business]] ''Jane''</td><td>[[Conceptual - Informational]] ''AMS/Wendell''</td><td>[[Conceptual - Computational]] ''AMS''/John</td><td>[[N/A]]</td></tr> |
| − | <tr><td>[[Specification - Platform-Independent | Platform-Independent]]</td><td>[[ | + | <tr><td>[[Specification - Platform-Independent | Platform-Independent]]</td><td>[[Platform-Independent - Business]] ''Jane''</td><td>[[Platform-Independent - Informational]] ''Cecil/Wendell''</td><td>[[Platform-Independent - Computational]] ''John''/''Dale''</td><td>[[N/A]]</td></tr> |
| − | <tr><td>[[Specification - Platform-Specific | Platform-Specific]]</td><td>[[ | + | <tr><td>[[Specification - Platform-Specific | Platform-Specific]]</td><td>[[Platform-Specific - Business]] ''Jane''/''Dale''</td><td>[[Platform-Specific - Informational]] ''Wendell''</td><td>[[Platform-Specific - Computational]] ''Dale''/''Tony''</td><td>[[Platform-Specific - Engineering]]</td></tr> |
</table> | </table> | ||
| − | '' | + | '''The Specification Stack''' |
| + | Relationships between artifacts emerging from cells in the same column is one of "traceability". Artifacts from the Conceptual row must be traceable to equivalent reference artifacts, Platform-Independent artifacts must be traceable to their associated Conceptual artifacts, and Platform-Specific designs must be traceable to their Platform-Independent equivalents. Note that in fact, one Conceptual Specification can yield multiple Platform-Independent variations, and a single Platform-Independent specification can yield multiple Platform-Specific variations. | ||
| − | + | 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, whether that is done in an automated fashion or in a human-mediated fashion. With that consideration, it is worth noting that in some cases, artifacts at a lower level 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. | |
| − | |||
| − | ''The | + | '''Topics''' |
| − | + | The ''Topic'' is the primary piece of metadata that is relevant to a particular Specification Stack. It provides the central focus of all specification and standardization efforts, and insures some alignment between domain concepts and organizational implementations. | |
| − | The | + | '''Consistency between cells''' |
| + | There are relationships between artifacts from the various cells at each row except the reference row. 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 Conceptual level, through the Platform-Indeppendent and Platform-Specific levels. (Note: Some reference artifacts do need to have a consistency relationship with each other, but they are not topic specific, and are not enforeceable through governance of this pattern. They are enforced through organizational governance.) | ||
| + | [[Category:ARB_work_in_progress]] | ||
Latest revision as of 18:25, 22 March 2010
Detail of the Specification Specification Stack and Constraint Pattern
Choose a square or three, then document it.
Use the content of the "Conceptual - Computational" cell as a template/guideline for content.
The author is to the left of the /, the reviewer to the right.
| Specification | Enterprise / Business Viewpoint | Information Viewpoint | Computational Viewpoint | Engineering Viewpoint |
| Reference | Reference - Business Jane | Reference - Informational Patrick | Reference - ComputationalJohn/Dale | N/A |
| Conceptual | Conceptual - Business Jane | Conceptual - Informational AMS/Wendell | Conceptual - Computational AMS/John | N/A |
| Platform-Independent | Platform-Independent - Business Jane | Platform-Independent - Informational Cecil/Wendell | Platform-Independent - Computational John/Dale | N/A |
| Platform-Specific | Platform-Specific - Business Jane/Dale | Platform-Specific - Informational Wendell | Platform-Specific - Computational Dale/Tony | Platform-Specific - Engineering |
The Specification Stack Relationships between artifacts emerging from cells in the same column is one of "traceability". Artifacts from the Conceptual row must be traceable to equivalent reference artifacts, Platform-Independent artifacts must be traceable to their associated Conceptual artifacts, and Platform-Specific designs must be traceable to their Platform-Independent equivalents. Note that in fact, one Conceptual Specification can yield multiple Platform-Independent variations, and a single Platform-Independent specification can yield multiple Platform-Specific variations.
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, whether that is done in an automated fashion or in a human-mediated fashion. With that consideration, it is worth noting that in some cases, artifacts at a lower level 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.
Topics The Topic is the primary piece of metadata that is relevant to a particular Specification Stack. It provides the central focus of all specification and standardization efforts, and insures some alignment between domain concepts and organizational implementations.
Consistency between cells There are relationships between artifacts from the various cells at each row except the reference row. 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 Conceptual level, through the Platform-Indeppendent and Platform-Specific levels. (Note: Some reference artifacts do need to have a consistency relationship with each other, but they are not topic specific, and are not enforeceable through governance of this pattern. They are enforced through organizational governance.)
