RES/MTS-202784ed181

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

RES/MTS-201873-11 v4.9.1

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

RES/MTS-202785v181

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

RES/MTS-201873-9v4121

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

The present document defines the support for object-oriented features in TTCN-3. TTCN-3 can be used for the
specification of all types of reactive system tests over a variety of communication ports. Typical areas of application are
protocol testing (including mobile and Internet protocols), service testing (including supplementary services), module
testing, testing of OMG CORBA based platforms, APIs, etc. TTCN-3 is not restricted to conformance testing and can
be used for many other kinds of testing including interoperability, robustness, regression, system and integration testing.
The specification of test suites for physical layer protocols is outside the scope of the present document.
TTCN-3 packages are intended to define additional TTCN-3 concepts, which are not mandatory as concepts in the
TTCN-3 core language, but which are optional as part of a package which is suited for dedicated applications and/or
usages of TTCN-3.
While the design of TTCN-3 package has taken into account the consistency of a combined usage of the core language
with a number of packages, the concrete usages of and guidelines for this package in combination with other packages
is outside the scope of the present document.

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

The present document defines a normative way of using ASN.1 as defined in Recommendations ITU-T X.680 [2],
X.681 [3], X.682 [4] and X.683 [5] with TTCN-3. The harmonization of other languages with TTCN-3 is not covered
by the present document.

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

The component metadata lifecycle needs a comprehensive infrastructure with systems that cooperate well together. To enable this level of cooperation this document provides in depth descriptions and definitions of what CMDI records, components and their representations in XML look like.
This document describes these XML representations, which enable the flexible construction of interoperable metadata schemas suitable for, but not limited to, describing language resources. The metadata schemas based on these representations can be used to describe resources at different levels of granularity (e.g. descriptions on the collection level or on the level of individual resources).

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

This document specifies requirements for implementations of the C++ programming language. The first such requirement is that they implement the language, so this document also defines C++. Other requirements and relaxations of the first requirement appear at various places within this document. C++ is a general purpose programming language based on the C programming language as described in ISO/IEC 9899:2018 Programming languages — C (hereinafter referred to as the C standard). C++ provides many facilities beyond those provided by C, including additional data types, classes, templates, exceptions, namespaces, operator overloading, function name overloading, references, free store management operators, and additional library facilities.

  • Standard
    1853 pages
    English language
    sale 15% off

This part of IEC 61804 specifies the electronic device description language (EDDL)
technology, which enables the integration of real product details using the tools of the
engineering life cycle.
This document specifies EDDL as a generic language for describing the properties of
automation system components. EDDL is capable of describing
• device parameters and their dependencies;
• device functions, for example, simulation mode, calibration;
• graphical representations, for example, menus;
• interactions with control devices;
• graphical representations:
– enhanced user interface,
– graphing system;
• persistent data store.
EDDL is used to create electronic device description (EDD) for e.g. concrete devices,
common usable profiles or libraries. This EDD is used with appropriate tools to generate an
interpretative code to support parameter handling, operation, and monitoring of automation
system components such as remote I/Os, controllers, sensors, and programmable controllers.
Tool implementation is outside the scope of this document.
This document specifies the semantic and lexical structure in a syntax-independent manner. A
specific syntax is defined in Annex A, but it is possible to use the semantic model also with
different syntaxes.
IEC 61804-4 specifies EDD interpretation for EDD applications and EDDs to support EDD
interoperability.
IEC 61804-5 specifies the EDDL builtin library and provides the profiles of the various
fieldbuses.

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

This part of IEC 61804 specifies the EDDL builtin library and provides the profiles of the various
fieldbuses.

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

This part of IEC 61804 specifies EDD interpretation for EDD applications and EDDs to support
EDD interoperability. This document is intended to ensure that field device developers use the
EDDL constructs consistently and that the EDD applications have the same interpretations of
the EDD. It supplements the EDDL specification to promote EDDL application interoperability
and improve EDD portability between EDDL applications.

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

