A web-based tool for managing architectural design decisions
ACM SIGSOFT Software Engineering Notes
Using Bayesian belief networks for change impact analysis in architecture design
Journal of Systems and Software
Collaboration in Software Engineering: A Roadmap
FOSE '07 2007 Future of Software Engineering
Modeling and Documenting the Evolution of Architectural Design Decisions
SHARK-ADI '07 Proceedings of the Second Workshop on SHAring and Reusing architectural Knowledge Architecture, Rationale, and Design Intent
Documenting after the fact: Recovering architectural design decisions
Journal of Systems and Software
Multi-tiered design rationale for change set based product line architectures
Proceedings of the 3rd international workshop on Sharing and reusing architectural knowledge
Extending Software Architecting Processes with Decision-Making Activities
Balancing Agility and Formalism in Software Engineering
On the Role of Architectural Design Decisions in Software Product Line Engineering
ECSA '08 Proceedings of the 2nd European conference on Software Architecture
Enriching software architecture documentation
Journal of Systems and Software
Effort Estimation in Capturing Architectural Knowledge
ASE '08 Proceedings of the 2008 23rd IEEE/ACM International Conference on Automated Software Engineering
Viability for codifying and documenting architectural design decisions with tool support
Journal of Software Maintenance and Evolution: Research and Practice
Reusable architectural decision models for enterprise application development
QoSA'07 Proceedings of the Quality of software architectures 3rd international conference on Software architectures, components, and applications
Architectural knowledge: getting to the core
QoSA'07 Proceedings of the Quality of software architectures 3rd international conference on Software architectures, components, and applications
QoSA'07 Proceedings of the Quality of software architectures 3rd international conference on Software architectures, components, and applications
Component-based specification of software architecture constraints
Proceedings of the 14th international ACM Sigsoft symposium on Component based software engineering
On-Demand quality-oriented assistance in component-based software evolution
CBSE'06 Proceedings of the 9th international conference on Component-Based Software Engineering
Architectural decision identification in architectural patterns
Proceedings of the WICSA/ECSA 2012 Companion Volume
Processes for creating and exploiting architectural design decisions with tool support
ECSA'07 Proceedings of the First European conference on Software Architecture
Towards architecture-centric evolution of long-living systems (the ADVERT approach)
Proceedings of the 9th international ACM Sigsoft conference on Quality of software architectures
ECSA'13 Proceedings of the 7th European conference on Software Architecture
Knowledge-based approaches in software documentation: A systematic literature review
Information and Software Technology
Hi-index | 0.00 |
Many claims have been made about the problems caused by not documenting design rationale. The general perception is that designers and architects usually do not fully understand the critical role of systematic use and capture of design rationale. However, there is to date little empirical evidence available on what design rationale mean to practitioners, how valuable they consider them, and how they use and document design rationale during the design process. This paper reports an empirical study that surveyed practitioners to probe their perception of the value of design rationale and how they use and document background knowledge related to their design decisions. Based on eighty-one valid responses, this study has discovered that practitioners recognize the importance of documenting design rationale and frequently use them to reason about their design choices. However, they have indicated barriers to the use and documentation of design rationale. Based on the findings, we conclude that much research is needed to develop methodology and tool support for design rationale capture and usage. Furthermore, we put forward some research questions that would benefit from further investigation into design rationale in order to support practice in industry.