Abstract :
The process of developing Army command and control information systems has been less than totally successful in producing fielded systems. One critical but often neglected aspect of that process, the requirements definition phase, is discussed. It is argued that the dynamic, high-risk, stressful military decision environment has unique characteristics which make it difficult merely to adapt information systems from, for example, a business environment. It is further argued that, within the military, the Army in particular has special characteristics that complicate the requirements definition process. Finally, the total acquisition process, particularly the time taken by that process, is shown to work against effective requirements definition. A series of solutions to these problems are proposed within the context of the concept-based requirements system.
