PRICES include / exclude VAT
Homepage>BS Standards>35 INFORMATION TECHNOLOGY. OFFICE MACHINES>35.100 Open systems interconnection (OSI)>35.100.01 Open systems interconnection in general>BS ISO/IEC 9646-3:1998 Information technology. Open systems interconnection. Conformance testing methodology and framework The Tree and tabular combined notation (TTCN)
Sponsored link
immediate downloadReleased: 1999-05-15
BS ISO/IEC 9646-3:1998 Information technology. Open systems interconnection. Conformance testing methodology and framework The Tree and tabular combined notation (TTCN)

BS ISO/IEC 9646-3:1998

Information technology. Open systems interconnection. Conformance testing methodology and framework The Tree and tabular combined notation (TTCN)

Format
Availability
Price and currency
English Secure PDF
Immediate download
399.30 EUR
You can read the standard for 1 hour. More information in the category: E-reading
Reading the standard
for 1 hour
39.93 EUR
You can read the standard for 24 hours. More information in the category: E-reading
Reading the standard
for 24 hours
119.79 EUR
English Hardcopy
In stock
399.30 EUR
Standard number:BS ISO/IEC 9646-3:1998
Pages:280
Released:1999-05-15
ISBN:0 580 32390 0
Status:Standard
DESCRIPTION

BS ISO/IEC 9646-3:1998


This standard BS ISO/IEC 9646-3:1998 Information technology. Open systems interconnection. Conformance testing methodology and framework is classified in these ICS categories:
  • 35.100.01 Open systems interconnection in general

1.1 This part of ISO/IEC 9646 defines an informal test notation, called the Tree and Tabular Combined Notation (TTCN), for OSI conformance test suites, which is independent of test methods, layers and protocols, and which reflects the abstract testing methodology defined in ISO/IEC 9646-1 and ISO/IEC 9646-2.

1.2 It also specifies requirements and provides guidance for using TTCN in the specification of system-independent conform-ance test suites for one or more OSI standards. It specifies two forms of the notation: one, a human-readable form, applicable to the production of conformance test suite standards for OSI protocols; and the other, a machine-processable form, applicable to processing within and between computer systems.

1.3 This part of ISO/IEC 9646 applies to the specification of conformance test cases which can be expressed abstractly in terms of control and observation of protocol data units and abstract service primitives. Nevertheless, for some protocols, test cases may be needed which cannot be expressed in these terms. The specification of such test cases is outside the scope of this part of ISO/IEC 9646, although those test cases may need to be included in a conformance test suite standard.

For example, some static conformance requirements related to an application service may require testing techniques which are specific to that particular application.

The specification of test cases in which more than one behaviour description is to be run in parallel is dealt with by the concurrency features (particularly involving the definition of Test Components and Test Component Configurations).

1.4 This part of ISO/IEC 9646 specifies requirements on what a test suite standard may specify about a conforming realization of the test suite, including the operational semantics of TTCN test suites.

1.5 This part of ISO/IEC 9646 applies to the specification of conformance test suites for OSI protocols in OSI layers 2 to 7, specifically including Abstract Syntax Notation One (ASN.1) based protocols. The following are outside the scope of this part of ISO/IEC 9646:

  1. the specification of conformance test suites for Physical layer protocols;

  2. the relationship between TTCN and formal description techniques;

  3. the means of realization of executable test suites (ETS) from abstract test suites.

1.6 This part of ISO/IEC 9646 defines mechanisms for using concurrency in the specification of abstract test cases. Concurrency in TTCN is applicable to the specification of test cases:

  1. in a multi-party testing context;

  2. which handle multiplexing and demultiplexing in either a single-party or multi-party testing context;

  3. which handle splitting and recombining in either a single-party or multi-party testing context;

  4. in a single-party testing context when the complexity of the protocol or set of protocols handled by the IUT is such that concurrency can simplify the specification of the test case.

1.7 TTCN modules are defined to allow sharing of common TTCN specifications between test suites.