NASA-LLIS-1715
Lessons Learned - The Pitfalls of "Engineering-by-Presentation" (2005)
Year: 2005
Abstract: Abstract:
Formal documentation of requirements, resolutions, and decisions was once a standard NASA practice. However, the increased use of informal documentation such as viewgraphs and e-mail may be inhibiting the ability of NASA projects to reference the basis for technical decisions and to validate or verify engineering designs. Produce a record of technical decisions and supporting information within technical reports and memos as a standard practice across the institution, with a defined process for review, approval, and records management.
Formal documentation of requirements, resolutions, and decisions was once a standard NASA practice. However, the increased use of informal documentation such as viewgraphs and e-mail may be inhibiting the ability of NASA projects to reference the basis for technical decisions and to validate or verify engineering designs. Produce a record of technical decisions and supporting information within technical reports and memos as a standard practice across the institution, with a defined process for review, approval, and records management.
Subject: Additional Categories.
Show full item record
contributor author | NASA - National Aeronautics and Space Administration (NASA) | |
date accessioned | 2017-09-04T18:50:43Z | |
date available | 2017-09-04T18:50:43Z | |
date copyright | 38701 | |
date issued | 2005 | |
identifier other | ANXCQCAAAAAAAAAA.pdf | |
identifier uri | http://yse.yabesh.ir/std;jsessionid=3826AF679D40527318548F1EFDEC014A/handle/yse/232128 | |
description abstract | Abstract: Formal documentation of requirements, resolutions, and decisions was once a standard NASA practice. However, the increased use of informal documentation such as viewgraphs and e-mail may be inhibiting the ability of NASA projects to reference the basis for technical decisions and to validate or verify engineering designs. Produce a record of technical decisions and supporting information within technical reports and memos as a standard practice across the institution, with a defined process for review, approval, and records management. | |
language | English | |
title | NASA-LLIS-1715 | num |
title | Lessons Learned - The Pitfalls of "Engineering-by-Presentation" (2005) | en |
type | standard | |
page | 4 | |
status | Active | |
tree | NASA - National Aeronautics and Space Administration (NASA):;2005 | |
contenttype | fulltext | |
subject keywords | Additional Categories. | |
subject keywords | Additional Categories.Configuration Management | |
subject keywords | Additional Categories.Flight Equipment | |
subject keywords | Additional Categories.Hardware | |
subject keywords | Additional Categories.Payloads | |
subject keywords | Additional Categories.Spacecraft | |
subject keywords | Engineering Design (Phase C/D). | |
subject keywords | Engineering Design (Phase C/D).Spacecraft and Spacecraft Instruments | |
subject keywords | Missions and Systems Requirements Definition. | |
subject keywords | Missions and Systems Requirements Definition.Configuration control and data management | |
subject keywords | Program Management. | |
subject keywords | Program Management.Configuration and data management | |
subject keywords | Safety and Mission Assurance. | |
subject keywords | Safety and Mission Assurance.Review systems and boards |