ISO-TR-14813-5-1999.pdf

上传人:哈尼dd 文档编号:3780806 上传时间:2019-09-23 格式:PDF 页数:15 大小:63.32KB
返回 下载 相关 举报
ISO-TR-14813-5-1999.pdf_第1页
第1页 / 共15页
ISO-TR-14813-5-1999.pdf_第2页
第2页 / 共15页
ISO-TR-14813-5-1999.pdf_第3页
第3页 / 共15页
ISO-TR-14813-5-1999.pdf_第4页
第4页 / 共15页
ISO-TR-14813-5-1999.pdf_第5页
第5页 / 共15页
亲,该文档总共15页,到这儿已超出免费预览范围,如果喜欢就下载吧!
资源描述

《ISO-TR-14813-5-1999.pdf》由会员分享,可在线阅读,更多相关《ISO-TR-14813-5-1999.pdf(15页珍藏版)》请在三一文库上搜索。

1、A Reference number ISO/TR 14813-5:1999(E) TECHNICAL REPORT ISO/TR 14813-5 First edition 1999-07-15 Transport information and control systems Reference model architecture(s) for the TICS sector Part 5: Requirements for architecture description in TICS standards Systmes de commande et dinformation des

2、 transports Architecture(s) de modle de rfrence pour le secteur TICS Partie 5: Exigences pour la description darchitecture dans les normes TICS Copyright International Organization for Standardization Provided by IHS under license with ISO Licensee=NASA Technical Standards 1/9972545001 Not for Resal

3、e, 04/21/2007 09:29:58 MDTNo reproduction or networking permitted without license from IHS -,-,- ISO/TR 14813-5:1999(E) ISO 1999 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

4、 photocopying and microfilm, without permission in writing from the publisher. International Organization for Standardization Case postale 56 CH-1211 Genve 20 Switzerland Internetisoiso.ch Printed in Switzerland ii ContentsPage 1 Scope1 2 Normative references1 3 Terms and definitions .2 3.1 Glossary

5、 of Terms 2 3.2 Glossary of Abbreviations.6 3.2.1 Numerical Notations6 4 Requirements.6 4.1 General Requirements6 4.2 TICS Architecture Elements.7 4.2.1 Conceptual Architecture.7 4.2.2 Logical Architecture7 4.2.3 Physical Architecture8 4.3 Application Architecture/Deployment (Implementation) Design.

6、8 4.4 Layout of Architecture Descriptions in TICS Standards.8 4.5 Further References.9 Annex A (informative) Examples of architecture types10 Copyright International Organization for Standardization Provided by IHS under license with ISO Licensee=NASA Technical Standards 1/9972545001 Not for Resale,

7、 04/21/2007 09:29:58 MDTNo reproduction or networking permitted without license from IHS -,-,- ISO ISO/TR 14813-5:1999(E) iii Foreword ISO (the International Organization for Standardization) is a worldwide federation of national standards bodies (ISO member bodies). The work of preparing Internatio

8、nal Standards is normally carried 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

9、, also take part in the work. ISO collaborates closely with the International Electrotechnical Commission (IEC) on all matters of electrotechnical standardization. The main task of technical committees is to prepare International Standards, but in exceptional circumstances, a technical committee may

10、 propose the publication of a Technical Report of one of the following types: type 1, when the required support cannot be obtained for the publication of an International Standard, despite repeated efforts; type 2, when the subject is still under technical development or where for any other reason t

11、here is the future but not immediate possibility of an agreement on an International Standard; type 3, when a technical committee has collected data of a different kind from that which is normally published as an International Standard (“state of the art“, for example). Technical Reports of types 1

12、and 2 are subject to review within three years of publication, to decide whether they can be transformed into International Standards. Technical Reports of type 3 do not necessarily have to be reviewed until the data they provide are considered to be no longer valid or useful. ISO/TR 14813-5, which

13、is a Technical Report of type 2, was prepared by Technical Committee ISO/TC 204, Transport information and control systems. It is intended that all standards developed for the Road Traffic and Transport Telematics (RTTT)/Transport Information and Control System (TICS) sector conform to these interpr

14、etations of definitions and that all standards for the TICS sector follow the prescribed format in documenting system architecture aspects of their standards. ISO/TR 14813 consists of the following parts, under the general title Transport information and control systems Reference model architecture(

15、s) for the TICS sector: Part 1: TICS fundamental services Part 2: Core reference model Part 3: Example elaboration Part 4: Reference model tutorial Part 5: Requirements for architecture description in TICS standards Part 6: Data presentation in ASN.1 Part 7: TICS data profiles Annex A of this part o

