NASA-LLIS-1220
Lessons Learned - Verification of program requirements at the element level
Year: 1998
Abstract: Description of Driving Event:
Throughout 1A/R and 2A verification closure (stage level), considerable resources were expended gathering element level compliance data to provide closure of the identical requirements at the system level (ISS, USOS, AIRD).
Root cause: Initial planning did not take into account that some system level requirements are met if and only if the same requirements are met by each element on a given flight. Efficiencies can be realized by transferring the verification responsibility for such requirements to the Functional Configuration Audit (FCA) process.
Throughout 1A/R and 2A verification closure (stage level), considerable resources were expended gathering element level compliance data to provide closure of the identical requirements at the system level (ISS, USOS, AIRD).
Root cause: Initial planning did not take into account that some system level requirements are met if and only if the same requirements are met by each element on a given flight. Efficiencies can be realized by transferring the verification responsibility for such requirements to the Functional Configuration Audit (FCA) process.
Subject: Administration/Organization
Show full item record
| contributor author | NASA - National Aeronautics and Space Administration (NASA) | |
| date accessioned | 2017-09-04T18:14:32Z | |
| date available | 2017-09-04T18:14:32Z | |
| date copyright | 36076 | |
| date issued | 1998 | |
| identifier other | HHVEQCAAAAAAAAAA.pdf | |
| identifier uri | http://yse.yabesh.ir/std;jsery=autho162s7D8308/handle/yse/197475 | |
| description abstract | Description of Driving Event: Throughout 1A/R and 2A verification closure (stage level), considerable resources were expended gathering element level compliance data to provide closure of the identical requirements at the system level (ISS, USOS, AIRD). Root cause: Initial planning did not take into account that some system level requirements are met if and only if the same requirements are met by each element on a given flight. Efficiencies can be realized by transferring the verification responsibility for such requirements to the Functional Configuration Audit (FCA) process. | |
| language | English | |
| title | NASA-LLIS-1220 | num |
| title | Lessons Learned - Verification of program requirements at the element level | en |
| type | standard | |
| page | 2 | |
| status | Active | |
| tree | NASA - National Aeronautics and Space Administration (NASA):;1998 | |
| contenttype | fulltext | |
| subject keywords | Administration/Organization | |
| subject keywords | Configuration Management | |
| subject keywords | Independent Verification and Validation | |
| subject keywords | Policy & Planning | |
| subject keywords | Safety & Mission Assurance | |
| subject keywords | Test & Verification |

درباره ما