000			03977nam a22003975i 4500
001			298262
003			MX-SnUAN
005			20160429155456.0
007			cr nn 008mamaa
008			150903s2008 gw | o |||| 0|eng d
020			_a9783540775836 _99783540775836
024	7		_a10.1007/9783540775836 _2doi
035			_avtls000351480
039		9	_a201509030448 _bVLOAD _c201405060251 _dVLOAD _y201402171138 _zstaff
040			_aMX-SnUAN _bspa _cMX-SnUAN _erda
050		4	_aQA76.758
100	1		_aBurge, Janet E. _eautor _9334523
245	1	0	_aRationale-Based Software Engineering / _cby Janet E. Burge, John M. Carroll, Raymond McCall, Ivan Mistrik.
264		1	_aBerlin, Heidelberg : _bSpringer Berlin Heidelberg, _c2008.
300			_brecurso en línea.
336			_atexto _btxt _2rdacontent
337			_acomputadora _bc _2rdamedia
338			_arecurso en línea _bcr _2rdacarrier
347			_aarchivo de texto _bPDF _2rda
500			_aSpringer eBooks
505	0		_aWhat is Rationale and Why Does It Matter? -- What Makes Software Different -- Rationale and Software Engineering -- Learning from Rationale Research in Other Domains -- Decision-Making in Software Engineering -- Uses for Rationale -- Presentation of Rationale -- Evaluation -- Support for Collaboration -- Change Analysis -- Rationale and Software Engineering -- Rationale and the Software Lifecycle -- Rationale and Requirements Engineering -- Rationale and Software Design -- Rationale and Software VV&T -- Rationale and Software Maintenance -- Rationale and Software Re-use -- Frameworks for Rationale-Based Software Engineering -- A Conceptual Framework -- An Architectural Framework -- Rationale-Based Software Engineering: Summary and Prospect.
520			_aMany decisions are required throughout the software development process. These decisions, and to some extent the decision-making process itself, can best be documented as the rationale for the system, which will reveal not only what was done during development but the reasons behind the choices made and alternatives considered and rejected. This information becomes increasingly critical as software development becomes more distributed and encompasses the corporate knowledge both used and refined during the development process. The capture of rationale helps to ensure that decisions are well thought out and justified and the use of rationale can help avoid the mistakes of the past during both the development of the current system and when software products (architecture and design, as well as code) are reused in future systems. Burge, Carroll, McCall, and Mistrík describe in detail the capture and use of design rationale in software engineering to improve the quality of software. Their book is the first comprehensive and unified treatment of rationale usage in software engineering. It provides a consistent conceptual framework and a unified terminology for comparing, contrasting and combining the myriad approaches to rationale in software engineering. It is both an excellent introductory text for those new to the field and a uniquely valuable reference for experienced rationale researchers. The book covers the use of rationale for decision making throughout the software lifecycle, starting from the first decisions in a project and continuing through requirements definition, design, implementation, testing, maintenance, redesign and reuse.
590			_aPara consulta fuera de la UANL se requiere clave de acceso remoto.
700	1		_aCarroll, John M. _eautor _9316819
700	1		_aMcCall, Raymond. _eautor _9328810
700	1		_aMistrik, Ivan. _eautor _9334524
710	2		_aSpringerLink (Servicio en línea) _9299170
776	0	8	_iEdición impresa: _z9783540775829
856	4	0	_uhttp://remoto.dgb.uanl.mx/login?url=http://dx.doi.org/10.1007/978-3-540-77583-6 _zConectar a Springer E-Books (Para consulta externa se requiere previa autentificación en Biblioteca Digital UANL)
942			_c14
999			_c298262 _d298262