Creativity and rationale in software design
ACM SIGSOFT Software Engineering Notes
Special issue: Design rationale
Artificial Intelligence for Engineering Design, Analysis and Manufacturing
Design rationale: Researching under uncertainty
Artificial Intelligence for Engineering Design, Analysis and Manufacturing
Using rationale to support pattern-based architectural design
Proceedings of the 2010 ICSE Workshop on Sharing and Reusing Architectural Knowledge
Architectural decision modeling with reuse: challenges and opportunities
Proceedings of the 2010 ICSE Workshop on Sharing and Reusing Architectural Knowledge
HCSE'10 Proceedings of the Third international conference on Human-centred software engineering
Abstract state machines and the inquiry process
Fields of logic and computation
Using rationale to drive product line architecture configuration
Proceedings of the 6th International Workshop on SHAring and Reusing Architectural Knowledge
Exploring techniques for rationale extraction from existing documents
Proceedings of the 34th International Conference on Software Engineering
Facilitating communication between engineers with CARES
Proceedings of the 34th International Conference on Software Engineering
Documenting and sharing knowledge about code
Proceedings of the 34th International Conference on Software Engineering
Seeing the forest and the trees: focusing team interaction on value and effort drivers
Proceedings of the ACM SIGSOFT 20th International Symposium on the Foundations of Software Engineering
Requirements sensemaking using concept maps
HCSE'12 Proceedings of the 4th international conference on Human-Centered Software Engineering
The value of design rationale information
ACM Transactions on Software Engineering and Methodology (TOSEM) - In memoriam, fault detection and localization, formal methods, modeling and design
Traceability and SysML design slices to support safety inspections: A controlled experiment
ACM Transactions on Software Engineering and Methodology (TOSEM)
Hi-index | 0.00 |
Many decisions are required throughout the software development process. These decisions, and to some extent the decision-making process itself, can best be documented as the rationale for the system, which will reveal not only what was done during development but the reasons behind the choices made and alternatives considered and rejected. This information becomes increasingly critical as software development becomes more distributed and encompasses the corporate knowledge both used and refined during the development process. The capture of rationale helps to ensure that decisions are well thought out and justified and the use of rationale can help avoid the mistakes of the past during both the development of the current system and when software products (architecture and design, as well as code) are reused in future systems. Burge, Carroll, McCall, and Mistrk describe in detail the capture and use of design rationale in software engineering to improve the quality of software. Their book is the firs t comprehensive and unified treatment of rationale usage in software engineering. It provides a consistent conceptual framework and a unified terminology for comparing, contrasting and combining the myriad approaches to rationale in software engineering. It is both an excellent introductory text for those new to the field and a uniquely valuable reference for experienced rationale researchers. The book covers the use of rationale for decision making throughout the software lifecycle, starting from the first decisions in a project and continuing through requirements definition, design, implementation, testing, maintenance, redesign and reuse.