AS/NZS 4225.1:1994

Defines a testing methodology and provides a framework for specifying abstract test cases for implementation testing, so providing a base for testing the interworking capability of ODA implementations. This Standard is identical with and has been reproduced from ISO/IEC TR 10183-1:1993.

This part of ISO/IEC TR 10183 defines a testing methodology and provides a framework for specifying abstract test cases for ISO 8613 implementation testing, the overall objective being the provision of a suitable base for testing the interworking capability of ODA implementations.Such testing will assist in the analysis of an implementation's ability to interwork in an environment of implementations of ISO 8613 and implementations of International Standardized Profiles (ISPs) based on ISO 8613. ISPs are standardized document application profiles that have been internationally harmonized. As such they represent agreed stabilized subsets of ISO 8613 designed for the interworking of ODA systems at different levels of functionality.In ISO 8613 the term "conformance" refers to the conformance of a data stream to the rules specified in ISO 8613. This includes the conformance of a data stream to a document application profile based on ISO 8613. Conformance testing methodology as defined in ISO 8613-1 Annex G covers the analysis of data streams without regard to the capabilities of implementations to generate or receive conforming data streams. To achieve an environment of interworking ODA systems, it is necessary to have a testing methodology that can verify implementation support for ISO 8613 and DAP's at the semantic level as well as the data stream or syntax level.Hence, implementation testing is additional testing that supplements the conformance testing of data streams. It increases the probability that different implementations of ISO 8613 and ISPs are able to interwork. Implementation testing is based on the concept of measuring an implementation's ability to generate and/or receive a representative set of documents. If an implementation can exhibit this capability, then it is more likely to successfully interwork with other verified implementations exchanging a wider range of documents.The implementation testing methodology introduces the requirement for abstract test cases as well as procedures for their use in the generation and reception testing of implementations.In establishing a framework for implementation testing, a conceptual model of ODA systems has been developed to describe, in an abstract sense, the multitude of configurations and limitations of real ODA systems.The methodology contained in this technical report caters for the testing of implementations of ISP's based on ISO 8613. The methodology may also be used for testing other Document Application Profiles based on ISO 8613.This part of ISO/IEC TR 10183- defines terms used in the context of Implementation testing; - presents a conceptual model of ODA implementations; - gives a phased approach to testing implementations;- determines the functional components in generation and reception testing;- gives the requirements for abstract test cases.This part of ISO/IEC TR 10183 does not cover the testing of user interfaces in an ODA based system. Any suitable system interface is only used as a point of control and observation to verify that ODA document transformations associated with the various ODA processes have been carried out as claimed by an implementor.Where appropriate, concepts and terminology described in ISO 9646 have been used in this Technical Report. In some cases, definitions and concepts have been adapted to cater for the fact that ODA is not an OSI protocol.

First published as Joint Standard AS/NZS 4225.1:1994.