This document specifies general requirements for ORGANIZATIONS in the application of RISK MANAGEMENT before, during and after the connection of a HEALTH IT SYSTEM within a HEALTH IT INFRASTRUCTURE, by addressing the KEY PROPERTIES of SAFETY, EFFECTIVENESS and SECURITY whilst engaging appropriate stakeholders.

  • Standard
    39 pages
    English language
    sale 10% off
    e-Library read for
    1 day

REN/ESI-0019412-4v121

  • Standard
    10 pages
    English language
    sale 10% off
    e-Library read for
    1 day
  • Standard
    10 pages
    English language
    sale 15% off
  • Standard
    10 pages
    English language
    sale 15% off
  • Draft
    10 pages
    English language
    sale 10% off
    e-Library read for
    1 day

REN/ESI-0019411-2v241

  • Standard
    31 pages
    English language
    sale 10% off
    e-Library read for
    1 day
  • Standard
    31 pages
    English language
    sale 15% off
  • Standard
    31 pages
    English language
    sale 15% off
  • Draft
    31 pages
    English language
    sale 10% off
    e-Library read for
    1 day

This document defines a storage format for derived visual tracks and an initial base set of related transformation operations. The format defined in this document enables the interchange, editing, and display of timed sequences of images that result from transformation operations applied to input still images or samples of timed sequences of images in the same presentation. This format defines normative structures used to contain the description of transformation operations, how to link that transformation operations to the inputs, and defines how to process those transformation operations to obtain a timed sequence of video frames.

  • Standard
    18 pages
    English language
    sale 15% off
  • Draft
    18 pages
    English language
    sale 15% off

This document defines the configuration rules required for a hierarchical structure, directory naming rules, and content identifiers for files and documents containing healthcare information. Content can be expressed as ISO/HL7 27931:2009 (also known as HL7 Ver2.5) as the data format to store clinical data such as prescriptions, lab results, and disease classifications, but can also include other types of file-type such as XML, CDA, DOC/DOCX, PDF, XLS/XLSX, JPEG, MP4, etc. This document does not address the security and privacy attributes of the healthcare information being stored; these are considered implementation-specific.

  • Technical specification
    13 pages
    English language
    sale 15% off

This document defines physical characteristics and test methods for cards with devices, including but not limited to, power supplying devices, displays, sensors, microphones, loudspeakers, buttons or keypads. This document also covers aspects of coexistence of technologies of devices on the card and other machine-readable card technologies. Additional requirements related to biometric capture devices are defined in ISO/IEC 17839-2. Such requirements can be applied in addition to the ones defined in this document. ISO/IEC 17839-2 defines a type S2 card; the physical dimensions of the type S2 card are specified in Annex A.

  • Standard
    25 pages
    English language
    sale 15% off
  • Draft
    25 pages
    English language
    sale 15% off

This document defines the air interface for radio frequency identification (RFID) devices operating in the 860 MHz to 960 MHz industrial, scientific, and medical (ISM) band used in item management applications. It provides a common technical specification for RFID devices that can be used to develop RFID application standards. This document is intended to allow for compatibility and to encourage inter-operability of products for the growing RFID market in the international marketplace. It defines the forward and return link parameters for technical attributes including, but not limited to, operating frequency, operating channel accuracy, occupied channel bandwidth, maximum effective isotropic radiated power (EIRP), spurious emissions, modulation, duty cycle, data coding, bit rate, bit rate accuracy, bit transmission order, and, where appropriate, operating channels, frequency hop rate, hop sequence, spreading sequence, and chip rate. It further defines the communications protocol used in the air interface. This document specifies the physical and logical requirements for a passive-backscatter, Interrogator-Talks-First (ITF) systems. The system comprises Interrogators, also known as readers, and tags, also known as labels. An Interrogator receives information from a tag by transmitting a continuous-wave (CW) RF signal to the tag; the tag responds by modulating the reflection coefficient of its antenna, thereby backscattering an information signal to the Interrogator. The system is ITF, i.e. a tag modulates its antenna reflection coefficient with an information signal only after being directed to do so by an Interrogator. This document specifies —   physical interactions (the signalling layer of the communication link) between Interrogators and tags; —   logical operating procedures and commands between Interrogators and Tags; —   the collision arbitration scheme used to identify a specific tag in a multiple-tag environment; —   optional security commands that allow the use of crypto suites of ISO/IEC 29167.

  • Standard
    332 pages
    English language
    sale 15% off
  • Draft
    331 pages
    English language
    sale 15% off

