|
|
|
|
| LEADER |
04291nmm a2200349 u 4500 |
| 001 |
EB000374629 |
| 003 |
EBX01000000000000000227681 |
| 005 |
00000000000000.0 |
| 007 |
cr||||||||||||||||||||| |
| 008 |
130626 ||| eng |
| 020 |
|
|
|a 9783540309987
|
| 100 |
1 |
|
|a Dutoit, Allen H.
|e [editor]
|
| 245 |
0 |
0 |
|a Rationale Management in Software Engineering
|h Elektronische Ressource
|c edited by Allen H. Dutoit, Raymond McCall, Ivan Mistrik, Barbara Paech
|
| 250 |
|
|
|a 1st ed. 2006
|
| 260 |
|
|
|a Berlin, Heidelberg
|b Springer Berlin Heidelberg
|c 2006, 2006
|
| 300 |
|
|
|a XXII, 434 p
|b online resource
|
| 505 |
0 |
|
|a 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
|
| 653 |
|
|
|a Models of Computation
|
| 653 |
|
|
|a Software engineering
|
| 653 |
|
|
|a Computer science
|
| 653 |
|
|
|a Software Engineering
|
| 653 |
|
|
|a Electronic data processing / Management
|
| 653 |
|
|
|a IT Operations
|
| 700 |
1 |
|
|a McCall, Raymond
|e [editor]
|
| 700 |
1 |
|
|a Mistrik, Ivan
|e [editor]
|
| 700 |
1 |
|
|a Paech, Barbara
|e [editor]
|
| 041 |
0 |
7 |
|a eng
|2 ISO 639-2
|
| 989 |
|
|
|b Springer
|a Springer eBooks 2005-
|
| 028 |
5 |
0 |
|a 10.1007/978-3-540-30998-7
|
| 856 |
4 |
0 |
|u https://doi.org/10.1007/978-3-540-30998-7?nosfx=y
|x Verlag
|3 Volltext
|
| 082 |
0 |
|
|a 005.1
|
| 520 |
|
|
|a 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 want something other than an alphabetic list of function definitions was just taking hold. There was an exciting (to me) vision of stakeholders accessing and contributing to explanations of how and why aspects of a system work as they do, tradeoff analysis of concomitant downsides, and perhaps even accounts of why other possible approaches were not followed. There were many challenges to overcome in achieving this vision. The most formidable is the belief that people do not like to create or use do- mentation. This negative image of documentation is (unfortunately) more than just the bias of a few incorrigible system developers. It is more like a deep truth about human information behavior, about how human beings construe and act towards information. Humans are, by default, active users of information; they want to try things out, and get things done. When documentation is interposed as a prerequisite between people and a desired activity, they try to skip through it, circumvent it, or undermine it. Desi- ing information to suit the needs and interests of its users is an abiding challenge, but we have come a long way from functional specifications as the only answer
|