The flight software on virtually every mission currently managed by JPL has several major flaws that make it vulnerable to potentially fatal software defects. Many of these problems can be addressed by recently developed partitioned operating systems (OS). JPL has avoided adopting a partitioned operating system on its flight missions, primarily because doing so would require significant changes in flight software design, and the risks associated with changes of that magnitude cannot be accepted by an active flight project. The choice of a partitioned OS can have a dramatic effect on the overall system and software architecture, allowing for realization of benefits far beyond the concerns typically associated with the choice of OS. Specifically, we believe that a partitioned operating system, when coupled with an appropriate architecture, can provide a strong infrastructure for developing systems for which reusability, modifiability, testability, and reliability are essential qualities. By adopting a partitioned OS, projects can gain benefits throughout the entire development lifecycle, from requirements and design, all the way to implementation, testing, and operations.
Safety-Critical Partitioned Software Architecture: A Partitioned Software Architecture for Robotic
Infotech@Aerospace 2011 ; 2011 ; Saint Louis, MO, United States
2011-03-21
Aufsatz (Konferenz)
Keine Angabe
Englisch
British Library Conference Proceedings | 2011
|SAE Technical Papers | 2016
|Partitioned Embedded Architecture Based on Hypervisor: The XtratuM Approach
Tema Archiv | 2010
|