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.
An Assessment of Space Shuttle Flight Software Development Processes
position in the organizational matrix, the members' individual and collective expertise, their independence, and their impartiality.
Thus, such a panel provides additional benefits to those provided by the ongoing safety efforts: independence and lack of involvement in internal politics, additional confidence that nothing falls through the cracks from a safety viewpoint, accountability to management and the public, and a means for an open forum and expanded communications for all levels and types of technical and administrative personnel.
Although software should be part of the normal ASAP activities, special expertise is needed to deal with software issues. A special subcommittee of the ASAP to consider software safety issues could demonstrate and give visibility to NASA's understanding of the growing importance of, and dependence upon, software to the safe accomplishment of NASA 's mission and its commitment to resolving the issues related to this relatively new technology.
Recommendation #10:NASA should establish better reporting and management relationshipsbetween developers, centers, programs, and the headquarters SafetyOffice.
Recommendation #11:NASA should consider the establishment of a NASA safety certificationpanel or board separate from the program offices and also the establishmentof a subcommittee of the Aerospace Safety Advisory Panel to dealwith software issues.