REN/ESI-0019102-1v121

  • Standard
    83 pages
    English language
    sale 10% off
    e-Library read for
    1 day
  • Standard
    83 pages
    English language
    sale 15% off
  • Standard
    83 pages
    English language
    sale 15% off
  • Draft
    83 pages
    English language
    sale 10% off
    e-Library read for
    1 day

IEC 60958-5:2021 enhances the consumer application of the interface for the interconnection of digital audio equipment defined in IEC 60958-1 and IEC 60958-3, introducing: - multichannel; - multi-stream; - high-resolution; - multimedia extension; - related applications.

  • Standard
    23 pages
    English language
    sale 10% off
    e-Library read for
    1 day
  • Draft
    20 pages
    English language
    sale 10% off
    e-Library read for
    1 day

IEC 62680-1-3:2021 defines the USB Type-C™ receptacles, plug and cables. The USB Type-C Cable and Connector Specification defines a new receptacle, plug, cable and detection mechanisms that are compatible with existing USB interface electrical and functional specifications. This specification covers the following aspects that are needed to produce and use this new USB cable/connector solution in newer platforms and devices, and that interoperate with existing platforms and devices: - USB Type-C receptacles, including electro-mechanical definition and performance requirements - USB Type-C plugs and cable assemblies, including electro-mechanical definition and performance requirements - USB Type-C to legacy cable assemblies and adapters - USB Type-C-based device detection and interface configuration, including support for legacy connections - USB Power Delivery optimized for the USB Type-C connector. This specification is intended as a supplement to the existing USB 2.0, USB 3.1 and USB Power Delivery specifications. It addresses only the elements required to implement and support the USB Type-C receptacles, plugs and cables. Normative information is provided to allow interoperability of components designed to this specification. Informative information, when provided, may illustrate possible design implementations. IEC 62680-1-3:2021 cancels and replaces the third edition published in 2018 and constitutes a technical revision. New release primarily for enabling USB4 over USB Type-C connectors and cables. Also includes incorporation of all approved ECNs as of the revision date plus editorial clean-up.

  • Standard
    367 pages
    English language
    sale 10% off
    e-Library read for
    1 day

This document provides information and requirements for identifying cost-effective technologies and related standards required to deploy, manage and operate sustainable “green” ITS technologies in surface transportations with eco-mobility. These ITS technologies can increase operational efficiencies and unlock enhanced transportation safety and eco-mobility applications. The ISO 20529 series builds on the existing standards and best practices of transport operation and management systems, as well as ITS applications, and aims to accommodate the specific needs of eco-mobility. G-ITS standards are expected to focus on the use of data exchange interface standards to enable the deployment of cloud-based multi-modal mobility solutions using wireless networks and nomadic devices. These forward-looking solutions are “infrastructure light” and can thus impact developing regions with little or no legacy transportation infrastructure. This document is intended to provide mobility information according to user preference on demand, utilizing a variety of existing apps on nomadic devices related to various means of transport. An integrated mobility information platform is defined in this document as a service methodology to be integrated with a variety of mobile apps with respect to different modes of transport. The framework described in this document includes: —   Identification of implementation aspects of related standards by means of use case. —   Identification of the multi-modal transport information necessary to support G-ITS. —   Eco-friendly route guidance according to user preference. —   Smart modal choice service based on carbon footprint, fuel efficiency and carbon-free zones for G-ITS.

  • Standard
    64 pages
    English language
    sale 15% off
  • Draft
    64 pages
    English language
    sale 15% off

