This wiki has undergone a migration to Confluence found Here
Difference between revisions of "Saeaf specification stack"
Jump to navigation
Jump to search
(New page: ''' 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. <table border=1> <tr><td...) |
|||
| Line 1: | Line 1: | ||
| − | ''' Detail of the Specification 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. | ||
| Line 6: | Line 6: | ||
<table border=1> | <table border=1> | ||
| − | <tr><td>Specification</td><td>Enterprise / Business Viewpoint</td><td>Information Viewpoint</td><td>Computational Viewpoint</td><td>Engineering Viewpoint</td></tr> | + | <tr><td>Specification [[Specification - Topic]]</td><td>Enterprise / Business Viewpoint</td><td>Information Viewpoint</td><td>Computational Viewpoint</td><td>Engineering Viewpoint</td></tr> |
| − | <tr><td>Reference | + | <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> | + | <tr><td>[[Specification - Conceptual | Conceptual ]]</td><td>[[Analysis - Business]] ''Jane''</td><td>[[Analysis - Informational]] ''AMS/Wendell''</td><td>[[Analysis - Computational]] ''AMS''/John</td><td>[[N/A]]</td></tr> |
| − | <tr><td> | + | <tr><td>[[Specification - Platform-Independent | Platform-Independent]]</td><td>[[Logical - Business]] ''Jane''</td><td>[[Logical - Informational]] ''Cecil/Wendell''</td><td>[[Logical - Computational]] ''John''</td><td>[[N/A]]</td></tr> |
| − | <tr><td> | + | <tr><td>[[Specification - Platform-Specific | Platform-Specific]]</td><td>[[Implementable - Business]] ''Jane''</td><td>[[Implementable - Informational]] ''Wendell''</td><td>[[Implementable - Computational]] ''Dale''</td><td>[[Implementable - Engineering]]</td></tr> |
</table> | </table> | ||
| + | |||
| + | Topics | ||
| + | |||
| + | The Specification Stack | ||
| + | |||
| + | Consistency between cells | ||
| + | |||
| + | |||
* 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. | * 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. | * 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. | ||
Revision as of 15:37, 2 April 2009
Detail of the Specification Specification Stack and Constraint Pattern
Choose a square or three, then document it.
the author is to the left of the /, the reviewer to the right.
| Specification Specification - Topic | Enterprise / Business Viewpoint | Information Viewpoint | Computational Viewpoint | Engineering Viewpoint |
| Reference | Reference - Business Jane | Reference - Informational Patrick | Reference - ComputationalJohn | N/A |
| Conceptual | Analysis - Business Jane | Analysis - Informational AMS/Wendell | Analysis - Computational AMS/John | N/A |
| Platform-Independent | Logical - Business Jane | Logical - Informational Cecil/Wendell | Logical - Computational John | N/A |
| Platform-Specific | Implementable - Business Jane | Implementable - Informational Wendell | Implementable - Computational Dale | Implementable - Engineering |
Topics
The Specification Stack
Consistency between cells
- 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.