This part of IEC 62714 specifies the integration of logic information as part of an AML model
for the data exchange in a heterogenous engineering tool landscape of production systems.
This document specifies three types of logic information: sequencing, behaviour, and
interlocking information.
This document deals with the six following sequencing and behaviour logic models (covering
the different phases of the engineering process of production systems) and how they are
integrated in AML: Gantt chart, activity-on-node network, timing diagram, Sequential Function
Chart (SFC), Function Block Diagram (FBD), and mathematical expression.
This document specifies how to model Gantt chart, activity-on-node network, and timing
diagram and how they are stored in Intermediate Modelling Layer (IML).
NOTE 1 With this, it is possible to transform one logic model into another one. A forward transformation supports
the information enrichment process and reduces or avoids a re-entry of information between the exchanging
engineering tools.
NOTE 2 Mapping of other logic models, e.g. event-driven logic models like state charts, onto IML is possible.
This document specifies how interlocking information is modelled (as interlocking source and
target groups) in AML. The interlocking logic model is stored in Function Block Diagram (FBD).
This document specifies the AML logic XML schema that stores the logic models by using
IEC 61131-10.
This document specifies how to reference PLC programs stored in PLCopen XML documents.
This document does not define details of the data exchange procedure or implementation
requirements for the import/export tools.

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

This document discusses the syntax and semantics for including online analytic processing (OLAP) capabilities in SQL, as defined in ISO/IEC 9075-2. It discusses the following features regarding OLAP capabilities of the SQL language: — Feature T611, "Elementary OLAP operations", — Feature T612, "Advanced OLAP operations", — Feature T614, "NTILE function", — Feature T615, "LEAD and LAG functions", — Feature T616, "Null treatment option for LEAD and LAG functions", — Feature T617, "FIRST_VALUE and LAST_VALUE functions", — Feature T618, "NTH_VALUE function", — Feature T619, "Nested window functions", — Feature T620, "WINDOW clause: GROUPS option", — Feature T621, "Enhanced numeric functions".

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

The present document specifies an extension of the Test Description Language (TDL) enabling the specification of
structured test objectives. The extension covers the necessary additional constructs in the abstract syntax, their
semantics, as well as the concrete graphical syntactic notation for the added constructs. In addition textual syntax
examples of the TDL Structured Test Objectives extensions as well as BNF rules for a textual syntax for TDL with the
Structured Test Objectives extensions are provided. The intended use of the present document is to serve both as a
foundation for TDL tools implementing support for the specification of structured test objectives, as well as a reference
for end users applying the standardized syntax for the specification of structured test objectives with TDL.
NOTE: OMG®, UML®, OCL™ and UTP™ are the trademarks of OMG (Object Management Group). This
information is given for the convenience of users of the present document and does not constitute an
endorsement by ETSI of the products named.

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

The present document specifies how the elements of the Test Description Language (TDL) should be mapped to Testing
and Test Control Notation version 3 (TTCN-3) [2]. The intended use of the present document is to serve as the basis for
the development of TDL tools. The meta-model of TDL and the meanings of the meta-classes are described in ETSI
ES 203 119-1 [1].

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

The present document specifies the concrete graphical syntax of the Test Description Language (TDL). The intended
use of the present document is to serve as the basis for the development of graphical TDL tools and TDL specifications.
The meta-model of TDL and the meanings of the meta-classes are described in ETSI ES 203 119-1 [1].
NOTE: OMG®, UML®, OCL™ and UTP™ are the trademarks of OMG (Object Management Group). This
information is given for the convenience of users of the present document and does not constitute an
endorsement by ETSI of the products named.

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

The present document specifies the abstract syntax of the Test Description Language (TDL) in the form of a
meta-model based on the OMG® Meta Object Facility™ (MOF) [1]. It also specifies the semantics of the individual
elements of the TDL meta-model. The intended use of the present document is to serve as the basis for the development
of TDL concrete syntaxes aimed at TDL users and to enable TDL tools such as documentation generators, specification
analysers and code generators.
The specification of concrete syntaxes for TDL is outside the scope of the present document. However, for illustrative
purposes, an example of a possible textual syntax together with its application on some existing ETSI test descriptions
are provided.
NOTE: OMG®, UML®, OCL™ and UTP™ are the trademarks of OMG (Object Management Group). This
information is given for the convenience of users of the present document and does not constitute an
endorsement by ETSI of the products named.

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

