Show simple item record

Lessons Learned - Concurrent Engineering

contributor authorNASA - National Aeronautics and Space Administration (NASA)
date accessioned2017-09-04T17:13:22Z
date available2017-09-04T17:13:22Z
date copyright05/27/2011
date issued2011
identifier otherYXXKMEAAAAAAAAAA.pdf
identifier urihttp://yse.yabesh.ir/std/handle/yse/136852
description abstractDescription of Driving Event:
Ares I-X showed the importance of concurrent engineering for large multiple-center projects. The team responsible for generating the processing procedures and for supporting on-vehicle testing should have been working with the design team early in the requirement development process. Ares I-X started using concurrent engineering late in the project and would have benefited by implementing it at the start of the project.
languageEnglish
titleNASA-LLIS-3758num
titleLessons Learned - Concurrent Engineeringen
typestandard
page2
statusActive
treeNASA - National Aeronautics and Space Administration (NASA):;2011
contenttypefulltext
subject keywordsContractor relationships
subject keywordsGround processing and manifesting
subject keywordsLaunch support systems
subject keywordsLaunch Systems
subject keywordsLevel II/III requirements definition
subject keywordsLogistics and maintenance
subject keywordsOrganizational Planning
subject keywordsProgram level review processes
subject keywordsProgram planning
subject keywordsdevelopment
subject keywordsand management
subject keywordsReview boards
subject keywordsRisk management
subject keywordsSpacecraft and Spacecraft Instruments
subject keywordsVehicle concepts


Files in this item

Thumbnail

This item appears in the following Collection(s)

Show simple item record