IDEF6: A Design Rationale Capture Method Concept Paper
Interim rept. Jan 1990-Mar 1991
TEXAS A AND M UNIV COLLEGE STATION KNOWLEDGE BASED SYSTEMS LAB
Pagination or Media Count:
When explicitly captured, design rationale typically exists in the form of unstructured textual comments. In addition to making it difficult, if not impossible to find relevant information on demand, lack of a structured method for organizing and providing completeness criteria for design rationale capture makes it unlikely that important information will be documented. Unlike design methods which serve to document WHAT a design is Design Specification, the IDEF6 Design Rationale Capture Method is targeted at capturing WHY a design is the way it is -- or WHY it is not manifested in some other form -- together with HOW the final design configuration was reached. IDEF6 was intended to be a method with the representational capability to capture information system design rationale and associate that rationale with the design models and documentation for the end system. Thus, IDEF6 attempts to capture the logic underlying the decisions contributing to, or resulting in, the final design. The explicit capture of design rationale serves to help avoid repeating past mistakes, provides a direct means for determining the impact of proposed design changes, forces the explicit statement of goals and assumptions, and aids in the communication of final system specifications. IDEF, Knowledge acquisition, Design, Information engineering, Method, Design rational, Integration, Systems engineering.
- Computer Systems