درباره ما
NASA-LLIS-2218
Lessons Learned – Flight Software Engineering Lessons
Year: 2009
Abstract: Abstract:
The engineering of flight software is a major consideration in establishing JPL project total cost and schedule because every mission requires a significant amount of new software to implement new spacecraft functionality. Constraints to the development and testing of software concurrent to engineering the rest of the flight system has led to flight software errors, including the loss of some missions. The findings of several JPL studies and flight mishap investigations suggest a number of recommendations for mitigating software engineering risk.
The engineering of flight software is a major consideration in establishing JPL project total cost and schedule because every mission requires a significant amount of new software to implement new spacecraft functionality. Constraints to the development and testing of software concurrent to engineering the rest of the flight system has led to flight software errors, including the loss of some missions. The findings of several JPL studies and flight mishap investigations suggest a number of recommendations for mitigating software engineering risk.
Subject: Early requirements and standards definition
Show full item record
| contributor author | NASA - National Aeronautics and Space Administration (NASA) | |
| date accessioned | 2017-09-04T15:36:04Z | |
| date available | 2017-09-04T15:36:04Z | |
| date copyright | 06/23/2009 | |
| date issued | 2009 | |
| identifier other | ORNFQCAAAAAAAAAA.pdf | |
| identifier uri | https://yse.yabesh.ir/std/handle/yse/38058 | |
| description abstract | Abstract: The engineering of flight software is a major consideration in establishing JPL project total cost and schedule because every mission requires a significant amount of new software to implement new spacecraft functionality. Constraints to the development and testing of software concurrent to engineering the rest of the flight system has led to flight software errors, including the loss of some missions. The findings of several JPL studies and flight mishap investigations suggest a number of recommendations for mitigating software engineering risk. | |
| language | English | |
| title | NASA-LLIS-2218 | num |
| title | Lessons Learned – Flight Software Engineering Lessons | en |
| type | standard | |
| page | 5 | |
| status | Active | |
| tree | NASA - National Aeronautics and Space Administration (NASA):;2009 | |
| contenttype | fulltext | |
| subject keywords | Early requirements and standards definition | |
| subject keywords | Engineering design and project processes and standards | |
| subject keywords | Flight Equipment | |
| subject keywords | Flight Operations | |
| subject keywords | Hardware | |
| subject keywords | Level II/III requirements definition | |
| subject keywords | Mission control Planning | |
| subject keywords | Payloads | |
| subject keywords | Planning of requirements verification processes | |
| subject keywords | Risk Management/Assessment | |
| subject keywords | Software | |
| subject keywords | Software Engineering | |
| subject keywords | Spacecraft | |
| subject keywords | Spacecraft and Spacecraft Instruments | |
| subject keywords | Test & Verification | |
| subject keywords | Training and simulation systems |