Skip to content. | Skip to navigation

Informatik 5
Information Systems
Prof. Dr. M. Jarke
Personal tools
You are here: Home Publications Requirements Elicitation and Validation with Real World Scenes


Prof. Dr. M. Jarke
RWTH Aachen
Informatik 5
Ahornstr. 55
D-52056 Aachen
Tel +49/241/8021501
Fax +49/241/8022321

How to find us

Annual Reports





Requirements Elicitation and Validation with Real World Scenes

Year 1998

Scenarios are an excellent means for eliciting and validating requirements. In contrast to a requirements specification which defines the requirements for the future system at a con-ceptual level (i.e. class or type level), a scenario represents a concrete example of current or future system usage. In early RE phases, scenarios are used to support the definition of the main goals (high level requirements) to be achieved by the new system. In many cases, most of those goals can be elicited by observing, documenting and analysing scenarios about current system usage, i.e. the new system must often fulfil most of the functional and non-functional goals of the existing system. To support the elicitation and validation of the goals achieved by the existing system we propose to capture current system usage using rich media (e.g. video, speech, pictures etc.) and to interrelate those observations with the goal definitions. More precisely, we propose 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(s). Thereby a fine-grained interre-lation between the conceptual goal model and the recorded observations is established. These interrelations provide the basis for 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; detecting, analysing and resolving a different interpretation of the observations; comparing different observations using computed goal annotations based on the inter-relations; refining or detailing a goal model during later process phases.


IEEE Transactions on Software Engineering: Special Issue on Scenario Management 24(12), pp. 1036-1054, December 1998

Related projects

Document Actions