ANSI INCITS ISO IEC 14362-1996 Information technology - Test methods for measuring conformance to Open Systems Interconnection (OSI) abstract data manipulation - Application Prograd.pdf

《ANSI INCITS ISO IEC 14362-1996 Information technology - Test methods for measuring conformance to Open Systems Interconnection (OSI) abstract data manipulation - Application Prograd.pdf》由会员分享，可在线阅读，更多相关《ANSI INCITS ISO IEC 14362-1996 Information technology - Test methods for measuring conformance to Open Systems Interconnection (OSI) abstract data manipulation - Application Prograd.pdf（88页珍藏版）》请在麦多课文档分享上搜索。

1、INTERNATIONAL STANDARD ISO/IEC 14362 First edition 1996-06-01 Information technology - Test methods for measuring conformance to Open Systems Interconnection (OS11 abstract data manipulation - Application Program Interface (API) Language independent Technologies de Iinforma tion - Mk thodes d essai

2、pour mesurer la conformit is la manipulation de don Telephone: +1202 371-0101; FAX: +1202 728-9614. Introduction vii INTERNATIONAL STANDARD OISO/IEC ISO/IEC 14362:1996(E) 1 Information technology-Test methods for 2 measuring conformance to Open Systems 3 Interconnection (OSI) abstract data 4 manipul

3、ation -Application Program 5 Interface (API) Language independent 6 7 8 This International Standard defines requirements for test methods for measuring 9 conformance to ISO/IEC 14360 (1). 10 ISO/IEC 14360 (1) is stated in terms that are independent of any particular pro- 11 gramming language, but ea

4、ch implementation that conforms to it implements a 12 particular programming language binding, and conforms to its programming 13 language binding specification. Each set of test methods for measuring confor- 14 mance to ISO/IEC 14360 (11 assumes a particular programming language binding 15 specific

5、ation. Each programming language binding specification may impose 16 further programming-language specific requirements on the test methods which, in 17 conjunction with the requirements imposed by this International Standard, consti- 18 tute the requirements that shall be satisfied by test methods

6、used for measuring 19 conformance to that programming language binding specification. This Interna- 20 tional Standard applies to all sets of test methods for measuring conformance to 21 any programming language binding specification for ISO/IEC 14360 11). Section 1: General 1.1 Scope 1.1 Scope ISOK

7、EX 14362:1996(E) OISO/IEC 22 The following standards contain provisions which, through reference in this text, 23 constitute provisions of this International Standard. At the time of publication, 24 the editions indicated were valid. All standards are subject to revision, and parties 25 to agreement

8、s based on this International Standard are encouraged to investigate 26 the possibility of applying the most recent editions of the standards indicated 27 below. Members of IEC and IS0 maintain registers of currently valid Interna- 28 tional Standards. 29 30 31 32 ca IEEE Std 1003.3-1991,1 IEEE Stan

9、dard for Information Technology-Test 33 Methods for Measuring Conformance to POSIX. 34 35 A set of test methods that conforms to this International Standard shall conform to 36 IEEE Std 1003.3-1991 2), with references to the “P0SIX.n test method 37 specification” being interpreted as references to t

10、his International Standard, and 38 references to “the POSIX standard for which conformance is being measured” being 39 interpreted as references to ISO/IEC 14360 (1). 40 In addition to meeting the conformance criteria defined in IEEE Std 1003.3-1991 41 (2), a set of test methods that conforms to thi

11、s International Standard shall test all 42 documentation assertions defined in this International Standard. 43 NOTE: Conformance to IEEE Std 1003.3-1991 (2) implies that the test methods will test all other 44 assertions defined in this International Standard. 1.2 Normative References (1) ISOAEC 143

12、60: 1996, Information technology-Open Systems Interconnec- tion (OSI) abstract data manipulation-Application Program Interface (API) Language independent. 1.3 Conformance 45 1) ISO/IEC documents can be obtained from the IS0 Central Secretariat, 1 Rue de Varembe, Case 46 Postale 56, CH-1211, Geneve 2

13、0, SwitzerlandkIuisse. IEEE documents can be obtained from the 47 IEEE Service Center, 445 Hoes Lane, P.O. Box 1331, Piscataway, NJ, 088551331, USA. 2 1 General OISO/IEC ISO/IEX 14362:1996(E) 2 3 2.1.1 General and Typographical Conventions 10 11 12 13 14 15 - The italic font is used for: 16 - Langua

14、ge-independent operation arguments, such as 17 source-valueqosition 18 - Introducing important terms 19 - Cross-references in 2.2 20 21 22 23 24 25 Section 2: Terminology and General Requirements 2.1 Conventions Language-independent, concrete OM class names; OM attribute names; and OM attribute valu

