NASA-LLIS-0938
Lessons Learned – Probable Scenario for Mars Polar Lander Mission Loss (1998)
Year: 2001
Abstract: Abstract:
Neither the MPL software requirements specification nor the software, subsystem or system test plans required verification of immunity to transient signals. MPL touchdown sensors generated known transient signals at leg deployment. Full leg deployment test was not repeated after wiring corrections. Tests should be re-run after test deficiencies are corrected or hardware or software is revised unless clear rationale exists for not doing so. Hardware operational characteristics, including transients and spurious signals must be reflected in software requirements and verified by test.
Neither the MPL software requirements specification nor the software, subsystem or system test plans required verification of immunity to transient signals. MPL touchdown sensors generated known transient signals at leg deployment. Full leg deployment test was not repeated after wiring corrections. Tests should be re-run after test deficiencies are corrected or hardware or software is revised unless clear rationale exists for not doing so. Hardware operational characteristics, including transients and spurious signals must be reflected in software requirements and verified by test.
Subject: Flight Equipment
Show full item record
| contributor author | NASA - National Aeronautics and Space Administration (NASA) | |
| date accessioned | 2017-09-04T15:22:00Z | |
| date available | 2017-09-04T15:22:00Z | |
| date copyright | 02/15/2001 | |
| date issued | 2001 | |
| identifier other | NAUEQCAAAAAAAAAA.pdf | |
| identifier uri | https://yse.yabesh.ir/std/handle/yse/22018 | |
| description abstract | Abstract: Neither the MPL software requirements specification nor the software, subsystem or system test plans required verification of immunity to transient signals. MPL touchdown sensors generated known transient signals at leg deployment. Full leg deployment test was not repeated after wiring corrections. Tests should be re-run after test deficiencies are corrected or hardware or software is revised unless clear rationale exists for not doing so. Hardware operational characteristics, including transients and spurious signals must be reflected in software requirements and verified by test. | |
| language | English | |
| title | NASA-LLIS-0938 | num |
| title | Lessons Learned – Probable Scenario for Mars Polar Lander Mission Loss (1998) | en |
| type | standard | |
| page | 3 | |
| status | Active | |
| tree | NASA - National Aeronautics and Space Administration (NASA):;2001 | |
| contenttype | fulltext | |
| subject keywords | Flight Equipment | |
| subject keywords | Hardware | |
| subject keywords | Policy & Planning | |
| subject keywords | Risk Management/Assessment | |
| subject keywords | Safety & Mission Assurance | |
| subject keywords | Software | |
| subject keywords | Software Test | |
| subject keywords | Spacecraft | |
| subject keywords | System Integration and Test | |
| subject keywords | Test & Verification | |
| subject keywords | Test Article | |
| subject keywords | Test Planning |

درباره ما