Evaluation of design and outputs: inputs
The inputs are the requirements and design documentation, the stakeholder, data and risk sections of the profile, the test data sets and the UI and UX design documentation.
What clause 9.2.2 asks
The inputs to the design and output evaluation are the documentation of the system requirements and the system design, the stakeholder identification, data representation and risk and impact assessment sections of the bias profile, the test data sets, and the documentation of the user interface and user experience design. Each input has a current version, and the evaluation is only as good as those versions.
Why it matters
The input list connects the evaluation to every earlier clause. The requirements give the standard, the stakeholder and data sections give the population, the risk section gives the priority, and the UI and UX documentation gives the human interface where bias can be introduced or hidden. A test team that receives only the model and the test set is missing most of the inputs the clause requires.
What good looks like
Collect the inputs as a versioned pack before the evaluation starts. Read the UI and UX documentation with the stakeholder attributes in hand, because a control that omits an attribute is a design bias that a model metric will not show. Confirm that the test data sets are identified and that their relation to the training data is known. Record any missing input and its effect on the evaluation.
Evidence an assessor asks for
The assessor will ask whether the test data was used in training. A test set that overlaps the training data cannot support the evaluation claim.
- Requirements and design pack The current requirements and design documents, with versions
- Profile extracts The stakeholder, data and risk sections used by the evaluation
- Test data record The test sets, their provenance and their relation to the training data
- UI and UX pack The interface design documentation, with the stakeholder attributes it must reflect
Where it commonly fails
- The evaluation receives only the model and a test set
- The UI and UX documentation is not reviewed
- The profile extracts are out of date
What to do before publication
Build the input pack at the start of the evaluation and record the versions. It is the evaluation's evidence base.
Read across
- 5.2.5 Evaluation in the life cycle
- 6.3 Outputs
- 7.3 Outputs
- 8.3 Outputs
- 9.2.3 Evaluation of design and outputs: outputs
← 9.2.1 Evaluation of design and outputs: purpose9.2.3 Evaluation of design and outputs: outputs →