ISO 13209-2-2012 Road vehicles - Open Test sequence eXchange format (OTX) - Part 2 Core data model specification and requirements《道路车辆 开路测试序列交换格式(OTX) 第2部分 核心数据.pdf

《ISO 13209-2-2012 Road vehicles - Open Test sequence eXchange format (OTX) - Part 2 Core data model specification and requirements《道路车辆 开路测试序列交换格式(OTX) 第2部分 核心数据.pdf》由会员分享，可在线阅读，更多相关《ISO 13209-2-2012 Road vehicles - Open Test sequence eXchange format (OTX) - Part 2 Core data model specification and requirements《道路车辆 开路测试序列交换格式(OTX) 第2部分 核心数据.pdf（212页珍藏版）》请在麦多课文档分享上搜索。

1、 Reference number ISO 13209-2:2012(E) ISO 2012INTERNATIONAL STANDARD ISO 13209-2 First edition 2012-08-15 Road vehicles Open Test sequence eXchange format (OTX) Part 2: Core data model specification and requirements Vhicules routiers Format public dchange de squence-tests (OTX) Partie 2: Exigences e

2、t spcifications du modle de donnes central ISO 13209-2:2012(E) COPYRIGHT PROTECTED DOCUMENT ISO 2012 All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm,

3、 without permission in writing from either ISO at the address below or ISOs member body in the country of the requester. ISO copyright office Case postale 56 CH-1211 Geneva 20 Tel. + 41 22 749 01 11 Fax + 41 22 749 09 47 E-mail copyrightiso.org Web www.iso.org Published in Switzerland ii ISO 2012 Al

4、l rights reserved ISO 13209-2:2012(E) ISO 2012 All rights reserved iii Contents Page Foreword . v Introduction vi 1 Scope 1 2 Normative references 1 3 Terms, definitions and abbreviated terms 2 3.1 Terms and definitions . 2 3.2 Abbreviated terms . 4 4 Requirements . 5 4.1 General . 5 4.2 Basic princ

5、iples for requirements definition 5 4.3 Clustering of requirements. 5 4.4 Requirement priorities 5 4.5 General format and language aspects 6 4.6 Test sequence development process support . 7 4.7 Language feature details 9 4.8 Boundaries . 15 5 Introduction to modelling in UML and XSD 17 5.1 General

6、aspects . 17 5.2 Class diagrams 17 5.3 Mapping to the XML Schema Definition language (XSD) 19 6 OTX principles . 23 6.1 General . 23 6.2 XML format . 23 6.3 Imperative and structured programming paradigm . 24 6.4 Graphical authoring of OTX sequences 24 6.5 Specification/Realisation concept . 24 6.6

7、Modular OTX extension concept and OTX-based runtime architecture 25 6.7 Context concept 26 6.8 Validities concept 27 6.9 Signature concept . 30 7 OTX Core data model specification . 31 7.1 General . 31 7.2 High-level overview of the OTX Core data model 32 7.3 Document root . 33 7.4 Imports 37 7.5 Gl

8、obal declarations . 38 7.6 Validity terms . 42 7.7 Signatures 44 7.8 Procedure signatures 46 7.9 Procedures . 48 7.10 Floating comments 51 7.11 Parameter declarations . 53 7.12 Local declarations . 55 7.13 Nodes 56 7.14 Actions 90 7.15 Terms 106 7.16 Universal types 140 Annex A (normative) OTX data

9、types . 162 ISO 13209-2:2012(E) iv ISO 2012 All rights reserved Annex B (normative) Scope and memory allocation 166 Annex C (normative) Comprehensive checker rule listing 168 Annex D (normative) Extension mechanism . 178 Annex E (normative) Schema annotations for exception handling 181 Annex F (norm

10、ative) XML Schemas . 182 Bibliography . 205 ISO 13209-2:2012(E) ISO 2012 All rights reserved v Foreword ISO (the International Organization for Standardization) is a worldwide federation of national standards bodies (ISO member bodies). The work of preparing International Standards is normally carri

11、ed out through ISO technical committees. Each member body interested in a subject for which a technical committee has been established has the right to be represented on that committee. International organizations, governmental and non-governmental, in liaison with ISO, also take part in the work. I

12、SO collaborates closely with the International Electrotechnical Commission (IEC) on all matters of electrotechnical standardization. International Standards are drafted in accordance with the rules given in the ISO/IEC Directives, Part 2. The main task of technical committees is to prepare Internati

13、onal Standards. Draft International Standards adopted by the technical committees are circulated to the member bodies for voting. Publication as an International Standard requires approval by at least 75 % of the member bodies casting a vote. Attention is drawn to the possibility that some of the el

