23 September 2013 Software engineering processes for Class D missions
Author Affiliations +
Abstract
Software engineering processes are often seen as anathemas; thoughts of CMMI key process areas and NPR 7150.2A compliance matrices can motivate a software developer to consider other career fields. However, with adequate definition, common-sense application, and an appropriate level of built-in flexibility, software engineering processes provide a critical framework in which to conduct a successful software development project. One problem is that current models seem to be built around an underlying assumption of “bigness,” and assume that all elements of the process are applicable to all software projects regardless of size and tolerance for risk. This is best illustrated in NASA’s NPR 7150.2A in which, aside from some special provisions for manned missions, the software processes are to be applied based solely on the criticality of the software to the mission, completely agnostic of the mission class itself. That is, the processes applicable to a Class A mission (high priority, very low risk tolerance, very high national significance) are precisely the same as those applicable to a Class D mission (low priority, high risk tolerance, low national significance). This paper will propose changes to NPR 7150.2A, taking mission class into consideration, and discuss how some of these changes are being piloted for a current Class D mission—the Cyclone Global Navigation Satellite System (CYGNSS).
© (2013) COPYRIGHT Society of Photo-Optical Instrumentation Engineers (SPIE). Downloading of the abstract is permitted for personal use only.
Ronnie Killough, Ronnie Killough, Debi Rose, Debi Rose, Randall J. Rose, Randall J. Rose, } "Software engineering processes for Class D missions", Proc. SPIE 8866, Earth Observing Systems XVIII, 88660E (23 September 2013); doi: 10.1117/12.2025334; https://doi.org/10.1117/12.2025334
PROCEEDINGS
14 PAGES


SHARE
Back to Top