National Academies Press: OpenBook
« Previous: Implementation of Recommended Strategy for Investment in ADA
Suggested Citation:"Bibliography." National Research Council. 1997. Ada and Beyond: Software Policies for the Department of Defense. Washington, DC: The National Academies Press. doi: 10.17226/5463.
×

Bibliography

Aerospace Industries Association (AIA). 1996. "AIA Position Statement on Ada." Unpublished manuscript. AIA, Washington, D.C., July 12.

Aley, James. 1996. "Give It Away and Get Rich." Fortune, June 10, p. 98.

AT&T. 1993. "Best Current Practices: Software Architecture Validation." AT&T, Murray Hill, N.J.


Boehm, Barry. 1981. Software Engineering Economics. Prentice-Hall, Englewood Cliffs, N.J.

Boehm, Barry, and W.E. Royce. 1988. "TRW IOC Ada COCOMO: Definition and Refinements." Proceedings of the 4th COCOMO Users Group, Pittsburgh, Pa., November.

Boehm, Barry. 1996. "Anchoring the Software Process." IEEE Software, Vol. 13, No. 4, July, pp. 73-82.

Boehm, Barry, et al. 1996. "The COCOMO 2.0 Software Cost Estimation Model: A Status Report." American Programmer, Vol. 9, No. 7, July, pp. 2-17.

Booch, Grady. 1987. Software Engineering with Ada, Third Edition, Chapter 3: "The History of Ada's Development." Benjamin/Cummings, Menlo Park, Calif.

Brooks, Jr., Frederick P. 1986. "No Silver Bullet-Essence and Accidents of Software Engineering." Information Processing 86, pp. 1069-1076. (Reprinted in IEEE Computer Magazine, April 1987.)

Brown, Norm. 1996. "Industrial Strength Management Strategies." IEEE Software, Vol. 13, No. 4, July, pp. 94103.


Carleton, Anita D., et al. 1992. "Defining and Using Software Measures." Software Engineering Institute Technical Reports, CMU-SEI-TR-11, 19-23. Software Engineering Institute, Pittsburgh, Pa.

Computer Science and Telecommunications Board (CSTB). 1989. Scaling Up: A Research Agenda for Software Engineering. National Academy Press, Washington, D.C.

CTA. 1991. "Survey and Analysis of Productivity and Cost Data on Ada and C++ Software Development Programs." CTA Incorporated, Burlington, Mass., June 26.


Department of Defense (DOD). 1976. Directive 5000.29, "Management of Computer Resources in Major Defense Systems." April 26.

Department of Defense (DOD). 1987a. Directive 3405.1, "Computer Programming Language Policy." April 2.

Department of Defense (DOD). 1987b. "Military Software." Defense Science Board Task Force on Military Software (Frederick P. Brooks, Jr., Chair), Office of the Under Secretary of Defense for Acquisition, DOD, Washington, D.C., September.

Department of Defense (DOD). 1991. "Draft DOD Software Technology Strategy." Director of Defense Research and Engineering, DOD, Washington, D.C., December.

Suggested Citation:"Bibliography." National Research Council. 1997. Ada and Beyond: Software Policies for the Department of Defense. Washington, DC: The National Academies Press. doi: 10.17226/5463.
×

Department of Defense (DOD). 1992. "Delegations of Authority and Clarifying Guidance on Waivers from the Use of the Ada Programming Language." April 17.

Department of Defense (DOD). 1994a. "Report of the Defense Science Board Task Force on Acquiring Defense Software Commercially." DOD, Washington, D.C., June.

Department of Defense (DOD). 1994b. "Specifications and Standards: A New Way of Doing Business." June 29.

Department of Defense (DOD). 1995a. "New World Vistas: Air and Space Power for the 21st Century. Information Technology Volume." Air Force Scientific Advisory Board, Washington D.C.

Department of Defense (DOD). 1995b. "Dual Use Technology: A Defense Strategy for Affordable, Leading-Edge Technology." Under Secretary of Defense for Acquisition and Technology, DOD, Washington, D.C., February.

Department of Defense (DOD). 1995c. "ARPA Software Review Panel-Final Report." DOD, Washington, D.C., October.

Department of Defense (DOD). 1996a. "Practical Software Measurement Version 2.1." Joint Logistics Commanders, Joint Group on Systems Engineering, DOD, Washington, D.C., March 27.

