Rationale Management in Software Engineering

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.