National Academy of Sciences | 150 Year Anniversary

Questions? Call 800-624-6242

| Items in cart [0]

The National Academies Press

PAPERBACK
price:$34.75
add to cart

Rights & Permissions

topleft topright

Critical Code: Software Producibility for Defense (2010)
Computer Science and Telecommunications Board (CSTB)

Citation Manager

. "Summary." Critical Code: Software Producibility for Defense. Washington, DC: The National Academies Press, 2010.

Please select a format:

BibTeX EndNote RefMan


Page
12
bottomleft bottomright

The following HTML text is provided to enhance online readability. Many aspects of typography translate only awkwardly to HTML. Please use the page image as the authoritative form to ensure accuracy.


Critical Code: Software Producibility for Defense

markets on the basis of initial investment in worthy projects by NITRD agencies. Under the auspices of professional societies, similar studies were published relating specifically to software engineering research.21 These reinforce the extent of the impact of well-managed investments.


Recommendation 5-2: The DOD should take action to undertake DoD-sponsored research programs in the following areas identified as critical to the advancement of defense software producibility: (1) architecture modeling and architectural analysis; (2) assurance: validation, verification, analysis of design and code; (3) process support and economic models for assurance and adaptability; (4) requirements; (5) language, modeling, coding, and tools; (6) cyber-physical systems; and (7) human-systems integration.

21

Mary Shaw, 2002, “The Tyranny of Transistors: What Counts about Software?” Proceedings of the Fourth Workshop on Economics-Driven Software Engineering Research, IEEE Computer Society, pp. 49-51; Barry Boehm, 2006, “A View of 20th and 21st Century Software Engineering,” Proceedings of the 28th International Conference on Software Engineering, ACM, pp. 12-29; and Leon J. Osterweil, Carlo Ghezzi, Jeff Kramer, and Alexander L. Wolf, 2008, “Determining the Impact of Software Engineering Research on Practice,” IEEE Computer 41(3):39-49.

Page
12