Department of Defense (DOD). 1996b. Directive 5000.1, "Defense Acquisition." February 21.

Department of Defense (DOD). 1996c. Regulation 5000.2-R, "Mandatory Procedures for Major Defense Acquisition Programs (MDAPs) and Major Automated Information System (MAIS) Acquisition Programs." March 15.

Department of Defense (DOD). 1996d. "Joint Warfighting Science and Technology Plan." Office of the Secretary of Defense, DOD, Washington, D.C., May.

Druffel, Larry. 1993. "Ada Position Paper." Unpublished manuscript, December 1.

Emery, James C., and Martin J. McCaffrey. 1991. "Ada and Management Information Systems: Policy Issues Concerning Programming Language Options for the Department of Defense." Naval Postgraduate School, Monterey, Calif., June.

Emery, James C., and Dani Zweig. 1993. "The Use of Ada for the Implementation of Automated Information Systems Within the Department of Defense." Naval Postgraduate School, Monterey, Calif., December 28.


Feigenbaum, Edward. 1996. "The Ada Mandate." Unpublished manuscript, Chief Scientist, U.S. Air Force.

Feldman, Michael B. 1996. "Ada as a Foundation Programming Language." Available on-line at http://www.seas.gwu.edu/faculty/mfeldman/CS 1-2.html#2.

Fisher, D.A. 1976. "A Common Programming Language for the Department of Defense-Background and Technical Requirements." Report P-1991. Institute for Defense Analyses, p. 6. (Cited by G. Booch in Software Engineering with Ada, Third Edition, 1987, p. 9.)

Fisher, David. 1974. "Automatic Data Processing Costs in the Defense Department." IDA Paper P-1046. Institute for Defense Analyses, Alexandria, Va., October.

Frazier, Thomas P., and John W. Bailey. 1996. "The Costs and Benefits of Domain-Oriented Software Reuse: Evidence from the STARS Demonstration Projects." IDA Paper P-3191. Institute for Defense Analyses, Alexandria, Va., June.


General Accounting Office. 1989. "Programming Language: Status, Costs, and Issues Associated with Defense's Implementation of Ada." GAO/IMTEC-89-9. General Accounting Office, Washington, D.C., March.

General Accounting Office. 1991. "Programming Language: Defense Policies and Plans for Implementing Ada." GAO/IMTEC-91-70BR. General Accounting Office, Washington, D.C., September.

General Accounting Office. 1993. "Software Reuse: Major Issues Need to Be Resolved Before Benefits Can Be Achieved." GAO/IMTEC-93-16. General Accounting Office, Washington, D.C., January.

Giallombardo, Robert J. 1992. "Effort and Schedule Estimating Models for Ada Software Development." MTR 11303. MITRE Corporation, Bedford, Mass., May.


Hook, Audrey A., et al. 1991. "Availability of Ada and C++ Compilers, Tools, Education and Training." IDA Paper P-2601. Institute for Defense Analyses, Alexandria, Va., June 12.

Hook, Audrey A., et al. 1995. "A Survey of Computer Programming Languages Currently Used in the Department of Defense." IDA Paper P-3054. Institute for Defense Analyses, Alexandria, Va., January.

Horowitz, Barry. 1991. "The Importance of Architecture in DOD Software." M91-35. MITRE Corporation, Bedford, Mass., July.


IBM Federal Systems Division. 1985. "Language Selection Analysis Report." FAA-85-S-0874. Prepared for the Federal Aviation Administration, Gaithersburg, Md., May.

Suggested Citation:"Bibliography." National Research Council. 1997. Ada and Beyond: Software Policies for the Department of Defense. Washington, DC: The National Academies Press. doi: 10.17226/5463.
×

IIT Research Institute (IITRI). 1996. "Catalog of Resources for Education in Ada and Software Engineering, Version 8.0." Prepared for the Ada Joint Program Office, Arlington, Va., January.

Jensen, L.W., and S. Lucas. 1983. "Sensitivity Analysis of the Jensen Software Model." Hughes Aircraft Co., Los Angeles, Calif.

Jones, Capers. 1994. "The Economics of Object Oriented Software." American Programmer, Vol. 7, No. 10, October, pp. 28-35.

Jones, Capers. 1995. "Backfiring: Converting Lines of Code to Function Points." Computer, Vol. 28, No. 11, November, pp. 87-88.