The present document defines extensions to the Test Description Language (TDL) to support the re-use of test
configurations.
NOTE: OMG®, UML®, OCL™ and UTP™ are the trademarks of OMG (Object Management Group). This
information is given for the convenience of users of the present document and does not constitute an
endorsement by ETSI of the products named.

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

The present document specifies the exchange format of the Test Description Language (TDL) in the form of an XML
Schema derived from the TDL meta-model [1]. The intended use of the present document is to serve as the specification
of the format used for exchange of model instances and tool interoperability between TDL-compliant tools.
NOTE: OMG®, UML®, OCL™ and UTP™ are the trademarks of OMG (Object Management Group). This
information is given for the convenience of users of the present document and does not constitute an
endorsement by ETSI of the products named.

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

The present document defines the Behaviour Types package of TTCN-3. TTCN-3 can be used for the specification of all types of reactive system tests over a variety of communication ports. Typical areas of application are protocol testing (including mobile and Internet protocols), service testing (including supplementary services), module testing, testing of APIs, etc. TTCN-3 is not restricted to conformance testing and can be used for many other kinds of testing including interoperability, robustness, regression, system and integration testing. The specification of test suites for physical layer protocols is outside the scope of the present document. TTCN-3 packages are intended to define additional TTCN-3 concepts, which are not mandatory as concepts in the TTCN-3 core language, but which are optional as part of a package which is suited for dedicated applications and/or usages of TTCN-3. This package defines types for behaviour definitions in TTCN-3. While the design of TTCN-3 package has taken into account the consistency of a combined usage of the core language with a number of packages, the concrete usages of and guidelines for this package in combination with other packages is outside the scope of the present document.

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

The present document defines the mapping rules for W3C® XML Schema (as defined in [7] to [9]) to TTCN-3 as defined in ETSI ES 201 873-1 [1] to enable testing of XML-based systems, interfaces and protocols.

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

The present document defines a normative way of using ASN.1 as defined in Recommendations ITU-T X.680 [2], X.681 [3], X.682 [4] and X.683 [5] with TTCN-3. The harmonization of other languages with TTCN-3 is not covered by the present document.

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

The present document defines the support of advance matching of TTCN-3. TTCN-3 can be used for the specification of all types of reactive system tests over a variety of communication ports. Typical areas of application are protocol testing (including mobile and Internet protocols), service testing (including supplementary services), module testing, testing of OMG CORBA® based platforms, APIs, etc. TTCN-3 is not restricted to conformance testing and can be used for many other kinds of testing including interoperability, robustness, regression, system and integration testing. The specification of test suites for physical layer protocols is outside the scope of the present document. TTCN-3 packages are intended to define additional TTCN-3 concepts, which are not mandatory as concepts in the TTCN-3 core language, but which are optional as part of a package which is suited for dedicated applications and/or usages of TTCN-3. While the design of TTCN-3 package has taken into account the consistency of a combined usage of the core language with a number of packages, the concrete usages of and guidelines for this package in combination with other packages is outside the scope of the present document.

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

The present document defines the Advanced Parameterization package of TTCN-3. TTCN-3 can be used for the specification of all types of reactive system tests over a variety of communication ports. Typical areas of application are protocol testing (including mobile and Internet protocols), service testing (including supplementary services), module testing, testing of CORBA based platforms, APIs, etc. TTCN-3 is not restricted to conformance testing and can be used for many other kinds of testing including interoperability, robustness, regression, system and integration testing. The specification of test suites for physical layer protocols is outside the scope of the present document. TTCN-3 packages are intended to define additional TTCN-3 concepts, which are not mandatory as concepts in the TTCN-3 core language, but which are optional as part of a package which is suited for dedicated applications and/or usages of TTCN-3. This package defines:
• Value parameters of types.
• Type parameterization.
While the design of TTCN-3 package has taken into account the consistency of a combined usage of the core language with a number of packages, the concrete usages of and guidelines for this package in combination with other packages is outside the scope of the present document.

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

