Detail of GB/T 44370-2024

Introduction of GB/T 44370-2024

GB/T 44370-2024 Systems and software engineering - Software product Quality Requirements and Evaluation (SQuaRE) - Common Industry Format (CIF) for Usability - User requirements specification 1 Scope This document provides a framework and consistent terminology for specifying user requirements. It specifies the common industry format (CIF) for a user requirement specification including the content elements and the format for stating those requirements. Note 1: A user requirements specification is the formal documentation of a set of user requirements, which aids in the development and evaluation of usable interactive systems. In this document, user requirements refers to: a) user-system interaction requirements for achieving intended outcomes (including requirements for system outputs and their attributes); b) use-related quality requirements that specify the quality criteria associated with the outcomes of users interacting with the interactive system and can be used as criteria for system acceptance. Note 2: ISO/IEC 25030 introduces the concept of quality requirements. The use-related quality requirements in this document are a particular type of quality requirement. The content elements of a user requirements specification are intended to be used as part of documentation resulting from the activities specified in ISO 9241-210, and from human centred design processes, such as those in ISO 9241-220. This document is intended to be used by requirements engineers, business analysts, product managers, product owners, and people acquiring systems from third parties. The CIF series of standards addresses usability-related information (as described in ISO 9241-11 and ISO/IEC TR 25060). Note 3: In addition to usability, user requirements can include other perspectives, such as human-centred quality introduced in ISO 9241-220, and other quality perspectives presented in ISO/IEC 25010, ISO/IEC TS 25011, and ISO/IEC 25030. Note 4: While this document was developed for interactive systems, the guidance can also be applied in other domains. This document does not prescribe any kind of method, lifecycle or process. The content elements of a user requirements specification can be used in iterative development which includes the elaboration and evolution of requirements (e.g. as in agile development). 2 Normative references There are no normative references in this document. 3 Terms and definitions For the purposes of this document, the following terms and definitions apply. ISO and IEC maintain terminological databases for use in standardization at the following addresses: ——ISO Online browsing platform: available at https://www.org/obp ——IEC Electropedia: available at https://www.electropedia.org/ 3.1 Terms related to user requirements 3.1.1 requirement condition or capability that must be met or possessed by a system, system component, product, or service to satisfy an agreement, standard, specification, or other formally imposed documents Note 1: Formally imposed documents can include User needs reports. Note 2: This definition is used in this document because it explicitly differentiates between user needs and user requirements which the ISO/IEC/IEEE 12207 definition does not explicitly differentiate. [SOURCE: ISO/IEC/IEEE 24765:2017, 3.3431/2, modified - The Noteshave been added.] 3.1.2 quality requirement requirement (3.1.1) for quality properties or attributes of a product, data or service that satisfy needs which ensue from the purpose for which that product, data or service is to be used [SOURCE: ISO/IEC DIS 25030:2018, 4.16, modified - Note 1 has been deleted.] 3.1.3 user person who interacts with a system, product or service Note 1: Users of a system, product or service include people who operate the system, people who make use of the output of the system and people who support the system (including providing maintenance and training). Note 2: This term corresponds to the definition "direct user" that is found in ISO/IEC 25010. [SOURCE: ISO 9241-11:2018, 3.1.7, modified - Note 2 has been added] 3.1.4 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 Example: Stakeholders can include: users, purchasers, systems owners or managers and people who are indirectly affected by the operation of a system, product or service. Note: Different stakeholders can have different needs, requirements or expectations. [SOURCE: ISO/IEC/IEEE 15288:2015, 4.1.44.] 3.1.5 user group subset of intended users (3.1.3) who are differentiated from other intended users by characteristics of the users, tasks (3.1.8) or environments that can influence usability (3.3.1) [SOURCE: GB/T 18978.11-2023, 3.1.8, modified.] 3.1.6 context of use combination of users (3.1.3), goals (3.1.7) and tasks (3.1.8), resources, and environment Note 1: The "environment" in a context of use includes the technical, physical, social, cultural and organizational environments. Note 2: This can apply to an existing context of use or an intended context of use. [SOURCE: GB/T 18978.11-2023, 3.1.15, modified - Note 2 has been added.] 3.1.7 goal intended outcome [SOURCE: GB/T 18978.11-2023, 3.1.10] 3.1.8 task set of activities undertaken to achieve a specific goal (3.1.7) Note 1: These activities can be physical, perceptual and/or cognitive. Note 2: While goals are independent of the means used to achieve them, tasks describe particular means of achieving goals. [SOURCE: GB/T 18978.11-2023, 3.1.11] 3.1.9 user need prerequisite identified as necessary for a user, or a set of users, to achieve an intended outcome, implied or stated within a specific context of use (3.1.6) Example 1: A presenter (user) needs to know how much time is left (prerequisite) in order to complete the presentation in time (goal) during a presentation with a fixed time limit (context of use). Example 2: An account manager (user) needs to know the number of invoices received and their amounts (prerequisite), in order to complete the daily accounting log (goal) as part of monitoring the cash flow (context of use). Note 1: A user need is independent of any proposed solution for that need. Note 2: User needs are identified based on various approaches including interviews with users, observations, surveys, evaluations, expert analysis, etc. Note 3: User needs often represent gaps (or discrepancies) between what should be and what is. Note 4: User needs are transformed into user requirements (3.1.9) considering the context of use, user priorities, trade-offs with other system requirements and constraints. [SOURCE: ISO/IEC 25064:2013, 4.19, modified - The expression "intended outcome" has been changed to "goal" in Examples 1 and 2.] 3.1.10 user requirements set of requirements (3.1.1) for use that provide the basis for design and evaluation of interactive systems to meet identified user needs (3.1.9) Note 1: User requirements are derived from user needs and capabilities in order to allow the user to make use of the system in an effective, efficient, safe and satisfying manner. Note 2: User requirements are not requirements on the users. Note 3: User requirements include user-system interaction requirements (3.1.11) and use-related quality requirements (3.1.12). Note 4: In software engineering terms, user requirements include both "functional" and "non-functional" requirements derived from user needs and capabilities. [SOURCE: ISO 9241-220:2019, 3.46]

Contents of GB/T 44370-2024