| 000 | 01160camuu22003374a 4500 | |
| 001 | 000045219871 | |
| 005 | 20060104110834 | |
| 008 | 060104s2006 gw a b 001 0 eng c | |
| 010 | ▼a 2005930639 | |
| 015 | ▼a GBA567602 ▼2 bnb | |
| 016 | 7 | ▼a 013270212 ▼2 Uk |
| 020 | ▼a 3540259937 (hbk.) | |
| 024 | 3 | ▼a 9783540259930 |
| 040 | ▼a UKM ▼b eng ▼c UKM ▼d BAKER ▼d AZS ▼d 211009 | |
| 042 | ▼a ukblsr ▼a pcc | |
| 049 | ▼a KUBA | |
| 050 | 4 | ▼a QA76.758 ▼b .V35 2006 |
| 082 | 0 4 | ▼a 005.10681 ▼2 22 |
| 090 | ▼a 005.10681 ▼b V215 | |
| 245 | 0 0 | ▼a Value-based software engineering / ▼c Stefan Biffl ... [et al.] (eds.). |
| 260 | ▼a Berlin ; ▼a New York : ▼b Springer , ▼c c2006. | |
| 300 | ▼a xxii, 388 p. : ▼b ill. ; ▼c 24 cm. | |
| 504 | ▼a Includes bibliographical references and index. | |
| 650 | 0 | ▼a Software engineering ▼x Costs. |
| 650 | 0 | ▼a Software engineering ▼x Evaluation ▼x Methodology. |
| 650 | 0 | ▼a Software engineering ▼x Management. |
| 700 | 1 | ▼a Biffl, Stefan. |
| 938 | ▼a Baker & Taylor ▼b BKTY ▼c 99.00 ▼d 99.00 ▼i 3540259937 ▼n 0006550307 ▼s active | |
| 945 | ▼a KINS | |
| 994 | ▼a C0 ▼b KUB |
소장정보
| No. | 소장처 | 청구기호 | 등록번호 | 도서상태 | 반납예정일 | 예약 | 서비스 |
|---|---|---|---|---|---|---|---|
| No. 1 | 소장처 과학도서관/Sci-Info(2층서고)/ | 청구기호 005.10681 V215 | 등록번호 121120046 (7회 대출) | 도서상태 대출가능 | 반납예정일 | 예약 | 서비스 |
컨텐츠정보
책소개
The 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, behavioral 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.
Ross Jeffery When, as a result of pressure from the CEO, the Chief Information Officer poses the question “Just what is this information system worth to the organization?” the IT staff members are typically at a loss. “That’s a difficult question,” they might say; or “well it really depends” is another answer. Clearly, neither of these is very satisfactory and yet both are correct. The IT community has struggled with qu- tions concerning the value of an organization’s investment in software and ha- ware ever since it became a significant item in organizational budgets. And like all questions concerning value, the first step is the precise determination of the object being assessed and the second step is the identification of the entity to which the value is beneficial. In software engineering both of these can be difficult. The p- cise determination of the object can be complex. If it is an entire information s- tem in an organizational context that is the object of interest, then boundary defi- tion becomes an issue. Is the hardware and middleware to be included? Can the application exist without any other applications? If however the object of interest is, say, a software engineering activity such as testing within a particular project, then the boundary definition becomes a little easier. But the measure of benefit may become a little harder.
New feature
The 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, behavioral 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.
정보제공 :
목차
Part 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
정보제공 :