Foundations for the study of software architecture
ACM SIGSOFT Software Engineering Notes
Toward Reference Models for Requirements Traceability
IEEE Transactions on Software Engineering
The 4+1 View Model of Architecture
IEEE Software
Contribution structures [Requirements artifacts]
RE '95 Proceedings of the Second IEEE International Symposium on Requirements Engineering
Towards Modeling and Reasoning Support for Early-Phase Requirements Engineering
RE '97 Proceedings of the 3rd IEEE International Symposium on Requirements Engineering
Architecture Decisions: Demystifying Architecture
IEEE Software
Journal of Software Maintenance and Evolution: Research and Practice
Software Architecture as a Set of Architectural Design Decisions
WICSA '05 Proceedings of the 5th Working IEEE/IFIP Conference on Software Architecture
A web-based tool for managing architectural design decisions
ACM SIGSOFT Software Engineering Notes
A rationale-based architecture model for design traceability and reasoning
Journal of Systems and Software
A Tool for Managing Software Architecture Knowledge
SHARK-ADI '07 Proceedings of the Second Workshop on SHAring and Reusing architectural Knowledge Architecture, Rationale, and Design Intent
Software Engineering Using RATionale
Journal of Systems and Software
IEEE Software
Tracing architectural concerns in high assurance systems (NIER track)
Proceedings of the 33rd International Conference on Software Engineering
Tracing architectural concerns in high assurance systems (NIER track)
Proceedings of the 33rd International Conference on Software Engineering
Knowledge-based approaches in software documentation: A systematic literature review
Information and Software Technology
| Hi-index | 0.01 |
Architectural analysis processes, such as the Architecture Trade-off and Analysis Method (ATAM), utilize a scenario based approach to evaluate the extent to which an architectural solution meets a potentially competing set of quality goals. The resulting architectural documents contain a rich set of trace relationships between quality goals, decisions, and architectural elements. Unfortunately this information is not readily accessible for supporting tasks other than initial architectural assessments. In this paper we describe a technique and supporting tools for extracting and generating traceability links from the architectural documents. A specialized Traceability Information Model is used to guide the user through the task of establishing traceability links from design decisions to the architectural elements in which the decision is realized. The retrieved and generated traceability links can then be used to support a far broader set of activities including visualization of design rationale and architectural preservation. We evaluate our approach using a case study of the NASA Crew Exploration Vehicle.