Includes bibliographical references and index.

Rationale Management in Software Engineering: Concepts and Techniques. Part 1 Fundamentals - Rationale Representation, Capture and Use.Three Studies of Design Rationale as Explanation - Effective Design Rationale: Understanding the Barriers - Rationale as a By-Product - Hypermedia Support for Argumentation-Based Rationale: 15 Years on from gIBIS and QOC. Part 2 Rationale Management for Requirements Engineering. A Hybrid Approach to Upstream Requirements: IBIS and Cognitive Mapping - From DREAM to Reality: Specificities of Interactive Systems Development with respect to Rationale Management - The WinWin Approach: Using a Requirements Negotiation Tool for Rationale Capture and Use - Design Rationale in Exemplary Business Process Modeling - Promotion and Supporting Requirements Engineering Creativity. Part 3 Design Rationale and Software Architecting. A Framework for Supporting Architecture Knowledge and Rationale Management - Capturing and Using Rationale for a Software Architecture - Rationale-based Support for Software Maintance - The Role of Rationale in the Design of Product Line Architectures - The Role and Impact of Assumptions in Software Engineering and its Products - Design Decisions: The Bridge between Rationale and Architecture. Part 4 Rationale for Organizing Bodies of Knowledge. Reusable Rationale Blocks: Improving Quality and Efficiency of Design Choices - Defining Agile Patterns - Capturing and Reusing Rationale Associated with Requirements Engineering Process Improvement - Using Patterns for Sharing Requirements Engineering Process Rationales. Index.

The emphasis on new and changing technologies and process models in today's software development obscures the fact that software engineering is still primarily a human-based activity and that the success of a software project largely depends on the decisions made by humans during engineering. Rationale management is concerned with making these design and development decisions explicit to all stakeholders involved. Dutoit, McCall, Mistrik and Paech begin their book with a historical survey of different rationale approaches. It is followed by four parts describing: the fundamental problems and possible solution approaches in rationale management, rationale management during requirements engineering, rationale management during software architecting, and rationale management for organizing reusable bodies of knowledge. The result is a detailed summary of research on design rationale. It provides researchers with an excellent state-of-the-art overview, and professional software engineers will find many examples, resources and incentives to enhance their ability to make decisions during all phases of the software lifecycle. 'Allen Dutoit, Ray McCall, Ivan Mistrik and Barbara Paech have done an excellent job of this in Rationale management in software engineering. The chapters in this volume show how design rationale can be incorporated into the heart of the software development process - into requirements engineering, software architecture, and code design' - John M. Carroll, Edward M. Frymoyer Professor of Information Sciences and Technology, Penn State University, USA, ACM CHI Lifetime Achievement Award.