Applying a Formal Requirements Method to Three NASA Systems: Lessons Learned

Recently, a formal requirements method called SCR (Software Cost Reduction) was used to specify software requirements of mission-critical components of three NASA systems. The components included a fault protection engine, which determines how a spacecraft should respond to a detected fault; a fault...

Full description

Saved in:
Bibliographic Details
Main Authors: Heitmeyer, Constance L, Jeffords, Ralph D
Format: Report
Language:English
Subjects:
Computer Programming and Software
COMPUTER PROGRAMS
CONTROL
COST REDUCTION
DISPLAY SYSTEMS
ENGINES
FAULT DETECTION
FAULTS
LESSONS LEARNED
MISSIONS
MONITORING
ORBITS
PROTECTION
RECOVERY
REQUIREMENTS
SOFTWARE ENGINEERING
SPACE CREWS
SPACECRAFT
SPECIFICATIONS
Online Access:Request full text
Tags: Add Tag
No Tags, Be the first to tag this record!
Description
Summary:Recently, a formal requirements method called SCR (Software Cost Reduction) was used to specify software requirements of mission-critical components of three NASA systems. The components included a fault protection engine, which determines how a spacecraft should respond to a detected fault; a fault detection, isolation and recovery component, which, in response to an undesirable event, outputs a failure notification and raises one or more alarms; and a display system, which allows a space crew to monitor and control on-orbit scientific experiments. This paper demonstrates how significant and complex requirements of one of the components can be translated into an SCR specification and describes the errors detected when the authors formulated the requirements in SCR. It also discusses lessons learned in using formal methods to document the software requirements of the three components. Based on the authors experiences, the paper presents several recommendations for improving the quality of requirements specifications of safety-critical aerospace software. The original document contains color images.