Aerospace Safety Advisory Panel

This report covers the activities of the Aerospace Safety Advisory Panel (ASAP) for calendar year 1998-a year of sharp contrasts and significant successes at NASA. The year opened with the announcement of large workforce cutbacks. The slip in the schedule for launching the International Space Station (ISS) created a 5-month hiatus in Space Shuttle launches. This slack period ended with the successful and highly publicized launch of the STS-95 mission. As the year closed, ISS assembly began with the successful orbiting and joining of the Functional Cargo Block (FGB), Zarya, from Russia and the Unity Node from the United States. Throughout the year, the Panel maintained its scrutiny of NASAs safety processes. Of particular interest were the potential effects on safety of workforce reductions and the continued transition of functions to the Space Flight Operations Contractor. Attention was also given to the risk management plans of the Aero-Space Technology programs, including the X-33, X-34, and X-38. Overall, the Panel concluded that safety is well served for the present. The picture is not as clear for the future. Cutbacks have limited the depth of talent available. In many cases, technical specialties are "one deep." The extended hiring freeze has resulted in an older workforce that will inevitably suffer significant departures from retirements in the near future. The resulting "brain drain" could represent a future safety risk unless appropriate succession planning is started expeditiously. This and other topics are covered in the section addressing workforce. In the case of the Space Shuttle, beneficial and mandatory safety and operational upgrades are being delayed because of a lack of sufficient present funding. Likewise, the ISS has little flexibility to begin long lead-time items for upgrades or contingency planning

Aerospace Safety Advisory Panel

During 1997, the Aerospace Safety Advisory Panel (ASAP) continued its safety reviews of NASA's human space flight and aeronautics programs. Efforts were focused on those areas that the Panel believed held the greatest potential to impact safety. Continuing safe Space Shuttle operations and progress in the manufacture and testing of primary components for the International Space Station (ISS) were noteworthy. The Panel has continued to monitor the safety implications of the transition of Space Shuttle operations to the United Space Alliance (USA). One area being watched closely relates to the staffing levels and skill mix in both NASA and USA. Therefore, a section of this report is devoted to personnel and other related issues that are a result of this change in NASA's way of doing business for the Space Shuttle. Attention will continue to be paid to this important topic in subsequent reports. Even though the Panel's activities for 1997 were extensive, fewer specific recommendations were formulated than has been the case in recent years. This is indicative of the current generally good state of safety of NASA programs. The Panel does, however, have several longer term concerns that have yet to develop to the level of a specific recommendation. These are covered in the introductory material for each topic area in Section 11. In another departure from past submissions, this report does not contain individual findings and recommendations for the aeronautics programs. While the Panel devoted its usual efforts to examining NASA's aeronautic centers and programs, no specific recommendations were identified for inclusion in this report. In lieu of recommendations, a summary of the Panel's observations of NASA's safety efforts in aeronautics and future Panel areas of emphasis is provided. With profound sadness the Panel notes the passing of our Chairman, Paul M. Johnstone, on December 17, 1997, and our Staff Assistant, Ms. Patricia M. Harman, on October 5, 1997. Other changes to the Panel composition during the past year were: the resignation of Mr. Dennis E. Fitch as a Consultant; the appointment of Mr. Roger D. Schaufele as a Consultant; and the assignment of Ms. Susan M. Smith as Staff Assistant

A view of software management issues

The Software Development Environment (SDE) Panel addressed key programmatic, scope, and structural issues raised by its members and the general audience regarding the proposed software development environment for the Space Station program. The general team approach taken by this group led to a consensus on 18 recommendations to NASA mangament regarding the acquisition and definition of the SDE. This approach was keyed by the initial issues presentation given to the general audience. Additional issues (for a total of 23) were developed by the panelists in their first closed session from which key areas were selected and discussed in open session. These discussions led to key recommendations which are summarized and described

Space Station Engineering Design Issues

Space Station Freedom topics addressed include: general design issues; issues related to utilization and operations; issues related to systems requirements and design; and management issues relevant to design

Developing a Competency Model for Highway Safety Engineers: A Delphi Method