The present document defines the support for object-oriented features in TTCN-3. TTCN-3 can be used for the specification of all types of reactive system tests over a variety of communication ports. Typical areas of application are protocol testing (including mobile and Internet protocols), service testing (including supplementary services), module testing, testing of OMG CORBA based platforms, APIs, etc. TTCN-3 is not restricted to conformance testing and can be used for many other kinds of testing including interoperability, robustness, regression, system and integration testing. The specification of test suites for physical layer protocols is outside the scope of the present document. TTCN-3 packages are intended to define additional TTCN-3 concepts, which are not mandatory as concepts in the TTCN-3 core language, but which are optional as part of a package which is suited for dedicated applications and/or usages of TTCN-3. While the design of TTCN-3 package has taken into account the consistency of a combined usage of the core language with a number of packages, the concrete usages of and guidelines for this package in combination with other packages is outside the scope of the present document.

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

The present document defines the Core Language of TTCN-3. TTCN-3 can be used for the specification of all types of
reactive system tests over a variety of communication ports. Typical areas of application are protocol testing (including
mobile and Internet protocols), service testing (including supplementary services), module testing, testing of CORBA®
based platforms, APIs, etc. TTCN-3 is not restricted to conformance testing and can be used for many other kinds of
testing including interoperability, robustness, regression, system and integration testing. The specification of test suites
for physical layer protocols is outside the scope of the present document.
TTCN-3 is intended to be used for the specification of test suites which are independent of test methods, layers and
protocols. In addition to the textual format defined in the present document, while GFT (ETSI ES 201 873-3 [i.2])
defines a graphical presentation format for TTCN-3. The specification of these formats is outside the scope of the
present document.
While the design of TTCN-3 has taken the eventual implementation of TTCN-3 translators and compilers into
consideration the means of realization of Executable Test Suites (ETS) from Abstract Test Suites (ATS) is outside the
scope of the present document.

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

This document specifies software programming language vulnerabilities to be avoided in the development of systems where assured behaviour is required for security, safety, mission-critical and business-critical software. In general, this guidance is applicable to the software developed, reviewed, or maintained for any application. This document describes the way that the vulnerabilities listed in ISO/IEC TR 24772-1 are manifested or avoided in the C language.

  • Technical report
    42 pages
    English language
    sale 15% off
  • Technical report
    42 pages
    English language
    sale 15% off

The Geography Markup Language (GML) is an XML encoding in accordance with ISO 19118 for the transport and storage of geographic information modelled in accordance with the conceptual modelling framework used in the ISO 19100 series of International Standards and including both the spatial and non-spatial properties of geographic features.
This document defines the XML Schema syntax, mechanisms and conventions that:
— provide an open, vendor-neutral framework for the description of geospatial application schemas for the transport and storage of geographic information in XML;
— allow profiles that support proper subsets of GML framework descriptive capabilities;
— support the description of geospatial application schemas for specialized domains and information communities;
— enable the creation and maintenance of linked geographic application schemas and datasets;
— support the storage and transport of application schemas and datasets;
— increase the ability of organizations to share geographic application schemas and the information they describe.
Implementers can decide to store geographic application schemas and information in GML, or they can decide to convert from some other storage format on demand and use GML only for schema and data transport.
NOTE If an ISO 19109 conformant application schema described in UML is used as the basis for the storage and transportation of geographic information, this document provides normative rules for the mapping of such an application schema to a GML application schema in XML Schema and, as such, to an XML encoding for data with a logical structure in accordance with the ISO 19109 conformant application schema.

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

This document specifies software programming language vulnerabilities to be avoided in the development of systems where assured behaviour is required for security, safety, mission-critical and business-critical software. In general, this document is applicable to the software developed, reviewed or maintained for any application. Vulnerabilities described in this document present the way that the vulnerability described in ISO/IEC TR 24772-1 are manifested in Ada.

  • Technical report
    45 pages
    English language
    sale 15% off

The present document defines the mapping rules for W3C® XML Schema (as defined in [7] to [9]) to TTCN-3 as
defined in ETSI ES 201 873-1 [1] to enable testing of XML-based systems, interfaces and protocols.

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

