Atjaunināt sīkdatņu piekrišanu

E-grāmata: Rationale Management in Software Engineering

4.00/5 (2 ratings by Goodreads)
Edited by , Edited by , Edited by , Edited by
  • Formāts: PDF+DRM
  • Izdošanas datums: 02-Feb-2007
  • Izdevniecība: Springer-Verlag Berlin and Heidelberg GmbH & Co. K
  • Valoda: eng
  • ISBN-13: 9783540309987
Citas grāmatas par šo tēmu:
  • Formāts - PDF+DRM
  • Cena: 106,47 €*
  • * ši ir gala cena, t.i., netiek piemērotas nekādas papildus atlaides
  • Ielikt grozā
  • Pievienot vēlmju sarakstam
  • Šī e-grāmata paredzēta tikai personīgai lietošanai. E-grāmatas nav iespējams atgriezt un nauda par iegādātajām e-grāmatām netiek atmaksāta.
Rationale Management in Software EngineeringPalielināt
  • Formāts: PDF+DRM
  • Izdošanas datums: 02-Feb-2007
  • Izdevniecība: Springer-Verlag Berlin and Heidelberg GmbH & Co. K
  • Valoda: eng
  • ISBN-13: 9783540309987
Citas grāmatas par šo tēmu:

DRM restrictions

  • Kopēšana (kopēt/ievietot):

    nav atļauts

  • Drukāšana:

    nav atļauts

  • Lietošana:

    Digitālo tiesību pārvaldība (Digital Rights Management (DRM))
    Izdevējs ir piegādājis šo grāmatu šifrētā veidā, kas nozīmē, ka jums ir jāinstalē bezmaksas programmatūra, lai to atbloķētu un lasītu. Lai lasītu šo e-grāmatu, jums ir jāizveido Adobe ID. Vairāk informācijas šeit. E-grāmatu var lasīt un lejupielādēt līdz 6 ierīcēm (vienam lietotājam ar vienu un to pašu Adobe ID).

    Nepieciešamā programmatūra
    Lai lasītu šo e-grāmatu mobilajā ierīcē (tālrunī vai planšetdatorā), jums būs jāinstalē šī bezmaksas lietotne: PocketBook Reader (iOS / Android)

    Lai lejupielādētu un lasītu šo e-grāmatu datorā vai Mac datorā, jums ir nepieciešamid Adobe Digital Editions (šī ir bezmaksas lietotne, kas īpaši izstrādāta e-grāmatām. Tā nav tas pats, kas Adobe Reader, kas, iespējams, jau ir jūsu datorā.)

    Jūs nevarat lasīt šo e-grāmatu, izmantojot Amazon Kindle.

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.

Recenzijas

Ten years ago, with Tom Moran, I edited a book entitled "Design Rationale." I think that book has held up quite well, though a decade onward it does seem a bit prefatory. It is past time for another detailed summary of research on design rationale. Allen Dutoit, Ray McCall, Ivan Mistrik and Barbara Paech have done an excellent job of this in "Rationale management in software engineering." The chapters in this volume show how design rationale can be incorporated into the heart of the software development process - into requirements engineering, software architecture, and code design. (John Carroll, School of Information Sciences and Technology, Penn State University, USA)

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.
Biežāk uzdotie jautājumi par e-grāmatām Biežāk uzdotie jautājumi par e-grāmatām
Permanent link: https://www.kriso.lv/db/97835403099872e.html
Keywords: