ADP (Automated Data Processing) Requirements Definition and Documentation through User-Developed Prototypes.
Abstract
The automated data processing requirements definition and documentation process does not work properly today. Users are spending more money for new or modified systems and continue to be dissatisfied with the results. Much of the dissatisfaction can be traced to seven factors that have reduced the effectiveness of the user's ability to define and communicate requirements. But, this process can be improved through user-developed prototypes supplementing the traditional ADP lifecycle. These prototypes include functioning software and hardware, a data list, a brief concept of operations, and written requirements as necessary to supplement the other documentation. User-developed prototypes offer many advantages and can vastly improve user satisfaction. This paper records many of the author's observations over the past 4 years regarding the mechanics of creating, documenting and communicating requirements. It also offers a proven method to improve requirements definition through user-produced prototypes.
Document Details
- Document Type
- Technical Report
- Publication Date
- Apr 01, 1988
- Accession Number
- ADA194407
Entities
People
- Dan W. Hanifen
Organizations
- Air Command and Staff College