This part of IEC 62541 describes the OPC Unified Architecture (OPC UA) security model. It describes the security threats of the physical, hardware, and software environments in which OPC UA is expected to run. It describes how OPC UA relies upon other standards for security. It provides definition of common security terms that are used in this and other parts of the OPC UA specification. It gives an overview of the security features that are specified in other parts of the OPC UA specification. It references services, mappings, and Profiles that are specified normatively in other parts of the OPC UA Specification. It provides suggestions or best practice guidelines on implementing security. Any seeming ambiguity between this part and one of the other normative parts does not remove or reduce the requirement specified in the other normative part.

  • Technical report
    51 pages
    English language
    sale 10% off
    e-Library read for
    1 day

This document establishes a learner information model specific to mobile learning to enable learning, education and training environments to reflect the specific needs of mobile participants. It gives guidance on the use of a learner information model for mobile technology in learning, education and training (mobile learning). This document can be used as a reference by software developers, implementers, instructional designers, teachers, trainers, automated systems and learning management systems.

  • Standard
    18 pages
    English language
    sale 15% off
  • Technical specification
    43 pages
    English language
    sale 10% off
    e-Library read for
    1 day

This part of IEC 63245 specifies requirements for spatial wireless power transfer based on multiple magnetic resonances (SWPT-MMR), which is a non-radiative wireless power transfer (WPT). This document contains two categories of requirements: general requirements and functional requirements. The general requirements cover charging procedures and charging zones. The functional requirements cover each component of a SWPT-MMR system, such as transmitter coils.

  • Standard
    18 pages
    English language
    sale 10% off
    e-Library read for
    1 day

This document defines the syntax and semantics in the field of electronic fee collection (EFC). The data types and assignment of vales are provided in accordance with the abstract syntax notation one (ASN.1) technique, as specified in ISO/IEC 8824 1. In particular, this document defines:
— ASN.1 (data) types within the fields of EFC and road user charging;
— ASN.1 (data) types of a more general use that are used more specifically in standards related to EFC.
This document does not seek to define ASN.1 (data) types that are primarily related to other fields that operate in conjunction with EFC, such as cooperative intelligent transport systems (C-ITS), the financial sector, etc.

  • Technical specification
    54 pages
    English language
    sale 10% off
    e-Library read for
    1 day

IEC 62680-1-2:2021 defines a power delivery system covering all elements of a USB system including: Hosts, Devices, Hubs, Chargers and cable assemblies. This specification describes the architecture, protocols, power supply behavior, connectors and cabling necessary for managing power delivery over USB at up to 100W. This specification is intended to be fully compatible and extend the existing USB infrastructure. It is intended that this specification will allow system OEMs, power supply and peripheral developers adequate flexibility for product versatility and market differentiation without losing backwards compatibility. This fourth edition cancels and replaces the fourth edition published in 2019 and constitutes a technical revision. It is also identified as USB Power Delivery Specification, Revision 3.0, Version 2.0 This updated release of the USB PD specification was made to incorporate all the ECNs that were made to USB PD 3.0, V1.2. This makes a full completed printed specifications with all ECNs incorporated into a hard copy specification.

  • Standard
    644 pages
    English language
    sale 10% off
    e-Library read for
    1 day
  • Draft
    683 pages
    English language
    sale 10% off
    e-Library read for
    1 day

This document defines a privacy architecture framework that:
— specifies concerns for ICT systems that process PII;
— lists components for the implementation of such systems; and
— provides architectural views contextualizing these components.
This document is applicable to entities involved in specifying, procuring, architecting, designing, testing, maintaining,
administering and operating ICT systems that process PII.
It focuses primarily on ICT systems that are designed to interact with PII principals.

  • Standard
    50 pages
    English language
    sale 10% off
    e-Library read for
    1 day
  • Draft
    47 pages
    English language
    sale 10% off
    e-Library read for
    1 day
  • Standard
    56 pages
    English language
    sale 10% off
    e-Library read for
    1 day
  • Draft
    50 pages
    English language
    sale 10% off
    e-Library read for
    1 day

This document complements and supplements the procedures and general requirements found in ISO/IEC 17025:2017 for laboratories performing testing based on ISO/IEC 19790 and ISO/IEC 24759.

  • Technical specification
    26 pages
    English language
    sale 15% off

This document complements and supplements the procedures and general requirements found in ISO/IECÂ 17025:2017 for laboratories performing evaluations based on the ISO/IECÂ 15408 series and ISO/IECÂ 18045.

  • Technical specification
    20 pages
    English language
    sale 15% off

