ISO/IEC TR 25060:2010 pdf – Systems and software engineering — Systems and software product Quality Requirements and Evaluation (SQuaRE) — Common Industry Format (CIF) for usability: General framework for usability-related information.
1 Scope This Technical Report describes a potential family of International Standards, named the Common Industry Formats (CIF), that document the specification and evaluation of the usability of interactive systems. It provides a general overview of the CIF framework and contents, definitions, and the relationship of the framework elements. The intended users of the framework are identified, as well as the situations in which the framework may be applied. The assumptions and constraints of the framework are also enumerated. The framework content includes the following: consistent terminology and classification of specification, evaluation and reporting; a definition of the type and scope of formats and the high-level structure to be used for documenting required information and the results of evaluation. This Technical Report is applicable to software and hardware products used for predefined tasks. The information items are intended to be used as part of system-level documentation resulting from development processes such as those in ISO 9241-210, and ISO/IEC JTC 1/SC 7 process standards. This Technical Report focuses on documenting those elements needed for design and development of usable systems, rather than prescribing a specific process. It is intended to be used in conjunction with existing International Standards, including ISO 9241, ISO 20282, ISO/IEC 9126 and the SQuaRE series (ISO/IEC 25000 to ISO/IEC 25099). This Technical Report does not prescribe any kind of method, life cycle or process. 2 Terms and definitions For the purposes of this document, the following terms and definitions apply. 2.1 accessibility 〈interactive system〉 usability of a product, service, environment or facility by people with the widest range of capabilities [ISO 9241-171:2008] 2.2 action user behaviour that a system accepts as a request for a particular operation [ISO/IEC TR 11580:2007]
2.3 context of use users, tasks, equipment (hardware, software and materials), and the physical and social environments in which a product is used [ISO 9241-11:1998] 2.4 dialogue interaction between a user and an interactive system as a sequence of user actions (inputs) and system responses (outputs) in order to achieve a goal [ISO 9241-110:2006] 2.5 effectiveness accuracy and completeness with which users achieve specified goals [ISO 9241-11:1998] 2.6 efficiency resources expended in relation to the accuracy and completeness with which users achieve goals [ISO 9241-11:1998] 2.7 goal intended outcome [ISO 9241-11:1998] 2.8 information architecture 〈human-centred〉 structure of an information space and the semantics for accessing required task objects, system objects and other information NOTE The appropriate combination of organization, labelling, navigation schemes and retrieval mechanisms within an information space will facilitate task completion and efficient access to content. 2.9 product part of the equipment (hardware, software and materials) for which usability is to be specified or evaluated [ISO 9241-11:1998] 2.10 satisfaction freedom from discomfort, and positive attitudes towards the use of the product [ISO 9241-11:1998]
2.11 stakeholder individual or organization having a right, share, claim, or interest in a system or in its possession of characteristics that meet their needs and expectations [ISO/IEC 15288:2008] 2.12 system combination of interacting elements organized to achieve one or more stated purposes NOTE 1 A system may be considered as a product or as the services it provides. NOTE 2 In practice, the interpretation of its meaning is frequently clarified by the use of an associative noun, e.g. aircraft system. Alternatively, the word system may be substituted simply by a context-dependent synonym, e.g. aircraft, though this may then obscure a system principles perspective. [ISO/IEC 15288:2002, 4.17] 2.13 task activities required to achieve a goal [ISO 9241-11:1998] NOTE The term “task” is used here, as in ISO 9241-11, in its widest sense, rather than in reference to the specifics of use of the dialogue system. 2.14 usability extent to which a product can be used by specified users to achieve specified goals with effectiveness, efficiency and satisfaction in a specified context of use [ISO 9241-11:1998] NOTE The definition of usability in this Technical Report is similar to that used to define “quality in use” in ISO/IEC 9126-1:2001. 2.15 usability objective stated level of usability expressed in terms of effectiveness, efficiency and satisfaction in a specified context of use which can be verified NOTE Usability objectives can be stated as user requirements, in which case the level to be achieved is a usability requirement, or they can be stated as desired “target levels” depending on their use in design and evaluation.