Abstract
Many software projects fail because they commit to a set of plans and specifications with little evidence that if these are used on the project, they will lead to a feasible system being developed within the project’s budget and schedule. An effective way to avoid this is to make the evidence of feasibility a first-class developer deliverable that is reviewed by independent experts and key decision milestones: shortfalls in evidence are risks to be considered in going forward. This further implies that the developer will create and follow processes for evidence development. This paper provides processes for developing and reviewing feasibility evidence, and for using risk to determine how to proceed at major milestones. It also provides quantitative result on ”how much investment in evidence is enough,” as a function of the project’s size, criticality, and volatility.
This is a preview of subscription content, log in via an institution to check access.
Access this chapter
Tax calculation will be finalised at checkout
Purchases are for personal use only
Preview
Unable to display preview. Download preview PDF.
References
Al Said, M.: Detecting Model Clashes During Software Systems Development. Doctoral Thesis. Department of Computer Science, University of Southern California (2003)
Beck, K.: Extreme Programming Explained. Addison-Wesley, Reading (1999)
Boehm, B.: Anchoring the Software Process. IEEE Software, 73–82 (July 1996)
Boehm, B., et al.: Software Cost Estimation with COCOMO II. Prentice Hall, Englewood Cliffs (2000)
Boehm, B., Lane, J.: Incremental Commitment Model Guide, version 0.5 (2009)
Boehm, B., Lane, J.: Using the ICM to Integrate System Acquisition, Systems Engineering, and Software Engineering. CrossTalk, 4–9 (October 2007)
Boehm, B., Port, D., Al Said, M.: Avoiding the Software Model-Clash Spiderweb. IEEE Computer, 120–122 (November 2000)
Glass, R.: Software Runaways. Prentice Hall, Englewood Cliffs (1998)
Kruchten, P.: The Rational Unified Process. Addison-Wesley, Reading (1999)
Maranzano, J., et al.: Architecture Reviews: Practice and Experience. IEEE Software (March/April 2005)
Pew, R., Mavor, A.: Human-System Integration in the System Development Process: A New Look. National Academy Press, Washington (2007)
Royce, W.: Software Project Management. Addison-Wesley, Reading (1998)
Royce, W., Bittner, K., Perrow, M.: The Economics of Iterative Software Development. Addison-Wesley, Reading (2009)
Standish Group 2009. CHAOS Summary (2009), http://standishgroup.com
Schwaber, K., Beedle, M.: Agile Software Development with Scrum. Prentice Hall, Englewood Cliffs (2002)
Author information
Authors and Affiliations
Editor information
Editors and Affiliations
Rights and permissions
Copyright information
© 2010 Springer-Verlag Berlin Heidelberg
About this paper
Cite this paper
Boehm, B., Lane, J.A. (2010). Evidence-Based Software Processes. In: Münch, J., Yang, Y., Schäfer, W. (eds) New Modeling Concepts for Today’s Software Processes. ICSP 2010. Lecture Notes in Computer Science, vol 6195. Springer, Berlin, Heidelberg. https://doi.org/10.1007/978-3-642-14347-2_7
Download citation
DOI: https://doi.org/10.1007/978-3-642-14347-2_7
Publisher Name: Springer, Berlin, Heidelberg
Print ISBN: 978-3-642-14346-5
Online ISBN: 978-3-642-14347-2
eBook Packages: Computer ScienceComputer Science (R0)