This International Standard specifies the OMG Interface Definition Language (IDL). IDL is a descriptive language used to define data types and interfaces in a way that is independent of the programming language or operating system/processor platform. The IDL specifies only the syntax used to define the data types and interfaces. It is normally used in connection with other standards that further define how these types/interfaces are utilized in specific contexts and platforms: ? Separate "language mapping" standards define how the IDL-defined constructs map to specific programming languages, such as, C/C++, Java, C#, etc. ? Separate "serialization" standards define how data objects and method invocations are serialized into a format suitable for network transmission. ? Separate "middleware" standards, such as, DDS or CORBA leverage the IDL to define data-types, services, and interfaces. The description of IDL grammar uses a syntax notation that is similar to Extended Backus-Naur Format (EBNF).

  • Standard
    105 pages
    English language
    sale 15% off

This document specifies software programming language vulnerabilities to be avoided in the development of systems where assured behaviour is required for security, safety, mission-critical and business-critical software. Language-specific descriptions of these vulnerabilities are provided in other parts of the ISO/IEC 24772 series. It is applicable to the software developed, reviewed, or maintained for any application. This document does not address software engineering and management issues such as how to design and implement programs, use configuration management tools, use managerial processes, and perform process improvement. Furthermore, the specification of properties and applications to be assured are not treated. Vulnerabilities are described in a generic manner that is applicable to a broad range of programming languages.

  • Technical report
    166 pages
    English language
    sale 15% off

This International Standard provides rules and guidelines for the use of a conceptual schema language within the context of geographic information. The chosen conceptual schema language is the Unified Modeling Language (UML). This International Standard provides a profile of the Unified Modelling Language (UML). The standardization target type of this standard is UML schemas describing geographic information.

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

RES/MTS-201873-1v4A1

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

The main purpose of ClaML is to formally represent the content and hierarchical structure of healthcare
classification systems in a markup language for the safe exchange and distribution of data and structure
between organizations and dissimilar software products.
The scope of healthcare classification systems covered by this document encompasses terminologies,
and is constrained to traditional paper-based systems (like ICD-10) and systems built according to
categorial structures and a cross thesaurus (like ICNP)[2]. ClaML is intended for representation of
healthcare classification systems in which classes have textual definitions, hierarchical ordering,
named hierarchical levels (such as “chapter”, “section”), inclusion and exclusion criteria, and codes. It
is not intended to cover any formal representation, neither for definition or composition of concepts,
nor for specification of classification rules. Systems with such formal specifications can at best be
partially represented using ClaML, and are hence out of scope. Most of the notes and examples in this
document relate to ICD. This is because ICD is the most common classification system in the scope of
this document. As a highly complex classification system it is an inexhaustible source for examples of
nearly any kind. But all these notes and examples represent also other similar classification systems,
if applicable, which are usually less complex. An overview of currently known classification systems
using ClaML is provided in a separate document which is electronically available (see 7.3).
This document is not intended to:
a) provide a normative syntax on how a healthcare classification system is to be constructed;
b) define link types between elements in a healthcare classification system (this is left to the
developers of healthcare classification systems);
c) provide a representation for direct viewing or printing.

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

This document defines ways in which Database Language SQL can be used in conjunction with multidimensional arrays.

  • Standard
    163 pages
    English language
    sale 15% off

The present document defines the support of advance matching of TTCN-3. TTCN-3 can be used for the specification
of all types of reactive system tests over a variety of communication ports. Typical areas of application are protocol
testing (including mobile and Internet protocols), service testing (including supplementary services), module testing,
testing of OMG CORBA® based platforms, APIs, etc. TTCN-3 is not restricted to conformance testing and can be used
for many other kinds of testing including interoperability, robustness, regression, system and integration testing. The
specification of test suites for physical layer protocols is outside the scope of the present document.
TTCN-3 packages are intended to define additional TTCN-3 concepts, which are not mandatory as concepts in the
TTCN-3 core language, but which are optional as part of a package which is suited for dedicated applications and/or
usages of TTCN-3.
While the design of TTCN-3 package has taken into account the consistency of a combined usage of the core language
with a number of packages, the concrete usages of and guidelines for this package in combination with other packages
is outside the scope of the present document.

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

