000			03637cam a22002417a 4500
001			vtls000002158
003			VRT
005			20250102224911.0
008			081118s2006 gw a |b 001 0 eng
020			_a3540259937
020			_a9783540259930
039		9	_a201402040103 _bVLOAD _c201007310925 _dmalmash _c200811191337 _dvenkatrajand _c200811181101 _dNoora _y200811181100 _zNoora
050	0	0	_aQA76.758 _b.V35 2006
245	0	0	_aValue-Based Software Engineering / _cStefan Biffl ... [et al.], (eds.).
260			_aBerlin : _bSpringer, _cc2006.
300			_axxii, 388 p. : _bill. ; _c24 cm.
504			_aIncludes bibliographical references and index.
505			_aPart 1: Foundations and Frameworks Value-Based Software Engineering: Overview and Agenda - An Initial Theory of Value-Based Software Engineering - Valuation of Software Initiatives under Uncertainty: Concepts, Issues, and Techniques - Prefernce-Based Decision Support in Software Engineering - Risk and The Economic Value of The Software Producer Part 2: Practices Value-Based Software Engineering: Seven Key Elements and Ethical Considerations - Stakehol'der Value Proposition, Elicitation, and Reconciliation - Measurement and Decision Making -Criteria for Selecting Software Requirements to Cretae Product Value: An Industrial Empirical Study - Collaborative Usability Testing to Facilitate Stakeholder Involvement Value-Based Management of Software Testing Part 3: Applications Decision Support for Value-Based Software Release Planning - PROSIM/RA Software Process Simulation Support of Risk Assessment - Tailoring Software Traceability to Value-Based Needs - Value-Based Knowledge Management: The Contribution of Group Processes - Quantifying The Value of New Technologies for Software Development - Valuing Software Intellectual Property Glossary
520			_aThe IT community has always struggled with questions concerning the value of an organization's investment in software and hardware. It is the goal of Value-Based Software Engineering (VBSE) to develop models and measures of value which are of use for managers, developers and users as they make tradeoff decisions between, for example, quality and cost or functionality and schedule - such decisions must be economically feasible and comprehensible to the stakeholders with differing value perspectives. VBSE has its roots in work on software engineering economics, pioneered by Barry Boehm in the early 1980s. However, the emergence of a wider scope that defines VBSE is more recent. VBSE extends the merely technical ISO software engineering definition with elements not only from economics, but also from cognitive science, finance, management science, behavioural sciences, and decision sciences, giving rise to a truly multi-disciplinary framework. Biffl and his co-editors invited leading researchers and structured their contributions into three parts, following an introduction into the area by Boehm himself. They first detail the foundations of VBSE, followed by a presentation of state-of-the-art methods and techniques. The third part demonstrates the benefits of VBSE through concrete examples and case studies. This book deviates from the more anecdotal style of many management-oriented software engineering books and so appeals particularly to all readers who are interested in solid foundations for high-level aspects of software engineering decision making, i.e., to product or project managers driven by economics and to software engineering researchers and students.
650		0	_aSoftware engineering _xManagement. _943735
700	1		_aBiffl, Stefan. _949250
942			_2lcc _n0 _cBK
999			_c23293 _d23293