16、f ISO/TR 14813 is for information only. Copyright International Organization for Standardization Provided by IHS under license with ISO Licensee=NASA Technical Standards 1/9972545001 Not for Resale, 04/21/2007 09:29:58 MDTNo reproduction or networking permitted without license from IHS -,-,- ISO/TR

17、14813-5:1999(E) ISO iv Introduction The word “Architecture” has been used in an informal manner to mean a variety of different concepts. This has limited the effective communication in the TICS sector by causing uncertainty as to the meaning of the word “Architecture” when it is used. The purpose of

18、 this part of ISO/TR 14813 is to specify the terminology to be used in describing architectural aspects of TICS standards, and provide a consistent form for TICS architecture description in standards in the TICS sector. In order to maximise the efficiency of co-existing TICS systems, and in order to

19、 obtain compatibility and/or interoperability and to eliminate contention, the systems need to co-exist and operate within a known and supportive architectural framework. In order for such a supportive architectural framework to be developed and for compatibility and interoperability to be obtained,

20、 it is a pre-requisite both to apply the same definition of terminology used, and to describe the requirements for architecture description in TICS standards in a consistent manner. This part of ISO/TR 14813 requires that the architecture aspects of TICS standards are described explicitly in each an

21、d every TICS standard and that all standards are related to the (one or more) TICS Fundamental Service(s) that they are designed to enable or support. Copyright International Organization for Standardization Provided by IHS under license with ISO Licensee=NASA Technical Standards 1/9972545001 Not fo

22、r Resale, 04/21/2007 09:29:58 MDTNo reproduction or networking permitted without license from IHS -,-,- TECHNICAL REPORT ISOISO/TR 14813-5:1999(E) 1 Transport information and control systems Reference model architecture(s) for the TICS sector Part 5: Requirements for architecture description in TICS

23、 standards 1 Scope A TICS architecture is a framework for TICS deployments. It is a high level description of the major elements and the interconnections among them. It provides the framework around which the interfaces, specifications and detailed TICS systems designs can be defined. A TICS Archite

24、cture is not a product design, nor a detailed specification for physical deployment, and it is not specific to any one location. The title Systems Architecture is perhaps the closest general terminology, but that term is sometimes too specific to include the conceptual aspects included in the termin

25、ology TICS Architecture and also often implies a location specific solution. The purpose of a TICS Architecture is to maximise efficiency, interoperability and multimodality of multiple interacting TICS systems in a complex and developing sector. This part of ISO/TR 14813 defines a) Terminology to b

26、e used when documenting or referencing aspects of architecture description in TICS standards. b) The form in which aspects of System Architecture are to be documented and described in TICS standards. In compiling this part of ISO/TR 14813, the authors have assumed that contemporary systems engineeri

27、ng practices are used. Such practices are not defined within this part of ISO/TR 14813. 2 Normative references The following normative documents contain provisions which, through reference in this text, constitute provisions of this part of ISO/TR 14813. For dated references, subsequent amendments t

28、o, or revisions of, any of these publications do not apply. However, parties to agreements based on this part of ISO/TR 14813 are encouraged to investigate the possibility of applying the most recent editions of the normative documents indicated below. For undated references, the latest edition of t

29、he normative document referred to applies. Members of ISO and IEC maintain registers of currently valid International Standards. ISO/TR 14813-1, Transport information and control systems Reference model architecture(s) for the TICS sector Part 1: TICS fundamental services. ISO/TR 14813-6, Transport

30、information and control systems Reference model architecture(s) for the TICS sector Part 6: Data presentation in ASN.1. ISO/IEC 8824-1:1995, Information technology Abstract Syntax Notation (ASN.1): Specification of basic notation. ISO/IEC 8824-1:1995/Amd.1:1996, Information technology Abstract Synta

31、x Notation (ASN.1): Specification of basic notation, Amendment 1: Rules of extensibility. ISO/IEC 8824-2:1995, Information technology Abstract Syntax Notation (ASN.1): Information object specification. Copyright International Organization for Standardization Provided by IHS under license with ISO Li

32、censee=NASA Technical Standards 1/9972545001 Not for Resale, 04/21/2007 09:29:58 MDTNo reproduction or networking permitted without license from IHS -,-,- ISO/TR 14813-5:1999(E) ISO 2 ISO/IEC 8824-2:1995/Amd.1:1996, Information technology Abstract Syntax Notation (ASN.1): Information object specific