14、ements of this document may be the subject of patent rights. ISO shall not be held responsible for identifying any or all such patent rights. ISO 13209-2 was prepared by Technical Committee ISO/TC 22, Road vehicles, Subcommittee SC 3, Electrical and electronic equipment. ISO 13209 consists of the fo

15、llowing parts, under the general title Road vehicles Open Test sequence eXchange format (OTX): Part 1: General information and use cases Part 2: Core data model specification and requirements Part 3: Standard extensions and requirements ISO 13209-2:2012(E) vi ISO 2012 All rights reserved Introductio

16、n Diagnostic test sequences are utilized whenever automotive components or functions with diagnostic abilities are being diagnosed, tested, reprogrammed or initialised by off-board test equipment. Test sequences define the succession of interactions between the user (i.e. workshop or assembly line s

17、taff), the diagnostic application (the test equipment) and the vehicle communication interface as well as any calculations and decisions that have to be carried out. Test sequences provide a means to define interactive, guided diagnostics or similar test logic. Today, the automotive industry mainly

18、relies on paper documentation and/or proprietary authoring environmments to document and to implement such test sequences for a specific test application. An author who is setting up engineering, assembly line or service diagnostic test applications needs to implement the required test sequences man

19、ually, supported by non-uniform test sequence documentation, most likely using different authoring applications and formats for each specific test application. This redundant effort can be greatly reduced if processes and tools support the OTX concept. ISO 13209 proposes an open and standardized for

20、mat for the human- and machine-readable description of diagnostic test sequences. The format supports the requirements of transferring diagnostic test sequence logic uniformly between electronic system suppliers, vehicle manufacturers and service dealerships/repair shops. This part of ISO 13209 repr

21、esents the requirements and technical specification for the fundament of the OTX format, namely the “OTX Core“. The Core describes the basic structure underlying every OTX document. This comprises detailed data model definitions of all required control structures by which test sequence logic is desc

22、ribed, but also definitions of the outer, enveloping document structure in which test sequence logic is embedded. To achieve extensibility the core also contains well-defined extension points that allow a separate definition of additional OTX features without the need to change the core data model.

23、ISO 13209-3 extends the Core by a set of additional features, using of the Core extension mechanism (which may also be applied for proprietary extensions). This part of ISO 13209 is the most generic and stand-alone part of ISO 13209. In principle, it is also applicable in other areas for any sequent

24、ial logic description, even outside the automotive domain. Automotive-specific features are therefore contained solely in ISO 13209-3. INTERNATIONAL STANDARD ISO 13209-2:2012(E) ISO 2012 All rights reserved 1 Road vehicles Open Test sequence eXchange format (OTX) Part 2: Core data model specificatio

25、n and requirements 1 Scope This part of ISO 13209 defines the OTX Core requirements and data model specifications. The requirements are derived from the use cases described in ISO 13209-1. They are listed in the requirements section which composes the first major part of this document. The data mode

26、l specification aims at an exhaustive definition of all OTX Core features implemented to satisfy the Core requirements. Since OTX is designed for describing test sequences, which themselves represent a kind of program, the Core data model follows the basic concepts common to most programming languag

27、es. Thus, this part of ISO 13209 establishes rules for syntactical entities like parameterised procedures, constant and variable declarations, data types, basic arithmetic, logic and string operations, flow control statements like loop, branch or return, simple statements like assignment or procedur

28、e call as well as exception handling mechanisms. Each of these syntactical entities is accompanied by semantic rules which determine how OTX documents are to be interpreted. The syntax rules are provided by UML class diagrams and XML schemas, whereas the semantics are given by UML activity diagrams

29、and prose definitions. With respect to documentation use cases, special attention is paid to defining a specification/realisation concept (which allows for “hybrid“ test sequences: human readable test sequences that are at the same time machine-readable) and so called floating comments (which can re

30、fer to more than one node of the sequence). The Core data model does NOT define any statements, expressions or data types that are dependent on a specific area of application. 2 Normative references The following referenced documents are indispensable for the application of this document. For dated

31、references, only the edition cited applies. For undated references, the latest edition of the referenced document (including any amendments) applies. ISO/IEC 10646:2011, Information technology Universal Coded Character Set (UCS) ISO 13209-1, Road vehicles Open Test sequence eXchange format (OTX) Par

32、t 1: General information and use cases ISO/IEC 19501:2005, Information technology Open Distributed Processing Unified Modeling Language (UML) Version 1.4.2 ISO 22901 (all parts), Road vehicles Open diagnostic data exchange (ODX) IEEE 754:2008, IEEE Standard for Floating-Point Arithmetic ISO 13209-2:

