A view of 20th and 21st century software engineering

ABSTRACT

George Santayana's statement, "Those who cannot remember the past are condemned to repeat it," is only half true. The past also includes successful histories. If you haven't been made aware of them, you're often condemned not to repeat their successes.In a rapidly expanding field such as software engineering, this happens a lot. Extensive studies of many software projects such as the Standish Reports offer convincing evidence that many projects fail to repeat past successes.This paper tries to identify at least some of the major past software experiences that were well worth repeating, and some that were not. It also tries to identify underlying phenomena influencing the evolution of software engineering practices that have at least helped the author appreciate how our field has gotten to where it has been and where it is.A counterpart Santayana-like statement about the past and future might say, "In an era of rapid change, those who repeat the past are condemned to a bleak future." (Think about the dinosaurs, and think carefully about software engineering maturity models that emphasize repeatability.)This paper also tries to identify some of the major sources of change that will affect software engineering practices in the next couple of decades, and identifies some strategies for assessing and adapting to these sources of change. It also makes some first steps towards distinguishing relatively timeless software engineering principles that are risky not to repeat, and conditions of change under which aging practices will become increasingly risky to repeat.

REFERENCES

• 1: ISO. Standard for Information Technology - Software Life Cycle Processes. ISO/IEC 12207, 1995.
• 2: ISO. Systems Engineering - System Life Cycle Processes. ISO/IEC 15288, 2002.
• 3: FCIO (Federal CIO Council), A Practical Guide to Federal Enterprise Architecture, Version 1.0, FCIO, Washington, DC, February 2001. zaqi4.
• 4: Alford, M.W., Software Requirements Engineering Methodology (SREM) at the Age of Four, COMPSAC 80 Proceedings, (October 1980) pp 366--374.
• 5: Anthes, G., The Future of IT. Computerworld, (March 7, 2005) 27--36.
• 6: Aron, J. Software Engineering, NATO Science Committee Report, January 1969.
• 7: Arthur, W. B., Increasing Returns and the New World of Business. Harvard Business Review (July/August, 1996) 100--109.
• 8: F. T. Baker, Structured programming in a production programming environment, Proceedings of the international conference on Reliable software, p.172-185, April 21-23, 1975, Los Angeles, California
• 9: Balzer, R.M. A Global View Of Automatic Programming, Proc. 3rd Joint Conference On Artificial Intelligence, August, 1973, pp. 494--499.
• 10: Balzer, R. M., T. E. Cheatham, and C. Green, Software Technology in the 1990's: Using a New Paradigm, Computer, Nov. 1983, pp. 3945.
• 11: Victor R. Basili , Marvin V. Zelkowitz, Analyzing medium-scale software development, Proceedings of the 3rd international conference on Software engineering, p.116-123, May 10-12, 1978, Atlanta, Georgia, United States
• 12: Len Bass , Paul Clements , Rick Kazman, Software architecture in practice, Addison-Wesley Longman Publishing Co., Inc., Boston, MA, 1998
• 13: Len J. Bass , Leonard J. Bass , Joelle Coutaz, Developing Software for the User Interface, Addison-Wesley Longman Publishing Co., Inc., Boston, MA, 1991
• 14: Kent Beck, Extreme programming explained: embrace change, Addison-Wesley Longman Publishing Co., Inc., Boston, MA, 1999
• 15: Belady, L. A. and Lehman, M. M., Characteristics of large systems, in Research Directions in Software Technology, P.Wegner (editor), MIT-Press, Cambridge, Massachusetts, 1979.
• 16: Benington, H. D., Production of Large Computer Programs, Proceedings of the ONR Symposium on Advanced Program Methods for Digital Computers, June 1956, pp. 15--27. Also available in Annals of the History of Computing, October 1983, pp. 350--361.
• 17: Berners-Lee, T., World Wide Web Seminar. http://www.w3.org/Talks/General.html (1991).
• 18: Tim Berners-Lee , Robert Cailliau , Ari Luotonen , Henrik Frystyk Nielsen , Arthur Secret, The World-Wide Web, Communications of the ACM, v.37 n.8, p.76-82, Aug. 1994 [doi>10.1145/179606.179671]
• 19: Best Current Practices: Software Architecture Validation, AT&T Bell Labs, 1990.
• 20: Stefan Biffl , Aybüke Aurum , Barry Boehm , Hakan Erdogmus , Paul Grünbacher, Value-Based Software Engineering, Springer-Verlag New York, Inc., Secaucus, NJ, 2005
• 21: D. Bjorner, On the use of formal methods in software development, Proceedings of the 9th international conference on Software Engineering, p.17-29, March 1987, Monterey, California, United States
• 22: Boehm, B., Software and its impact: a quantitative assessment. Datamation, pages 48--59, May 1973.
• 23: Boehm, B. W., J. R. Brown, H. Kaspar, M. Lipow, G. J. MacLeod, M. J. Merritt, Characteristics of Software Quality, TRW Software Series TRW-SS-73-09, December 1973.
• 24: Boehm, B., Software engineering. IEEE Trans. Computers, 100(25):1226--1241, 1976.
• 25: Barry W. Boehm, Software engineering-as it is, Proceedings of the 4th international conference on Software engineering, p.11-21, September 17-19, 1979, Munich, Germany
• 26: Barry W. Boehm, Software Engineering Economics, Prentice Hall PTR, Upper Saddle River, NJ, 1981
• 27: Boehm, B., Standish, T. A. Software Technology in the 1990's: Using an Evolutionary Paradigm. IEEE Computer 16(11): 30--37 (1983).
• 28: Barry W. Boehm, A Spiral Model of Software Development and Enhancement, Computer, v.21 n.5, p.61-72, May 1988 [doi>10.1109/2.59]
• 29: Boehm B., An Early Application generator and Other Recollections, in Glass, R. L., In The Beginning: Recollections of Software Pioneers, IEEE CS Press, 1988.
• 30: Barry W. Boehm, Software risk management, IEEE Press, Piscataway, NJ, 1989
• 31: B. W. Boehm , R. Ross, Theory-W Software Project Management Principles and Examples, IEEE Transactions on Software Engineering, v.15 n.7, p.902-916, July 1989 [doi>10.1109/32.29489]
• 32: Barry W. Boehm, A Spiral Model of Software Development and Enhancement, Computer, v.21 n.5, p.61-72, May 1988 [doi>10.1109/2.59]
• 33: Barry Boehm, Anchoring the Software Process, IEEE Software, v.13 n.4, p.73-82, July 1996 [doi>10.1109/52.526834]
• 34: Barry Boehm, Managing Software Productivity and Reuse, Computer, v.32 n.9, p.111-113, September 1999 [doi>10.1109/2.789755]
• 35: Boehm, B., Brown, A.W, Basili, V. and Turner R., Spiral Acquisition of Software-Intensive Systems. CrossTalk, May 2004, pp. 4--9.
• 36: Boehm , Richard Turner, Balancing Agility and Discipline: A Guide for the Perplexed, Addison-Wesley Longman Publishing Co., Inc., Boston, MA, 2003
• 37: Boehm, B., Jain, A. An Initial Theory of Value-Based Software Engineering. In: Aurum, A., Biffl, S., Boehm, B., Er-dogmus, H., Gruenbacher, P. (eds.): Value-Based Software Engineering, Springer Verlag (2005).
• 38: Barry Boehm, Some future trends and implications for systems and software engineering processes, Systems Engineering, v.9 n.1, p.1-19, January 2006 [doi>10.1002/sys.v9:1]
• 39: Boehm, B. and Lane, J., 21st Century Processes for Acquiring 21st Century Software Intensive Systems of Systems, Cross Talk, May 2006 (to appear).
• 40: Corrado Böhm , Giuseppe Jacopini, Flow diagrams, turing machines and languages with only two formation rules, Communications of the ACM, v.9 n.5, p.366-371, May 1966 [doi>10.1145/355592.365646]
• 41: Grady Booch , James Rumbaugh , Ivar Jacobson, The Unified Modeling Language user guide, Addison Wesley Longman Publishing Co., Inc., Redwood City, CA, 1999
• 42: Frederick P. Brooks, Jr., The mythical man-month (anniversary ed.), Addison-Wesley Longman Publishing Co., Inc., Boston, MA, 1995
• 43: Frederick P. Brooks, Jr., No silver bullet: essence and accidents of software engineering, Computer, v.20 n.4, p.10-19, April 1987 [doi>10.1109/MC.1987.1663532]
• 44: J. N. Buxton , B. Randell, Software Engineering Techniques: Report of a conference sponsored by the NATO Science Committee, Rome, Italy, 27-31 Oct. 1969, Brussels, Scientific Affairs Division, NATO, 1970
• 45: PDL/74 Program Design Language Reference Guide (Processor Version 3), Caine Farber Gordon Inc., 1977.
• 46: Robert N. Charette, Software engineering risk analysis and management, McGraw-Hill, Inc., New York, NY, 1989
• 47: Geoffrey M. Clemm, The workshop system: a practical knowledge-based software environment, ACM SIGSOFT Software Engineering Notes, v.13 n.5, p.55-64, November 1988
• 48: Constantine, L. L. The Programming Profession, Programming Theory, and Programming Education. Computers and Automation 17,2 (Feb. 1968) pp. 14--19.
• 49: Diane Crawford, Editorial pointers, Communications of the ACM, v.44 n.10, p.5, Oct. 2001 [doi>10.1145/383845.383846]
• 50: Cooper, J. D., Characteristics of the Average Coder, personal communication, May 1975.
• 51: Conrow, E. H., Risk Management for Systems of Systems, CrossTalk, v. 18, n. 2 (February 2005), pages 8--12.
• 52: Michael A. Cusumano, The Software Factory: A Historical Interpretation, IEEE Software, v.6 n.2, p.23-30, March 1989 [doi>10.1109/MS.1989.1430446]
• 53: Cusumano, M., Selby, R.: Microsoft's Secrets. HarperCollins (1996).
• 54: Dahl, O., and Nygaard, K. Simula: a language for programming and description of discrete event systems. Tech. rep., Norwegian Computing Center, 1967.
• 55: Tom DeMarco, Structured Analysis and System Specification, Prentice Hall PTR, Upper Saddle River, NJ, 1979
• 56: Edsger Wybe Dijkstra, Cooperating Sequential Processes, Technical Report EWD-123, 1965
• 57: Drexler, E.K.: Engines of Creation. Anchor Press (1986)
• 58: Drexler, K.E., Peterson, C., Pergamit, G.: Unbounding the Future: The Nanotechnology Revolution. William Morrow & Co. (1991).
• 59: Dreyfus, H., Dreyfus, S.: Mind over Machine. Macmillan (1986).
• 60: Druffel, L.E.. and Buxton, J.N. Requirements for an Ada programming support environment: Rationale for STONEMAN. In Proceedings of COMPSAC 80. IEEE Computer Society, (Oct. 1980), 66--72.
• 61: George B. Dyson, Darwin among the Machines: The Evolution of Global Intelligence, Addison-Wesley Longman Publishing Co., Inc., Boston, MA, 1997
• 62: Pelle Ehn, Work-Oriented Design of Computer Artifacts, Lawrence Erlbaum Associates, Inc., Mahwah, NJ, 1990
• 63: Amr Elssamadisy , Gregory Schalliol, Recognizing and responding to "bad smells" in extreme programming, Proceedings of the 24th International Conference on Software Engineering, May 19-25, 2002, Orlando, Florida [doi>10.1145/581339.581418]
• 64: Jacky Estublier , David Leblang , André van der Hoek , Reidar Conradi , Geoffrey Clemm , Walter Tichy , Darcy Wiborg-Weber, Impact of software engineering research on the practice of software configuration management, ACM Transactions on Software Engineering and Methodology (TOSEM), v.14 n.4, p.383-430, October 2005 [doi>10.1145/1101815.1101817]
• 65: M. E. Fagan, Design and code inspections to reduce errors in program development, IBM Systems Journal, v.38 n.2-3, p.258-287, 1999
• 66: Friedman, T. L., The World Is Flat: A Brief History of the Twenty-First Century. Farrar, Straus & Giroux. New York. 2005.
• 67: Erich Gamma , Richard Helm , Ralph Johnson , John Vlissides, Design patterns: elements of reusable object-oriented software, Addison-Wesley Longman Publishing Co., Inc., Boston, MA, 1995
• 68: Grant, E., and H. Sackman., An Exploratory Investigation of Programmer Performance Under On-Lineand Off-Line Conditions. Report SP-2581, System Development Corp., September 1966.
• 69: James Gosling , Bill Joy , Guy L. Steele, The Java Language Specification, Addison-Wesley Longman Publishing Co., Inc., Boston, MA, 1996
• 70: C. A. R. Hoare, An axiomatic basis for computer programming, Communications of the ACM, v.12 n.10, p.576-580, Oct. 1969 [doi>10.1145/363235.363259]
• 71: C. A. R. Hoare, Assertions: A Personal Perspective, IEEE Annals of the History of Computing, v.25 n.2, p.14-25, April 2003 [doi>10.1109/MAHC.2003.1203056]
• 72: Floyd, C. Records and References in Algol-W, Computer Science Department, Stanford University, Stanford, California, 1969.
• 73: Freiman, F. R. and Park, R. E., The PRICE Software Cost Model, RCA Price Systems, Cherry Hill, NJ, Feb. 1979.
• 74: James A. Highsmith, III, Adaptive software development: a collaborative approach to managing complex systems, Dorset House Publishing Co., Inc., New York, NY, 2000
• 75: John Vogel Guttag, The specification and application to programming of abstract data types., 1975
• 76: Halstead, M., Elements of Software Science, North Holland, 1977.
• 77: Harned, D., Lundquist, J. "What Transformation Means for the Defense Industry". The McKinsey Quarterly, November 3, 2003: 57--63.
• 78: Holtzmann, G, The SPIN Model Checker, Addison Wesley, 2004.
• 79: Hofstede, G., Culture and Organizations. McGraw Hill (1997).
• 80: Hosier, W. A., Pitfalls and Safeguards in Real-Time Digital Systems with Emphasis on Programming, IRE Trans. Engineering Management, EM-8, June, 1961.
• 81: Watts S. Humphrey, Managing the software process, Addison-Wesley Longman Publishing Co., Inc., Boston, MA, 1989
• 82: M. A. Jackson, Principles of Program Design, Academic Press, Inc., Orlando, FL, 1975
• 83: Ivar Jacobson , Martin Griss , Patrik Jonsson, Software reuse: architecture, process and organization for business success, ACM Press/Addison-Wesley Publishing Co., New York, NY, 1997
• 84: Ivar Jacobson , Grady Booch , James Rumbaugh, The unified software development process, Addison-Wesley Longman Publishing Co., Inc., Boston, MA, 1999
• 85: Joy, B.: Why the Future Doesn't Need Us: Wired (April, 2000).
• 86: Kurzweil, R., The Age of Spiritual Machines. Penguin Books (1999).
• 87: Philippe Kruchten, The Rational Unified Process: an introduction, Addison-Wesley Longman Publishing Co., Inc., Boston, MA, 1999
• 88: Lane, J., Valerdi, R. "Synthesizing System-of-Systems Concepts for Use in Cost Estimation," IEEE SMC, 2005.
• 89: Steven Levy, Hackers: heroes of the computer revolution, Doubleday, New York, NY, 1984
• 90: Bennett P. Lientz , E. Burton Swanson, Software Maintenance Management, Addison-Wesley Longman Publishing Co., Inc., Boston, MA, 1980
• 91: Lim, W.C., Managing Software Reuse, Prentice Hall, 1998.
• 92: Barbara Liskov , Stephen Zilles, Programming with abstract data types, Proceedings of the ACM SIGPLAN symposium on Very high level languages, p.50-59, March 28-29, 1974, Santa Monica, California, United States
• 93: Littlewood, B. and Verrall, J. L., A Bayesian Reliability Growth Model for Computer Software, Appl. Statist., Vol. 22, pp. 332--346 (1973).
• 94: Maier, M., Architecting Principles for Systems of Systems, Proceedings of the Sixth Annual International Symposium, International Council on Systems Engineering, Boston, 1996, pages 567--574.
• 95: Marca, D. and Bock, G. eds., Groupware, IEEE CS Press, 1992.
• 96: Joseph F. Maranzano , Sandra A. Rozsypal , Gus H. Zimmerman , Guy W. Warnken , Patricia E. Wirth , David M. Weiss, Architecture Reviews: Practice and Experience, IEEE Software, v.22 n.2, p.34-43, March 2005 [doi>10.1109/MS.2005.28]
• 97: James Martin, Rapid application development, Macmillan Publishing Co., Inc., Indianapolis, IN, 1991
• 98: Maslow, A., Motivation and Personality, Harper and Row (1954).
• 99: Matsumoto, Y., Evaluation of the digital prediction filter applied to control a class of sevomotor by microcomputers, IEEE Transactions on IECI, Vol. IECI-23, No.4, pp.359--363(Nov. 1976).
• 100: McCabe, T., A Software Complexity Measure, IEEE Trans. Software Engineering Vol 2, No 12, 1976.
• 101: McCracken, D.D. A maverick approach to systems analysis and design. In System Analysis and Design: A Foundation for the 1980's, W.W. Cotterman, J.D. Gouger, N.L. Enger, and F. Harold, Eds. North-Holland, Amsterdam, 1981, pp. 446--451.
• 102: Steve McConnell, Rapid Development: Taming Wild Software Schedules, Microsoft Press, Redmond, WA, 1996
• 103: Stephen J. Mellor , Anthony N. Clark , Takao Futagami, Guest Editors' Introduction: Model-Driven Development, IEEE Software, v.20 n.5, p.14-18, September 2003 [doi>10.1109/MS.2003.1231145]
• 104: Bertrand Meyer, Object-oriented software construction (2nd ed.), Prentice-Hall, Inc., Upper Saddle River, NJ, 1997
• 105: Glenford J Myers, Reliable software through composite design, Petrocelli/Charter, 1975
• 106: National Institute of Standards and Technology, Gaithersberg. Reference Model for Frameworks of Software Engineering Environments, draft version 1.5 edition, 1991.
• 107: Naur, P. and Randell, B. (Eds.). Software Engineering: Report of a conference sponsored by the NATO Science Committee (7-11 Oct. 1968), Garmisch, Germany. Brussels, Scientific Affairs Division, NATO, 1969.
• 108: Neighbors, J.M., The Draco Approach to constructing Software from reusable components, IEEE Trans. Software Engineering, vol.SE-10, No.5, pp.564--574, September, 1984.
• 109: Nelson, E., Management Handbook for the Estimation of Computer Programming Costs, Systems Development Corporation, Oct. 1966.
• 110: Nunamaker, J. et. al., "Lessons from a Dozen years of Group Support Systems Research: A Discussion of lab and Field Findings," J.MIS, vol. B, no.3 (1996-1997), pp. 163--207.
• 111: L. Osterweil, Software processes are software too, Proceedings of the 9th international conference on Software Engineering, p.2-13, March 1987, Monterey, California, United States
• 112: Leon Osterweil , Carlo Ghezzi , Jeff Kramer , Alexander Wolf, Editorial, ACM Transactions on Software Engineering and Methodology (TOSEM), v.14 n.4, p.381-382, October 2005 [doi>10.1145/1101815.1101816]
• 113: Paulk, M., Weber, C., Curtis, B., Chrissis, M., The Capability Maturity Model. Addison Wesley (1994).
• 114: CORPORATE Carnegie Mellon University , Mark C. Paulk , Charles V. Weber , Bill Curtis , Mary Beth Chrissis, The capability maturity model: guidelines for improving the software process, Addison-Wesley Longman Publishing Co., Inc., Boston, MA, 1995
• 115: D. L. Parnas, On the criteria to be used in decomposing systems into modules, Communications of the ACM, v.15 n.12, p.1053-1058, Dec. 1972 [doi>10.1145/361598.361623]
• 116: Parnas, D. L. On the design and development of program families, IEEE Trans. Software Engineering 2(1), 1--9, 1976.
• 117: Parnas, D. L. Designing software for ease of extension and contraction, IEEE Trans. Software Engineering SE-5(2), 128--138, 1979.
• 118: David A. Patterson, 20^th century vs. 21^st century C&C: the SPUR manifesto, Communications of the ACM, v.48 n.3, March 2005 [doi>10.1145/1047671.1047688]
• 119: Maria H. Penedo , E. Don Stuckle, PMDB—a project master database for software engineering environments, Proceedings of the 8th international conference on Software engineering, p.150-157, August 28-30, 1985, London, England
• 120: Dewayne E. Perry , Alexander L. Wolf, Foundations for the study of software architecture, ACM SIGSOFT Software Engineering Notes, v.17 n.4, p.40-52, Oct. 1992 [doi>10.1145/141874.141884]
• 121: Monvorath Phongpaibul , Barry Boehm, Improving quality through software process improvement in Thailand: initial analysis, Proceedings of the third workshop on Software quality, May 17-17, 2005, St. Louis, Missouri
• 122: PITAC (President's Information Technology Advisory Committee), Report to the President: Information Technology Research: Investing in Our Future (1999).
• 123: Poore, J. H. and Carmen J. Trammell, Bringing Respect to Testing Through Statistical Science, American Programmer, Vol. 10, No. 8, August, 1997.
• 124: Poulin, J.S., Measuring Software Reuse, Addison Wesley, 1997.
• 125: Putnam, L. H., A General Empirical Solution to the Macro Software Sizing and Estimating Problem, IEEE Trans. Software Engineering, Vol 4, No 4, 1978.
• 126: Putman, J. Architecting with RM-ODP. Prentice Hall, 2001.
• 127: Eric S. Raymond , Tim O'Reilly, The Cathedral and the Bazaar, O'Reilly & Associates, Inc., Sebastopol, CA, 1999
• 128: Donald J. Reifer, Practical Software Reuse, John Wiley & Sons, Inc., New York, NY, 1997
• 129: Samuel T. Redwine, Jr. , William E. Riddle, Software technology maturation, Proceedings of the 8th international conference on Software engineering, p.189-200, August 28-30, 1985, London, England
• 130: Ross, D. Structured Analysis (SA): A Language for Communicating Ideas. IEEE Trans. Software Engineering, SE-3, 1 (Jan. 1977). 16--34.
• 131: Royce, W. W., Managing the Development of Large Software Systems: Concepts and Techniques, Proceedings of WESCON, August 1970.
• 132: Walker Royce, Software project management: a unified framework, Addison-Wesley Longman Publishing Co., Inc., Boston, MA, 1998
• 133: Barbara G. Ryder , Mary Lou Soffa , Margaret Burnett, The impact of software engineering research on modern progamming languages, ACM Transactions on Software Engineering and Methodology (TOSEM), v.14 n.4, p.431-477, October 2005 [doi>10.1145/1101815.1101818]
• 134: Sage, A., Cuppan, C., On the Systems Engineering and Management of Systems of Systems and Federations of Systems, Information, Knowledge, and Systems Management, v. 2 (2001), pages 325--345.
• 135: Douglas C. Schmidt, Guest Editor's Introduction: Model-Driven Engineering, Computer, v.39 n.2, p.25, February 2006 [doi>10.1109/MC.2006.58]
• 136: Mary Shaw , David Garlan, Software architecture: perspectives on an emerging discipline, Prentice-Hall, Inc., Upper Saddle River, NJ, 1996
• 137: Ben Shneiderman, Software psychology: Human factors in computer and information systems (Winthrop computer systems series), Winthrop Publishers, 1980
• 138: Shooman, M.L., Probabilistic Models for Software Reliability Prediction. Statistical Computer Performance Evaluation, Academic Press, New York, pp. 485--502 (1972).
• 139: Richard M. Stallman, Free Software, Free Society: Selected Essays of Richard M. Stallman, Gnu Press, 2002
• 140: Standish Group, Extreme Chaos, http://www.standishgroup.com (2001).
• 141: Bjarne Stroustrup, The C++ programming language, Addison-Wesley Longman Publishing Co., Inc., Boston, MA, 1986
• 142: Teichroew, D. and Sayani, H. Automation of system building. Datamation 17,16 (August 15, 1971), 25--30.
• 143: The Open Road: A History of Free Software, http://www.sdmagazine.com/opensourcetimeline/sources.htm
• 144: Toulmin, S., Cosmopolis, University of Chicago Press (1992).
• 145: Will Tracz, Test and analysis of software architectures, Proceedings of the 1996 ACM SIGSOFT international symposium on Software testing and analysis, p.1-3, January 08-10, 1996, San Diego, California, United States
• 146: Webster's Collegiate Dictionary, Merriam-Webster, 2002.
• 147: G. M. Weinberg, The psychology of computer programming, Van Nostrand Reinhold Co., New York, NY, 1988
• 148: Wirth, N. The programming language Pascal. Acta Infformatica, 1:35--63, 1971.
• 149: N. Wirth, Programming in Modula-2, Springer-Verlag Telos, 1983
• 150: Wulf, W. A., London, R., and Shaw, M., An Introduction to the Construction and Verification of Alphard Program. IEEE Trans. Software Engineering, SE-2, 1976, pp. 253--264.
• 151: Ye Yang , Jesal Bhuta , Barry Boehm , Daniel N. Port, Value-Based Processes for COTS-Based Applications, IEEE Software, v.22 n.4, p.54-62, July 2005 [doi>10.1109/MS.2005.112]
• 152: Yang, Y., Boehm, B., and Port, D. A Contextualized Study of COTS-Based E-Service Projects. Proceedings, Software Process Workshop 2005 (May, 2005).
• 153: Yourdon E. and Constantine, L. L., Structured Design. Yourdon Press, 1975.
• 154: John A. Zachman, A framework for information systems architecture, IBM Systems Journal, v.26 n.3, p.276-292, 1987

INDEX TERMS

Primary Classification:
  D. Software
  D.2 SOFTWARE ENGINEERING
      D.2.9 Management
          Subjects: Cost estimation

Additional Classification:
  D. Software
  D.2 SOFTWARE ENGINEERING
      D.2.9 Management
          Subjects: Software configuration management; Life cycle; Productivity

General Terms:
Economics, Human Factors, Management

Keywords:
software engineering, software futures, software history