REQUIREMENT VALIDATION VS. REQUIREMENT ELICITATION

Abstract

To support the evocation and validation of the goals achieved by the existing system and to illustrate problems of the old system, we suggest to capture current system usage using rich media (e.g., video, speech, pictures, etc.) and to interrelate those observations with the goal definitions .Therefore it becomes necessary to relate the parts of the observations which have caused the definition of a goal or against which a goal was validated with the corresponding goal in every phase of software development process. These interrelations provide the base for: 1) explaining and illustrating a goal model to, e.g., untrained stakeholders and/or new team members, and thereby improving a common understanding of the goal model; 2) detecting, analyzing, and resolving a different interpretation of the observations; 3) comparing different observations using computed goal annotations; and 4) refining or detailing a goal model during later process phase. Using the PRIME implementation framework, we have implemented the PRIME-CREWS environment, which supports the interrelation of conceptual models and captured system usage observations. We report on our experiences with PRIME-CREWS gained in a first experimental case study. The successful implementation of proposed requirement evocation and validation process can have a good impact on the production of quality software product.