Search NASA⌕ Search

Engineering topics

Wetherholt, Martha

Publications and source records attributed to Wetherholt, Martha.

Final Report of the NASA Office of Safety and Mission Assurance Agile Benchmarking Team

To ensure that the NASA Safety and Mission Assurance (SMA) community remains in a position to perform reliable Software Assurance (SA) on NASAs critical software (SW) systems with the software industry rapidly transitioning from waterfall to Agile processes, Terry Wilcutt, Chief, Safety and Mission Assurance, Office of Safety and Mission Assurance (OSMA) established the Agile Benchmarking Team (ABT). The Team's tasks were: 1. Research background literature on current Agile processes, 2. Perform benchmark activities with other organizations that are involved in software Agile processes to determine best practices, 3. Collect information on Agile-developed systems to enable improvements to the current NASA standards and processes to enhance their ability to perform reliable software assurance on NASA Agile-developed systems, 4. Suggest additional guidance and recommendations for updates to those standards and processes, as needed. The ABT's findings and recommendations for software management, engineering and software assurance are addressed herein.

Software Assurance↗

OSMA Research and Technology Strategy Team Summary

This slide presentation reviews the work of the Office of Safety and Mission Assurance (OSMA), and the OSMA Research and Technology Strategy (ORTS) team. There is discussion of the charter of the team, Technology Readiness Levels (TRLs) and how the teams responsibilities are related to these TRLs. In order to improve the safety of all levels of the development through the TRL phases, improved communication, understanding and cooperation is required at all levels, particularly at the mid level technologies development.

Wetherholt, Martha↗

NASA Software Assurance's Roles in Research and Technology

This slide presentation reviews the interactions between the scientist and engineers doing research and technology and the software developers and others who are doing software assurance. There is a discussion of the role of the Safety and Mission Assurance (SMA) in developing software to be used for research and technology, and the importance of this role as the technology moves to the higher levels of the technology readiness levels (TRLs). There is also a call to change the way the development of software is developed.

Wetherholt, Martha↗