The article discusses the role of software in NASA’s mission directorates and the efforts of the Software Technical Discipline Team to improve best practices and minimize the risk of errors in software. Key findings from a study of historical software incidents are highlighted, including the prevalence of unexpected behavior and the importance of complete requirements. The team is using these findings to improve software processes and resilience to errors.
