1、 Reference number ISO/TR 25104:2008(E) ISO 2008TECHNICAL REPORT ISO/TR 25104 First edition 2008-02-01 Intelligent transport systems System architecture, taxonomy, terminology and data modelling Training requirements for ITS architecture Systmes intelligents de transport Architecture, taxinomie, term
2、inologie et modlisation de donnes, relatives aux systmes Exigences de formation pour une architecture ITS ISO/TR 25104:2008(E) PDF disclaimer This PDF file may contain embedded typefaces. In accordance with Adobes licensing policy, this file may be printed or viewed but shall not be edited unless th
3、e typefaces which are embedded are licensed to and installed on the computer performing the editing. In downloading this file, parties accept therein the responsibility of not infringing Adobes licensing policy. The ISO Central Secretariat accepts no liability in this area. Adobe is a trademark of A
4、dobe Systems Incorporated. Details of the software products used to create this PDF file can be found in the General Info relative to the file; the PDF-creation parameters were optimized for printing. Every care has been taken to ensure that the file is suitable for use by ISO member bodies. In the
5、unlikely event that a problem relating to it is found, please inform the Central Secretariat at the address given below. COPYRIGHT PROTECTED DOCUMENT ISO 2008 All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized in any form or by any means, elect
6、ronic or mechanical, including photocopying and microfilm, 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.o
7、rg Web www.iso.org Published in Switzerland ii ISO 2008 All rights reservedISO/TR 25104:2008(E) ISO 2008 All rights reserved iii Contents Page Foreword iv Introduction v 1 Scope . 1 2 Normative references . 1 3 Terms and definitions. 1 4 Symbols and abbreviated terms . 2 5 Subjects for education and
8、 training . 3 5.1 Background information 3 5.2 What are “Intelligent Transport Systems”? .3 5.3 “User Needs” and “Fundamental Services” requiring ITS. 3 5.4 Systems architectures for ITS . 4 5.5 Standardization for ITS. 4 5.6 Interoperability is important and achievable . 5 5.7 Systems engineering f
9、or ITS . 5 6 Example curricula for training related to ITS architecture and ITS standards. 5 6.1 Prerequisite training. 5 6.2 Introduction to ITS 5 6.3 ITS technology 6 6.4 ITS theory 6 6.5 Architecture aspects of ITS service provision 7 6.6 Technology aspects of ITS service provision (as they relat
10、e to system architecture) 7 6.7 National and regional architecture development 8 6.8 Strategies to use standards in ITS 8 6.9 The process of standards development for ITS 8 6.10 National standards development organizations (SDO) for ITS 9 6.11 Other organizations relevant to ITS standards 9 6.12 Oth
11、er architecture related issues 9 Bibliography . 10 ISO/TR 25104:2008(E) iv ISO 2008 All rights reservedForeword ISO (the International Organization for Standardization) is a worldwide federation of national standards bodies (ISO member bodies). The work of preparing International Standards is normal
12、ly 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, also take part in the
13、 work. ISO 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 I
14、nternational 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. In exceptional circumstances, when a technical co
15、mmittee has collected data of a different kind from that which is normally published as an International Standard (“state of the art”, for example), it may decide by a simple majority vote of its participating members to publish a Technical Report. A Technical Report is entirely informative in natur
16、e and does not have to be reviewed until the data it provides are considered to be no longer valid or useful. Attention is drawn to the possibility that some of the elements of this document may be the subject of patent rights. ISO shall not be held responsible for identifying any or all such patent
17、 rights. ISO/TR 25104 was prepared by Technical Committee ISO/TC 204, Intelligent transport systems. ISO/TR 25104:2008(E) ISO 2008 All rights reserved v Introduction The objective of this Technical Report is to propose generic training requirements for the skills required to understand and develop a
18、rchitectural models for Intelligent Transport Systems (ITS). This Technical Report has been prepared to assist organizations in developing the knowledge and skills of their own staff and those of allied organizations such a suppliers and customers, and to assist academic institutions to develop curr
19、iculum and syllabus. The approach taken is the proposal of a taxonomy of the knowledge elements of ITS architectural theory and practice. This approach has been widely used in other fields where it is often entitled as the “Body of Knowledge” (BOK), for example the software engineering BOK or SWEBOK
20、. TECHNICAL REPORT ISO/TR 25104:2008(E) ISO 2008 All rights reserved 1 Intelligent transport systems System architecture, taxonomy, terminology and data modelling Training requirements for ITS architecture 1 Scope This Technical Report discusses the development for generic education and training req
21、uirements for the teaching of ITS architecture, and the acquisition of skills to interpret and develop ITS architectures. This Technical Report provides suggestions to those planning education and/or training courses associated with ITS system architecture as to the subjects that should be studied.
22、2 Normative references The following referenced documents are indispensable for the application of this document. For dated references, only the edition cited applies. For undated references, the latest edition of the referenced document (including any amendments) applies. ISO 14813-1, Intelligent t
23、ransport systems Reference model architecture(s) for the ITS sector Part 1: ITS service domains, service groups and services ISO/TR 14813-2, Transport information and control systems Reference model architecture(s) for the TICS sector Part 2: Core TICS reference architecture ISO/IEC 19501, Informati
24、on technology Open Distributed Processing Unified Modeling Language (UML) Version 1.4.2 3 Terms and definitions For the purposes of this document, the following terms and definitions apply. 3.1 architecture set of concepts and rules describing the interrelationship between entities in the entire sys
25、tem, independent of the hardware and software environment, reference 1 and described through a series of views that may be at varying levels of generality/specificity, abstraction/concretion, totality/component and so on 3.2 system architecture (Intelligent transport) framework for ITS deployments N
26、OTE It is a single, high-level description of the major elements or objects and the interconnections amongst them. It provides the framework around which the interfaces, specifications and detailed system designs can be defined. An architecture is not a product design, nor a detailed specification f
27、or physical deployment, reference 1. ISO/TR 25104:2008(E) 2 ISO 2008 All rights reserved3.3 business case structured proposal for business improvement that functions as a decision package for decision-makers The business case should explain why a project is required for the business and what the pro
28、duct or service is going to be. It should include an outline of the “Return on Investment” (ROI), or a cost/benefit analysis for the project, the projects product and performance characteristics, major project risks and the opportunities. The business case addresses, at a high level, the business ne
29、eds that the project seeks to meet. It includes the reasons for the project, the expected business benefits, the options considered (with reasons for rejecting or carrying forward each option), the expected costs of the project, a GAP analysis and the expected risks. 4 Symbols and abbreviated terms
30、AASHTO American Association of State Highway and Transportation Officials ANSI American National Standards Institute APTA American Public Transportation Association APEC Asia Pacific Economic Cooperation ARIB Association of Radio Industries and Businesses (Japan) ARINC Air Radio Incorporated ASTM Am
31、erican Society for Testing and Materials BCA Benefit cost analysis CEN Comit europen de normalisation CEPT Confrence europenne des administrations des postes et des tlcommunications ETSI European Telecommunications Standards Institute EU European Union FCC Federal Communications Commission (USA) GAP
32、 good/average/poor ICT Information and Communications Technology IEC International Electrotechnical Commission IEEE Institute of Electrical and Electronics Engineers IETF Internet Engineering Task Force ITE Institute of Transportation Engineers ITS Intelligent Transport Systems ITU International Tel
33、ecommunications Union ITU-T International Telecommunications Union Telecommunications ITU-R International telecommunications Union Radio NEMA National Electrical Manufacturers Association OASIS Organization for the Advancement of Structured Information Standards ISO/TR 25104:2008(E) ISO 2008 All rig
34、hts reserved 3 OMG Object Management Group ROI Return on Investment SAE Society of Automotive Engineers TE freight and fleet management; activities that expedite the authorization process for cargo at national and jurisdictional boundaries and expedite cross-modal transfers for authorized cargo. ISO
35、/TR 25104:2008(E) 4 ISO 2008 All rights reserved Public transport Operation of public transport services and the provision of operational information to the operator and user, including multimodal aspects. Emergency Services delivered in response to incidents that are categorized as emergencies. Tra
36、nsport-related electronic payment Transactions and reservations for transport-related services. Road transport related personal safety Protection of transport users including pedestrians and vulnerable users. Weather and environmental conditions monitoring Activities that monitor and notify weather
37、and environmental conditions. Disaster response management and coordination Road transport-based activities in response to natural disasters, civil disturbances or terror attacks. National security Activities that directly protect or mitigate physical or operational harm to persons and facilities du
38、e to natural disasters, civil disturbances or terror attacks. ITS data management Collation, management and supply of ITS data to legitimate interested parties. Within these domains, ISO/TR 14813-1 identifies some 123 specific service types, or “fundamental services”. (This list of services is dynam
39、ic and will change over time). Each of the ITS services has associated with it, one or more use cases and actors as shown in ISO/TR 14813-2. 5.4 Systems architectures for ITS In common with all other forms of complex ICT, there is a need for an overall view of the extent and purposes of the systems
40、and networks employed in ITS. This is accomplished by means of so-called systems architecture, comprising the top-level functional and physical system frameworks. These systems architectures can be most easily developed from a generic form, commonly called a reference or framework architecture. A sy
41、stem architecture comprises one or more technology-independent viewpoints that each concentrate on a specific aspect of the future deployment, e.g. logical (functional) viewpoints, physical viewpoints, communications viewpoints, organizational viewpoints. NOTE Early system architectures used to give
42、 the title “architecture” to these viewpoints, which caused a certain amount of confusion. From the geographical point of view, architectures may be defined at regional, national and international levels. The benefit of using an architectural approach is long-term, with potential problems and issues
43、 being able to be identified early in the ITS deployment lifecycle, and hence being much cheaper to resolve than they would be if not identified until later, c.f. the 10:100:1 000 rule for the cost of fixing software faults throughout the software lifecycle. Being technology-independent, an ITS arch
44、itecture can have a long life-time, though it will need to be maintained at regular intervals to ensure that it still covers the services that are required. 5.5 Standardization for ITS Standardization is a natural consequence of using ITS architectures, with the (need for) standards being identified
45、 easily from the various viewpoints, in particular the “communications” viewpoints. ISO/TR 25104:2008(E) ISO 2008 All rights reserved 5 5.6 Interoperability is important and achievable Interoperability has been defined by the ITS standards technical committee (TC204) as follows: The ability of syste
46、ms to provide services to and accept services from other systems and to use the services so exchanged to enable them to operate effectively together. Interoperability is increasingly being recognised as more than attending only to interfaces, embracing: user interfaces, documentation and training of
47、 users, i.e., operators and maintainers; protocol and message compatibility; compatible information models such that related meanings of data structures are consistent; semantic interoperability that ensures that the interpretation of the information that has been defined for compatibility and inter
48、operability is also consistent and predictable to all involved parties. 5.7 Systems engineering for ITS The key to the effective definition of requirements, analysis, design and specification of ITS is a systems engineering process that goes further than the traditional building or project services
49、subcontract. Systems engineering is critical to success and cost-effectiveness of complex systems projects and ITS is no exception to that principle. This is increasingly recognised in such publications as the recently published guidebook from the USDoT 3 . Advice can also be obtained from the “International Council of Systems Engineering” (http:/www.incose.org/). 6 Example curricula for training related to ITS architecture and ITS standards 6.1 Prerequisite trainin
