Informationsteknik, kontorsutrustning

This document is a specialization of the more general reference model for Software and Systems product line engineering and management, ISO/IEC 26550. The specialization defined herein addresses a class of methods and tools referred to as Feature-based Software and Systems Product Line Engineering, or Feature-based PLE, which has emerged as a proven and repeatable product line engineering and management (PLE) practice supported by commercial tool providers.

The scope of this document is to:

• provide the terms and definitions specific to Feature-based PLE;

• define how Feature-based PLE is a specialization within the general ISO/IEC 26550 reference model for Product Line Engineering and Management;

• define a reference model for the overall structure and processes of Feature-based PLE and describe how the elements of the reference model fit together;

• define interrelationships, and methods for applying the elements and tools of the product line reference model;

• define required and supporting tool capabilities.

In this document, products of Feature-based PLE include digital work products that support the engineering of a system. Some of the artefacts are actually part of the delivered products, while other artefacts can be non-deliverable, such as physical or digital design models.

The intended audience for this document comprises:

• technology providers who wish to provide automated tool support for the reference model and processes described in this document;

• champions within an organization who wish to introduce Feature-based PLE throughout that organization;

• IT staff within a PLE organization who will introduce and maintain the necessary technology to support Feature-based PLE;

• practitioner stakeholders who will use the provided technology to practice Feature-based PLE;

• technical and business managers who will sponsor and direct the methods necessary to practice Feature-based PLE;

• university professors, researchers, corporate trainers, and other educators who will create and share pedagogical materials about Feature-based PLE and its benefits.

This document embodies a distinct separation of concerns between the Feature-based PLE technology providers (the first bullet in the audience list above) and Feature-based technology users (the last four bullets in the audience list). For each of these stakeholder concerns, the scope of this document is to define only what is necessary and sufficient to enable Feature-based PLE practice. For technology providers, this imparts flexibility in how the necessary and sufficient technical capabilities are provided, as well as the opportunity to offer more expansive capabilities that are possible in an ideal

solution. For technology users, this provides flexibility to select among the technology providers and to apply the methods that best match their technical and business objectives for Feature-based PLE.

This document, including the product line reference model and the terms and definitions, has been produced starting from the general approach outlined in reference [10]. In addition to this background work, lifecycle models from ISO/IEC/IEEE 12207 and ISO/IEC/IEEE 15288 have been used as a baseline.

This document specifies test processes that can be used to govern, manage and implement software testing for any organization, project or testing activity. It comprises generic test process descriptions that define the software testing processes. Supporting informative diagrams describing the processes are also provided.

This document is applicable to testing in all software development lifecycle models.

This document is intended for, but not limited to, testers, test managers, developers and project managers, particularly those responsible for governing, managing and implementing software testing.

This document specifies software test documentation templates that can be used for any organization, project

or testing activity. It describes the test documentation that is an output of the processes specified in

ISO/IEC/IEEE 29119-2 Test processes. An overview of the test documentation is provided in Figure 1 below.

Figure 1 — Overview of test documentation

This document is applicable to testing in all software development lifecycle models. This document is intended

for, but not limited to, testers, test managers, developers, and project managers, particularly those responsible

for governing, managing, and implementing software testing.

In this document, for simplicity, each item of test documentation is described as if it were a separate hardcopy

document. Document titles and contents provided in this standard may be modified (e.g. added to, combined or

re-titled) and use of the nomenclature used in Clauses 5, 6, 7 and 8 is not mandatory. Test documentation shall

be considered as conforming if it is available in electronic format (e.g. records in a test management tool or

spreadsheet), divided into separate documents, or combined with other documents into one document.

ISO/IEC 23009-1:2014 primarily specifies formats for the Media Presentation Description and Segments for dynamic adaptive streaming delivery of MPEG media over HTTP. It is applicable to streaming services over the Internet.

ISO/IEC 23008-2 specifies high efficiency video coding.

This document provides guidance on the ways an organization can plan and prepare for, and implement, electronic discovery from the perspective of both technology and processes.

