The first thing to do in the construction of a feature checklist is the definition of the types of software (programs or components thereof), or, in terms of section Towards formalisation and automation, the types of members of the set that one is concerned with. This is done in section Design and function of translation memory.
The second step is then to define useful attributes for each type of object of evaluation. This is what is done below. Attributes for a feature checklist are given for each type. As the main user-oriented organizing principle, we used the 6 quality characteristics for software defined in ISO-9126 (see section ISO 9126). Moreover, the checklist given here is constructed on the principle of rigorous test methods: attributes are included only if they take well-defined formal values and a reliable test procedure (inspection or benchmarking) is imaginable.