Jones, Capers. 1996a. "Estimating and Measuring Object-Oriented Software." Unpublished manuscript, February 1.

Jones, Capers. 1996b. "The Economic Impact of the Year 2000 Software Problem in the United States-Version 2." Software Productivity Research Inc., Burlington, Mass., February 22.

Jones, Capers. 1996c. "Programming Languages Table, Version 8.2." Software Productivity Research Inc., available on-line at http://www.spr.com/library/langtbl.html.

Jones, Capers. 1996d. "Using Function Points to Evaluate CASE Tools, Version 4." Software Productivity Research Inc., Burlington, Mass., August 6.


Landry, Huet C. 1996. "Comments on Ada Mandate." Unpublished manuscript, Defense Information Systems Agency/JEBEB, Software Engineering Standards.

Lawlis, Patricia K. 1996. "Guidelines for Choosing a Computer Language: Support for the Visionary Organization." C.J. Kemp Systems Inc., March.

Lubashevsky. 1996. "'Backfire' Will BACKFIRE." Measure Up. Software Productivity Solutions Inc., Indiatlantic, Fla., January, pp. 1-6.


Maranzano, Joe. 1995. "System Architecture Validation Review Findings." AT&T Software Technology Center, April.

Masters, Michael W. 1996. "Programming Languages and Life-Cycle Cost." Naval Surface Weapons Center, Dahlgren, Va., March 18.

McGarry, Frank, et al., 1994. "Software Process Improvement in the NASA Software Engineering Laboratory." CMU SEI-94-TR-22. Software Engineering Institute, Pittsburgh, Pa., December.

Mosemann, Lloyd K. 1991. "Ada and C++: A Business-Case Analysis." Deputy Assistant Secretary of the Air Force, Washington, D.C., July 9.


National Academy of Engineering. 1996. Defense Software Research, Development and Demonstration: Capitalizing on Continued Growth in Private-Sector Investment. National Academy Press, Washington, D.C., March.

National Research Council. 1995. Research-Doctorate Programs in the United States: Continuity and Change. National Academy Press, Washington, D.C.


Paulk, Mark C., et al. 1993. "Capability Maturity Model for Software, Version 1.1." CMU/SEI-93-TR-24. Software Engineering Institute, Carnegie Mellon University, Pittsburgh, Pa., February.

Perry, William. 1996a. "National Academy of Engineering, Bueche Prize Acceptance Address." Transcript. National Academy of Engineering, Washington, D.C., October 2.

Perry, William. 1996b. "Defense in an Age of Hope." Foreign Affairs, November-December, pp. 64-79. Porter, Michael E. 1990. The Competitive Advantage of Nations. The Free Press, New York. Powell, Colin. 1992. "C41 for the Warrior." DOD Joint Chiefs of Staff, Washington, D.C., June 12.


Quade, E.S., ed. 1964. Analysis for Military Decisions. Rand McNally, Chicago. Quade, E.S., and Boucher, W.I., eds. 1968. Systems Analysis and Policy Planning: Applications in Defense. American Elsevier, New York.


Reifer, Donald J. 1996. "Quantifying the Debate: Ada Versus C++." Crosstalk: The Journal of Defense Software Engineering. Hill AFB, Utah, July.

Riehle, Richard. 1996. "Ada: An Update." Object Magazine, June, pp. 50-52.

Royce, Walker. 1990. "TRW's Ada Process Model for Incremental Development of Large Software Systems." Proceedings ICSE 12, IEEE/ACM, March, pp. 2-11.


Shaw, Mary, and David Garlan. 1996. Software Architecture: Perspectives on an Emerging Discipline. Prentice-Hall, Englewood Cliffs, N.J.


Telos Corporation. 1994. "Ada Marketing Communications Study Precampaign Survey." Telos Corporation, May.

Tokar, Joyce. 1996. "Ada 95: The Language for the '90s and Beyond." Object Magazine, June, pp. 53-56.

Suggested Citation:"Bibliography." National Research Council. 1997. Ada and Beyond: Software Policies for the Department of Defense. Washington, DC: The National Academies Press. doi: 10.17226/5463.
×

TRW. 1991. "Ada and C++: A Life-cycle Cost Analysis." TRW Inc., Redondo Beach, Calif., June 1.

TRW. 1991. "Case Study: Ada and C++ Cost Comparison for CCPDS-R." TRW Inc., Redondo Beach, Calif., June 1.

