ABSTRACT
This paper presents an initial "4+1" theory of value-based software engineering (VBSE) that builds around the stakeholder win-win Theory W, and addresses the questions of "which values are important?" and "how is success assured?" for a given software engineering enterprise. The central Theory W then draws upon four additional theories - utility theory (how important are the values?), decision theory (how do stakeholders' values determine decisions?), dependency theory (how do dependencies affect value realization?), and control theory (how to adapt to change and control value realization?).
- S. Adams, Dilbert Comic Strips, 1995.Google Scholar
- C. Alexander, The Timeless Way of Building, Oxford University Press, 1979.Google Scholar
- C. Argyris, Organizational Learning, Addison-Wesley, 1978.Google Scholar
- B. Boehm and P. Bose, A Collaborative Spiral Software Process Model Based on Theory W, Proceedings, ICSP 3, IEEE, October 1994.Google ScholarCross Ref
- B. Boehm and A. Jain, "An Initial Theory of Value-Based Software Engineering", USC-CSE Technical Report 2005-505, March 2005.Google Scholar
- B. Boehm and L. Huang, Value-Based Software Engineering: A Case Study, IEEE Computer, March 2003, pp. 21--29. Google ScholarDigital Library
- B. Boehm and R. Turner, Balancing Agility and Discipline, Addison Wesley, 2004. Google ScholarDigital Library
- B. Boehm, and R. Ross, Theory-W Software Project Management: Principles and Examples, IEEE Trans. SW Engineering., July 1989, pp. 902--916. Google ScholarDigital Library
- D. Blackwell and M. Girshick, Theory of Games and Statistical Decisions, Wiley, 1954.Google Scholar
- W. Brogan, Modern Control Theory, Prentice Hall, 1974 (3rd ed., 1991). Google ScholarDigital Library
- R. Burns, To a Mouse, November 1785.Google Scholar
- P. Checkland, Systems Thinking, Systems Practice, Wiley, 1981.Google Scholar
- C. W. Churchman, R. Ackoff, and E. Arnoff, An Introduction to Operations Research, Wiley, 1957.Google Scholar
- W. Collins, K. Miller, B. Spielman, and J. Wherry, "How Good is Good Enough?", Comm. ACM, January 1994, pp. 81--91. Google ScholarDigital Library
- R. M. Cyert and J. G. March, A Behavioral Theory of the Firm, Prentice Hall, 1963.Google Scholar
- G. Debreu, Theory of Value, Wiley, 1959.Google Scholar
- T. DeMarco, Controlling Software Projects, Yourdon Press, 1982.Google Scholar
- J. Dupuit, On the Measurement of the Utility of Public Works, Translated by R. H. Barback, International Economic Papers 2:83--110, 1844 (1952).Google Scholar
- P. C. Fishburn, The Foundations of Expected Utility, Dordrecht, 1982.Google Scholar
- R. Fisher and W. Ury, Getting To Yes: Negotiating Agreement Without Giving In, Houghton Mifflin, 1981.Google Scholar
- D. A. Gioia and E. Pitre, Multi-Paradigm Perspectives on Theory Building, Academy of Management Review, 15, pp. 584--602, 1990.Google ScholarCross Ref
- C. G. Hempel and P. Oppenheim, Problems of the Concept of General Law, in (eds.) A. Danto and S. Mogenbesser, Philosophy of Science, Meridian Books, 1960.Google Scholar
- J. Highsmith, Adaptive Software Development, Dorset House, 2000. Google ScholarDigital Library
- W. S. Humphrey, Managing the Software Process, Addison-Wesley, 1989. Google ScholarDigital Library
- M. Jeffery, S. Shah, and R. Sweeney, "Real Options and Enterprise technology Project Selection and Deployment Strategies", MIS Quarterly, April 2003.Google Scholar
- R. Kaplan and D. Norton, The Balanced Scorecard: Translating Strategy into Action, Harvard Business School Press, 1996.Google Scholar
- R. L. Keeney and H. Raiffa, Decisions with Multiple Objectives: Preferences and Value Tradeoffs, Cambridge University Press, 1976.Google Scholar
- M. J. Lee, Foundations of the WinWin Requirements Negotiation System, Ph.D. dissertation, University of Southern California, 1996. Google ScholarDigital Library
- R. D. Luce and H. Raiffa, Games and Decisions, John Wiley, 1957.Google Scholar
- J. March and H. Simon, Organizations, Wiley, 1958.Google Scholar
- J. Marschak and R. Radner, Economic Theory of Teams, Yale University Press, 1972.Google Scholar
- A. Maslow, Motivation and Personality, Harper, 1954Google Scholar
- T. Parsons, Social Systems and the Evolution of Action Theory, The Free Press, 1977.Google Scholar
- C. H. Patterson, Theories of counseling and psychotherapy, Harper and Row, 1983.Google Scholar
- D. Port and S. Chen, Assessing COTS Assessment: How Much Is Enough?, ICCBSS 2004 Proceedings, Springer, 2004.Google ScholarCross Ref
- H. Raiffa, The Art and Science of Negotiation, Belknap/Harvard U. Press, 1982.Google Scholar
- J. Rawls, A Theory of Justice, Belknap/Harvard U. Press, 1971, 1999.Google Scholar
- E. Rechtin, Systems Architecting: Creating and Building Complex Systems, Prentice-Hall, 1991. Google ScholarDigital Library
- S. RifKin, The Parsons Game: The First Simulation of Talcott Parsons' Theory of Action, Ph.D. dissertation, George Washington University, 2004.Google Scholar
- M. Scott Morton, The Corporation of the 1990s: Information Technology and Organization Transformation, Oxford University Press, 1991. Google ScholarDigital Library
- H. Simon, The Science of the Artificial, MIT Press, 1969.Google Scholar
- H. Simon, Models of Man, Wiley, 1957.Google Scholar
- J. Thorp and DMR's Center for Strategic Leadership, The Information Paradox: Realizing the Benefits of Information Technology, McGraw-Hill, 1998.Google Scholar
- R. J. Torraco, Theory-Building Research Methods, in R. A. Swanson & E. F. Holton III (eds.), Human Resource Development Handbook: Linking Research and Practice pp. 114--137, Berrett-Koehler, 1997.Google Scholar
- S. Toulmin, Cosmopolis: The Hidden Agenda of Modernity, U. of Chicago Press, 1992 reprint edition.Google Scholar
- J. von Neumann and O. Morgenstern, Theory of Games and Eonomic Behavior, Princeton University Press, 1944.Google Scholar
- A. W. Wymore, A Mathematical Theory of Systems Engineering: The Elements, Wiley, New York, 1967Google Scholar
Index Terms
- Developing a theory of value-based software engineering
Recommendations
Developing a theory of value-based software engineering
This paper presents an initial "4+1" theory of value-based software engineering (VBSE) that builds around the stakeholder win-win Theory W, and addresses the questions of "which values are important?" and "how is success assured?" for a given software ...
Value-based software engineering
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; ...
Developing a process framework using principles of value-based software engineering: Research Sections
Special Issue on Software Process SimulationIn this article we present a software process framework using the 4 + 1 theory and principles of value-based software engineering (VBSE). The value-based process framework serves as a 6-step process guide, and explains critical interactions between the ...
Comments