MARC details
| 000 -LEADER |
|---|
| fixed length control field |
04743nam a22004935i 4500 |
| 001 - CONTROL NUMBER |
|---|
| control field |
978-3-540-30998-7 |
| 003 - CONTROL NUMBER IDENTIFIER |
|---|
| control field |
DE-He213 |
| 005 - DATE AND TIME OF LATEST TRANSACTION |
|---|
| control field |
20160302162242.0 |
| 007 - PHYSICAL DESCRIPTION FIXED FIELD--GENERAL INFORMATION |
|---|
| fixed length control field |
cr nn 008mamaa |
| 008 - FIXED-LENGTH DATA ELEMENTS--GENERAL INFORMATION |
|---|
| fixed length control field |
100301s2006 gw | s |||| 0|eng d |
| 020 ## - INTERNATIONAL STANDARD BOOK NUMBER |
|---|
| International Standard Book Number |
9783540309987 |
| -- |
978-3-540-30998-7 |
| 024 7# - OTHER STANDARD IDENTIFIER |
|---|
| Standard number or code |
10.1007/978-3-540-30998-7 |
| Source of number or code |
doi |
| 050 #4 - LIBRARY OF CONGRESS CALL NUMBER |
|---|
| Classification number |
QA76.758 |
| 072 #7 - SUBJECT CATEGORY CODE |
|---|
| Subject category code |
UMZ |
| Source |
bicssc |
| 072 #7 - SUBJECT CATEGORY CODE |
|---|
| Subject category code |
COM051230 |
| Source |
bisacsh |
| 082 04 - DEWEY DECIMAL CLASSIFICATION NUMBER |
|---|
| Classification number |
005.1 |
| Edition number |
23 |
| 245 10 - TITLE STATEMENT |
|---|
| Title |
Rationale Management in Software Engineering |
| Medium |
[electronic resource] / |
| Statement of responsibility, etc. |
edited by Allen H. Dutoit, Raymond McCall, Ivan Mistrík, Barbara Paech. |
| 264 #1 - PRODUCTION, PUBLICATION, DISTRIBUTION, MANUFACTURE, AND COPYRIGHT NOTICE |
|---|
| Place of production, publication, distribution, manufacture |
Berlin, Heidelberg : |
| Name of producer, publisher, distributor, manufacturer |
Springer Berlin Heidelberg, |
| Date of production, publication, distribution, manufacture, or copyright notice |
2006. |
| 300 ## - PHYSICAL DESCRIPTION |
|---|
| Extent |
XXII, 434 p. |
| Other physical details |
online resource. |
| 336 ## - CONTENT TYPE |
|---|
| Content type term |
text |
| Content type code |
txt |
| Source |
rdacontent |
| 337 ## - MEDIA TYPE |
|---|
| Media type term |
computer |
| Media type code |
c |
| Source |
rdamedia |
| 338 ## - CARRIER TYPE |
|---|
| Carrier type term |
online resource |
| Carrier type code |
cr |
| Source |
rdacarrier |
| 347 ## - DIGITAL FILE CHARACTERISTICS |
|---|
| File type |
text file |
| Encoding format |
PDF |
| Source |
rda |
| 505 0# - FORMATTED CONTENTS NOTE |
|---|
| Formatted contents note |
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. |
| 520 ## - SUMMARY, ETC. |
|---|
| Summary, etc. |
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. |
| 650 #0 - SUBJECT ADDED ENTRY--TOPICAL TERM |
|---|
| Topical term or geographic name as entry element |
Computer science. |
| 650 #0 - SUBJECT ADDED ENTRY--TOPICAL TERM |
|---|
| Topical term or geographic name as entry element |
Software engineering. |
| 650 #0 - SUBJECT ADDED ENTRY--TOPICAL TERM |
|---|
| Topical term or geographic name as entry element |
Computers. |
| 650 #0 - SUBJECT ADDED ENTRY--TOPICAL TERM |
|---|
| Topical term or geographic name as entry element |
Management information systems. |
| 650 14 - SUBJECT ADDED ENTRY--TOPICAL TERM |
|---|
| Topical term or geographic name as entry element |
Computer Science. |
| 650 24 - SUBJECT ADDED ENTRY--TOPICAL TERM |
|---|
| Topical term or geographic name as entry element |
Software Engineering. |
| 650 24 - SUBJECT ADDED ENTRY--TOPICAL TERM |
|---|
| Topical term or geographic name as entry element |
Management of Computing and Information Systems. |
| 650 24 - SUBJECT ADDED ENTRY--TOPICAL TERM |
|---|
| Topical term or geographic name as entry element |
Models and Principles. |
| 700 1# - ADDED ENTRY--PERSONAL NAME |
|---|
| Personal name |
Dutoit, Allen H. |
| Relator term |
editor. |
| 700 1# - ADDED ENTRY--PERSONAL NAME |
|---|
| Personal name |
McCall, Raymond. |
| Relator term |
editor. |
| 700 1# - ADDED ENTRY--PERSONAL NAME |
|---|
| Personal name |
Mistrík, Ivan. |
| Relator term |
editor. |
| 700 1# - ADDED ENTRY--PERSONAL NAME |
|---|
| Personal name |
Paech, Barbara. |
| Relator term |
editor. |
| 710 2# - ADDED ENTRY--CORPORATE NAME |
|---|
| Corporate name or jurisdiction name as entry element |
SpringerLink (Online service) |
| 773 0# - HOST ITEM ENTRY |
|---|
| Title |
Springer eBooks |
| 776 08 - ADDITIONAL PHYSICAL FORM ENTRY |
|---|
| Relationship information |
Printed edition: |
| International Standard Book Number |
9783540309970 |
| 856 40 - ELECTRONIC LOCATION AND ACCESS |
|---|
| Uniform Resource Identifier |
<a href="http://dx.doi.org/10.1007/978-3-540-30998-7">http://dx.doi.org/10.1007/978-3-540-30998-7</a> |
| 912 ## - |
|---|
| -- |
ZDB-2-SCS |
