Search NASA⌕ Search

Engineering topics

Lorraine Prokop

Publications and source records attributed to Lorraine Prokop.

Considerations for Software Fault Prevention and Tolerance

Mission or safety-critical spaceflight systems should be developed to both reduce the likelihood of software faults pre-flight and to detect/mitigate the effects of software errors should they occur in-flight. New data is available that categorizes software errors from significant historic spaceflight software incidents with implications and considerations to better develop and design software to both minimize and tolerate these most likely software failures.

Avionics↗

NASA Framework for the Ethical Use of Artificial Intelligence (AI)

The NASA Framework for the Ethical Use of Artificial Intelligence (AI) provides six key principles to guide NASA's use of AI. The principles are NASA's AI must be 1. Fair, 2., Explainable and transparent, 3. Accountable, 4. Secure and safe, 5. Human-centric and societally beneficial, and 6. Scientifically and technically robust. The framework describes each ethical AI principle, and then applies that principle to NASA work. The framework also includes a list of questions practitioners should use to guide their AI work. Finally, the framework focuses on concrete, practical considerations for the next five - ten years, while also beginning to lay the foundation for longer-term disruptive change as human-level (or beyond) AI is created.

Artificial Intelligence↗

Historical Aerospace Software Errors Categorized to Influence Fault Tolerance

- Motivation - Very little literature exists characterizing software errors in real-time avionic systems - How, where, and why is software most likely to fail? - Purpose - Raise awareness of how software fails through historical study - Recommend improvements to software fault tolerant design based on historical study - Outline - Discuss Software Failures - Common Cause, Failure Classes, Mitigation strategies - Review NASA requirements for Software Fault Tolerance - Review Historical Software Failures - Analyze failures and provide statistics - Erroneous vs. fail-Silent - Reboot recoverability likelihood - Code Location - Missing or unknown code?

Flilght↗