1、BS ISO/IEC 18384-1:2016Information technology Reference Architecture forService Oriented Architecture(SOA RA)Part 1: Terminology and concepts for SOABSI Standards PublicationWB11885_BSI_StandardCovs_2013_AW.indd 1 15/05/2013 15:06BS ISO/IEC 18384-1:2016 BRITISH STANDARDNational forewordThis British
2、Standard is the UK implementation of ISO/IEC18384-1:2016.The UK participation in its preparation was entrusted to TechnicalCommittee IST/38, Cloud Computing and Distributed Platforms.A list of organizations represented on this committee can beobtained on request to its secretary.This publication doe
3、s not purport to include all the necessaryprovisions of a contract. Users are responsible for its correctapplication. The British Standards Institution 2016.Published by BSI Standards Limited 2016ISBN 978 0 580 81293 4ICS 35.100.05Compliance with a British Standard cannot confer immunity fromlegal o
4、bligations.This British Standard was published under the authority of theStandards Policy and Strategy Committee on 30 June 2016.Amendments/corrigenda issued since publicationDate T e x t a f f e c t e dBS ISO/IEC 18384-1:2016Information technology Reference Architecture for Service Oriented Archite
5、cture (SOA RA) Part 1: Terminology and concepts for SOATechnologie de linformation Architecture de rfrence pour larchitecture oriente service (SOA RA) Partie 1: Terminologie et concepts pour SOAINTERNATIONAL STANDARDISO/IEC18384-1Reference numberISO/IEC 18384-1:2016(E)First edition2016-06-01 ISO/IEC
6、 2016BS ISO/IEC 18384-1:2016ii ISO/IEC 2016 All rights reservedCOPYRIGHT PROTECTED DOCUMENT ISO/IEC 2016, Published in SwitzerlandAll rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized otherwise in any form or by any means, electronic or mechanical
7、, including photocopying, or posting on the internet or an intranet, without prior written permission. Permission can be requested from either ISO at the address below or ISOs member body in the country of the requester.ISO copyright officeCh. de Blandonnet 8 CP 401CH-1214 Vernier, Geneva, Switzerla
8、ndTel. +41 22 749 01 11Fax +41 22 749 09 47copyrightiso.orgwww.iso.orgISO/IEC 18384-1:2016(E)BS ISO/IEC 18384-1:2016ISO/IEC 18384-1:2016(E)Foreword ivIntroduction v1 Scope . 12 Terms and definitions . 13 Abbreviated terms 84 Notations. 94.1 General . 94.2 UML . 94.3 Entity Relationship 94.4 Cycles .
9、 94.5 Flows 95 Conventions 106 Conformance 107 SOA Concepts .107.1 Introduction to SOA . 107.2 Concepts 117.2.1 Roles 117.2.2 Services . 147.2.3 Semantics 157.2.4 Tasks and Activities 157.2.5 Compositions and Processes 157.2.6 Service Registration and Discovery 187.2.7 Service Description, Interface
10、s, Policies and Contracts 197.2.8 Service and SOA solution lifecycle .237.2.9 Loosely coupled .277.3 Cross Cutting Concerns . 277.3.1 Defining Cross Cutting .277.3.2 Integration 277.3.3 Cross Domain interaction 277.3.4 Service Integration 287.3.5 Management and Security 297.3.6 SOA Solution Governan
11、ce 328 SOA Architectural Principles .338.1 Architectural Principles defined . 338.2 Interoperable Syntactic, semantic 338.3 Described 348.4 Reusable . 358.5 Discoverable . 368.6 Late Bind-able . 378.7 Composable 378.8 Self-Contained 388.9 Loosely coupled . 388.10 Manageable . 39Annex A (informative)
12、 SOA Governance Framework 40Annex B (informative) Management and Security Concerns 44Bibliography .50 ISO/IEC 2016 All rights reserved iiiContents PageBS ISO/IEC 18384-1:2016ISO/IEC 18384-1:2016(E)ForewordISO (the International Organization for Standardization) and IEC (the International Electrotech
13、nical 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 committees established by the respective organization to deal with particular fields of technical ac
14、tivity. 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 the work. In the field of information technology, ISO and IEC have established a joint technical com
15、mittee, ISO/IEC JTC 1.The procedures used to develop this document and those intended for its further maintenance are described in the ISO/IEC Directives, Part 1. In particular the different approval criteria needed for the different types of document should be noted. This document was drafted in ac
16、cordance with the editorial rules of the ISO/IEC Directives, Part 2 (see www.iso.org/directives). Attention is drawn to the possibility that some of the elements of this document may be the subject of patent rights. ISO and IEC shall not be held responsible for identifying any or all such patent rig
17、hts. Details of any patent rights identified during the development of the document will be in the Introduction and/or on the ISO list of patent declarations received (see www.iso.org/patents). Any trade name used in this document is information given for the convenience of users and does not consti
18、tute an endorsement.For an explanation on the meaning of ISO specific terms and expressions related to conformity assessment, as well as information about ISOs adherence to the WTO principles in the Technical Barriers to Trade (TBT) see the following URL: Foreword - Supplementary informationThe comm
19、ittee responsible for this document is ISO/IEC JTC 1, Information technology, Subcommittee SC 38, Cloud Computing and Distributed Platforms.ISO/IEC 18384 consists of the following parts, under the general title Reference Architecture for Service Oriented Architecture (SOA RA): Part 1: Terminology an
20、d Concepts for SOA Part 2: Reference Architecture for SOA Solutions Part 3: Service Oriented Architecture Ontologyiv ISO/IEC 2016 All rights reservedBS ISO/IEC 18384-1:2016ISO/IEC 18384-1:2016(E)IntroductionService oriented architecture (SOA) is an architectural style in which business and IT system
21、s are designed in terms of services available at an interface and the outcomes of these services. A service is a logical representation of a set of activities that has specified outcomes, is self-contained, and it may be composed of other services but consumers of the service need not be aware of an
22、y internal structure.SOA takes “service” as its basic element to constitute and integrate information systems so that they are suitable for a variety of solution requirements. SOA enables interactions between businesses without needing to specify aspects of any particular business domain. Using the
23、SOA architectural style can improve the efficiency of developing information systems, and integrating and reusing IT resources. In addition, using the SOA architectural style can help realize agile and rapid response of information systems to ever-changing business needs.This International Standard
24、describes a single set of SOA technical principles, specific norms, and standards for the world-wide market to help remove confusion about SOA and improve the standardization and quality of solutions.This International Standard defines the terminology, technical principles, reference architecture, a
25、nd the ontology for SOA. The targeted audience of this International Standard includes, but is not limited to, standards organizations, architects, architecture methodologists, system and software designers, business people, SOA service providers, SOA solution and service developers, and SOA service
26、 consumers who are interested in adopting and developing SOA. For example, this part of ISO/IEC 18384 can be used to introduce SOA concepts and to guide to the developing and managing SOA solutions.This International Standard contains three parts:a) ISO/IEC 18384-1 which defines the terminology, bas
27、ic technical principles and concepts for SOA;b) ISO/IEC 18384-2 which defines the detailed SOA reference architecture layers, including a metamodel, capabilities, architectural building blocks, as well as types of services in SOA solutions;c) ISO/IEC 18384-3 which defines the core concepts of SOA an
28、d their relationships in the Ontology.Users of this part of ISO/IEC 18384 will find it useful to read this part of ISO/IEC 18384 for an understanding of SOA basics. This part of ISO/IEC 18384 should be read before reading or applying ISO/IEC 18384-2. For those new to SOA, ISO/IEC 18384-2:2016, Claus
29、e 4 provides a high level understanding of the reference architecture for SOA solutions. The remaining clauses provide comprehensive details of the architectural building blocks and trade-offs needed for a SOA solution. ISO/IEC 18384-3 contains the SOA Ontology, which is a formalism of the core conc
30、epts and terminology of SOA, with mappings to both UML and OWL. The SOA Ontology can be used independent of or in conjunction with ISO/IEC 18384-1 and ISO/IEC 18384-2.This part of ISO/IEC 18384 presents and explains basic SOA concepts. It gives definitions for terms that are used in ISO/IEC 18384 wi
31、th specific meanings that may differ or be more precise than the definitions of those terms found in major English language dictionaries. The terms defined here are used in a unique fashion for SOA. Terms used in their normal English sense are not redefined. ISO/IEC 2016 All rights reserved vBS ISO/
32、IEC 18384-1:2016BS ISO/IEC 18384-1:2016Information technology Reference Architecture for Service Oriented Architecture (SOA RA) Part 1: Terminology and concepts for SOA1 ScopeThis part of ISO/IEC 18384 establishes vocabulary, guidelines, and general technical principles underlying service oriented a
33、rchitecture (SOA), including principles relating to functional design, performance, development, deployment, and management.2 Terms and definitionsFor the purposes of this document, the following terms and definitions apply.2.1actorperson or system component that interacts with the system as a whole
34、 and that provides stimulus which invokes actionsSOURCE: ISO/IEC 16500-8:1999, 3.12.2architecturefundamental concepts or properties of a system in its environment embodied in its elements, relationships, and in the principles of its design and evolutionSOURCE: ISO/IEC/IEEE 42010:2011, 3.22.3choreogr
35、aphytype of composition (2.5) whose elements (2.8) interact in a non-directed fashion with each autonomous part knowing and following an observable predefined pattern of behaviour for the entire (global) compositionNote 1 to entry: Choreography does not require complete or perfect knowledge of the p
36、attern of behaviour.Note 2 to entry: See ISO/IEC 18384-3:2016, 8.3.2.4collaborationtype of composition (2.5) whose elements (2.8) interact in a non-directed fashion, each according to their own plans and purposes without a predefined pattern of behaviourNote 1 to entry: See ISO/IEC 18384-3:2016, 8.3
37、.2.5compositionresult of assembling a collection of elements (2.8) for a particular purposeNote 1 to entry: See ISO/IEC 18384-3:2016, 8.2.INTERNATIONAL STANDARD ISO/IEC 18384-1:2016(E) ISO/IEC 2016 All rights reserved 1BS ISO/IEC 18384-1:2016ISO/IEC 18384-1:2016(E)2.6endpointlocation at which inform
38、ation is received to invoke and configure interaction2.7effectoutcome of an interaction with a service (2.20)Note 1 to entry: The effect is how a service delivers results to its consumer, through the element (2.8) that performs it. Note 2 to entry: See ISO/IEC 18384-3:2016, 7.10.2.8elementunit at a
39、given level of abstraction and with a clearly defined boundaryNote 1 to entry: An element can be any type of entity (2.9).Note 2 to entry: See ISO/IEC 18384-3:2016, 5.1.2.9entityindividual element (2.8) in a system with an identity which can act as a service provider (2.50) or service consumer (2.29
40、)Note 1 to entry: Examples of entities are organizations, enterprises and individuals, software, and hardware.2.10eventsomething that occurs to which an element (2.8) may choose to respondNote 1 to entry: Any element can generate (emit) or respond to an event.Note 2 to entry: See ISO/IEC 18384-3:201
41、6, Clause 10.2.11execution contextset of technical and business elements (2.8) needed by those with needs and capabilities to permit service providers (2.50) and service consumers (2.29) instantiation and communicationNote 1 to entry: The execution context of a service interaction (2.37) is the set
42、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 capabilities.Note 2 to entry: See Reference 8.2.12human actoractor (2.1) restricted to a p
43、erson or an organizational entity (2.9)Note 1 to entry: This classification is not exhaustive.Note 2 to entry: See ISO/IEC 18384-3:2016, 6.2.2.13human tasktask (2.60) which is done by a human actor (2.12)2 ISO/IEC 2016 All rights reservedBS ISO/IEC 18384-1:2016ISO/IEC 18384-1:2016(E)2.14interfacesha
44、red boundary between two functional units, defined by various characteristics pertaining to the functions, physical interconnections, signal exchanges, and other characteristics, as appropriateSOURCE: ISO/IEC 2382:2015, 21213082.15loose couplingprinciple where dependencies between elements (2.8) of
45、a SOA solution (2.56) are intentionally reduced2.16orchestrationtype of composition (2.5) where one particular element (2.8) is used by the composition to oversee and direct the other elementsNote 1 to entry: The element that directs an orchestration is not part of the orchestration (Composition ins
46、tance) itself.Note 2 to entry: See ISO/IEC 18384-3:2016, 8.3.2.17policystatement that an entity (2.9) intends to follow or intends that another entity should followNote 1 to entry: See ISO/IEC 18384-3:2016, Clause 9).2.18processtype of composition (2.5) whose elements (2.8) are composed into a seque
47、nce or flow of activities and interactions with the objective of carrying out certain workNote 1 to entry: A process may also be a collaboration (2.4), choreography (2.3), or orchestration (2.16).Note 2 to entry: See ISO/IEC 18384-3:2016, 8.6.2.19real-world effectchange relevant to and experienced b
48、y specific stakeholdersNote 1 to entry: See Reference 8.2.20servicelogical representation of a set of activities that has specified outcomes, is self-contained, may be composed of other services, and is a “black box” to consumers of the serviceNote 1 to entry: The word “activity” in the “service” de
49、finition is used in the general English language sense of the word, not in the process-specific sense of that same word i.e. activities are not necessarily process (2.18) activities.Note 2 to entry: See ISO/IEC 18384-3:2016, 7.2.2.21service brokerelement (2.8) that enables the communication with services (2.20), either at a business level or at the implementation level, i.e. with intermediariesNote 1 to entry: The intermediaries provide any number of functions, such as unified service registration (2.51) and publishing, service di
