1、 INCITS/ISO/IEC TR 30102:2012 2015 (ISO/IEC TR 30102:2012, IDT) Information technology - Distributed Application Platforms and Services (DAPS) - General technical principles of Service Oriented Architecture (Technical Report) INCITS/ISO/IEC TR 30102:2012 2015 PDF disclaimer This PDF file may contain
2、 embedded typefaces. In accordance with Adobes licensing policy, this file may be printed or viewed but shall not be edited unless the typefaces which are embedded are licensed to and installed on the computer performing the editing. In downloading this file, parties accept therein the responsibilit
3、y of not infringing Adobes licensing policy. The ISO Central Secretariat accepts no liability in this area. Adobe is a trademark of Adobe 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 parame
4、ters were optimized for printing. Every care has been taken to ensure that the file is suitable for use by ISO member bodies. In the unlikely event that a problem relating to it is found, please inform the Central Secretariat at the address given below. Registered by INCITS (InterNational Committee
5、for Information Technology Standards) as an American National Standard. Date of Registration: 4/26/2015 Published by American National Standards Institute, 25 West 43rd Street, New York, New York 10036 Copyright 2015 by Information Technology Industry Council (ITI). All rights reserved. These materi
6、als are subject to copyright claims of International Standardization Organization (ISO), International Electrotechnical Commission (IEC), American National Standards Institute (ANSI), and Information Technology Industry Council (ITI). Not for resale. No part of this publication may be reproduced in
7、any form, including an electronic retrieval system, without the prior written permission of ITI. All requests pertaining to this standard should be submitted to ITI, 1101 K Street NW, Suite 610, Washington DC 20005. Printed in the United States of America ii ITIC 2015 All rights reserved Reference n
8、umberISO/IEC TR 30102:2012(E)ISO/IEC 2012TECHNICAL REPORT ISO/IECTR30102First edition2012-12-01Information technology Distributed Application Platforms and Services (DAPS) General technical principles of Service Oriented Architecture Technologie de linformation Plate-formes et services dapplications
9、 distribues (DAPS) Principes techniques gnraux de larchitecture oriente services ISO/IEC TR 30102:2012(E) COPYRIGHT PROTECTED DOCUMENT ISO/IEC 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 me
10、chanical, 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.org Web www.
11、iso.org Published in Switzerland ii ISO/IEC 2012 All rights reservedISO/IEC TR 30102:2012(E) ISO/IEC 2012 All rights reserved iiiContents Page Foreword . v Introduction vi 1 Scope 1 2 Terms and definitions . 1 2.1 Definitions 1 2.2 Acronyms . 8 3 SOA Principles and Concepts 8 3.1 Introduction to SOA
12、 8 3.2 Concepts 9 3.2.1 Roles . 9 3.2.2 Services 10 3.2.3 Semantics . 11 3.2.4 Compositions and Processes 11 3.2.5 Service Registration and Discovery 13 3.2.6 Service Description, Interfaces, Contracts and Policies . 14 1.1.1 Service Lifecycle . 16 3.2.7 SOA Lifecycle 16 3.2.8 Tasks and Activities 1
13、7 3.3 Architectural Principles 17 3.3.1 Architectural Principles defined 17 3.3.2 Interoperable syntactic, semantic 18 3.3.3 Described . 18 3.3.4 Reusable . 19 3.3.5 Discoverable 20 3.3.6 Composable . 21 3.3.7 Self-Contained . 21 3.3.8 Loosely coupled 21 1.1.2 Manageable 22 3.4 Cross Cutting Aspects
14、 23 3.4.1 Integration 23 3.4.2 Management and Security 25 3.4.3 SOA Governance . 30 4 SOA Technical Framework . 32 4.1 Introduction to the SOA Technical Framework 32 4.2 Reference Architecture for SOA Solutions . 33 4.2.1 Operational and IT Systems Layer 34 4.2.2 Service Components Layer 35 4.2.3 Se
15、rvices Layer . 36 4.2.4 Process Layer 36 4.2.5 Consumer Interface Layer 37 4.2.6 Integration Layer . 38 4.2.7 Management and Security Layer . 38 4.2.8 Information Layer 40 4.2.9 Governance Layer . 40 4.2.10 Development Layer . 41 4.3 Common Services Categories . 42 4.3.1 Common Services Categories O
16、verview 42 4.3.2 Mediation Services 43 4.3.3 Interaction Services 43 4.3.4 Process Services . 43 ISO/IEC TR 30102:2012(E) iv ISO/IEC 2012 All rights reserved4.3.5 Information Services .43 4.3.6 Access Services .44 4.3.7 Security Services .44 4.3.8 Partner Services .45 4.3.9 Lifecycle Service 45 4.3.
17、10 Asset and Registry Services 45 4.3.11 Infrastructure Services 45 4.3.12 Management Services .45 4.3.13 Development Services 46 4.3.14 Strategy and Planning Services .46 4.3.15 Business Application Services 46 4.3.16 Business Services .46 4.3.17 Considering Implementations of Common Service Catego
18、ries using Reference Architecture 46 Annex A (informative) The Open Group SOA Reference Architecture 49 Annex B (informative) The OASIS SOA Reference Model and Reference Architecture 52 Annex C (informative) OMG SOA / Modeling Language 53 Annex D (informative) Chinas Technical Reference Architecture
19、 for SOA Solutions 54 Annex E (informative) SC 32 SOA Registry Metamodel 59 Annex F (informative) SOA Related Function - Japanese Technical Reference Model (TRM) for the Government Procurement of Information Systems .60 Bibliography 72 ISO/IEC TR 30102:2012(E) ISO/IEC 2012 All rights reserved vForew
20、ord ISO (the International Organization for Standardization) and IEC (the International Electrotechnical Commission) form the specialized system for worldwide standardization. National bodies that are members of ISO or IEC participate in the development of International Standards through technical c
21、ommittees established by the respective organization to deal with particular fields of technical activity. ISO and IEC technical committees collaborate in fields of mutual interest. Other international organizations, governmental and non-governmental, in liaison with ISO and IEC, also take part in t
22、he work. In the field of information technology, ISO and IEC have established a joint technical committee, ISO/IEC JTC 1. International Standards are drafted in accordance with the rules given in the ISO/IEC Directives, Part 2. The main task of the joint technical committee is to prepare Internation
23、al Standards. Draft International Standards adopted by the joint technical committee are circulated to national bodies for voting. Publication as an International Standard requires approval by at least 75 % of the national bodies casting a vote. In exceptional circumstances, when the joint technical
24、 committee 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 to publish a Technical Report. A Technical Report is entirely informative in nature and shall be subject to review every five years in
25、 the same manner as an International Standard. Attention is drawn to the possibility that some of the elements of this Technical Report may be the subject of patent rights. ISO shall not be held responsible for identifying any or all such patent rights. ISO/IEC TR 30102 was prepared by Joint Technic
26、al Committee ISO/IEC JTC 1, Information technology, Subcommittee SC 38, Distributed application platforms and services (DAPS). ISO/IEC TR 30102:2012(E) vi ISO/IEC 2012 All rights reservedIntroduction Service Oriented Architecture (abbreviated SOA) is an architectural style that supports service orie
27、ntation and is a paradigm for business and IT (see 3.1.40). This architectural style is for designing systems in terms of services available at an interface and the outcomes of services. A service is a logical representation of a repeatable business activity that has specified outcomes, is self cont
28、ained, may be composed of other services and is a “black box” to consumers of the service (see 3.1.14). To enable this co-operation and collaboration business-oriented SOA takes service as its basic element to constitute and integrate information systems so that they are suitable for a wider variety
29、 of application requirements. Some of the benefits of using SOA are improvement in the efficiency of development of information systems, efficiency of integration and efficiency of re-use of IT resources. It also enables agile and rapid response of information systems to ever-changing business needs
30、. Many companies across many industries world-wide have developed SOA enterprise architectures, solutions and products. This report is intended to be a single set of SOA technical principles, specific norms, and standards for the world-wide market to help remove confusion about SOA, improve the stan
31、dardization and quality of solutions, as well as promote effective large-scale adoption of SOA. The benefits of this technical report contribute to improving the standardization, interoperability, and quality of solutions supporting SOA. This technical report defines the basic technical principles a
32、nd reference architecture for SOA rather than being focused on the business aspects. It also discusses the functional, performance, development, deployment, and governance aspects of SOA. This technical report can be used to introduce SOA concepts, as a guide to the development and management of SOA
33、 solutions, as well as be referenced by business and industry standards. This technical report includes the following clauses: Clause 3 terminology defines terms used when discussing or designing service oriented solutions. Terms defined here are used in some unique fashion for SOA. It does not defi
34、ne terms that are used in general English manner. Clause 4 Concepts and Principles articulates basic SOA concepts and expands on the key terms in clause 3. Clause 5 SOA Technical Framework documents an overview of a reference architecture for building SOA based solutions. The targeted audience of th
35、is technical report includes, but is not limited to, standards organizations, architects, SOA service providers, SOA solution and service developers, and SOA service consumers who are interested in adopting and developing SOA. TECHNICAL REPORT ISO/IEC TR 30102:2012(E) ISO/IEC 2012 All rights reserve
36、d 1Information technology Distributed Application Platforms and Services (DAPS) General technical principles of Service Oriented Architecture 1 Scope This Technical Report describes the general technical principles underlying Service Oriented Architecture (SOA), including principles relating to func
37、tional design, performance, development, deployment and management. It provides a vocabulary containing definitions of terms relevant to SOA. It includes a domain-independent technical framework, addressing functional requirements and non-functional requirements. 2 Terms and definitions For the purp
38、oses of this document, the following terms and definitions apply 2.1 Definitions 2.1.1 actor person or system component who interacts with the system as a whole and who provides stimulus which invoke actions NOTE See ISO/IEC 16500-8:1999, 3.1. 2.1.2 architecture fundamental concepts or properties of
39、 a system in its environment embodied in its elements, relationships, and in the principles of its design and evolution ISO/IEC/IEEE 42010:2011, 3.2). ISO/IEC 40210:2011 2.1.3 choreography omposition whose elements interact in a non-directed fashion with each autonomous member knowing and following
40、an observable predefined pattern of behavior for the entire (global) composition NOTE See Bibliography Reference 21. 2.1.4 collaboration omposition whose elements interact in a non-directed fashion, each according to their own plans and purposes without a predefined pattern of behavior NOTE See Bibl
41、iography Reference 21. 2.1.5 composition result of assembling a collection of things for a particular purpose ISO/IEC TR 30102:2012(E) 2 ISO/IEC 2012 All rights reservedNOTE See Bibliography Reference 21. 2.1.6 effect outcome of an interaction with a service NOTE 1 If service contracts exist, they u
42、sually define effects. The effect is how a service, through the element that performs it, delivers value to its consumer. NOTE 2 See Bibliography Reference 21. 2.1.7 element unit that is indivisible at a given level of abstraction,and has a clearly defined boundary NOTE 1 An Element can be any type
43、of entity. NOTE 2 See Bibliography Reference 21. 2.1.8 entity individual in a service system with an identity which can act as a service provider or consumer NOTE Examples of entities are organizations, enterprises and individuals, software and hardware. 2.1.9 event something that occurs,to which an
44、 element may choose to respond NOTE Events can be responded to by any element and events may be generated (emitted) by any element. 2.1.10 execution context set of technical and business elements that form a path between those with needs and those with capabilities and that permit service providers
45、and consumers to interact NOTE 1 The execution context of a service interaction is the set of infrastructure elements, process entities, policy assertions and agreements that are identified as part of an instantiated service interaction, and thus forms a path between those with needs and those with
46、capabilities. NOTE 2 See Bibliography Reference 19. 2.1.11 human actor person or an organizational entity NOTE 1 In principle, this classification is not exhaustive. NOTE 2 See Bibliography Reference 21. 2.1.12 human tasks tasks which are done by people or organizations, specifically instances of Hu
47、man Actor 2.1.13 information Type type of information given or received in a service interface 2.1.14 orchestration composition for which there is one particular element used by the composition that oversees and directs the other elements ISO/IEC TR 30102:2012(E) ISO/IEC 2012 All rights reserved 3NO
48、TE 1 The element that directs an orchestration by definition is different than the orchestration (Composition instance) itself. NOTE 2 See Bibliography Reference 21. 2.1.15 process composition whose elements are composed into a sequence or flow of activities and interactions with the objective of ca
49、rrying out certain work NOTE 1 A process may also be a collaboration, choreography, or orchestration. NOTE 2 See Bibliography Reference 21. 2.1.16 REST architectural style for distributed hypermedia systems. REST provides a set of architectural constraints that, when applied as a whole, emphasizes scalability of component interactions, generality of interfaces, independent deployment of components, and intermed