This document defines a set of lossless (bit-preserving) and lossy compression methods for coding continuous-tone, bi-level, grey-scale, colour digital still images, or multi-component images. This document: –     specifies extended decoding processes for converting compressed image data to reconstructed image data; –     specifies an extended codestream syntax containing information for interpreting the compressed image data; –     specifies an extended file format; –     specifies a container to store image metadata; –     defines a standard set of image metadata; –     provides guidance on extended encoding processes for converting source image data to compressed image data; –     provides guidance on how to implement these processes in practice.

  • Standard
    333 pages
    English language
    sale 15% off
  • Draft
    360 pages
    English language
    sale 15% off

This document identifies and collects use cases for the integration of the DLT/blockchain within IoT systems, applications, and/or services. The use cases presented in this document use the IoT use case template

  • Technical report
    39 pages
    English language
    sale 15% off

This document describes: • key features of the socialized IoT systems, e.g. sensing the external physical world, resolving the uncertainties of targets, satisfying users' demand and providing quality service, etc.; • socialized attributes, i.e. socialized network, socialized collaboration, and socialized services, which are derived from the key features; and • guidelines on how to use or apply the socialized attributes in the design and development of IoT systems.

  • Technical report
    29 pages
    English language
    sale 15% off

This document specifies protocols, procedures, and managed objects used to ensure that the synchronization requirements are met for time-sensitive applications, such as audio, video, and time-sensitive control, across networks, for example, IEEE 802 and similar media. This includes the maintenance of synchronized time during normal operation and following addition, removal, or failure of network components and network reconfiguration. It specifies the use of IEEE 1588™ specifications where applicable in the context of IEEE Std 802.1Q™-2018.1 Synchronization to an externally provided timing signal [e.g., a recognized timing standard such as Coordinated Universal Time (UTC) or International Atomic Time (TAI)] is not part of this standard but is not precluded.

  • Standard
    403 pages
    English language
    sale 15% off
  • Draft
    403 pages
    English language
    sale 15% off

This document defines enrichments, extensions and structuring mechanisms of Petri nets, applied on the definitions proposed in ISO/IEC 15909-1. This document facilitates the definitions of new kinds of Petri nets and their interoperability, while remaining compatible with those defined in ISO/IEC 15909-1. This document is written as a reference for designers of new Petri net variants, by defining common enrichments, extensions and structuring mechanisms, as well as a generalized process for defining new ones. This document is applicable to a wide variety of concurrent discrete event systems and in particular distributed systems. Generic fields of application include: —   requirements analysis; —   development of specifications, designs and test suites; —   descriptions of existing systems prior to re-engineering; —   modelling business and software processes; —   providing the semantics for concurrent languages; —   simulation of systems to increase confidence; —   formal analysis of the behaviour of systems; —   and development of Petri net support tools. This document can be applied to the design of a broad range of systems and processes, including aerospace, air traffic control, avionics, banking, biological and chemical processes, business processes, communication protocols, computer hardware architectures, control systems, databases, defence command and control systems, distributed computing, electronic commerce, fault-tolerant systems, games, hospital procedures, information systems, Internet protocols and applications, legal processes, logistics, manufacturing systems, metabolic processes, music, nuclear power systems, operating systems, transport systems (including railway control), security systems, telecommunications and workflow.

  • Standard
    15 pages
    English language
    sale 15% off

Specifies mid-span power insertion into generic cabling as specified in ISO/IEC 11801, the location and allocation requirements in case of the replacement of a generic cabling component or components.

  • Technical report
    1 page
    English language
    sale 15% off

This document addresses bias in relation to AI systems, especially with regards to AI-aided decision-making. Measurement techniques and methods for assessing bias are described, with the aim to address and treat bias-related vulnerabilities. All AI system lifecycle phases are in scope, including but not limited to data collection, training, continual learning, design, testing, evaluation and use.

  • Technical report
    39 pages
    English language
    sale 15% off

This document provides requirements and recommendations for representing subject fields and concept relations in TBX-compliant terminological document instances. Examples in this document utilize the DCA style of TBX markup.

  • Technical specification
    15 pages
    English language
    sale 15% off