This document is relevant to both non-technical and technical personnel involved in some or all of the electronic discovery activities. It is important to note that this guidance is not intended to contradict or supersede local jurisdictional laws and regulations, so care should be exercised to ensure compliance with the prevailing jurisdictional requirements.

This part of ISO 19170 supports the definition of:

— a Discrete Global Grid System Core comprising

— a reference system using geometry with zonal identifiers, and

— functions providing import, export and topological query,

— Common Classes for spatio-temporal geometry, topology, zones, and zonal identifiers based on ISO

19111 coordinate systems. The spatio-temporal scope is constrained to

— spatial elements that are invariant through all time, and

— temporal elements that are invariant across all space.

— Equal Area Earth Reference System for DGGS.

This document specifies omnidirectional/360-degree image and motion contents using Rec. ITU-T T.81 | ISO/IEC 10918‑1, Rec. ITU-T T.800 (11/2015) | ISO/IEC 15444‑1, and ISO/IEC 18477-3.

This Recommendation | International Standard specifies the encapsulation of image formats specified in the JPEG 2000 family of Recommendations | International Standards in the framework defined in ISO/IEC 23008-12.

This part of ISO/IEC 23008 specifies MPEG media transport (MMT) technologies, which include a single encapsulation format, delivery protocols and signalling messages for transport and delivery of multimedia data over heterogeneous packet-switched networks for multimedia services. Types of packet-switched networks supported by this part of ISO/IEC 23008 include bidirectional networks such as Internet Protocol (IP) networks and unidirectional networks such as digital broadcast networks (which may or may not use the IP).

The technologies specified by this part of ISO/IEC 23008 belong to one of three functional areas of MMT: media processing unit (MPU) format, signalling messages and delivery protocol.

Media processing unit format specifies the "mpuf" branded ISO based media file format encapsulating both timed and non-timed media contents. The MPU format is a self-contained ISOBMFF structure enabling independent consumption of media data, which hides codec-specific details from the delivery function.

Signalling functional area specifies the formats of signalling messages carrying information for managing media content delivery and consumption, e.g. specific media locations and delivery configuration of media contents.

Delivery functional area specifies the payload formats that is independent of media and codec types, which allows fragmentation and aggregation of contents encapsulated as specified by this part of ISO/IEC 23008 for delivery using packet-switched oriented transport protocols. The delivery functional area also provides an application layer transport protocol that allows for advanced delivery of media contents.

This part of ISO/IEC 15961 focuses on the abstract interface between an application and the data processor, and includes the specification and definition of application commands and responses. It allows data and commands to be specified in a standardised way, independent of the particular air interface of ISO/IEC 18000.

This part of ISO/IEC 15961

⎯ provides guidelines on how data shall be presented as objects;

⎯ defines the structure of Object Identifiers, based on ISO/IEC 9834-1;

⎯ specifies the commands that are supported for transferring data between an application and the radio frequency identification (RFID) tag;

⎯ specifies the responses that are supported for transferring data between the tag and the application;

⎯ does not specify any required transfer syntax with ISO/IEC 15962, but provides the non-normative information in Annex A to provide backward compatibility with ISO/IEC 15961:2004.

It is expected that this part of ISO/IEC 15961 will be used as a reference to develop software appropriate for particular applications, or for particular RFID equipment.

This document describes tests that verify on-board unit (OBU) conformance of implementations of

functions and data structures, as defined in the implementation conformance statement based on

ISO 14906 for electronic fee collection (EFC) applications.

It defines tests for assessment of OBU conformance in terms of :

— basic dedicated short-range communication (DSRC) L7 functionality,

— EFC application functions,

— EFC attributes (i.e. EFC application information),

— the addressing procedures of EFC attributes and (hardware) components,

— the EFC transaction model, which defines the common elements and steps of any EFC transaction,

and

— the behaviour of the interface so as to support interoperability on an EFC-DSRC application interface

level.

After the tests of isolated data items and functions (C.2 to C.4), an example is given for testing of a

complete EFC transaction (C.3).

Whereas this document defines examples of test cases for DSRC and EFC functionality in Annex C, it does