15、e names are spelled with hyphens between words. The first letters of language-independent OM class and OM attribute names are capitalized (e.g., Arbitrary-Encoding). Language-independent datatype, operation, argument and error names are lower- case and are spelled with underscores between words (e.g

16、., om-get . The use of fonts in this International Standard is as follows: - The Helvetica font is used for: - Language-independent operation names, such as om-copy-value - Language-independent datatype names, such as om-exclusions-type - Language-independent error names, such as no-such-class - The

17、 bold font is used for: - Language-independent, concrete OM class names, such as External - Language-independent OM attribute names, such as Arbitrary-Encoding - Language-independent OM attribute values, such as insert-at-certain-point 2.1 Conventions 3 ISO/IEC 14362:1996(E) OISOAEC 26 27 28 29 30 3

18、1 32 2.1.3 Test Methods Conventions 33 34 35 This International Standard contains an assertion for each statement that is 36 derived from the standard to which conformance is being measured, that pertains 37 to the documentation associated with the implementation being tested, and that is 38 true fo

19、r a conforming implementation. These assertions are called documentation 39 assertions. Each documentation assertion is labelled Dnn, where nn is a two digit 40 number that is unique within this International Standard. 41 2.2 Definitions 42 43 44 2.2.1.1 conformance document: A document provided by

20、an implementor that 45 contains implementation details as described in ISO/IEC 14360 11). 46 2.2.1.2 implementation defined: An indication that the implementation shall 47 define and document the requirements for correct program constructs and correct 48 data of a value or behavior ISOAEC 9945-l (Bl

21、). 49 50 With respect to implementations, the word may is to be interpreted as an optional 51 feature that is not required in this International Standard, but can be provided. 52 With respect to Strictly Conforming Applications, the word may means that the 53 optional feature shall not be used. - Th

22、e bold italic font is used for: - Language-independent, abstract OM class names, such as Object - The constant width (Courier) font is used for: - References to terms defined in the X.400 standards. 2.1.2 Language-Independent Conventions The language-independent conventions defined in ISO/IEC 14360

23、l shall apply in this International Standard. The assertion classification and labelling schemes defined in IEEE Std 1003.3-1991 (2 are used in this International Standard, with the following addition. 2.2.1 Terminology For the purposes of this International Standard, the following definitions apply

24、: 2.2.1.3 may: An indication of an optional feature ISO/IEC 9945-l Bl. 4 2 Terminology and General Requirements OISO/IEC ISOiIEC 14362:1996(E) 54 55 56 (1) With respect to implementations, an indication of an implementation 57 recommendation, but not a requirement. 58 (2) With respect to application

25、s, an indication of a recommended program- 59 ming practice for applications and a requirement for Strictly Conforming 60 Application 61 62 Certain functionality in this International Standard is optional, but the interfaces 63 to that functionality are always required. If the functionality is suppo

26、rted, the 64 interfaces work as specified by this International Standard (except that they do not 65 return the error condition indicated for the unsupported case). If the functionality 66 is not supported, the interface shall always return the indication specified for this 67 situation ISO/IEC 9945

27、-l Bl. 68 2.2.1.7 system documentation: All documentation provided with an implemen- 69 tation, except the conformance document ISO/IEC 9945-l Bl. 70 71 72 2.2.1.8 undefined: An indication that this International Standard imposes no 73 portability requirements on an applications use of an indetermin

28、ate value or its 74 behavior with erroneous program constructs or erroneous data ISO/IEC 9945-l 75 BUI. 76 Implementations (or other standards) may specify the result of using that value or 77 causing that behavior. An application using such behaviors is using extensions, as 78 defined in ISO/IEC 14

29、360 1). 79 2.2.1.9 unspecified: An indication that this International Standard imposes no 80 portability requirements on applications for correct program constructs or correct 81 data regarding a value or behavior ISO/IEC 9945-l Bl. 82 Implementations (or other standards) may specify the result of u

30、sing that value or 83 causing that behavior. An application requiring a specific behavior, rather than 84 tolerating any behavior when using that functionality, is using extensions, as 85 defined in ISOiIEC 14360 l. 2.2.1.4 shall: An indication of a requirement on the implementation or on Strictly C

31、onforming Applications, where appropriate ISO/IEC 9945-l Bl. 2.2.1.5 should: 2.2.1.6 supported: A condition regarding optional functionality. Electronically distributed documents for an implementation are considered part of the system documentation. 2.2 Definitions ISO/IEC14362:1996(E) OISO/IEC 2.2.

32、2 General Terms For the purposes of this International Standard, the following definitions apply: 86 2.2.2.1 abstract class: A class, instances of which are forbidden unless they belong to one of its concrete subclasses ISOLIEC 14360 l . 87 88 89 2.2.2.2 accessible object: An object for which the cl

