Rationale Management in Software Engineering
Thirty years ago, I first entered the dark realm of software engineering, through a prior interest in documentation. In those days, documentation pretty much meant functional specifications. The idea that stakeholders in a system (its implementers, its end-users, its maintainers, and so forth) might...
| Συγγραφή απο Οργανισμό/Αρχή: | |
|---|---|
| Άλλοι συγγραφείς: | , , , |
| Μορφή: | Ηλεκτρονική πηγή Ηλ. βιβλίο |
| Γλώσσα: | English |
| Έκδοση: |
Berlin, Heidelberg :
Springer Berlin Heidelberg,
2006.
|
| Θέματα: | |
| Διαθέσιμο Online: | Full Text via HEAL-Link |
Πίνακας περιεχομένων:
- Fundamentals – Rationale Representation, Capture, and Use
- Rationale Management in Software Engineering: Concepts and Techniques
- Three Studies of Design Rationale as Explanation
- Effective Design Rationale: Understanding the Barriers
- Rationale as a By-Product
- Hypermedia Support for Argumentation-Based Rationale
- 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
- Promoting and Supporting Requirements Engineering Creativity
- 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 Maintenance
- The Role of Rationale in the Design of Product Line Architectures – A Case Study from Industry
- The Role and Impact of Assumptions in Software Engineering and its Products
- Design Decisions: The Bridge between Rationale and Architecture
- 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: A Case Study
- Using Patterns for Sharing Requirements Engineering Process Rationales.