not intend to specify a complete test suite for a certain implementation. To compose a test suite for a

specific EFC implementation, the test cases may have to be modified and new test cases may have to be

defined and added for the conformance test suite to be complete. It can be useful to consider the following

when defining a complete test suite:

— small range: “exhaustive testing” of critical interoperability/compatibility features,

— large range: testing of boundaries and random values, and

— composite types: testing of individual items in sequence or parallel.

It is outside the scope of this document to define tests that assess

— performance,

— robustness, and

— reliability of an implementation.

NOTE 1 ISO 14907-1 defines test procedures that are aimed at assessing performance, robustness and reliability

of EFC equipment and systems.

NOTE 2 The ISO/IEC 10373 series defines test methods for proximity, vicinity, integrated circuit(s) cards and

related devices that may be relevant for OBUs that support such cards.

Annex D provides an informative overview of Japanese OBE conformance tests that are based on the ISO

14907 series, in order to illustrate how these can be applied in practice.

This document describes tests that verify on-board unit (OBU) conformance of implementations of

functions and data structures, as defined in the implementation conformance statement based on

ISO 14906 for electronic fee collection (EFC) applications.

It defines tests for assessment of OBU conformance in terms of :

— basic dedicated short-range communication (DSRC) L7 functionality,

— EFC application functions,

— EFC attributes (i.e. EFC application information),

— the addressing procedures of EFC attributes and (hardware) components,

— the EFC transaction model, which defines the common elements and steps of any EFC transaction,

and

— the behaviour of the interface so as to support interoperability on an EFC-DSRC application interface

level.

After the tests of isolated data items and functions (C.2 to C.4), an example is given for testing of a

complete EFC transaction (C.3).

Whereas this document defines examples of test cases for DSRC and EFC functionality in Annex C, it does

not intend to specify a complete test suite for a certain implementation. To compose a test suite for a

specific EFC implementation, the test cases may have to be modified and new test cases may have to be

defined and added for the conformance test suite to be complete. It can be useful to consider the following

when defining a complete test suite:

— small range: “exhaustive testing” of critical interoperability/compatibility features,

— large range: testing of boundaries and random values, and

— composite types: testing of individual items in sequence or parallel.

It is outside the scope of this document to define tests that assess

— performance,

— robustness, and

— reliability of an implementation.

NOTE 1 ISO 14907-1 defines test procedures that are aimed at assessing performance, robustness and reliability

of EFC equipment and systems.

NOTE 2 The ISO/IEC 10373 series defines test methods for proximity, vicinity, integrated circuit(s) cards and

related devices that may be relevant for OBUs that support such cards.

Annex D provides an informative overview of Japanese OBE conformance tests that are based on the ISO

14907 series, in order to illustrate how these can be applied in practice.

This part of ISO 23247 provides an overview and general principles of a Digital Twin for manufacturing.

The ISO 23247 series defines a framework to guide the creation of Digital Twins of observable manufacturing elements including personnel, equipment, materials, processes, facilities, environment, products, and supporting documents.

The following are within the scope of this part of ISO 23247:

— scope statement for ISO 23247 as a whole;

— terms and definitions used throughout ISO 23247;

— overview and requirements of the Digital Twin framework for manufacturing.

The following are described in other parts of ISO 23247:

— reference architecture (Part 2);

— digital representation of manufacturing elements (Part 3);

— information exchange requirements for Digital Twins (Part 4).

The following are outside the scope of ISO 23247, but will be identified as use cases in technical reports;

— selection of the manufacturing devices and other resources to be represented by Digital Twins;

— selection of the manufacturing processes to be represented by Digital Twins;

— selection of the manufacturing products to be represented by Digital Twins.

This part of ISO 23247 provides a reference architecture for the Digital Twin in manufacturing.

The ISO 23247 series defines a framework to guide the creation of Digital Twins of observable manufacturing elements including personnel, equipment, materials, processes, facilities, environment, products, and supporting documents.

The following are within the scope of this part of ISO 23247:

— reference architecture goals and objectives;

— reference model;

