quirements information can be grouped and organized according to the kinds of information that the developers want to discover, which is also the kind of information the UIP will contain. The developers and customers can address all related issues and, when they come to an agreement, state the requirements formally. Appropriate models for stating the agreed upon requirements formally should be chosen based on the application domain, on the nature of the application to be developed, and on many other factors. The number and types of these models and the level of detail can be chosen after deciding if the prototype will be thrown away. All prototyped aspects have to be modeled. The chosen method should have the capability of representing the aspects listed above, in order to produce a good requirements model and avoid losing valuable information about software requirements.
The presented approach attempts to deal with the every-day prototyping reality, the approach to prototype construction, the distinction between the information the prototype contains and the modeling method, and the use of the prototype as a requirements elicitation aid and as a requirements model itself.
To validate the approach, we have carried out a case study applying the solution approach to the development of the TSG system. Space limitations preclude giving any details of the case study. The reader is referred to the first author's thesis for the missing details ( Ravid 1999). In that document, the reader will find an adaptation of the general approach to the specific UIPing technique used to learn the requirements for the TSG, a detailed description of the case study, an evaluation of the effectiveness of the solution, and lessons learned.
Andriole, S. J. ( 1994). "Fast Cheap Requirements: Prototype or Else!". IEEE Software, 14(2), 85-87.
Brooks, F. P., Jr. ( 1995). The Mythical Man Month, Second Edition. Reading: Addison Wesley.
Connell, J. L. & Shafer, L. B. ( 1989). Structured Rapid Prototyping. Englewood-Cliffs: Prentice Hall, Yourdon Press.
Connell, J. L. & Shafer, L. B. ( 1995). Object-Oriented Rapid Prototyping. Englewood- Cliffs: Prentice Hall, Yourdon Press.
Ravid, A. ( 1999). A Method for Extracting and Stating Software Requirements that a User Interface Prototype Contains. M.Sc. Thesis, Faculty of Computer Science, Technion, Haifa, Israel, available at ftp://www.cs.technion.ac.il/pub/misc/dberry/Thesis.doc.