An Initial Theory of Value-Based Software Engineering

Boehm, Barry; Jain, Astha

doi:10.1007/3-540-29263-2_2

Cited by 42 publications

(63 citation statements)

References 37 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…For further process details see [Boehm-Jain, 2005;Boehm-Jain, 20061. Step 1 Many process models do not address how the system life-cycle process gets started. With VBTSE, the process gets started when a protagonist becomes convinced that existing systems are seriously inadequate, but that improving them involves dependencies upon other success-critical stakeholders.…”

Section: The 6-step Process Framework and Dependency Analysismentioning

confidence: 99%

3.4.3 The Value‐Based Theory of Systems Engineering: Identifying and Explaining Dependencies

Boehm

Jain

2007

INCOSE International Symp

Self Cite

View full text Add to dashboard Cite

Abstract. The Value-Based Theory of Systems Engineering brings together many interdisciplinary theoretical lenses into a state of synchrony and allows reasoning about systems in different dimensions, and at various levels of abstraction. The theory's primary strength is in its ability to identify and work through the dependencies of most socio-political-technical systems and explain success in such contexts by situating the success-critical stakeholders at the forefront. In this paper we present the 4+1 theoretical lenses of the Value-Based Theory of Systems Engineering with a core emphasis on the Dependency Theory -the first and most complex of the four component theories.

show abstract

Section: The 6-step Process Framework and Dependency Analysismentioning

confidence: 99%

3.4.3 The Value‐Based Theory of Systems Engineering: Identifying and Explaining Dependencies

Boehm

Jain

2007

INCOSE International Symp

Self Cite

View full text Add to dashboard Cite

show abstract

“…As examples, protagonists can be organization leaders with goals, authority, and resources, entrepreneurs with goals and resources, inventors with goals and ideas, or consortia with shared goals and distributed leadership and resources. (For further process details in a software context, see [Boehm and Jain, 2005].) Each class of protagonist will take a somewhat different approach in visiting the seven main steps in Figure 3 to create and sustain a win-win combination of SCSs to achieve their goals.…”

Section: Using and Testing The Vbtse: Process Framework And Examplementioning

confidence: 99%

“…The Sierra example in the previous section provides an opportunity to evaluate the VBTSE theory with respect to a set of criteria for a good theory discussed further in [Boehm and Jain, 2005].…”

Section: Vbse Theory Evaluation With Respect To Goodness Criteriamentioning

confidence: 99%

6.1.3 A Value‐Based Theory of Systems Engineering

Boehm

Jain

2006

INCOSE International Symp

Self Cite

View full text Add to dashboard Cite

Abstract. The INCOSE definition of "systems engineering" is "an interdisciplinary approach and means to enable the realization of successful systems." The Value-Based Theory of Systems Engineering presents necessary and sufficient conditions for realizing a successful system and elaborates them into an executable process. The theory and process are illustrated on a supply-chain system example, and evaluated with respect to criteria for a good theory.

show abstract

“…In Standish Group CHAOS report (The-Standish-Group, 1995) valueoriented shortfalls such as lack of user input, changing requirements, lack of resources and unrealistic time frames etc., are described as common causes of most software project failures. A value-based software engineering (VBSE) agenda has emerged (Boehm, 2003;Boehm & Jain, 2005). The focus is to integrate value considerations into current and emerging software engineering principles and practices.…”

Section: Introduction To Value Based Software Engineering (Vbse)mentioning

confidence: 99%

Managing Requirements Risks: A Value-Based Process

Ikram¹,

Usman²,

Samad³

et al. 2010

Advances in Risk Management

View full text Add to dashboard Cite

The technological, cost, people and schedule issues faced during software development, make it vulnerable for several types of risks. The requirements' related risks are one of the most occurring risks. If remain unnoticed or unmanaged, the requirements related risks can cost a project greatly, financially and otherwise. It is extremely important to manage requirements related risks efficiently and effectively. Moreover, a project can never be successful if stakeholders do not get their "valued" things. Every requirement contributes towards some value for stakeholder(s). Therefore it is important to manage requirements risks to the satisfaction of stakeholders. Different stakeholders have different perception of risk, it is therefore necessary to have a process that not only manages requirements' risks but it also fulfills the values of stakeholders as well. This chapter presents a Value-Based Requirements Risk Management (VRRM) process that is designed (Samad et al., 2008) to manage requirements related risks in a value based manner.

show abstract

An Initial Theory of Value-Based Software Engineering

Cited by 42 publications

References 37 publications

3.4.3 The Value‐Based Theory of Systems Engineering: Identifying and Explaining Dependencies

3.4.3 The Value‐Based Theory of Systems Engineering: Identifying and Explaining Dependencies

6.1.3 A Value‐Based Theory of Systems Engineering

Managing Requirements Risks: A Value-Based Process

Contact Info

Product

Resources

About