33、ient possesses a valid desig- 90 nator or handle ISO/IEC 14360 (111. 91 2.2.2.3 assertion: A statement that is derived from the standard to which confor- 92 mance is being measured, that is true for a conforming implementation, and that 93 pertains either to functionality or behavior of a functional

34、 interface or namespace 94 allocation or to the documentation associated with the implementation being tested 95 ISO/IEC 14360 Ill. 96 2.2.2.4 attribute: A component of an object, comprised of an integer denoting the 97 type of the attribute and an ordered sequence of one or more attribute values, e

35、ach 98 accompanied by an integer denoting the syntax of the value ISO/IEC 14360 l . 99 2.2.2.5 base assertion: An assertion that is required to be tested for required 100 features and for implemented conditional features IEEE Std 1003.3-1991 2. 101 2.2.2.6 bit string: An ordered sequence of zero or

36、more bits ISO/IEC 14360 l. 102 2.2.2.7 byte: A unit of machine storage containing an ordered sequence of 8 bits 103 ISO/IEC 14360 (l. 104 2.2.2.8 character string: An ordered sequence of zero or more characters 105 ISOLIEC 14360 l. 106 2.2.2.9 class: A category into which objects are placed on the b

37、asis of both their 107 purpose and their internal structure ISO/IEC 14360 (111. 108 2.2.2.10 client: Sofkware that uses the interface ISO/IEC 14360 l . 109 2.2.2.11 concrete class: A class, instances of which are permitted either by 110 direct instantiation or the instantiation of its concrete subcl

38、asses ISO/IEC 14360 111 IN. 112 2.2.2.12 datatype: A collection of distinguished values, together with a collection 113 of characterizing operations on those values ISOLIEC 14360 l . 114 2.2.2.13 documentation assertion: An assertion that pertains to the documen- 115 tation associated with the imple

39、mentation being tested. 2 Terminology and General Requirements OISO/IEC ISODFX 14362:1996(E) 116 117 118 2.2.2.15 extended assertion: An assertion that is not required to be tested 119 IEEE Std 1003.3-1991 21. 120 2.2.2.16 generic interface: The interface, defined at a level that is independent 121

40、of any particular programming language ISO/IEC 14360 l . 122 2.2.2.17 immediate subclass: A subclass, of a class C, having no superclasses 123 that are themselves subclasses of C ISO/IEC 14360 l). 124 2.2.2.18 immediate subobject: One object that is a value of an attribute of 125 another ISO/IEC 143

41、60 l. 126 2.2.2.19 immediate superclass: The superclass, of a class C, having no sub- 127 classes that are themselves superclasses of C ISO/IEC 14360 l . 128 2.2.2.20 immediate superobject: One object that contains another among its 129 attribute values ISO/IEC 14360 (111. 130 2.2.2.21 inaccessible

42、object: An object for which the client does not possess a 131 valid designator or handle ISO/IEC 14360 l. 132 2.2.2.22 independent copy: A copy of the object plus independent copies of all 133 its subobjects (applied recursively) ISO/IEC 14360 (l. 134 2.2.2.23 instance: An object in the category rep

43、resented by a class ISO/IEC 135 14360 (l. 136 2.2.2.24 intermediate datatype: Any of the basic datatypes in terms of which 137 the other, substantive datatypes of the interface are defined ISO/IEC 14360 l. 138 2.2.2.25 length: The number of bytes required to represent any string ISO/IEC 139 14360 WI

44、. 140 2.2.2.26 minimally consistent object: An object that satisfies various condi- 141 tions set forth in the definition of its class ISO/IEC 14360 l) . 2.2.2.14 element: Any of the bits of a bit string, the octets of an octet string, or the bytes by means of which the characters of a character str

45、ing are represented ISO/IEC 14360 (l). 2.2 Definitions 7 ISO/JEC 14362:1996(E) OISO/IEC 142 143 This International Standard does not specify when a name is bound to its value: at 144 compile time, link time, or load time. The use of a name as a parameter in a data- 145 type specification does not im

46、ply that its value is defined at compile time ISO/IEC 146 14360 (l. 147 2.2.2.28 object: Any of the complex information objects created, examined, 148 modified, or destroyed by means of the interface (ISO/IEC 14360 (111. 149 2.2.2.29 octet string: An ordered sequence of zero or more octets ISO/IEC 1

47、4360 150 (111. 151 2.2.2.30 operation: A program abstraction with formal input and output param- 152 eters that are bound to objects or values in the application that invokes it ISO/IEC 153 14360 (l. 154 2.2.2.31 OS1 abstract data manipulation application program interface: 155 The interface defined

48、 in (ISO/IEC 14360 (111. 156 2.2.2.32 package: A group of related classes ISO/IEC 14360 (l. 157 2.2.2.33 package closure: The set of classes that need to be supported in order to 158 be able to create all possible instances of all classes defined in the package 159 ISO/IEC 14360 (l). 160 2.2.2.34 po

49、sition (within a string): The ordinal position of one element of a 161 string relative to another (ISO/IEC 14360 (l). 162 2.2.2.35 position (within an attribute): The ordinal position of one value rela- 163 tive to another ISO/IEC 14360 (111. 164 2.2.2.36 primary representation: The form in which the service supplies an 165 attribute value to the client ISO/IEC 14360 (l). 166 2.2.2.37 private object: The internal representation of the language- 167 independent mod