درباره ما
NASA-LLIS-0195
Lessons Learned - Orbiter Software Upgrades.
Year: 1992
Abstract: Description of Driving Event:
The movement of some requests for software upgrades to crew procedures is a matter of serious concern. The crew already has a very large number of procedures with which to be familiar. Adding to that load, particularly with items that could be handled easily with greater reliability and safety by software, does not seem wise. Procedures such as "do not touch the keyboard for X seconds after the occurrence of event Y" can be handled easily by software. If such procedures are contingencies that are employed infrequently, the chance of error when they are needed rises.
A review of all computer-related procedures to ascertain whether or not there is significant potential for design-induced human errors should be mounted. This review should include crew representatives, experts on human factors, and members of safety and mission quality organization.
The movement of some requests for software upgrades to crew procedures is a matter of serious concern. The crew already has a very large number of procedures with which to be familiar. Adding to that load, particularly with items that could be handled easily with greater reliability and safety by software, does not seem wise. Procedures such as "do not touch the keyboard for X seconds after the occurrence of event Y" can be handled easily by software. If such procedures are contingencies that are employed infrequently, the chance of error when they are needed rises.
A review of all computer-related procedures to ascertain whether or not there is significant potential for design-induced human errors should be mounted. This review should include crew representatives, experts on human factors, and members of safety and mission quality organization.
Subject: Flight Equipment
Show full item record
| contributor author | NASA - National Aeronautics and Space Administration (NASA) | |
| date accessioned | 2017-09-04T15:15:39Z | |
| date available | 2017-09-04T15:15:39Z | |
| date copyright | 33912 | |
| date issued | 1992 | |
| identifier other | MGZCQCAAAAAAAAAA.pdf | |
| identifier uri | https://yse.yabesh.ir/std/handle/yse/14685 | |
| description abstract | Description of Driving Event: The movement of some requests for software upgrades to crew procedures is a matter of serious concern. The crew already has a very large number of procedures with which to be familiar. Adding to that load, particularly with items that could be handled easily with greater reliability and safety by software, does not seem wise. Procedures such as "do not touch the keyboard for X seconds after the occurrence of event Y" can be handled easily by software. If such procedures are contingencies that are employed infrequently, the chance of error when they are needed rises. A review of all computer-related procedures to ascertain whether or not there is significant potential for design-induced human errors should be mounted. This review should include crew representatives, experts on human factors, and members of safety and mission quality organization. | |
| language | English | |
| title | NASA-LLIS-0195 | num |
| title | Lessons Learned - Orbiter Software Upgrades. | en |
| type | standard | |
| page | 2 | |
| status | Active | |
| tree | NASA - National Aeronautics and Space Administration (NASA):;1992 | |
| contenttype | fulltext | |
| subject keywords | Flight Equipment | |
| subject keywords | Flight Operations | |
| subject keywords | Human Factors | |
| subject keywords | Software |