This document specifies a taxonomy and an ontology for blockchain and distributed ledger technologies (DLT). The taxonomy includes a taxonomy of concepts, a taxonomy of DLT systems and a taxonomy of application domains, purposes and economy activity sections for use cases. The ontology includes classes and attributes as well as relations between concepts. The audience includes but is not limited to academics, architects, customers, users, tool developers, regulators, auditors and standards development organizations.

  • Technical specification
    28 pages
    English language
    sale 15% off
  • Draft
    24 pages
    English language
    sale 15% off

This document specifies low complexity enhancement video coding.

  • Standard
    119 pages
    English language
    sale 15% off
  • Draft
    119 pages
    English language
    sale 15% off

This document addresses environmental control within data centres based upon the criteria and classifications for “availability”, “security” and “energy efficiency enablement” within ISO/IEC 22237‑1. This document specifies requirements and recommendations for the following: a) temperature control; b) fluid movement control; c) relative humidity control; d) particulate control; e) vibration; f) physical security of environmental control systems.

  • Standard
    24 pages
    English language
    sale 15% off
  • Draft
    24 pages
    English language
    sale 15% off

This document specifies data interchange formats for signature/sign behavioural data captured in the form of a multi-dimensional time series using devices such as digitizing tablets or advanced pen systems. The data interchange formats are generic, in that they can be applied and used in a wide range of application areas where handwritten signs or signatures are involved. No application-specific requirements or features are addressed in this document. This document contains: —   a description of what data can be captured; —   three binary data formats for containing the data: a full format for general use, a compression format capable of holding the same amount of information as the full format but in compressed form, and a compact format for use with smart cards and other tokens that does not require compression/ decompression but conveys less information than the full format; —   an XML schema definition; and —   examples of data record contents and best practices in capture. Specifying which of the format types and which options defined in this document are to be applied in a particular application is out of scope; this needs to be defined in application-specific requirements specifications or application profiles. It is advisable that cryptographic techniques be used to protect the authenticity, integrity, and confidentiality of stored and transmitted biometric data; yet such provisions are beyond the scope of this document. This document also specifies elements of conformance testing methodology, test assertions and test procedures as applicable to this document. It establishes test assertions on the structure and internal consistency of the signature/sign time series data formats defined in this document (type A level 1 and 2 as defined in ISO/IEC 19794-1) and semantic test assertions (type A level 3 as defined in ISO/IEC 19794-1). The conformance testing methodology specified in this document does not establish: —   tests of other characteristics of biometric products or other types of testing of biometric products (e.g. acceptance, performance, robustness, security); or —   tests of conformance of systems that do not produce data records claimed to conform to the requirements of this document.

  • Standard
    84 pages
    English language
    sale 15% off
  • Draft
    84 pages
    English language
    sale 15% off
  • Standard
    55 pages
    English language
    sale 15% off
  • Draft
    55 pages
    English language
    sale 15% off
  • Standard
    193 pages
    English language
    sale 15% off
  • Draft
    193 pages
    English language
    sale 15% off
  • Standard
    13 pages
    English language
    sale 15% off
  • Draft
    13 pages
    English language
    sale 15% off

This Recommendation | International Standard specifies the framework, concepts, methodology for testing, and criteria to be achieved to claim compliance to Rec. ITU-T T.800 | ISO/IEC 15444-1 or Rec. ITU-T T.814 | ISO/IEC 15444-15. It provides a framework for specifying abstract test suites (ATSs) and for defining the procedures to be followed during compliance testing. This Recommendation | International Standard: ‒     specifies compliance testing procedures for encoding and decoding using Rec. ITU-T T.800 | ISO/IEC 15444-1 and Rec. ITU-T T.814 | ISO/IEC 15444-15; ‒     specifies codestreams, decoded images, and error metrics to be used with the testing procedures; ‒     specifies ATSs; ‒     provides guidance for creating an encoder compliance test This Recommendation | International Standard does not include the following tests: Acceptance testing: the process of determining whether an implementation satisfies acceptance criteria and enables the user to determine whether or not to accept the implementation. This includes the planning and execution of several kinds of tests (e.g., functionality, quality, and speed performance testing) that demonstrate that the implementation satisfies the user requirements. Performance testing: measures the performance characteristics of an implementation under test (IUT) such as its throughput and responsiveness, under various conditions. Robustness testing: the process of determining how well an implementation processes data which contains errors.

  • Standard
    41 pages
    English language
    sale 15% off
  • Draft
    57 pages
    English language
    sale 15% off

