User profiles behave like parameterisations of requirements statements, capturing regular variation in requirements for similar types of system.
Different users may have different functional requirements, and so require different subsets of functionality to be evaluated, or they may have different non-functional constraints on functions.
The terms ``user'' and ``user profile'' will not be used so generally in what follows. It is the terminology used in our efforts towards formalisation; however, the factors that affect and parameterise software requirements do not only derive from end-users of the software, nor yet from only human elements in the software's intended environment.
The term that will generally be used in what follows for the overall context of use is setup, following (Galliers93); this will be returned to later. Within that usage, the actual operator of software will usually be called the end-user; the person or organisation to whom the evaluation is addressed will be called the customer of the evaluation. Profiling, or the systematic acquisition of information about variable requirements, can be applied more or less independently to many different parts of a setup. Particularly where we are talking about adequacy evaluation, it may be necessary to analyse a number of different setups to capture the (possibly disjoint) requirements of all customers of the evaluation.