Embed Size (px)
Citation preview
VBSE Theory, and SimVBSE
CSE, Annual Research Review
Apurva Jain, Barry Boehm
Version 1.0 (modified March 02, 2006)
March 14, 2006 CSE, Annual Research Review 2
Outlineo Motivationo The 4+1 Theory of VBSEo SimVBSE
o Overviewo Demonstration
March 14, 2006 CSE, Annual Research Review 3
Why VBSE?o Software initiatives are
essentially investments that create value.
o VBSE calls for integrating stakeholder value considerations in the full range of software development practices and principles.o Most currently value-neutral
o Ignoring stakeholder values usually result in suboptimality.
Research Motivation - I
March 14, 2006 CSE, Annual Research Review 4
Day in the life of a decision maker
o Vendor propositiono Our automatic test data
generator (ATG) will cut your test costs in half
o We’ll provide it to you for 30% of your test costs
o After you run all your tests for 50% of your original cost, you are 20% ahead
o Any concerns with vendor proposition?
Research Motivation - II
March 14, 2006 CSE, Annual Research Review 5
VBSE Response: Case in point
o Test data generator is value-neutraloAssumes every test case,
defect is equally importantoUsually, it’s a Pareto
distribution—20% of test cases cover 80% of business value
Research Motivation - III
March 14, 2006 CSE, Annual Research Review 6
VBSE Response: Case in point
o Experience report (Bullock, 2000)
% of Valuefor
CorrectCustomer
Billing
Customer Type
100
80
60
40
20
5 10 15
Automated test generation tool - all tests have equal value
Research Motivation - IV
March 14, 2006 CSE, Annual Research Review 7
VBSE Response: Case in point
o The example was only ROI driven; value-based testing will also involve: o Identifying other stakeholder
values such as customer satisfaction, customer retention, organization’s goodwill, brand
o Such value-neutrality is usually true for other SE techniques too.
Research Motivation - V
March 14, 2006 CSE, Annual Research Review 8
Applying VBSEo Emerging techniques
o Example, value-based testing and value-based monitoring and control (others in Biffl et. al., 2005)
o But the paradigm appears to lack a theoretical unifying frameworko That keeps the overarching
principles of VBSE at its heart.o And, serves usefully through
the entire software’s life cycle.
Research Motivation - VI
March 14, 2006 CSE, Annual Research Review 9
The 4+1 Structure
Utility Theory
Theory W:SCS Win-Win
Decision Theory
Dependency Theory
Control Theory
How do dependencies affect value realization?
How to adapt to change and control value realization?
How do values determine decision choices?
How important are the values?
What values are important?How is success assured?
SCS: Success-critical Stakeholders
The 4+1 Theory of VBSE
March 14, 2006 CSE, Annual Research Review 10
The 7-Step Process FrameworkIntegrating the 4+1 theories
Utility Theory
Theory W:SCS Win-Win
Decision Theory
Dependency Theory
Control Theory
6a, 7c. State measurement, prediction, correction; Milestone synchronization
5a. Investment analysis, Risk analysis
1. Protagonist goals3a. Solution exploration7. Risk, opportunity, change management
5a, 7b. Prototyping
2a. Results Chains3b, 5a, 7b. Cost/schedule/performance tradeoffs
2. Identify SCSs
3b, 7a. Solution Analysis
5a, 7b. Option, solution development & analysis
4. SCS expectations management
3. SCS Value Propositions(Win conditions)
SCS: Success-Critical Stakeholder
6, 7c. Refine, Execute, Monitor & Control Plans
5. SCS Win-Win Negotiation
Demonstration
Backups