Rec. ITU-T T.800 | ISO/IEC 15444-1 defines a set of lossless and lossy compression methods for coding continuous-tone, bi-level, greyscale or colour digital still images. This Recommendation | International Standard provides three independently created software reference implementations of Rec. ITU-T T.800 | ISO/IEC 15444-1, in order to assist implementers of Rec. ITU-T T.800 | ISO/IEC 15444-1 in testing and understanding its content. The packages are JASPER, JJ2000 and OPENJPEG. This Recommendation | International Standard also provides an independently created software reference implementation of Rec. ITU-T T.814 | ISO/IEC 15444-15, which specifies a high-throughput (HT) block coding algorithm that can be used in place of the block coding algorithm of Rec. ITU-T T.800 | ISO/IEC 15444-1, in order to assist implementers of Rec. ITU-T T.814 | ISO/IEC 15444-15 in testing and understanding its content. The package is TT. This Recommendation | International Standard additionally provides an independently created software reference implementation for parsing of a JP2 file format specified in Rec. ITU-T T.800 | ISO/IEC 15444-1 and a JPH file format specified in Rec. ITU-T T.814 | ISO/IEC 15444-15, The package is Codestream-parser. This Recommendation | International Standard does not define any additional part of the JPEG 2000 image coding system. Each version of the J2K reference software contains source code, which can be compiled to provide the following functionality: –     Transcoding from selected, widely available image formats into a JPEG 2000 codestream. –     Transcoding from selected, widely available image formats into the JP2 file format. –     Selection of a wide range of JPEG 2000 encoding options (as documented in each reference software). –     Decoding from a JPEG 2000 codestream to a range of selected widely available image formats. –     Processing of a JP2 file to extract a JPEG 2000 codestream for decoding and conversion to a range of selected widely available image formats. –     The ability to extract metadata from a JP2 file, including the contents of the Image Header box and the colour space. –     The decoding of JP2 files that use the three-component matrix-based form of the restricted ICC method for the specification of colour space and the conversion of the decoded image data to the sRGB colour space for display, including limited upsampling of all decoded components to the same resolution. –     The decoding of JP2 files that use the monochrome form of the restricted ICC method for the specification of colour space and the conversion of the decoded image data to the sRGB based greyscale space as defined within the JP2 file format. –     The decoding of JP2 files that use the sYCC colour space and the conversion of the decoded image data to the sRGB colour space for display, including upsampling of all decoded components to the same resolution. –     Some additional tools to help with evaluation and testing. The TT HTJ2K reference software contains source code, which can be compiled to provide the following functionality: –     Decoding from a HTJ2K codestream to a range of selected widely available image formats. The codestream-parser reference software contains source code, which can provide the following functionality: –     Parsing of JP2 file format; –     Parsing of JPH file format. The reference software is intended for use as a testing and validation tool for other implementations of JPEG 2000, and to help in the understanding of Rec. ITU-T T.800 | ISO/IEC 15444-1 and Rec. ITU-T T.814 | ISO/IEC 15444-15.

  • Standard
    25 pages
    English language
    sale 15% off
  • Draft
    25 pages
    English language
    sale 15% off

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.

  • Standard
    54 pages
    English language
    sale 15% off
  • Draft
    54 pages
    English language
    sale 15% off

REN/ESI-0019122-1v121

  • Standard
    62 pages
    English language
    sale 15% off
  • Standard
    62 pages
    English language
    sale 10% off
    e-Library read for
    1 day
  • Standard
    62 pages
    English language
    sale 15% off
  • Draft
    62 pages
    English language
    sale 10% off
    e-Library read for
    1 day

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. 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.

  • Standard
    84 pages
    English language
    sale 15% off
  • Draft
    84 pages
    English language
    sale 15% off

