Abstract
It is still too often the case that Computer-Based Information Systems (CIS) are developed behind schedule, over cost, do not do as much as promised, and do not satisfy their users. After 25 years of experience building these systems, why do these troubles continue to arise? A good part of the answer is that the requirements for these systems were never stated accurately and/or completely in the first place. If the requirement statements are erroneous or incomplete, how can the resulting system be expected to perform satisfactorily? In addition, errors caught or requirements discovered in later phases of the system development process can have very adverse affects on cost targets and meeting time deadlines.