Using scenarios to validate requirements in a plausibility-centred approach

Abstract

The situations within which Information Systems Development in general, and Requirements Engineering in particular are positioned, can be regarded as design situations. We subscribe to the view that understanding the problem amounts to solving it. The implication of this is that RE involves a continuous cycle of problem generationconjecture -evaluation. This paper is concerned with the evaluation of designs for a given set of requirements. Our approach is based on a framework that demands a reflective stance whereby the issues, positions and arguments are clearly visible to all participants and a rationale behind the design decisions taken is kept for future examination. Within this context, we are concerned with both the reasoning for the planning of designing the target artefact, and the alternative specifications in the design 'product' themselves.

Goal Modeling in Requirements Engineering

“…Through simulation it is possible to develop scenarios of system behaviour for a variety of concerns, such as human computer interaction (Carroll, 2000), software development (Abdel-Hamid, Madnick, and Sloan School of Management. Center for Information Systems Research., 1988) and requirements engineering (Carroll, 2002;Filippidou and Loucopoulos, 1997;Potts, Takahashi, and Anton, 1994). A common feature of scenarios in all these domains is their use in examining alternative future situations.…”