33、ation, Amendment 1: Rules of extensibility. ISO/IEC 8824-3:1995, Information technology Abstract Syntax Notation (ASN.1): Constraint specification. ISO/IEC 8824-4:1995, Information technology Abstract Syntax Notation (ASN.1): Parameterization of ASN.1 specifications. ISO/IEC 8825-1:1995, Information

34、 technology ASN.1 encoding rules: Specification of Basic Encoding Rules (BER), Canonical Encoding Rules (CER) and Distinguished Encoding Rules (DER). ISO/IEC 8825-2:1996, Information technology ASN.1 encoding rules: Specification of Packed Encoding Rules (PER). 3 Terms and definitions For the purpos

35、es of this part of ISO/TR 14813, the following terms and definitions apply. 3.1 Glossary of Terms This Glossary of Terms shall be used in TICS standards where architectures are described or TICS architecture aspects are referred to. 3.1.1 Application Architecture a set of functions combined to form

36、a high level system design 3.1.2 Architecture Element a definable element of a system, which forms part of a component or system, but does not necessarily have independent operational functionality 3.1.3 ASN.1 Abstract Syntax Notation Number One, as defined in ISO/IEC 8824 3.1.4 Basic Encoding Rules

37、 a standardised determination of data encoding to conform to the requirements of ISO/IEC 8824 ASN.1 (Abstract Syntax Notation One) NOTE The Basic Encoding Rules (BER) are defined in ISO/IEC 8825. Note that there are alternate forms of encodation such as Packed Encoding Rules (PER) (see Packed Encodi

38、ng Rules). 3.1.5 Class a class is a descriptor of a set of objects with similar structure, behaviour and relationships 3.1.6 Compatibility the ability of any (sub)system to interact with another (sub)system according to a set of predefined rules in the form of interface specification and protocol de

39、finition 3.1.7 Conceptual Architecture an overall description of a system incorporating operational concepts and user requirements, together with its known inter-relationships with other systems Copyright International Organization for Standardization Provided by IHS under license with ISO Licensee=

40、NASA Technical Standards 1/9972545001 Not for Resale, 04/21/2007 09:29:58 MDTNo reproduction or networking permitted without license from IHS -,-,- ISO ISO/TR 14813-5:1999(E) 3 NOTE Normally expressed/supported by means of vision/mission statements, a simple hierarchy chart or network diagram (e.g.

41、reference model) dealing with only the overall concepts and relationships and reference points. A Conceptual Architecture is not specific to any location. 3.1.8 Control Architecture describes the control behaviour of TICS Architecture elements to effect change from one state (condition) to another (

42、state transition management) NOTE A Control Architecture is not specific to any location. 3.1.9 Data Construct a group of one or more data elements (primitive or constructed as defined in ISO 8825) used to represent state or information 3.1.10 Deployment Design Implementation Design the specific des

43、ign for a deployment describes the actual equipment to achieve the application architecture NOTE The Deployment Design is not considered appropriate for Standardisation. The Deployment (Implementation) Design is sometimes incorrectly referred to as a Physical Architecture. However, the Deployment (A

44、pplication) Design is specific in location and often also in time, whereas a TICS Architecture is not. 3.1.11 Deployment of TICS the actual TICS equipment, software, facilities, devices etc. at a specific location and at a specific time 3.1.12 Design the way that parts or constituents are related to

45、 an organised whole (Webster) 3.1.13 Electronic Data Interchange (EDI) the passing of a data message, or series of messages, between computers and/or between different software systems (e.g. EDIFACT) 3.1.14 Electronic Data Transfer (EDT) the passing of data sets comprising an entire message from one

46、 computer to another or from one software system to another 3.1.15 Functional Architecture a Functional Architecture is an aspect of a Logical, Process Oriented decomposition of an overall TICS Architecture (see Process Oriented Logical Architecture) NOTE A Functional Architecture is not specific to

47、 any location. 3.1.16 Information Architecture with respect to process oriented decomposition, the Information Architecture defines the entities and the relationships of information (Data model) and the principal data constructs (see Process Oriented and Logical Architecture) NOTE The Information Ar

48、chitecture is not specific to any location. Copyright International Organization for Standardization Provided by IHS under license with ISO Licensee=NASA Technical Standards 1/9972545001 Not for Resale, 04/21/2007 09:29:58 MDTNo reproduction or networking permitted without license from IHS -,-,- ISO/TR 14813-5:1999(E) ISO 4 3.1.17 Institutional Architecture an architecture based on political or administrational infrastructure partitioning and its division of responsibilities (rather than fun

展开阅读全文
相关资源
猜你喜欢
相关搜索

当前位置:首页 > 其他


经营许可证编号:宁ICP备18001539号-1