Programutveckling och systemdokumentation

1.1 Field of application
This document is applicable to a VSE and defines the terms common to the ISO/IEC 29110 series.
1.2 Target audience
This document is targeted both at the general audience wishing to understand the ISO/IEC 29110 series of documents, and more specifically, at users of the ISO/IEC 29110 series. It should be read first when initially exploring VSE profile documents. While there is no specific prerequisite to read this document, it will be helpful to the user in understanding the terms used in the other parts.

This document provides guidance on aspects of the design of human-system interaction, including: conceptual design, user-system interaction design, user interface design, and navigation design for interactive systems.
This document applies to all design and development approaches and methodologies (including: human-centred design, object-oriented, waterfall, HFI (human factors integration), agile and rapid development).
This document refers to applicable international standards, where available, rather than duplicating  their content. It also provides guidance that is not available in other international standards.

This document defines a set of core practices and concepts that have wide acceptance in organizations and industries using agile approaches. This document defines a set of core practices that are present in agile methodologies.
The practices and concepts defined in this document are applicable to a single agile team, as well as for multiple agile teams. These practices and concepts are applicable throughout the lifecycle of software systems, products and services.

This International Standard specifies the Common Industry Format (CIF) for the content of a quantitative usability test report. The required and recommended content elements of a quantitative usability test report, the measures of user performance and response, and measures of user satisfaction in accordance with ISO/IEC 25066:2016 are included.
This document provides a common format for human factors engineers and usability professionals in supplier companies to report the methods and results of quantitative usability tests to customer organizations.
This International Standard is intended to be used by:
— usability professionals within supplier organizations to generate reports that can be used by customer organizations
— customer organizations to verify that a particular report conforms to this International Standard
— human factors or other usability professionals in customer organizations who are evaluating both the technical merit of usability tests and the usability of the products
— other technical professionals and managers in the customer organization who are using the test results to make business decisions about product suitability and purchase.
The quantitative usability test report in this International Standard is applicable to software and hardware systems, products or services used for predefined tasks (excluding generic products, such as a display screen or a keyboard). 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 JTC 1/SC 7 process standards.
The content elements for documenting usability evaluations can be integrated in any type of process model.
NOTE For the purpose of establishing process models, ISO/IEC 24774 and ISO/IEC 33020 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 ISO/IEC 15504-6 (to be replaced by ISO/IEC 33060) 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.

This document describes a set of useful activities, tasks, methods, and practices that acquirers of software and related services from unrelated (external) suppliers can apply to help ensure an efficient and effective acquisition of software or software services. These practices can be applied in competitive and in sole source procurements and regardless of the type, size, complexity, and cost of the acquisition. The document can be applied to software that runs on any computer system regardless of the size, complexity, or criticality of the software. The software supply chain can include integration of off-the-shelf (OTS), custom, software as a service (SaaS), or open-source software. Software services can include software development and sustainment (maintenance), integration, verification (testing) and operation. Security and safety are included as attributes to be considered during the acquisition.
However, specific requirements for acquisition of information assurance (security), safety, and cloud services are not included.
Each organization or individual using this document can identify the specific set of activities to include within the organization’s acquisition process, given its legal and regulatory environment, procurement guidelines, and life cycle processes.

The lifecycle processes described in the ISO/IEC 29110 series are not intended to preclude or discourage their use by organisations bigger than VSEs. This document applies for the development of non safety critical products. The ISO/IEC 29110–4-6 will identify the requirements applicable to the tasks and work products described in this document. This document is targeted for VSEs that do not develop safety critical products and have little or no experience with systems engineering (SE) process planning and implementation using the ISO/IEC/IEEE 15288. This document is also targeted for VSEs which are familiar with the management and engineering guide of the systems engineering Intermediate profile (ISO/IEC TR 29110 5-6-3) for their system development projects and are involved in the development of more than one project in parallel with more than one work team. This document is intended to be used with any process, technique and method that enhances the VSE’s stakeholder satisfaction and productivity.