The primary purpose of this study was to determine the core competencies needed by State DOT Highway Safety Engineers as perceived by Highway Safety experts in the United States. First, a list of competencies was identified. Next, a panel of Highway Safety experts determined the importance of each identified competency for the current year (2020) and for the future (year 2030). Finally, ratings provided by the panel were tested for the presence of consensus. For this study, the researcher used a Delphi Method as classified by Delbecq, Van de Ven, and Gaustafson (1975). Through this method, a panel of forward-thinking experts in the field of Highway Safety were surveyed to find consensus of important and needed technical competencies for current and future Highway Safety Engineers (Gupta & Clarke, 1996). Through three rounds, these panel members were able to suggest and rate competencies, with the option to provide any feedback they deemed necessary. Based on previous literature, a review of various professional organizations, and extensive interviews, 50 competencies were generated. During Round 1, this list of competencies was sent to identified highway safety experts across the U.S. and asked, “Is this competency important for Highway Safety Engineers for the year 2020 (or 2030)?” Here, the panel suggested edits to 9 currently listed competencies and defined 18 additional competencies. In Round 2, participants rated all 68 competencies on a five-point anchored scale. In Round 3, the panel was provided the median scores for each competency listed in Round 2 and asked to keep or change their rating to match the group’s rating and provide any justification as necessary. At the conclusion of Round 3, all competencies were listed as achieving consensus as established a’ priori at greater than 50% indicating a set of core competencies essential to the role of Highway Safety engineers in the year 2020 and 2030. Since the panel was shown to be effective and forward-thinking in their views, the researcher recommends state DOTs and national organizations involved in trainings regarding highway safety engineers move toward the inclusion of all competencies rated substantial or high importance in required training

Software test and evaluation study phase I and II : survey and analysis

Issued as Final report, Project no. G-36-661 (continues G-36-636; includes A-2568

Proceedings of the Fifteenth Annual Software Engineering Workshop

The Software Engineering Laboratory (SEL) is an organization sponsored by GSFC and created for the purpose of investigating the effectiveness of software engineering technologies when applied to the development of applications software. The goals of the SEL are: (1) to understand the software development process in the GSFC environment; (2) to measure the effect of various methodologies, tools, and models on this process; and (3) to identify and then to apply successful development practices. Fifteen papers were presented at the Fifteenth Annual Software Engineering Workshop in five sessions: (1) SEL at age fifteen; (2) process improvement; (3) measurement; (4) reuse; and (5) process assessment. The sessions were followed by two panel discussions: (1) experiences in implementing an effective measurement program; and (2) software engineering in the 1980's. A summary of the presentations and panel discussions is given

Software component testing : a standard and the effectiveness of techniques

This portfolio comprises two projects linked by the theme of software component testing, which is also often referred to as module or unit testing. One project covers its standardisation, while the other considers the analysis and evaluation of the application of selected testing techniques to an existing avionics system. The evaluation is based on empirical data obtained from fault reports relating to the avionics system. The standardisation project is based on the development of the BC BSI Software Component Testing Standard and the BCS/BSI Glossary of terms used in software testing, which are both included in the portfolio. The papers included for this project consider both those issues concerned with the adopted development process and the resolution of technical matters concerning the definition of the testing techniques and their associated measures. The test effectiveness project documents a retrospective analysis of an operational avionics system to determine the relative effectiveness of several software component testing techniques. The methodology differs from that used in other test effectiveness experiments in that it considers every possible set of inputs that are required to satisfy a testing technique rather than arbitrarily chosen values from within this set. The three papers present the experimental methodology used, intermediate results from a failure analysis of the studied system, and the test effectiveness results for ten testing techniques, definitions for which were taken from the BCS BSI Software Component Testing Standard. The creation of the two standards has filled a gap in both the national and international software testing standards arenas. Their production required an in-depth knowledge of software component testing techniques, the identification and use of a development process, and the negotiation of the standardisation process at a national level. The knowledge gained during this process has been disseminated by the author in the papers included as part of this portfolio. The investigation of test effectiveness has introduced a new methodology for determining the test effectiveness of software component testing techniques by means of a retrospective analysis and so provided a new set of data that can be added to the body of empirical data on software component testing effectiveness

Software system safety

Software itself is not hazardous, but since software and hardware share common interfaces there is an opportunity for software to create hazards. Further, these software systems are complex, and proven methods for the design, analysis, and measurement of software safety are not yet available. Some past software failures, future NASA software trends, software engineering methods, and tools and techniques for various software safety analyses are reviewed. Recommendations to NASA are made based on this review