The present document defines the Core Language of TTCN-3. TTCN-3 can be used for the specification of all types of
reactive system tests over a variety of communication ports. Typical areas of application are protocol testing (including
mobile and Internet protocols), service testing (including supplementary services), module testing, testing of CORBA®
based platforms, APIs, etc. TTCN-3 is not restricted to conformance testing and can be used for many other kinds of
testing including interoperability, robustness, regression, system and integration testing. The specification of test suites
for physical layer protocols is outside the scope of the present document.
TTCN-3 is intended to be used for the specification of test suites which are independent of test methods, layers and
protocols. In addition to the textual format defined in the present document, while GFT (ETSI ES 201 873-3 [i.2])
defines a graphical presentation format for TTCN-3. The specification of these formats is outside the scope of the
present document.
While the design of TTCN-3 has taken the eventual implementation of TTCN-3 translators and compilers into
consideration the means of realization of Executable Test Suites (ETS) from Abstract Test Suites (ATS) is outside the
scope of the present document.

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

The present document defines the Configuration and Deployment Support package of TTCN-3. TTCN-3 can be used
for the specification of all types of reactive system tests over a variety of communication ports. Typical areas of
application are protocol testing (including mobile and Internet protocols), service testing (including supplementary
services), module testing, testing of APIs, etc. TTCN-3 is not restricted to conformance testing and can be used for
many other kinds of testing including interoperability, robustness, regression, system and integration testing. The
specification of test suites for physical layer protocols is outside the scope of the present document.
TTCN-3 packages are intended to define additional TTCN-3 concepts, which are not mandatory as concepts in the
TTCN-3 core language, but which are optional as part of a package which is suited for dedicated applications and/or
usages of TTCN-3.
This package defines the TTCN-3 support for static test configurations.
While the design of TTCN-3 package has taken into account the consistency of a combined usage of the core language
with a number of packages, the concrete usages of and guidelines for this package in combination with other packages
is outside the scope of the present document.

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

This Technical Report describes the support in SQL for Multi-Dimensional Arrays (MDA) as defined in ISO/IEC 9075-15.

  • Technical report
    67 pages
    English language
    sale 15% off

The present document defines the support for object-oriented features in TTCN-3. TTCN-3 can be used for the
specification of all types of reactive system tests over a variety of communication ports. Typical areas of application are
protocol testing (including mobile and Internet protocols), service testing (including supplementary services), module
testing, testing of OMG CORBA based platforms, APIs, etc. TTCN-3 is not restricted to conformance testing and can
be used for many other kinds of testing including interoperability, robustness, regression, system and integration testing.
The specification of test suites for physical layer protocols is outside the scope of the present document.
TTCN-3 packages are intended to define additional TTCN-3 concepts, which are not mandatory as concepts in the
TTCN-3 core language, but which are optional as part of a package which is suited for dedicated applications and/or
usages of TTCN-3.
While the design of TTCN-3 package has taken into account the consistency of a combined usage of the core language
with a number of packages, the concrete usages of and guidelines for this package in combination with other packages
is outside the scope of the present document.

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

This specification describes the form and establishes the interpretation of programs written in the C# programming language. It describes: — The representation of C# programs; — The syntax and constraints of the C# language; — The semantic rules for interpreting C# programs; — The restrictions and limits imposed by a conforming implementation of C#. This specification does not describe — The mechanism by which C# programs are transformed for use by a data-processing system; — The mechanism by which C# applications are invoked for use by a data-processing system; — The mechanism by which input data are transformed for use by a C# application; — The mechanism by which output data are transformed after being produced by a C# application; — The size or complexity of a program and its data that will exceed the capacity of any specific data-processing system or the capacity of a particular processor; — All minimal requirements of a data-processing system that is capable of supporting a conforming implementation.

  • Standard
    511 pages
    English language
    sale 15% off

The present document defines the support of advance matching of TTCN-3. TTCN-3 can be used for the specification
of all types of reactive system tests over a variety of communication ports. Typical areas of application are protocol
testing (including mobile and Internet protocols), service testing (including supplementary services), module testing,
testing of OMG CORBA based platforms, APIs, etc. TTCN-3 is not restricted to conformance testing and can be used
for many other kinds of testing including interoperability, robustness, regression, system and integration testing. The
specification of test suites for physical layer protocols is outside the scope of the present document.
TTCN-3 packages are intended to define additional TTCN-3 concepts, which are not mandatory as concepts in the
TTCN-3 core language, but which are optional as part of a package which is suited for dedicated applications and/or
usages of TTCN-3.
While the design of TTCN-3 package has taken into account the consistency of a combined usage of the core language
with a number of packages, the concrete usages of and guidelines for this package in combination with other packages
is outside the scope of the present document.

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

