000 04743nam a22004935i 4500
001 978-3-540-30998-7
003 DE-He213
005 20160302162242.0
007 cr nn 008mamaa
008 100301s2006 gw | s |||| 0|eng d
020 _a9783540309987
_9978-3-540-30998-7
024 7 _a10.1007/978-3-540-30998-7
_2doi
050 4 _aQA76.758
072 7 _aUMZ
_2bicssc
072 7 _aCOM051230
_2bisacsh
082 0 4 _a005.1
_223
245 1 0 _aRationale Management in Software Engineering
_h[electronic resource] /
_cedited by Allen H. Dutoit, Raymond McCall, Ivan Mistrík, Barbara Paech.
264 1 _aBerlin, Heidelberg :
_bSpringer Berlin Heidelberg,
_c2006.
300 _aXXII, 434 p.
_bonline resource.
336 _atext
_btxt
_2rdacontent
337 _acomputer
_bc
_2rdamedia
338 _aonline resource
_bcr
_2rdacarrier
347 _atext file
_bPDF
_2rda
505 0 _aFundamentals – 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.
520 _aThirty 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.
650 0 _aComputer science.
650 0 _aSoftware engineering.
650 0 _aComputers.
650 0 _aManagement information systems.
650 1 4 _aComputer Science.
650 2 4 _aSoftware Engineering.
650 2 4 _aManagement of Computing and Information Systems.
650 2 4 _aModels and Principles.
700 1 _aDutoit, Allen H.
_eeditor.
700 1 _aMcCall, Raymond.
_eeditor.
700 1 _aMistrík, Ivan.
_eeditor.
700 1 _aPaech, Barbara.
_eeditor.
710 2 _aSpringerLink (Online service)
773 0 _tSpringer eBooks
776 0 8 _iPrinted edition:
_z9783540309970
856 4 0 _uhttp://dx.doi.org/10.1007/978-3-540-30998-7
912 _aZDB-2-SCS
999 _c176352
_d176352