Capturing and reusing rationale associated with requirements engineering process improvement: a case study
- B. Palyagar, D. Richards
- In Rationale Management in Software Engineering
Rationale research in software development is a challenging area because while there is no shortage of advocates for its value, there is also no shortage of reasons for why rationale is unlikely to be captured in practice. Despite more than thirty years of research there still remains much uncertainty—how useful are the potential benefits and how insurmountable are the barriers? Will the value of the rationale (design and otherwise) justify the cost of collecting it? While there have been numerous rationale research projects, many, if not most, received little or no empirical evaluation. There also have not been many studies examining what the needs are of the practitioners who would be supported by the rationale. This paper discusses the “doom and gloom” predictions of rationale’s failure, provides a survey of evaluations of rationale systems, and discusses what we hope is a brighter outlook for rationale research in the future. There are development standards and synergistic research areas that may help with rationale research and its acceptance in the software community that we should be working with. This paper also presents the results of a pilot survey of software developers who were asked how they would envision using rationale and what they believe the most important barriers are. While some results were as expected, there were some surprises too. Research on technology transfer indicates that, among other things, to transition successfully from research into practice we need to understand the need that is being met and demonstrate the value of our approach. Until we have determined how our work is needed by the people we are trying to help we will remain researching under uncertainty.