Academic
Publications
Value-based software engineering

Value-based software engineering,10.1145/638750.638776,ACM Sigsoft Software Engineering Notes,Barry W. Boehm,LiGuo Huang

Value-based software engineering   (Citations: 181)
BibTex | RIS | RefWorks Download
Much of current software engineering practice and research is done in a value-neutral setting, in which every requirement, use case, object, and defect is treated as equally important; methods are presented and practiced as largely logical activities; and a "separation of concerns" is practiced, in which the responsibility of software engineers is confined to turning software requirements into verified code. In earlier times, when software decisions had relatively minor influences on a system's cost, schedule, and value, the value-neutral approach was reasonably workable. But today and increasingly in the future, software has a major influence on most systems' cost, schedule, and value; and value-neutral software decisions can seriously degrade project outcomes.This paper presents an agenda for a discipline of Value-Based Software Engineering. It accepts the challenge of integrating value considerations into all of the existing and emerging software engineering principles and practices, and of developing an overall framework in which they compatibly reinforce each other. Example elements of this agenda include value-based requirements engineering, architecting, design and development, verification and validation, planning and control, risk management, quality management, and people management. It presents seven key elements that provide candidate foundations for value-based software engineering: Benefits Realization Analysis; Stakeholder Value Proposition Elicitation and Reconciliation; Business Case Analysis; Continuous Risk and Opportunity Management; Concurrent System and Software Engineering; Value-Based Monitoring and Control; and Change as Opportunity.
Journal: ACM Sigsoft Software Engineering Notes , vol. 28, no. 2, 2003
Cumulative Annual
View Publication
The following links allow you to view full publications. These links are maintained by other sources not affiliated with Microsoft Academic Search.
    • ...Then we interpret survivability from the perspective of value-based software engineering [5] as the capability of maximizing the satisfaction level of the system value proposition, which defines how the “earned business value” at system side is measured to facilitate the “when” part of the problem...

    Bihuan Chenet al. Survivability-oriented self-tuning of web systems

    • ...The basis of CSES stems from and is consistent with the spirit of Value Based Software Engineering [30, 31]...

    Robert K. Abercrombieet al. Addressing the need for independence in the CSE model

    • ...The value-based software engineering (VBSE) [11] and value-based requirements engineering (VBRE) [12] are two views with emphasis on integrating value into the SE and RE principles and practices...
    • ...E. Value-Based SE and RE. Our method sible to integrate business value considerations into the goal models [11]...

    Bihuan Chenet al. Are your sites down? Requirements-driven self-tuning for the survivabi...

    • ...A recent theory of value-based software engineering (VBSE) and its associated software processes [17] provide a starting point for addressing these challenges, and for extending them to systems engineering processes...
    • ...A book on VBSE approaches [7] contains further insights and emerging directions for VBSE processes...

    Barry Boehm. Some Future Software Engineering Opportunities and Challenges

    • ...The economic impact of monitoring decisions and resolving uncertainty over time has been analyzed extensively by several authors [21] using decision trees and real-option theory...
    • ...Viewing risk and cost as drivers in architecture decision making has led to approaches like the Cost Benefit Analysis Method (CBAM) [9] and the Architecture Rationalization Method (ARM) [30]that relate architectural decisions to the benefits they bring to an organization, studies that emphasize business implications of architectural decisions [22], and approaches that consider architectural decisions as investment decisions [21], [31]...

    Eltjo R. Poortet al. Architecting as a Risk and Cost Management Discipline

Sort by: