This wiki has undergone a migration to Confluence found Here
SAEAF Constraint Pattern
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.
Specification | Enterprise / Business Viewpoint | Information Viewpoint | Computational Viewpoint | Engineering Viewpoint |
Reference | Reference - Business Jane | Reference - Informational Patrick | Reference - ComputationalJohn | N/A |
Analysis | Analysis - Business Jane | Analysis - Informational AMS | Analysis - Computational AMS/John | N/A |
Logical | Logical - Business Jane | Logical - Informational Cecil | Logical - Computational John | N/A |
Implementable | Implementable - Business Jane | Implementable - Informational | Implementable - Computational Dale | Implementable - 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.
- 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.