Bridging the requirements gap: policies, goals and domains

Abstract

A model for requirements engineering is described which uses a taxonomy of goal-types to guide further analysis. Goals are classified according to the desired system state described in requirements statements. Heuristics then prompt further description of functions according to each goal class. Other analyses encourage expansion of goal statements into specification of objects agents, activity and information processes. These link functional decomposition of requirements to object oriented modelling. Implications of the model and supporting tools are briefly reviewed.<>