NASA study on flight software complexity

AIAA Infotech at Aerospace Conference and Exhibit and AIAA Unmanned...Unlimited Conference

Volumn , Issue , 2009, Pages

  Dvorak, Daniel L ^a  

^a CALIFORNIA INSTITUTE OF TECHNOLOGY   (United States)

Author keywords

[No Author keywords available]

Indexed keywords

CHIEF ENGINEERS; FLIGHT SOFTWARE; REQUIREMENTS DEFINITION; SPACE MISSIONS;

LAUNCHING; NASA;

SPACE FLIGHT;

EID: 77958512400     PISSN: None     EISSN: None     Source Type: Conference Proceeding    
DOI: None     Document Type: Conference Paper

References (31)

1. Aldiwan, W. and Wang, J., "Flight Software 101: Ten Things JPL Engineers Should Know about Flight Software," Flight Software and Data Systems Section, JPL/Caltech (unpublished).
2. Dvorak, D., editor, "NASA Study on Flight Software Complexity," Final Report submitted to NASA Office of Chief Engineer, March 2009, http://oce.nasa.gov.
3. Augustine, N., "Augustine's Laws," 6th Edition, American Institute of Aeronautics and Astronautics, June 1977.
4. th Digital Avionics Systems Conference, November 1998.
5. Lyu, M., editor, Handbook of Software Reliability Engineering, McGraw-Hill, 1996.
6. Chien, S., Sherwood, R., Tran, D., Cichy, B., Rabideau, G., Castano, R., Davies, A., Mandl, D., Frye, S., Trout, B., Shulman, S., and Boyer, D. "Using Autonomy Software to Improve Science Return on Earth Observing One," Journal of Aerospace Computing, Information, and Communication, April 2005.
7. IEEE Standard Computer Dictionary: A Compilation of IEEE Standard Computer Glossaries. New York, NY: 1990.
8. Dietrich Dörner, D., "The Logic of Failure: Recognizing and Avoiding Error in Complex Situations," Rowohlt Verlag GMBH 1989. English translation: Basic Books, 1996.
9. Perrow, C., Normal Accidents: Living with High-Risk Technologies, Basic Books, 1984. Updated by Princeton University Press, 1999.
10. Shapiro, S., "Splitting the Difference: The Historical Necessity of Synthesis in Software Engineering," IEEE Annals of the History of Computing, Vol. 19, No. 1, 1997.
11. Brooks, Jr., Frederick, "No Silver Bullet: Essence and Accidents of Software Engineering," Proceedings of the IFIP Tenth World Computing Conference, pp. 1069-1076, 1986.
12. Boehm, B. W., Software Engineering Economics, Englewood Cliff, Prentice Hall, 1981.
13. Charette, R. N., "This Car Runs on Code," IEEE Spectrum, Feb. 2009.
14. NPR 7123.1A, NASA Systems Engineering Processes and Requirements, http://nodis3.gsfc.nasa.gov/lib-docs.cfm?range=7-.
15. NASA Systems Engineering Handbook, NASA/SP-2007-6105 Rev1, December 2007, http://education.ksc.nasa.gov/esmdspacegrant/Documents/NASA%20SP-2007- 6105%20Rev%201%20Final%2031Dec2007.pdf.
16. Defense Acquisition University, "Best Practices Clearinghouse," https://bpch.dau.mil.
17. Ferguson, J., "Crouching Dragon, Hidden Software: Software in DoD Weapon Systems," IEEE Software, vol. 18, no. 4, pp. 105-107, July/Aug. 2001.
18. Shaw, M. and Garlan, D., Software Architecture: Perspectives on an Emerging Discipline, Prentice Hall, 1996.
19. Center for Systems and Software Engineering, University of Southern California, COCOMO II, http://sunset.usc.edu/csse/research/COCOMOII/cocomo-main. html.
20. Maranzano, J., Rozsypal, S., Zimmerman, G., Warnken, G., Wirth, P., and Weiss, D., "Architecture Reviews: Practice and Experience," IEEE Software, March/April 2005.
21. Clements, P., Kazman, R., and Klein, M., Evaluating Software Architectures: Methods and Case Studies, October 2001, Addison-Wesley.
22. Weiss, K., "Software Architecture Review Process," internal document at JPL/Caltech (unpublished), 2008.
23. Schuler, P., "Peer Review Inspection Checklists," internal document at NASA Langley Research Center (unpublished).
24. Kleinknecht, K., "Design Principles Stressing Simplicity", Chapter 2 of "What Made Apollo a Success?," March 1970, NASA SP-287, http://history.nasa.gov/SP-287/sp287.htm.
25. Reed, P., "Reference Architecture: The Best of Best Practices," September 2002, http://www.ibm.com/developerworks/rational/library/2774.html.
26. Wilmot, J., "A Core Plug and Play Architecture for Reusable Flight Software Systems", Space Mission Challenges for Information Technology 2007, July 2007, Pasadena. http://ntrs.nasa.gov/search.jsp?R=304271&id= 2&qs=N%3D4294669721.
27. Coverity, Inc., "Controlling Software Complexity: The Business Case for Static Source Code Analysis," http://www.coverity.com.
28. st Annual AAS Guidance and Control Conference, AAS 08-031, American Astronautical Society, Feb. 2008.
29. Brooks, Jr., F., The Mythical Man-Month - Essays on Software Engineering, Addison-Wesley Publishing Company, Inc, 1975.
30. National Science Foundation, Directorate for Computer & Information Science & Engineering and Directorate for Engineering, Cyber-Physical Systems, program solicitation, NSF 08-611, http://www.nsf.gov/pubs/2008/ nsf08611/nsf08611.htm.
31. NASA Planetary Spacecraft Fault Management Workshop, http://icpi.nasaprs. com/NASAFMWorkshop.