— functional view.

The following are described in other parts of ISO 23247:

— overview and general principles (Part 1);

— digital representation of manufacturing elements (Part 3);

— information exchange requirements for Digital Twins (Part 4).

The following are outside of the scope of ISO 23247, but will be identified as use cases in technical reports.

— selection of the manufacturing devices and other resources to be represented by Digital Twins;

— selection of the manufacturing processes to be represented by Digital Twins;

— selection of the manufacturing products to be represented by Digital Twins.

This part of ISO 23247 provides a list of basic information attributes for the observable manufacturing elements.

The ISO 23247 series defines a framework to guide the creation of Digital Twins of observable manufacturing elements including personnel, equipment, materials, processes, facilities, environment, products, and supporting documents.

The following are within the scope of this part of ISO 23247:

— digital representation of observable manufacturing elements.

The following are described in other parts of ISO 23247:

— overview and general principles (Part 1);

— reference architecture (Part 2);

— Information exchange requirements for Digital Twins (Part 4).

The following are outside of the scope of ISO 23247, but will be identified as use cases in technical reports.

— selection of the manufacturing devices and other resources to be represented by Digital Twins;

— selection of the manufacturing processes to be represented by Digital Twins;

— selection of the manufacturing products to be represented by Digital Twins.

This part of ISO 23247 identifies technical requirements for information exchange between entities within the reference architecture.

The ISO 23247 series defines a framework to guide the creation of Digital Twins of observable manufacturing elements including personnel, equipment, materials, processes, facilities, environment, products, and supporting documents.

The requirements for information exchange in the following networks are within the scope of this part of ISO 23247:

— User network that connects the User entity and Core entity;

— Service network that connects sub-entities within the Core entity;

— Access network that connects the Data collection and device control entity to the Core entity and to the User entity;

— Proximity network that connects the Data collection and device control entity to the observable manufacturing elements.

The following are described in other parts of ISO 23247:

— overview and general principles (Part 1);

— reference architecture (Part 2);

— digital representation of manufacturing elements (Part 3).

The following are outside of the scope of ISO 23247, but will be identified as use cases in technical reports.

— selection of the manufacturing devices and other resources to be represented by Digital Twins;

— selection of the manufacturing processes to be represented by Digital Twins;

— selection of the manufacturing products to be represented by Digital Twins.

This part of ISO 21219 defines an index to the complete set of TPEG Generation 2 toolkit components and applications. New applications are enumerated with an Application Identification (AID) as they are added to the TPEG applications family.

This part of ISO 21219 will be updated when such developments occur, to indicate the latest status and the inter-working of the various TPEG specifications. It will be issued as a new editorial version every time a new issue of any other specification is issued. Preliminary AIDs are allocated and managed by TISA and are listed on the TISA homepage www .tisa .org.

This part of ISO/TS 21219 defines the TPEG Conditional Access Information (CAI) application. It allows to protect the content of a TPEG service from unauthorized access. It further supports the management of subscriber information (e.g. Control Words and ECM) on the client devices in order to setup, prolong or revoke a subscription on a given client device.

The application defines

— the logical channel, for the transmission of the additional CA information (CAI), and

— how the CAI is linked and synchronized to the scrambled content.

This part of ISO/TS 21219 is related to conditional access applied on service component level. It is open for an integration of different conditional access systems.

NOTE The basic concept behind the CAI application is to transport CAI in separate TPEG service components of a dedicated application type and to define an SNI table that contains the link between scrambled content and related CAI.

This part of ISO/TS 21219 specifies the TPEG Parking Information application which has been designed

to deliver parking information to a variety of receivers using a number of different channels, foremost

of course are digital broadcasting and Internet technologies. Parking information may be presented to

the user in many different ways, including text, voice, or graphics.

Today, traffic congestion has become a serious problem in urban areas. Some traffic congestion is

attributed to drivers searching for parking spaces. Therefore, timely provision of parking information

could help ease traffic congestion. Furthermore, parking information would be valuable for the visitor,

particularly when it could be used to signal where a temporary parking facility is established for a

special occasion.