Theory-W Software Project Management Principles and Examples
IEEE Transactions on Software Engineering
SIBYL: A qualitative decision management system
Artificial intelligence at MIT expanding frontiers
Using design history systems for technology transfer
Proceedings of the MIT-JSME workshop on Computer-aided cooperative product development
Supporting Systems Development by Capturing Deliberations During Requirements Engineering
IEEE Transactions on Software Engineering - Special issue on knowledge representation and reasoning in software development
Getting around the task-artifact cycle: how to make claims and design by scenario
ACM Transactions on Information Systems (TOIS)
Inquiry-Based Requirements Analysis
IEEE Software
Argumentation-based design rationale: what use at what cost?
International Journal of Human-Computer Studies
An empirical evaluation of design rationale documents
Proceedings of the SIGCHI Conference on Human Factors in Computing Systems
Design rationale: concepts, techniques, and use
Design rationale: concepts, techniques, and use
Questions, options, and criteria: elements of design space analysis
Design rationale
Making argumentation serve design
Design rationale
A process-oriented approach to design rationale
Design rationale
Evaluating opportunities for design capture
Design rationale
Automated capture of rationale for the detailed design process
AAAI '99/IAAI '99 Proceedings of the sixteenth national conference on Artificial intelligence and the eleventh Innovative applications of artificial intelligence conference innovative applications of artificial intelligence
Software technology maturation
ICSE '85 Proceedings of the 8th international conference on Software engineering
From MCC and CMM: technology transfers bright and dim
Proceedings of the 22nd international conference on Software engineering
A generic model for reflective design
ACM Transactions on Software Engineering and Methodology (TOSEM)
Applying WinWin to quality requirements: a case study
ICSE '01 Proceedings of the 23rd International Conference on Software Engineering
Making Use: Scenario-Based Design of Human-Computer Interactions
Making Use: Scenario-Based Design of Human-Computer Interactions
Representing and Maintaining Process Knowledge for Large-Scale Systems Development
IEEE Expert: Intelligent Systems and Their Applications
PROFES '00 Proceedings of the Second International Conference on Product Focused Software Process Improvement
Capturing Geometry Rationale for Collaborative Design
WET-ICE '97 Proceedings of the 6th Workshop on Enabling Technologies on Infrastructure for Collaborative Enterprises
Design History Systems: Data Models & Prototype Implementation
Proceedings of the IFIP TC5 WG5.2 Third Workshop on Knowledge Intensive CAD
Design Pattern Rationale Graphs: linking design to source
Proceedings of the 25th International Conference on Software Engineering
Integrating software process models and design rationales
KBSE '96 Proceedings of The 11th Knowledge-Based Software Engineering Conference
An evaluation of inquiry-based requirements analysis for an Internet service
RE '95 Proceedings of the Second IEEE International Symposium on Requirements Engineering
Using Rationale for Software Engineering Education
CSEET '05 Proceedings of the 18th Conference on Software Engineering Education & Training
Rationale Management in Software Engineering
Rationale Management in Software Engineering
Technology transfer: why some succeed and some don't
Proceedings of the 2006 international workshop on Software technology transfer in software engineering
Houston, we have a success story: technology transfer at the NASA IV&V facility
Proceedings of the 2006 international workshop on Software technology transfer in software engineering
Proceedings of the 2006 ACM/IEEE international symposium on Empirical software engineering
A version-aware tool for design rationale
WebMedia '06 Proceedings of the 12th Brazilian Symposium on Multimedia and the web
A survey of architecture design rationale
Journal of Systems and Software
A rationale-based architecture model for design traceability and reasoning
Journal of Systems and Software
Rationale-Based Software Engineering
Rationale-Based Software Engineering
Kuaba ontology: design rationale representation and reuse in model-based designs
ER'05 Proceedings of the 24th international conference on Conceptual Modeling
Creativity and rationale in software design
ACM SIGSOFT Software Engineering Notes
Reflective design documentation
Proceedings of the Designing Interactive Systems Conference
A mixed-method approach for the empirical evaluation of the issue-based variability modeling
Journal of Systems and Software
Advanced Engineering Informatics
Hi-index | 0.00 |
Rationale research in software development is a challenging area because although 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 30 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? Although 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 article 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 with which we should be working. This article 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. Although some results were as expected, there were also some surprises. 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.