35.080 - Software
ICS 35.080 Details
Software
Softwareentwicklung. Systemdokumentation
Logiciels
Programska oprema
General Information
e-Library Subscription
Create subscription and get permanent access to documents within 35.080 - Software
Currently subscription includes documents marked with .We are working on making all documents available within the subscription.
This document specifies requirements and gives guidelines for designing accessible software for people with the widest range of physical, sensory and cognitive abilities, including those who are temporarily or situationally disabled, and the elderly. It addresses software considerations for accessibility that complement general design for usability as addressed by parts of the ISO 9241 series, especially ISO 9241-11 and ISO 9241-210. This document is applicable to the accessibility of interactive systems. It addresses a wide range of software (e.g. home, mobile, office, web, learning support and library systems). It promotes the increased usability of systems for a wider range of users in the widest range of contexts of use. This document does not apply to the behaviour of, or requirements for, assistive technologies (including assistive software), but it does address the use of assistive technologies as an integrated component of interactive systems. It is intended for use by those responsible for the specification, design, development, evaluation and procurement of software platforms and software applications.
- Standard103 pagesEnglish languagesale 15% off
- Standard114 pagesFrench languagesale 15% off
This document provides management guidelines to the organizational profile specified in ISO/IEC 29110-4-2 through organizational management, product portfolio management, resource management and process management processes. This document applies to VSEs that develop software or works thru operating processes. This document is intended to be used with any processes, techniques and methods that enhance the VSEs’ customer satisfaction and productivity.
- Standard43 pagesEnglish languagesale 15% off
This document defines a process assessment model for safety processes, conforming to the requirements of ISO/IEC 33004, for use in performing a process assessment in accordance with the requirements of ISO/IEC 33002. This document supports the use of the process assessment models for system and software life cycle processes (ISO/IEC TS 33060 and ISO/IEC TS 33061) when applied to assessment of processes in the development of (functional or non-functional) safety related systems in order to make consistent judgment regarding either process quality or improvement priorities, or both.
- Technical specification21 pagesEnglish languagesale 15% off
Web Content Accessibility Guidelines (WCAG) 2.2 defines how to make Web content more accessible to people with disabilities. Accessibility involves a wide range of disabilities, including visual, auditory, physical, speech, cognitive, language, learning, and neurological disabilities. Although these guidelines cover a wide range of issues, they are not able to address the needs of people with all types, degrees, and combinations of disability. These guidelines also make Web content more usable by older individuals with changing abilities due to aging and often improve usability for users in general. WCAG 2.2 success criteria are written as testable statements that are not technology-specific. Guidance about satisfying the success criteria in specific technologies, as well as general information about interpreting the success criteria, is provided in separate documents. The WCAG 2.2 standard, technical and educational material supporting implementation of WCAG 2.2, and translations of WCAG 2.2 are available from the Web Content Accessibility Guidelines (WCAG) Overview.
- Draft72 pagesEnglish languagesale 15% off
This document provides guidelines for very small entities (VSEs) that want to reinforce their agile environment to develop software using an agile approach with practices of the ISO/IEC 29110 series. This document is applicable to VSEs that do not develop business- or safety-critical products.
- Standard73 pagesEnglish languagesale 15% off
This document specifies the mechanisms and criteria to be applied for the selection and approval of the object identifier resolution system (ORS) operational agency and includes procedures that the operational agency is required to follow. It also addresses any future modification of the procedures and the procedures for any change of the operational agency. This document: — lists the object identifier (OID) nodes for which the operational agency is required to provide ORS support and gives the required level of support for these nodes; — gives the procedures by which lower-level nodes can apply for ORS support (class A, class B, or class C) and the role of the operational agency in providing these levels of support; — determines the basis for charges that can be levied for these levels of support.
- Standard8 pagesEnglish languagesale 15% off
This document covers the following information technology asset management (ITAM) system processes: a) management system processes for the overall system of IT asset management (not described in ISO/IEC 19770-1 in detail), which are specified in this document for comprehensive coverage and consistency of explanations; these include: — understanding the external context and shareholder needs (7.1, 7.2 and 10.2); — leadership, policy and organization (10.3); — establishing and maintaining the management system (10.4); — planning and risk management (10.5); — support (including resources, competence, awareness, and communication – 10.6); — executing functional and life cycle processes (10.7); — performance evaluation and improvement (10.8); b) functional management processes for IT assets (not described in ISO/IEC 19770-1 in detail), which are cross-cutting processes that integrate with life-cycle processes for IT assets and which are shared with most IT management system standards, though sometimes slightly differently grouped; these include: — change management (11.2; also required by ISO/IEC 19770-1); — data management; — license management; — security management; — relationship and contract management; — financial management; — service level management; — other risk management; c) life cycle management processes for IT assets as specified in ISO/IEC 19770-1, which are grouped and named slightly differently by different methodologies; these include: — specification; — development; — acquisition; — release; — deployment; — operation; — retirement. This document is applicable to all ITAM implementations. This document can be applied to all types of IT assets and by all types and sizes of organizations.
- Technical specification144 pagesEnglish languagesale 15% off
This document defines the requirements for capabilities of build and deployment tools to support and automate building, packaging, and deploying work. This document is intended for use in evaluating and selecting build and deployment tools according to the procedures defined in ISO/IEC 20741. This document is applicable to different development methodologies and approaches (e.g. Waterfall, Agile, or DevOps).
- Standard32 pagesEnglish languagesale 15% off
This document specifies the requirements for the effective control of non-deliverable software. This document can be used during the design, development, test, production, release, use, maintenance, and retirement of non-deliverable software. This can include non-deliverable software procured from external suppliers and utilized in the design, production, evaluation, test, acceptance, or calibration of a deliverable product.
This document focuses solely on the unique requirements of the operational processes that pertain to non-deliverable software as identified below:
This document applies to non-deliverable software (including firmware) that affects a deliverable product or service. Following are several applications and supporting examples of non-deliverable software that is within the scope of this document:
— design and development: modelling, simulation, virtual reality, virtual machine, computer-aided design (CAD), three-dimensional (3D) modelling and analysis tools, software compiler, and code generators;
— manufacturing: additive manufacturing, computer numerical controlled (CNC) programs, robotics, factory automation, tools that load deliverable software, software used in special process (e.g. heat treat, shot peen, sonic wall inspection), and automated manufacturing software (i.e. pick and place);
— verification, validation and maintenance: coordinate measuring machine (CMM) programs, hardware or software qualification, code coverage, test scripts, analysis tools, acceptance test, production acceptance, calibration (inspection, test or calibration), simulator, emulator, and software used in post-delivery service provisions.
The following types of software are not within scope of this document:
— deliverable software (refer to EN 9115);
— manufacturing and measuring equipment embedded software (e.g. operating system, drivers);
— enterprise or office software (e.g. MS Office, word processing or spreadsheet applications, Teams, network software, email, employee management system).
Operational processes not covered in this document are addressed by the respective organization’s quality management system (QMS), based on the EN 9100-series (i.e. EN 9100, EN 9110, EN 9120) and/or ISO 9001 standards.
- Standard14 pagesEnglish languagesale 10% offe-Library read for1 day
This document specifies the requirements for the effective control of non-deliverable software. This document can be used during the design, development, test, production, release, use, maintenance, and retirement of non-deliverable software. This can include non-deliverable software procured from external suppliers and utilized in the design, production, evaluation, test, acceptance, or calibration of a deliverable product.
This document focuses solely on the unique requirements of the operational processes that pertain to non-deliverable software as identified below:
This document applies to non-deliverable software (including firmware) that affects a deliverable product or service. Following are several applications and supporting examples of non-deliverable software that is within the scope of this document:
— design and development: modelling, simulation, virtual reality, virtual machine, computer-aided design (CAD), three-dimensional (3D) modelling and analysis tools, software compiler, and code generators;
— manufacturing: additive manufacturing, computer numerical controlled (CNC) programs, robotics, factory automation, tools that load deliverable software, software used in special process (e.g. heat treat, shot peen, sonic wall inspection), and automated manufacturing software (i.e. pick and place);
— verification, validation and maintenance: coordinate measuring machine (CMM) programs, hardware or software qualification, code coverage, test scripts, analysis tools, acceptance test, production acceptance, calibration (inspection, test or calibration), simulator, emulator, and software used in post-delivery service provisions.
The following types of software are not within scope of this document:
— deliverable software (refer to EN 9115);
— manufacturing and measuring equipment embedded software (e.g. operating system, drivers);
— enterprise or office software (e.g. MS Office, word processing or spreadsheet applications, Teams, network software, email, employee management system).
Operational processes not covered in this document are addressed by the respective organization’s quality management system (QMS), based on the EN 9100-series (i.e. EN 9100, EN 9110, EN 9120) and/or ISO 9001 standards.
- Standard14 pagesEnglish languagesale 10% offe-Library read for1 day
This document defines a process assessment model for system life cycle processes, conformant with the requirements of ISO/IEC 33004, for use in performing a conformant assessment in accordance with the requirements of ISO/IEC 33002.
- Technical specification65 pagesEnglish languagesale 15% off
This document defines a process assessment model for quantitative processes, conforming to the requirements of ISO/IEC 33004, for use in performing a process assessment in accordance with the requirements of ISO/IEC 33002.
- Technical specification18 pagesEnglish languagesale 15% off
This document describes processes targeted at VSEs that want to sustain and grow as an independent competitive system development organization. This document provides management and engineering guidelines for the systems engineering Advanced profile of the generic profile group. This document is applicable to VSEs that do not develop critical systems and have little or no experience with systems engineering (SE) process planning and implementation using the ISO/IEC/IEEE 15288. This document is also applicable to VSEs which are familiar with the management and engineering guidelines 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.
- Standard83 pagesEnglish languagesale 15% off
This document provides the management and engineering guidelines to the software Entry profile specified in ISO/IEC 29110-4-1 through project management and software implementation processes. This document applies to VSEs that do not develop safety-critical software. This document applies for software development projects, which can fulfil an external or internal agreement. This document applies to start-up VSEs (e.g. VSEs that started their operation less than three years ago) and/or VSEs working on small projects (e.g. projects with a size of less than six person-months).
- Standard36 pagesEnglish languagesale 15% off
This document provides management and engineering guidelines to the software Basic profile specified in ISO/IEC 29110-4-1 through project management and software implementation processes. This document applies to VSEs that do not develop safety-critical software. This document applies for software development projects, which can fulfil an external or internal agreement. This document is applicable to VSEs developing a single product by a single work team.
- Standard93 pagesEnglish languagesale 15% off
This document defines a method for measuring the non-functional size of the software. It complements ISO/IEC 20926:2009, which defines a method for measuring the functional size of the software. This document also describes the complementarity of functional and non-functional sizes, so that deriving the sizes from the functional and the non-functional requirements does not result in duplication in the distinct functional and non-functional sizes. In general, there are many types of non-functional requirements. Moreover, non-functional requirements and their classification evolve over time as the technology advances. This document does not intend to define the type of NFR for a given context. Users can choose ISO 25010 or any other standard for the definition of NFR. It is assumed that users size the NFR based on the definitions they use. This document covers a subset of non-functional requirements. It is expected that, with time, the state of the art can improve and that potential future versions of this document can define an extended coverage. The ultimate goal is a version that, together with ISO/IEC 20926:2009, covers every aspect that can be required of any prospective piece of software, including aspects such as process and project directives that are hard or impossible to trace to the software's algorithm or data. The combination of functional and non-functional sizes would then correspond to the total size necessary to bring the software into existence. Estimating the cost, effort and duration of the implementation of the NFR is outside the scope of this document.
- Standard71 pagesEnglish languagesale 15% off
IEC 62974-1:2024 specifies product and performance requirements for devices that fall under the heading of "monitoring and measuring systems used for data collection, aggregation and analysis", for industrial, commercial, and similar use rated below or equal to 1 kV AC and 1,5 kV DC.
These devices are fixed and are intended to be used indoors as panel-mounted devices, or as modular devices fixed on a DIN rail, or as housing devices fixed on a DIN rail, or as devices fixed by other means inside a cabinet.
These devices are used to upload or download information (energy measured on loads, power metering and monitoring data, temperature information, etc.), mainly for energy efficiency purposes. These devices are known as energy servers (ESE), energy data loggers (EDL), data gateways (DGW) and I/O data concentrators (IODC) and are grouped together under the family name of Data Management Devices (DMD).
This document does not cover:
• devices used only in the consumer market (living quarters) or household;
• devices used in the smart metering infrastructure (e.g. smart meters);
• devices used in the smart grid infrastructure;
• devices used as IT servers in the information technology business;
• power metering and monitoring devices (PMD);
• I/O data concentrators already covered by a specific product standard;
• communication protocols and interoperability;
• power quality instruments (PQI);
• software used for the data collection and analysis of the power quality for the supply side.
IEC 62974-1:2024 cancels and replaces the first edition published in 2017. This edition constitutes a technical revision.
This edition includes the following significant technical changes with respect to the previous edition:
a) the performance criteria have been reviewed;
b) EMC and safety requirements have been improved;
c) mechanical requirements have been clarified and amended.
- Standard34 pagesEnglish languagesale 10% offe-Library read for1 day
This document describes the common industry format (CIF) for reporting usability evaluations. It provides a classification of evaluation approaches and the specifications for the content items (content elements) to be included in an evaluation report based on the selected evaluation approach(es). The intended users of the usability evaluation reports are identified, as well as the situations in which the usability evaluation report can be applied. The usability evaluation reports in this document are applicable to software and hardware systems and 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 the ISO/IEC JTC 1/SC 7 process standards (e.g. ISO/IEC/IEEE 15288 on systems lifecycle management, ISO/IEC/IEEE 12207 on software lifecycle management and ISO/IEC 33001 on process capability assessment).
- Standard30 pagesEnglish languagesale 15% off
This document defines an efficient and consistent solution for keyword-driven testing by: — giving an introduction to keyword-driven testing; — providing a reference approach to implement keyword-driven testing; — defining requirements on frameworks for keyword-driven testing to enable testers to share their work items, such as test cases, test data, keywords, or complete test specifications; — defining requirements for tools that support keyword-driven testing; these requirements are applicable to any tool that supports the keyword-driven approach (e.g. test automation, test design and test management tools); — defining interfaces and a common data exchange format to ensure that tools from different vendors can exchange their data (e.g. test cases, test data and test results); — defining levels of hierarchical keywords, and advising use of hierarchical keywords; this includes describing specific types of keywords (e.g. keywords for navigation or for checking a value) and when to use "flat" structured keywords; — providing an initial list of example generic technical (low-level) keywords, such as "inputData" or "checkValue"; these keywords can be used to specify test cases on a technical level and can be combined to create business-level keywords as required. This document is applicable to all those who want to create keyword-driven test specifications, create corresponding frameworks, or build test automation based on keywords.
- Standard55 pagesEnglish languagesale 15% off
This document defines quality measures for quantitatively evaluating cloud services quality in terms of characteristics and sub-characteristics defined in ISO/IEC TS 25052-1 and is intended to be used together with ISO/IEC TS 25052-1. This document contains the following: — a basic set of quality measures for each characteristic and sub-characteristics; — an explanation of how to apply quality measures to cloud services. Since the quality model defined in ISO/IEC TS 25052-1 is the extension to the existing quality models defined in ISO/IEC 25010 to ISO/IEC 25019, it can be used with the product quality model, IT service quality model, data quality model, and quality-in-use model according to evaluation purposes. For the same reason, the quality measures defined in this document can also be used with the quality measures for software ICT products, IT services, data, and quality-in-use. As there are several cloud service categories, this document focuses on the quality model of SaaS (software as a service). This document does not address PaaS (platform as a service) and IaaS (infrastructure as a service).
- Technical specification18 pagesEnglish languagesale 15% off
This document specifies requirements and recommendations for tactile/haptic hardware and software interactions. It provides guidance on the design and selection of hardware, software and combinations of hardware and software interactions, including:
— the design or use of tactile/haptic inputs, outputs and/or combinations of inputs and outputs, with general guidance on their design or use as well as on designing or using combinations of tactile and haptic interactions for use in combination with other modalities or as the exclusive mode of interaction;
— the tactile/haptic encoding of information, including textual data, graphical data and controls;
— the design of tactile/haptic objects;
— the layout of tactile/haptic space;
— interaction techniques.
The recommendations given in this document are applicable to a variety of tactile/haptic devices, representing the real world or virtual or mixed realities (e.g. exoskeletons, wearables, force feedback devices, touchables, tangibles) and stimulation types (e.g. acoustic radiation pressure, electrical muscle stimulation) and they can also be found in virtual and augmented environments.
This document provides general information about how various forms of tactile/haptic interaction can be applied to various user tasks.
This document does not include guidance on the role of walking in virtual or mixed realities for tactile/haptic interaction.
NOTE It is recognized that some interactive scenarios can be constrained by the limitation that a real workspace is to be modelled in a virtual environment. Objects can be in suboptimal positions or conditions for tactile/haptic interaction by virtue of the situation being modelled.
- Standard36 pagesEnglish languagesale 10% offe-Library read for1 day
This document outlines a quality model for AI systems and is an application-specific extension to the standards on SQuaRE. The characteristics and sub-characteristics detailed in the model provide consistent terminology for specifying, measuring and evaluating AI system quality. The characteristics and sub-characteristics detailed in the model also provide a set of quality characteristics against which stated quality requirements can be compared for completeness.
- Standard23 pagesEnglish languagesale 10% offe-Library read for1 day
This document specifies requirements and recommendations for tactile/haptic hardware and software interactions. It provides guidance on the design and selection of hardware, software and combinations of hardware and software interactions, including:
— the design or use of tactile/haptic inputs, outputs and/or combinations of inputs and outputs, with general guidance on their design or use as well as on designing or using combinations of tactile and haptic interactions for use in combination with other modalities or as the exclusive mode of interaction;
— the tactile/haptic encoding of information, including textual data, graphical data and controls;
— the design of tactile/haptic objects;
— the layout of tactile/haptic space;
— interaction techniques.
The recommendations given in this document are applicable to a variety of tactile/haptic devices, representing the real world or virtual or mixed realities (e.g. exoskeletons, wearables, force feedback devices, touchables, tangibles) and stimulation types (e.g. acoustic radiation pressure, electrical muscle stimulation) and they can also be found in virtual and augmented environments.
This document provides general information about how various forms of tactile/haptic interaction can be applied to various user tasks.
This document does not include guidance on the role of walking in virtual or mixed realities for tactile/haptic interaction.
NOTE It is recognized that some interactive scenarios can be constrained by the limitation that a real workspace is to be modelled in a virtual environment. Objects can be in suboptimal positions or conditions for tactile/haptic interaction by virtue of the situation being modelled.
- Standard36 pagesEnglish languagesale 10% offe-Library read for1 day
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, human factors integration (HFI), agile and rapid development.
It is intended for the following types of users:
— user interface designers, who will apply the guidance during the development process;
— developers, who will apply the guidance during the design and implementation of system functionality;
— evaluators, who are responsible for ensuring that products meet the recommendations;
— designers of user interface development tools and style guides to be used by user interface designers;
— project managers, who are responsible for managing development processes.
- Standard34 pagesEnglish languagesale 10% offe-Library read for1 day
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, 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 its size, complexity, or criticality. 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.
- Standard81 pagesEnglish languagesale 15% off
This document provides a specification for associating the processes of ISO/IEC TS 33073 with the process attribute outcomes of ISO/IEC 33020 with the intent of demonstrating support for levels 1 to 3 of the process capability measurement scale defined in ISO/IEC 33020.
- Technical report68 pagesEnglish languagesale 15% off
This document provides a specification for associating the life cycle processes of ISO/IEC/IEEE 12207 with the process attribute outcomes of ISO/IEC 33020 with the intent of demonstrating support for levels 1 to 3 of the process capability measurement scale defined in ISO/IEC 33020.
- Technical report107 pagesEnglish languagesale 15% off
This document provides the framework for quality evaluation of ICT (information and communication technology) products (including software products), data, and IT services, which includes its concepts, and requirements, and recommendations for its processes to be implemented and enhanced. This document is applicable for those who need to perform quality evaluations on target entities, including development organization (integrators, developers, and quality assurance group), acquirers, IT service providers, and independent evaluators. This document does not provide specific test methods for quality evaluation or guidance on utilizing evaluation results.
- Standard29 pagesEnglish languagesale 15% off
This document outlines a quality model for AI systems and is an application-specific extension to the standards on SQuaRE. The characteristics and sub-characteristics detailed in the model provide consistent terminology for specifying, measuring and evaluating AI system quality. The characteristics and sub-characteristics detailed in the model also provide a set of quality characteristics against which stated quality requirements can be compared for completeness.
- Standard23 pagesEnglish languagesale 10% offe-Library read for1 day
This document defines a set of core practices and concepts that have wide acceptance in organizations and industries using agile practices and concepts. 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 to multiple agile teams. These practices and concepts are applicable throughout the life cycle of software systems, products and services.
- Standard42 pagesEnglish languagesale 15% off
This document contains guidance for certification that can be used by certification or qualification bodies regarding the description of knowledge, skill and competence within their particular schemes based on ISO/IEC 24773-1.
- Standard21 pagesEnglish languagesale 15% off
This document defines the terms common to the ISO/IEC 29110 series. This document is applicable to very small entities (VSEs), and their customers, assessors, standards producers, tool vendors and methodology vendors.
- Standard18 pagesEnglish languagesale 15% off
This document establishes the major concepts required to understand and use the ISO/IEC 29110 series. It specifies the characteristics and requirements of a VSE, and clarifies the rationale for VSE-specific profiles, documents, profile specifications and guidelines. This document introduces the taxonomy (catalogue) of ISO/IEC 29110 profiles and the ISO/IEC 29110 series. This document is applicable to a VSE but can also be used by an entity that is larger than a VSE.
- Standard14 pagesEnglish languagesale 15% off
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, human factors integration (HFI), agile and rapid development.
It is intended for the following types of users:
— user interface designers, who will apply the guidance during the development process;
— developers, who will apply the guidance during the design and implementation of system functionality;
— evaluators, who are responsible for ensuring that products meet the recommendations;
— designers of user interface development tools and style guides to be used by user interface designers;
— project managers, who are responsible for managing development processes.
- Standard34 pagesEnglish languagesale 10% offe-Library read for1 day
This document describes a methodology for calculating the rate of carbon emissions for a software system; that is, its SCI score. The purpose of this score is to increase awareness and transparency of an application's sustainability credentials. The score will help software practitioners make better, evidence-based decisions during system design, development, and deployment, that will ultimately minimize carbon emissions. A reliable, consistent, fair and comparable measure allows targets to be defined during development and progress to be tracked.
- Standard9 pagesEnglish languagesale 15% off
This document provides guidance for the life cycle management of systems and software, complementing the processes described in ISO/IEC/IEEE 15288 and ISO/IEC/IEEE 12207. This document: — addresses systems concepts and life cycle concepts, models, stages, processes, process application, key points of view, adaptation and use in various domains and by various disciplines; — establishes a common framework for describing life cycles, including their individual stages, for the management of projects that provide or acquire either products or services; — defines the concept of a life cycle; — supports the use of the life cycle processes within an organization or a project; organizations and projects can use these life cycle concepts when acquiring and supplying either products or services; — provides guidance on adapting a life cycle model and the content associated with a life cycle or a part of a life cycle; — describes the relationship between life cycles and their use in applying the processes in ISO/IEC/IEEE 15288 (systems aspects) and ISO/IEC/IEEE 12207 (software systems aspects); — shows the relationships of life cycle concepts to the hardware, human, services, process, procedure, facility and naturally occurring entity aspects of projects; — describes how its concepts relate to detailed process standards, for example, in the areas of measurement, project management, risk management and model-based systems and software engineering.
- Standard76 pagesEnglish languagesale 15% off
The proposed project is a revision of ISO/IEC/IEEE 24748-2:2018, Systems and software engineering — Life cycle management — Part 2: Guidelines for the application of ISO/IEC/IEEE 15288 (System life cycle processes). There are no scope changes. ISO/IEC/IEEE 24748-2 is a guideline for the application of ISO/IEC/IEEE 15288. It addresses system, life cycle, organizational, project, and process, concept application, principally through reference to ISO/IEC/IEEE 24748-1 and ISO/IEC/IEEE 15288. It gives guidance on applying ISO/IEC/IEEE 15288 from the aspects of strategy, planning, application in organizations, and application on projects. It also provides comparison of the differences between ISO/IEC/IEEE 15288 current revision and the prior version, ISO/IEC 15288:2015.
- Standard63 pagesEnglish languagesale 15% off
This document describes information items enabling systematic human-centred design for interactive
systems.
Some of these information items are elaborated by separate International Standards, named the
Common Industry Format (CIF) for usability-related information.
This document provides the framework of information items, including definitions and the content for
each information item.
This document includes the following:
— the intended users of the information items;
— consistent terminology;
— the high-level content structure to be used for documenting each information item.
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, ISO 9241-220 and ISO/IEC JTC 1/SC 7 process
standards (e.g. ISO/IEC/IEEE 15288, ISO/IEC/IEEE 29148).
This document focuses on those information items needed for design, development and evaluation
of usable systems, rather than prescribing a specific process. It is intended to be used in conjunction
with existing International Standards, including the standards of the ISO 9241 series and the SQuaRE
documents.
This document does not prescribe any kind of method, life cycle or process.
NOTE The information items produced by human-centred design activities can be incorporated in design
approaches as diverse as object-oriented, waterfall, HFI (human factors integration), agile and rapid development.
- Technical report28 pagesEnglish languagesale 10% offe-Library read for1 day
This document establishes a framework for defining quality models which are composed of quality characteristics and sub-characteristics. In particular, this document provides: — the concept of a quality model; — the structure and semantics of quality models; — the relationship between quality models and the other concepts, including measurement, requirement definition, and evaluation; — guidelines, requirements and examples for using quality models.
- Standard17 pagesEnglish languagesale 15% off
1.1 This document specifies the process and technical requirements for the development of software for programmable electronic systems for use in:
- control, command for signalling applications,
- applications on-board of rolling stock.
This document is not intended to be applied in the area of electric traction power supply (fixed installations) or for power supply and control of conventional applications, e.g. station power supply for offices, shops. These applications are typically covered by standards for energy distribution and/or non-railway sectors and/or local legal frameworks.
1.2 This document is applicable exclusively to software and the interaction between software and the system of which it is part.
1.3 Intentionally left blank
1.4 This document applies to software as per subclause 1.1 of this document used in railway systems, including:
- application programming,
- operating systems,
- support tools,
- firmware.
Application programming comprises high level programming, low level programming and special purpose programming (for example: programmable logic controller ladder logic).
1.5 This document also addresses the use of pre-existing software (as defined in 3.1.16) and tools. Such software can be used if the specific requirements in 7.3.4.7 and 6.5.4.16 on pre-existing software and for tools in 6.7 are fulfilled.
1.6 Intentionally left blank
1.7 This document considers that modern application design often makes use of software that is suitable as a basis for various applications. Such software is then configured by application data for producing the executable software for the application.
1.8 Intentionally left blank
1.9 This document is not intended to be retrospective. It therefore applies primarily to new developments and only applies in its entirety to existing systems if these are subjected to major modifications. For minor changes, only 9.2 applies. However, application of this document during upgrades and maintenance of existing software is advisable.
1.10 For the development of User Programmable Integrated Circuits (e.g. field programmable gate arrays (FPGA) and complex programmable logic devices (CPLD)) guidance is provided in EN 50129:2018 Annex F for safety related functions and in EN 50155:2017 for non-safety related functions. Software running on softcore processors of User Programmable Integrated Circuits is within the scope of this document.
- Standard125 pagesEnglish languagesale 10% offe-Library read for1 day
This document provides specifications for a transport format which enables the digital encapsulation of this data. This document refers to an encapsulation of hardware identification (HWID) data as a HWID tag, just as ISO/IEC 19770-2 refers to software identification (SWID) tags for software identification. This document applies to the following. — Tag producers: organizations that create HWID tags for use by others in the market. A tag producer can be part of the organization creating the hardware or a third-party organization. These organizations can be broken down into two major categories. — Device or component providers: entities responsible for the manufacturing or creation of the hardware device and/or associated operating system, virtual environment, or application platform. Platform providers which support this document can additionally provide tag management capabilities at the level of the platform or operating system. — Tag tool providers: entities that provide tools to create hardware identification tags. For example, tools within development environments that generate hardware identification tags, or installation tools that can create tags on behalf of the installation process, and/or desktop management tools that can create tags for underlying hardware, virtual machines, or platforms that did not originally have a hardware identification tag. — Tag consumers: tools and/or organizations who utilize information from HWID tags are broken down into the following two major categories. — Device or component consumers: entities that purchase, install, integrate, and/or otherwise deploy physical or virtual hardware or components. — IT discovery and processing tool providers: entities that provide tools to collect, store, and process hardware identification tags. These tools may be targeted at a variety of different market segments, including security, asset management, and logistics. This document deals only with hardware device or component identification. This document does not detail information technology asset management (ITAM) processes required for discovery and management of hardware (which is provided in ISO/IEC 19770-1) software identification tags (as defined by ISO/IEC 19770-2), entitlement tags (as defined by ISO/IEC 19770-3), or resource utilization measurements (as defined by ISO/IEC 19770-4).
- Standard41 pagesEnglish languagesale 15% off
This document provides guidance for evaluation of artificial intelligence (AI) systems using an AI system quality model. The document is applicable to all types of organizations engaged in the development and use of AI.
- Technical specification20 pagesEnglish languagesale 15% off
This document defines a quality-in-use model composed of three characteristics (which are further subdivided into sub-characteristics) that can influence stakeholders when products or systems are used in a specified context of use. This model is applicable to the entire spectrum of information system and IT service system, including both computer systems in use and software products in use. This document provides a set of quality characteristics for specifying, measuring, evaluating and improving quality-in-use. In this document, because context of use is specified as prerequisite of quality-in-use, context of use is necessary to be re-specified to change prerequisite when a product or service intend to fulfil to context of use changes. The model can be applied, in particular, by those responsible for specifying and evaluating software product quality, such as developers, acquirers, quality assurance and control staff, and independent evaluators. Activities during product development that can benefit from the use of the quality model can include, but are not limited to: — identifying requirements for information system and IT service system in use; — validating the comprehensiveness of a quality-in-use requirements specification; — identifying information system and IT service system design objectives for quality-in-use; — identifying quality-in-use control criteria as part of overall quality assurance; — identifying acceptance criteria for information system and IT service system or information systems; — establishing measures to address the consequences of using products in specified context-of -use; — presenting evaluation items for ethics considerations when using information system and IT service system; — supporting governance of digitalization activities.
- Standard31 pagesEnglish languagesale 15% off
This document defines a product quality model, which is applicable to ICT (information and communication technology) products and software products. The product quality model is composed of nine characteristics (which are further subdivided into subcharacteristics) that relate to quality properties of the products. The characteristics and subcharacteristics provide a reference model for the quality of the products to be specified, measured and evaluated. NOTE 1 In this document, a product refers to an ICT product that is part of an information system. ICT product components include subsystems, software, firmware, hardware, data, communication infrastructure, and other elements that are part of the ICT product. This model can be used for requirements specification and evaluation of the target products’ quality throughout their lifecycle by several stakeholders, including developers, acquirers, quality assurance and control staff and independent evaluators. Activities in the product lifecycle that can benefit from the use of this model include: — eliciting and defining product and information system requirements; — validating the comprehensiveness of requirements definition; — identifying product and information system design objectives, and design necessary process for achieving quality; — identifying product and information system testing objectives; — identifying quality control criteria as the part of quality assurance; — identifying acceptance criteria for a product and/or an information system; — establishing measures of product quality characteristics in support of these activities. NOTE 2 Usage of the quality model for measurement is explained in Annex C.
- Standard22 pagesEnglish languagesale 15% off
Add the following note after the paragraph in 1.6:
'NOTE This document was derived from the signalling standard EN 50128 which in many cases was also applied in Rolling Stock applications. Subclause 1.6 ensures continuity in the application of the standards, i.e., software that was developed in accordance with EN 50128 can still be re-used for new projects.'
- Amendment5 pagesEnglish languagesale 10% offe-Library read for1 day
Add the following note after the paragraph in 1.6: 'NOTE This document was derived from the signalling standard EN 50128 which in many cases was also applied in Rolling Stock applications. Subclause 1.6 ensures continuity in the application of the standards, i.e., software that was developed in accordance with EN 50128 can still be re-used for new projects.'
- Amendment5 pagesEnglish languagesale 10% offe-Library read for1 day
This document specifies the concept of integrity levels with the corresponding integrity level requirements for achieving the integrity levels. Requirements and recommended methods are provided for defining and using integrity levels and their corresponding integrity level requirements. This document covers systems, software products, and their elements, as well as relevant external dependences. This document is applicable to systems and software and is intended for use by: a) definers of integrity levels such as industry and professional organizations, standards organizations, and government agencies; b) users of integrity levels such as developers and maintainers, suppliers and acquirers, system or software users, assessors of systems or software and administrative and technical support staff of systems and/or software products. One important use of integrity levels is by suppliers and acquirers in agreements, for example, to aid in assuring safety, financial, or security characteristics of a delivered system or product. This document does not prescribe a specific set of integrity levels or their integrity level requirements. In addition, it does not prescribe the way in which integrity level use is integrated with the overall system or software engineering life cycle processes. It does, however, provide an example of use of this document in Annex A.
- Standard21 pagesEnglish languagesale 15% off
This document: — describes frequently occurring risks during development and maintenance of custom software; — describes possible controls for frequently occurring risks; — describes the related: — activities, facilities and roles typically used for these controls; — properties of products and processes; — standards, measurements, testing and assessment of the properties of products and processes.
- Technical report36 pagesEnglish languagesale 15% off