A value-based approach for documenting design decisions rationale: a replicated experiment
Proceedings of the 3rd international workshop on Sharing and reusing architectural knowledge
Automating the Trace of Architectural Design Decisions and Rationales Using a MDD Approach
ECSA '08 Proceedings of the 2nd European conference on Software Architecture
Applying empirical software engineering to software architecture: challenges and lessons learned
Empirical Software Engineering
Decision-making techniques for software architecture design: A comparative survey
ACM Computing Surveys (CSUR)
Traceability and SysML design slices to support safety inspections: A controlled experiment
ACM Transactions on Software Engineering and Methodology (TOSEM)
| Hi-index | 0.00 |
The explicit documentation of the rationale of design decisions is a practice generally encouraged, but rarely implemented in industry because of a variety of inhibitors. Methods proposed in the past for Design Decisions Rationale Documentation (DDRD) aimed to maximize benefits for the DDRD consumer by imposing on the producer of DDRD the burden to document all the potentially useful information. We propose here a compromise which consists in tailoring DDRD, based on its intended use or purpose. In our view, the adoption of a tailored DDRD, consisting only of the required set of information, would mitigate the effects of DDRD inhibitors. The aim of this paper is twofold: i) to discuss the application of Value-Based Software Engineering principles to DDRD, ii) to describe a controlled experiment to empirically analyze the feasibility of the proposed method. Results show that the level of utility related to the same category of DDRD information significantly changes depending on its purpose; such result is novel and it demonstrates the feasibility of the proposed value-based DDRD.