[Beck 1999] Beck, K. 1999. Extreme Programming Explained. Boston: Addison-Wesley.

[Boehm 1976] Boehm, B. 1976. Software engineering. IEEE Transactions on Computers 25(12): 1226–1241.

[Boehm 1980] Boehm, B. 1980. Developing small-scale software application products: Some experimental results. Proceedings of the IFIP Congress 1980: 321–326.

[Boehm 1981] Boehm, B. 1981. Software Engineering Economics. Upper Saddle River, NJ: Prentice-Hall.

[Boehm 1996] Boehm, B. 1996. Anchoring the software process. Software 13(4): 73–82.

[Boehm 2000] Boehm, B. 2000. Unifying software engineering and systems engineering. Computer 33(3): 114–116.

[Boehm and Lane 2007] Boehm, B., and J. Lane. 2007. Using the incremental commitment model to integrate system acquisition, systems engineering, and software engineering. CrossTalk (Oct. 2007): 4–9.

[Boehm and Lane 2009] Boehm, B., J. Lane. 2009. Guide for Using the Incremental Commitment Model (ICM) for Systems Engineering of DoD Projects, Version 0.5. USC-CSSE-2009-500. Available at http://csse.usc.edu/csse/TECHRPTS/2009/usc-csse-2009-500/usc-csse-2009-500.pdf.

[Boehm and Port 1999] Boehm, B., and D. Port. 1999. Escaping the software tar pit: Model clashes and how to avoid them. ACM Software Engineering Notes 24(1): 36–48.

[Boehm and Port 2001] Boehm, B., and D. Port. 2001. Balancing discipline and flexibility with the spiral model and MBASE. CrossTalk (Dec. 2001): 23–28.

[Boehm and Royce 1989] Boehm, B., and W. Royce. 1989. Ada COCOMO and the Ada process model. Paper presented at the 5th COCOMO Users’ Group, October 17–19, in Pittsburgh, PA. Available at http://csse.usc.edu/csse/TECHRPTS/1989/usccse89-503/usccse89-503.pdf.

[Boehm et al. 1998] Boehm, B.A., Egyed, J. Kwan, D. Port, A. Shah, and R. Madachy. 1998. Using the WinWin spiral model: a case study. IEEE Computer 31(7): 33–44.

[Boehm et al. 2000] Boehm, B., C. Abts, A.W. Brown, S. Chulani, B. Clark, E. Horowitz, R. Madachy, D. Reifer, and B. Steece. 2000. Software Cost Estimation with COCOMO II. Upper Saddle River, NJ: Prentice-Hall.

[Boehm et al. 2010] Boehm, B., J. Lane, S. Koolmanojwong, and R. Turner. 2010. Architected Agile Solutions for Software-Reliant Systems. In Agile Software Development: Current Research and Future Directions, ed. T. Dingsøtr, T. Dybå, and N.B. Moe, 165–184. Berlin: Springer-Verlag.

[Clements et al. 2002] Clements, P., R. Kazman, and M. Klein. 2002. Evaluating Software Architectures. Boston: Addison-Wesley.

[Daly 1977] Daly, E. 1977. Management of software engineering. IEEE Transactions on Software Engineering. 3(3): 229–242.

[Elssamadisy and Schalliol 2002] Elssamadisy, A., and G. Schalliol. 2002. Recognizing and Responding to “Bad Smells” in Extreme Programming. Proceedings of the 24th International Conference on Software Engineering: 617–622.

[Fagan 1976] Fagan, M. 1976. Design and code inspections to reduce errors in program development. IBM Systems Journal 15(3): 182–211.

[Jacobson et al. 1999] Jacobson, I., G. Booch, and J. Rumbaugh. 1999. The Unified Software Development Process. Reading, MA: Addison-Wesley.

[Kruchten 1999] Kruchten, P. 1999. The Rational Unified Process: An Introduction. Reading, MA: Addison-Wesley.

[Li and Alshayeb 2002] Li, W., and M. Alshayeb. 2002. An Empirical Study of XP Effort. Paper presented at the 17th International Forum on COCOMO and Software Cost Modeling, October 22–25, in Los Angeles, CA.

[Maranzano et al. 2005] Maranzano, J., S.A. Rozsypal, G.H. Zimmerman, G.W. Warnken, P.E. Wirth, and D.M. Weiss. 2005. Architecture reviews: Practice and experience. Software 22(2):34–43.

[McGibbon 1996] McGibbon, T. 1996. Software reliability data summary. Data & Analysis Center for Software Technical Report.

[Parnas 1979] Parnas, D. 1979. Designing software for ease of extension and contraction, IEEE Transactions on Software Engineering 5(2): 128–138.

[Pew and Mavor 2007] Pew, R., and A. Mavor, ed. 2007. Human-System Integration in the System Development Process. Washington, D.C.: National Academies Press.

[Rechtin 1991] Rechtin, E. 1991. Systems Architecting. Englewood Cliffs, NJ: Prentice-Hall.

[Rechtin and Maier 1997] Rechtin, E., and M. Maier. 1997. The Art of Systems Architecting. Boca Raton, FL: CRC Press.

[Reifer 2002] Reifer, D. 2002. How to get the most out of extreme programming/agile methods. Proceedings of the Second XP Universe and First Agile Universe Conference on Extreme Programming and Agile Methods: 185–196.

[Royce 1998] Royce, W. 1998. Software Project Management: A Unified Framework. Reading, MA: Addison-Wesley.

[Shull et al. 2002] Shull, F., V. Basili, B. Boehm, A.W. Brown, P. Costa, M. Lindvall, D. Port, I. Rus, R. Tesoreiro, and M. Zelkowitz. 2002. What we have learned about fighting defects. Proceedings of the 8th International Symposium on Software Metrics: 249–258.

[Stephenson 1976] Stephenson, W. 1976. An analysis of the resources used in the SAFEGUARD software system development. Proceedings of the 2nd international conference on software engineering: 312–321.

[Valerdi 2005] Valerdi, R. 2005. The constructive systems engineering cost model (COSYSMO). PhD diss., University of Southern California.

[Valerdi and Boehm 2010] Valerdi, R., and B. Boehm. 2010. COSYSMO: A systems engineering cost model. Génie Logiciel 92: 2–6.