U.S. Army. 1992. "Implementation of the Ada Programming Language." HQDA LTR 25-92-1. September 18.

U.S. Army. 1994. "Change to HQDA Letter 25-92-1, Implementation of the Ada Programming Language." HQDA LTR 25-94-1. July 17.

U.S. Army. 1995. "Change to HQDA Letter 25-94-1, Implementation of the Ada Programming Language." HQDA LTR 25-95-1. July 17.

U.S. Navy. 1994. "Ada Programming Language Policy," SECNAVINST 5234.2A. April 28.

U.S. Navy. 1994. "Ada Implementation Guide," 2 Vol. Naval Information Systems Management Center, April.


Vyssotsky, Victor. 1996. "Whither Ada?" Unpublished manuscript, May 12.


Waligora, Sharon, John Baily, and Mike Stark. 1995. "Impact of Ada and Object-Oriented Design in the Flight Dynamics Division at Goddard Space Flight Center." NASA-SEL Report, SEL-95-001. Goddard Space Flight Center, March.

Weiderman, Nelson. 1991. "A Comparison of Ada 83 and C++." SEI-91-SR-4. Software Engineering Institute, Pittsburgh, Pa., June.


Zeigler, Stephen F. 1995. "Comparing Development Costs of C and Ada." Rational Software Corporation, Santa Clara, Calif., March 30.

Suggested Citation:"Bibliography." National Research Council. 1997. Ada and Beyond: Software Policies for the Department of Defense. Washington, DC: The National Academies Press. doi: 10.17226/5463.
×
Page 69
Suggested Citation:"Bibliography." National Research Council. 1997. Ada and Beyond: Software Policies for the Department of Defense. Washington, DC: The National Academies Press. doi: 10.17226/5463.
×
Page 70
Suggested Citation:"Bibliography." National Research Council. 1997. Ada and Beyond: Software Policies for the Department of Defense. Washington, DC: The National Academies Press. doi: 10.17226/5463.
×
Page 71
Suggested Citation:"Bibliography." National Research Council. 1997. Ada and Beyond: Software Policies for the Department of Defense. Washington, DC: The National Academies Press. doi: 10.17226/5463.
×
Page 72
Next: A DOD Draft Software Management Policy Directive with Further Modifications Suggested by the Committee »
Ada and Beyond: Software Policies for the Department of Defense Get This Book
×
Buy Paperback | $45.00
MyNAP members save 10% online.
Login or Register to save!
Download Free PDF

The Ada programming language was created by the U.S. Department of Defense (DOD) nearly two decades ago to provide a general-purpose programming language for defense and commercial use, but has evolved into a niche solution for safety-critical systems, primarily in defense applications. Ada and Beyond presents an approach for the DOD to move beyond the debate over its policy that requires the use of Ada for all new software development.

It describes the importance of the software engineering process and recommends to DOD mechanisms for more effective review of software development and improved collection of data on software project outcomes. The volume also analyzes the technical, empirical, and business cases for using Ada and other programming languages, makes recommendations regarding the appropriate conditions under which DOD should continue to require the use of Ada, and details activities that require funding by DOD in order for Ada to remain a viable programming language.

  1. ×

    Welcome to OpenBook!

    You're looking at OpenBook, NAP.edu's online reading room since 1999. Based on feedback from you, our users, we've made some improvements that make it easier than ever to read thousands of publications on our website.

    Do you want to take a quick tour of the OpenBook's features?

    No Thanks Take a Tour »
  2. ×

    Show this book's table of contents, where you can jump to any chapter by name.

    « Back Next »
  3. ×

    ...or use these buttons to go back to the previous chapter or skip to the next one.

    « Back Next »
  4. ×

    Jump up to the previous page or down to the next one. Also, you can type in a page number and press Enter to go directly to that page in the book.

    « Back Next »
  5. ×

    Switch between the Original Pages, where you can read the report as it appeared in print, and Text Pages for the web version, where you can highlight and search the text.

    « Back Next »
  6. ×

    To search the entire text of this book, type in your search term here and press Enter.

    « Back Next »
  7. ×

    Share a link to this book page on your preferred social network or via email.

    « Back Next »
  8. ×

    View our suggested citation for this chapter.

    « Back Next »
  9. ×

    Ready to take your reading offline? Click here to buy this book in print or download it as a free PDF, if available.

    « Back Next »
Stay Connected!