BS EN ISO/IEC 25064:2017
$142.49
Systems and software engineering. Software product Quality Requirements and Evaluation (SQuaRE). Common Industry Format (CIF) for usability: User needs report
| Published By | Publication Date | Number of Pages |
| BSI | 2017 | 32 |
This International Standard describes the Common Industry Format (CIF) for reporting user needs. This specifies the contents and provides a sample format of user needs reports. Specification of management needs, as well as other stakeholder needs, is considered to the extent that they directly impact on user needs. The purpose of the User Needs Report and the intended users of the information are identified, as well as the relationship of user needs to other outputs of human-centred design. The audience of this standard includes all users stated in the scope of ISO/IEC 25000. Annex B of ISO/IEC 25000 describes the users of the information item “user needs report” in detail. Annex A of this International Standard provides a list of typical users of a User Needs Report.
User Needs Reports include:
-
documentation of information collected from various sources relevant to user needs
-
the consolidated user needs based on the analysis of the collected information
The User Needs Report is applicable to software and hardware systems, products or services (excluding generic products, such as a display screen or keyboard). User Needs Reports are relevant for existing and new products, services and systems, although the extent to which use needs are reported depends upon the type of system, product, or service involved. It can also contribute to determining, verifying, changing and elaborating the context of use. The content elements 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 JTC1/SC7 process standards.
This International Standard does not prescribe any kind of method, lifecycle or process. To ensure that these content elements can be used within the broadest range of process models and used in combination with other information items, the descriptions use the classifications in ISO/IEC 15289 and ISO/IEC 15504-6.
NOTE The content elements documenting user needs can be integrated in any process models. For the purpose of establishing process models, ISO/IEC 24774 and ISO/IEC 15504-2 specify the format and conformance requirements for process models respectively. In addition ISO/IEC 15289 defines the types and content of information items developed and used in process models for system and software lifecycle management. ISO/IEC 15504-5 and 6 define work products, including information items, for the purpose of process capability assessment. Process models and associated information items for human-centred design of interactive systems are contained in ISO TR 18529 and ISO TS 18152 respectively.
PDF Catalog
| PDF Pages | PDF Title |
|---|---|
| 2 | National foreword |
| 4 | European foreword Endorsement notice |
| 10 | 1 Scope 2 Conformance |
| 11 | 3 Normative references 4 Terms and definitions |
| 14 | 5 Purposes of a User Needs Report 5.1 General |
| 15 | 5.2 User Needs Reports for existing products, services and systems 5.3 User Needs Reports for new products, services and systems 5.4 User Needs Reports for determining, verifying, changing and elaborating context of use 5.5 Relationship to other CIF information items 6 Content of a User Needs Report 6.1 Content elements |
| 16 | 6.2 Initial indicators of the needs for system/product/service or improvement 6.3 User responsibilities and goals 6.4 Source data on which user needs are based 6.4.1 General |
| 17 | 6.4.2 Identified and reported user needs 6.4.2.1 General 6.4.2.2 Content elements of each user needs statement |
| 18 | 6.4.2.3 Additional content to be provided with each need statement 6.4.2.3.1 Information to be provided 6.4.2.3.2 Source of need 6.4.2.3.3 User responsibilities or goals related to the need 6.4.2.3.4 Rationale for the need 6.4.2.3.5 Type of need 6.4.2.3.5.1 Identifying and reporting 6.4.2.3.5.2 Informational needs 6.4.2.3.5.3 Processing needs |
| 19 | 6.4.2.3.5.4 Enjoyment needs 6.4.2.3.5.5 Environmental needs 6.4.2.3.5.6 Other types of identified needs 6.4.2.3.6 Frequency of occurrence 6.4.2.3.7 Quality attributes 6.4.2.4 Requirements on the elements of a user needs statement |
| 20 | 6.4.3 Identified and reported management and other stakeholder needs that impact on user needs 6.4.3.1 General 6.4.3.2 Content elements 6.4.3.3 Organizational responsibilities or goals related to need 6.4.3.4 Impact on user needs |
| 21 | 6.4.3.5 Type of need 6.4.3.5.1 General 6.4.3.5.2 Output needs 6.4.3.5.3 Procedural needs 6.4.3.5.4 Other needs 6.4.4 Identified performance deficiencies/problems/potential improvements 6.4.4.1 General 6.4.4.2 Performance deficiencies |
| 22 | 6.4.4.3 Problems |
| 23 | 6.4.4.4 Potential improvements 6.4.4.5 Deficiency/problem/improvement analysis 6.5 Consolidated user needs |
| 24 | 6.6 Recommendations (if appropriate) 6.7 Data collection methods/procedures 6.7.1 Content |
| 25 | 6.7.2 Selection of participants for user needs assessment 6.7.3 Description of user needs assessment participants |
| 26 | 6.7.4 Methods and procedures 6.8 Supporting information 6.8.1 System/Product/Service description, objectives, constraints |
| 27 | 6.8.2 Data collection instruments 6.8.3 Data summaries |
