1. VBSE Theory, and SimVBSE CSE, Annual Research Review Apurva Jain, Barry Boehm Version 1.0 (modified March 02, 2006)

2. March 14, 2006CSE, Annual Research Review2 Outline o Motivation o The 4+1 Theory of VBSE o SimVBSE o Overview o Demonstration

3. March 14, 2006CSE, Annual Research Review3 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

4. March 14, 2006CSE, Annual Research Review4 Day in the life of a decision maker o Vendor proposition o 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

5. March 14, 2006CSE, Annual Research Review5 VBSE Response: Case in point o Test data generator is value- neutral o Assumes every test case, defect is equally important o Usually, it’s a Pareto distribution — 20% of test cases cover 80% of business value Research Motivation - III

6. March 14, 2006CSE, Annual Research Review6 VBSE Response: Case in point o Experience report (Bullock, 2000) % of Value for Correct Customer Billing Customer Type 100 80 60 40 20 51015 Automated test generation tool - all tests have equal value Research Motivation - IV

7. March 14, 2006CSE, Annual Research Review7 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

8. March 14, 2006CSE, Annual Research Review8 Applying VBSE o 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 framework o That keeps the overarching principles of VBSE at its heart. o And, serves usefully through the entire software’s life cycle. Research Motivation - VI

9. March 14, 2006CSE, Annual Research Review9 The 4+1 Structure SCS: Success-critical Stakeholders The 4+1 Theory of VBSE

10. March 14, 2006CSE, Annual Research Review10 The 7-Step Process Framework Integrating the 4+1 theories

11. Demonstration

12. Backups