33、2012(E) 2 ISO 2012 All rights reserved RFC 2045, Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies RFC 2046, Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types RFC 4122, A Universally Unique IDentifier (UUID) URN Namespace W3C XSD:2004, W3C Reco

34、mmendation: XML Schema (all parts) W3C XML:2008, W3C Extensible Markup Language (XML) 1.0 (Fifth Edition) W3C XMLNS:2009, W3C Recommendation: Namespaces in XML 1.0 (Third Edition) W3C XMLBASE:2009, W3C Recommendation: XML Base (Second Edition) W3C XLink:2010, W3C Recommendation: XML Linking Language

35、 (XLink) Version 1.1 3 Terms, definitions and abbreviated terms 3.1 Terms and definitions For the purposes of this document, the terms and definitions given in ISO 13209-1 and the following apply. 3.1.1 attribute a property of a UML class 3.1.2 attribute named property of an XSD complex type or an X

36、ML element 3.1.3 after market part of the automotive industry concerned with manufacturing, remanufacturing, distribution, retailing, and installation of all vehicle parts, chemicals, tools, equipment and accessories for light and heavy vehicles, after the sale of the automobile by the original equi

37、pment manufacturer (OEM) to the consumer 3.1.4 after sales after sales department department of an automotive OEM that is concerned with the distribution, retailing, servicing, repair and installation of vehicles of that OEM 3.1.5 constant identifier of a non-writable memory location 3.1.6 context e

38、nvironmental circumstances which influence test sequence execution NOTE OTX test sequences can be configured to behave differently according to different context situations. Contextual information depends on factors such as the particular vehicle that is currently attached to the test application (e

39、.g. the current vehicles model type, the engine type, etc.), on the test application settings (e.g. a setting controlling whether the test sequence shall run in debug mode) or on other factors such as whether the test sequence is running in a manufacturing or a service workshop environment, etc. ISO

40、 13209-2:2012(E) ISO 2012 All rights reserved 3 3.1.7 engineering engineering department department of an automotive OEM which is concerned with the design, development, integration and testing of vehicles of that OEM 3.1.8 expression syntactical construct which describes a specific computation with

41、 a set of arguments and a single return value 3.1.9 identification routine method or software by which a diagnostic application identifies contextual information 3.1.10 manufacturing manufacturing department department of an automotive OEM which is concerned with the production and end-of-line testi

42、ng of vehicles of that OEM 3.1.11 original equipment manufacturer OEM automotive company that engineers, manufactures, sells and services vehicles 3.1.12 OTX Core most generic and stand-alone part of the overall OTX data model which describes the basic structure underlying every OTX document and com

43、prises detailed data model definitions of all required control structures (loops, branches, ) by which test sequence logic is described, but also definitions of the outer, enveloping document structure in which test sequence logic is embedded 3.1.13 OTX Extension OTX Standard Interface Definition ot

44、xIFD set of OTX data type-, action-, term- and signature-definitions that are tailored for a specific area of application and that are defined aside of the OTX Core NOTE OTX Extensions model the data types, actions, terms and signatures needed for communication through diverse interfaces. By using t

45、hese interfaces, calls can be performed to external systems whose internal behaviour does not have to be known to the (client) OTX test sequence/runtime. The system-side interface (server-side) can be proprietary because the adapter design pattern is applied. 3.1.14 procedure signature description o

46、f the interface of an OTX procedure 3.1.15 reference value which refers to data in memory 3.1.16 session instance of test sequence execution 3.1.17 term value described by and computed from an expression ISO 13209-2:2012(E) 4 ISO 2012 All rights reserved 3.1.18 test sequence test procedure defining

47、a full test NOTE A test sequence is a procedure also, but not all procedures are test sequences. In an OTX document, the procedure representing a test sequence shall be named “main“. By using procedures, a test sequence may be split into several procedure modules. An adequately assembled set of freq

48、uently needed procedures may serve as a library which provides procedures that can be called from any other (client) procedure or test sequence. 3.1.19 test procedure procedure stand-alone, parameterisable flow of OTX actions that can be called from other OTX procedures 3.1.20 validity Boolean conte

49、xt variable, global Boolean constant or a named Boolean expression used for activat- ing/deactivating parts of the OTX test sequences according to the current context situation NOTE Parts of OTX test sequences which are marked with a validity name shall be executed only if the associated Boolean expression is true according to the current context situation. 3.1.21 variable identifier of a writable memory location NOTE The term “variable“ is used as a collective term for document scope variables, local variabl