This document defines test design techniques that can be used during the test design and implementation process that is defined in ISO/IEC/IEEE 29119‑2. Each technique follows the test design and implementation process that is defined in ISO/IEC/IEEE 29119‑2 and shown in Figure 1. This document is intended for, but not limited to, testers, test managers, and developers, particularly those responsible for managing and implementing software testing.

  • Standard
    135 pages
    English language
    sale 15% off
  • Draft
    136 pages
    English language
    sale 15% off

This document specifies reliability assessment criteria for high-throughput gene-expression data. It is applicable to assessing the accuracy, reproducibility, and comparability of gene-expression data that are generated from microarray, next-generation sequencing, and other forms of high-throughput technologies. This document identifies the quality-related data for the process of the next-generation sequencing of RNA (RNA-seq). The sequencing platform covered by this document is limited to short-read sequencers. The use of RNA-seq for mutation detection and virus identification is outside of the scope of this document. This document is applicable to human health associated species such as human, cell lines, and preclinical animals. Other biological species are outside the scope of this document. From a biological point of view, expression profiles of all genetic sequences including genes, transcripts, isoforms, exons, and junctions are within the scope of this document

  • Technical specification
    11 pages
    English language
    sale 15% off
  • Draft
    11 pages
    English language
    sale 15% off

This document provides an overview and general principles of a digital twin framework for manufacturing including: —   terms and definitions; —   requirements of the digital twin framework for manufacturing.

  • Standard
    12 pages
    English language
    sale 15% off
  • Draft
    12 pages
    English language
    sale 15% off

This document defines key management mechanisms based on asymmetric cryptographic techniques. It specifically addresses the use of asymmetric techniques to achieve the following goals. a) Establish a shared secret key for use in a symmetric cryptographic technique between two entities A and B by key agreement. In a secret key agreement mechanism, the secret key is computed as the result of a data exchange between the two entities A and B. Neither of them is able to predetermine the value of the shared secret key. b) Establish a shared secret key for use in a symmetric cryptographic technique between two entities A and B via key transport. In a secret key transport mechanism, the secret key is chosen by one entity A and is transferred to another entity B, suitably protected by asymmetric techniques. c) Make an entity's public key available to other entities via key transport. In a public key transport mechanism, the public key of entity A is transferred to other entities in an authenticated way, but not requiring secrecy. Some of the mechanisms of this document are based on the corresponding authentication mechanisms in ISO/IEC 9798‑3. This document does not cover certain aspects of key management, such as: —   key lifecycle management; —   mechanisms to generate or validate asymmetric key pairs; and —   mechanisms to store, archive, delete, destroy, etc., keys. While this document does not explicitly cover the distribution of an entity's private key (of an asymmetric key pair) from a trusted third party to a requesting entity, the key transport mechanisms described can be used to achieve this. A private key can in all cases be distributed with these mechanisms where an existing, non-compromised key already exists. However, in practice the distribution of private keys is usually a manual process that relies on technological means such as smart cards, etc. This document does not specify the transformations used in the key management mechanisms. NOTE      To provide origin authentication for key management messages, it is possible to make provisions for authenticity within the key establishment protocol or to use a public key signature system to sign the key exchange messages.

  • Standard
    90 pages
    English language
    sale 15% off
  • Draft
    86 pages
    English language
    sale 15% off

This document provides an overview of agile readiness factors that are likely to determine whether an organization, project, product or team is ready to start the transition to using an agile approach to their system and software development and maintenance activities. This document provides a general approach that is applicable to all agile methodologies and does not cover specific agile methodologies, such as Scrum, SAFe and eXtreme Programming (XP).

  • Technical report
    19 pages
    English language
    sale 15% off
  • Draft
    19 pages
    English language
    sale 15% off

This document specifies the conformance and reference software for omnidirectional media format (specified in ISO/IEC 23090‑2). This document describes the reference software modules and the features that is supports. It also provides a description of how the reference software can be utilized. In addition, the document lists and describes test vectors comprising ISO base media file format files, media presentation descriptions, segments and combinations thereof that conform to ISO/IEC 23090‑2.

  • Standard
    9 pages
    English language
    sale 15% off
  • Draft
    9 pages
    English language
    sale 15% off