Getting User Requirements into the Development-to-Delivery Loop,
Abstract
Many who coordinate with military users of training systems are aware that some trainers fall to satisfy important user requirements. Conscientious people working in the requirement-to-delivery loop may never intentionally neglect or distort end-user needs. However, such oversight or misunderstanding does occur within the operations of complex military, government, and industry organizations. The character of formal and informal information flows within and between these organizations as they relate to identification, establishment and communication of requirements hold the key to improved procedures. What is recommended is consideration for increased emphasis on the collection and use of unfiltered needs statements of lower echelon users during the system development-to-delivery process. This envisioned emphasis would also include information feed-back loops to the end-user culminating in a user orientation manual covering the intended purpose of the trainer, a brief history of the system development, and training logistics support, and maintenance philosophies. (Author)
Document Details
- Document Type
- Technical Report
- Publication Date
- Jan 01, 1982
- Accession Number
- ADP000155
Entities
People
- Frederic W. Snyder
Organizations
- Boeing Military Aircraft