The present document defines the Configuration and Deployment Supportpackage of TTCN-3. TTCN-3 can be used for
the specification of all types of reactive system tests over a variety of communication ports. Typical areas of application
are protocol testing (including mobile and Internet protocols), service testing (including supplementary services),
module testing, testing of APIs, etc. TTCN-3 is not restricted to conformance testing and can be used for many other
kinds of testing including interoperability, robustness, regression, system and integration testing. The specification of
test suites for physical layer protocols is outside the scope of the present document.
TTCN-3 packages are intended to define additional TTCN-3 concepts, which are not mandatory as concepts in the
TTCN-3 core language, but which are optional as part of a package which is suited for dedicated applications and/or
usages of TTCN-3.
This package defines the TTCN-3 support for static test configurations.
While the design of TTCN-3 package has taken into account the consistency of a combined usage of the core language
with a number of packages, the concrete usages of and guidelines for this package in combination with other packages
is outside the scope of the present document.

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

The present document defines the Behaviour Types package of TTCN-3. TTCN-3 can be used for the specification of
all types of reactive system tests over a variety of communication ports. Typical areas of application are protocol testing
(including mobile and Internet protocols), service testing (including supplementary services), module testing, testing of
APIs, etc. TTCN-3 is not restricted to conformance testing and can be used for many other kinds of testing including
interoperability, robustness, regression, system and integration testing. The specification of test suites for physical layer
protocols is outside the scope of the present document.
TTCN-3 packages are intended to define additional TTCN-3 concepts, which are not mandatory as concepts in the
TTCN-3 core language, but which are optional as part of a package which is suited for dedicated applications and/or
usages of TTCN-3.
This package defines types for behaviour definitions in TTCN-3.
While the design of TTCN-3 package has taken into account the consistency of a combined usage of the core language
with a number of packages, the concrete usages of and guidelines for this package in combination with other packages
is outside the scope of the present document.

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

The present document specifies the exchange format of the Test Description Language (TDL) in the form of an XML
Schema derived from the TDL meta-model [1]. The intended use of the present document is to serve as the specification
of the format used for exchange of model instances and tool interoperability between TDL-compliant tools.
NOTE: OMG®, UML®, OCL™ and UTP™ are the trademarks of OMG (Object Management Group). This
information is given for the convenience of users of the present document and does not constitute an
endorsement by ETSI of the products named.

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

The present document specifies the concrete graphical syntax of the Test Description Language (TDL). The intended
use of the present document is to serve as the basis for the development of graphical TDL tools and TDL specifications.
The meta-model of TDL and the meanings of the meta-classes are described in ETSI ES 203 119-1 [1].
NOTE: OMG®, UML®, OCL™ and UTP™ are the trademarks of OMG (Object Management Group). This
information is given for the convenience of users of the present document and does not constitute an
endorsement by ETSI of the products named.

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

The present document specifies the abstract syntax of the Test Description Language (TDL) in the form of a
meta-model based on the OMG® Meta Object Facility™ (MOF) [1]. It also specifies the semantics of the individual
elements of the TDL meta-model. The intended use of the present document is to serve as the basis for the development
of TDL concrete syntaxes aimed at TDL users and to enable TDL tools such as documentation generators, specification
analysers and code generators.
The specification of concrete syntaxes for TDL is outside the scope of the present document. However, for illustrative
purposes, an example of a possible textual syntax together with its application on some existing ETSI test descriptions
are provided.
NOTE: OMG®, UML®, OCL™ and UTP™ are the trademarks of OMG (Object Management Group). This
information is given for the convenience of users of the present document and does not constitute an
endorsement by ETSI of the products named.

  • Standard
    112 pages
    English language
    sale 15% off
  • Standard
    113 pages
    English language
    sale 15% off
  • Standardization document
    112 pages
    English language
    sale 10% off
    e-Library read for
    1 day