next previous contents
Next: Problem domain requirements Up: Requirements analysis in LE Previous: Introduction

Overview

Requirements analysis for evaluation aims first at providing a description of the problem domain requirements. This description must support the subsequent development of detailed reportable attributes for systems under test. The requirements part proper should consist of

(The tasks and setups identified can feed directly into the test design phase of evaluation, discussed in section Methods for system measurement.)

A requirements analysis procedure for LE evaluation aims to provide guidelines for the construction of these outputs and the final output of reportable attributes. Such guidelines will never amount to a deterministic procedure. Instead, they should form a framework which can support the activity of requirements analysis by making available

An important part of the usefulness of generic or pre-existing requirements elements is the fact that, having been used in previous evaluations, they are associated with elements of the library of available test types.

The basic steps are:

As previously mentioned, notions of sequence are often misleading in this sort of development activity, and the actual processes by which these results are arrived at are more likely to follow an iterative procedure, such as formalised in Boehm's (Boehm88) spiral software development process model. This is because the process is both top-down (driven by problem requirements) and bottom-up (driven by the need to bottom out at measureable primitives).


next up previous contents
Next: Problem domain requirements Up: Requirements analysis in LE Previous: Introduction

ceditor@tnos.ilc.pi.cnr.it