BS ISO IEC 18384-1-2016 Information technology Reference Architecture for Service Oriented Architecture (SOA RA) Terminology and concepts for SOA《信息技术 面向服务架构用参考架构 (SOA RA).pdf

1、BS ISO/IEC 18384-1:2016 Information technology Reference Architecture for Service Oriented Architecture (SOA RA) Part 1: Terminology and concepts for SOA BSI Standards Publication WB11885_BSI_StandardCovs_2013_AW.indd 1 15/05/2013 15:06BS ISO/IEC 18384-1:2016 BRITISH STANDARD National foreword This

2、British Standard is the UK implementation of ISO/IEC 18384-1:2016. The UK participation in its preparation was entrusted to Technical Committee IST/38, Cloud Computing and Distributed Platforms. A list of organizations represented on this committee can be obtained on request to its secretary. This p

3、ublication does not purport to include all the necessary provisions of a contract. Users are responsible for its correct application. The British Standards Institution 2016. Published by BSI Standards Limited 2016 ISBN 978 0 580 81293 4 ICS 35.100.05 Compliance with a British Standard cannot confer

4、immunity from legal obligations. This British Standard was published under the authority of the Standards Policy and Strategy Committee on 30 June 2016. Amendments/corrigenda issued since publication Date T e x t a f f e c t e dBS ISO/IEC 18384-1:2016 Information technology Reference Architecture fo

5、r Service Oriented Architecture (SOA RA) Part 1: Terminology and concepts for SOA Technologie de linformation Architecture de rfrence pour larchitecture oriente service (SOA RA) Partie 1: Terminologie et concepts pour SOA INTERNATIONAL STANDARD ISO/IEC 18384-1 Reference number ISO/IEC 18384-1:2016(E

6、) First edition 2016-06-01 ISO/IEC 2016 BS ISO/IEC 18384-1:2016ii ISO/IEC 2016 All rights reserved COPYRIGHT PROTECTED DOCUMENT ISO/IEC 2016, Published in Switzerland All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized otherwise in any form or b

7、y any means, electronic or mechanical, 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 office Ch. de Blandonnet 8 C

8、P 401 CH-1214 Vernier, Geneva, Switzerland Tel. +41 22 749 01 11 Fax +41 22 749 09 47 copyrightiso.org www.iso.org ISO/IEC 18384-1:2016(E)BS ISO/IEC 18384-1:2016ISO/IEC 18384-1:2016(E)Foreword iv Introduction v 1 Scope . 1 2 T erms and definitions . 1 3 Abbreviated terms 8 4 Notations. 9 4.1 General

9、 . 9 4.2 UML . 9 4.3 Entity Relationship 9 4.4 Cycles . 9 4.5 Flows 9 5 Conventions 10 6 Conformance 10 7 SOA Concepts .10 7.1 Introduction to SOA .10 7.2 Concepts 11 7.2.1 Roles 11 7.2.2 Services .14 7.2.3 Semantics 15 7.2.4 Tasks and Activities 15 7.2.5 Compositions and Processes 15 7.2.6 Service

10、Registration and Discovery 18 7.2.7 Service Description, Interfaces, Policies and Contracts 19 7.2.8 Service and SOA solution lifecycle .23 7.2.9 Loosely coupled .27 7.3 Cross Cutting Concerns .27 7.3.1 Defining Cross Cutting .27 7.3.2 Integration 27 7.3.3 Cross Domain interaction 27 7.3.4 Service I

11、ntegration 28 7.3.5 Management and Security 29 7.3.6 SOA Solution Governance 32 8 SOA Architectural Principles .33 8.1 Architectural Principles defined .33 8.2 Interoperable Syntactic, semantic 33 8.3 Described 34 8.4 Reusable .35 8.5 Discoverable .36 8.6 Late Bind-able .37 8.7 Composable 37 8.8 Sel

12、f-Contained 38 8.9 Loosely coupled .38 8.10 Manageable .39 Annex A (informative) SOA Governance Framework 40 Annex B (informative) Management and Security Concerns 44 Bibliography .50 ISO/IEC 2016 All rights reserved iii Contents PageBS ISO/IEC 18384-1:2016ISO/IEC 18384-1:2016(E) Foreword ISO (the I

13、nternational 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 committees esta

14、blished 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 the work. In th

15、e field of information technology, ISO and IEC have established a joint technical committee, 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 neede

16、d for the different types of document should be noted. This document was drafted in accordance 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

17、. ISO and IEC shall not be held responsible for identifying any or all such patent rights. 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

18、in this document is information given for the convenience of users and does not constitute 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 Barr

19、iers to Trade (TBT) see the following URL: Foreword - Supplementary information The committee 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

20、Reference Architecture for Service Oriented Architecture (SOA RA): Part 1: Terminology and 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) Introduction Se

21、rvice oriented architecture (SOA) is an architectural style in which business and IT systems 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, an

22、d it may be composed of other services but consumers of the service need not be aware of any 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

23、 businesses without needing to specify aspects of any particular business domain. Using the 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

24、response of information systems to ever-changing business needs. This International Standard 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 I

25、nternational Standard defines the terminology, technical principles, reference architecture, and 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

26、, business people, SOA service providers, SOA solution and service developers, and SOA service 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 In

27、ternational Standard contains three parts: a) ISO/IEC 18384-1 which defines the terminology, basic 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 a

28、s types of services in SOA solutions; c) ISO/IEC 18384-3 which defines the core concepts of SOA and 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

29、 read before reading or applying ISO/IEC 18384-2. For those new to SOA, ISO/IEC 18384-2:2016, Clause 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 f

30、or a SOA solution. ISO/IEC 18384-3 contains the SOA Ontology, which is a formalism of the core concepts 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 presen

31、ts and explains basic SOA concepts. It gives definitions for terms that are used in ISO/IEC 18384 with 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. T

32、erms used in their normal English sense are not redefined. ISO/IEC 2016 All rights reserved vBS ISO/IEC 18384-1:2016BS ISO/IEC 18384-1:2016Information technology Reference Architecture for Service Oriented Architecture (SOA RA) Part 1: Terminology and concepts for SOA 1 Scope This part of ISO/IEC 18

33、384 establishes vocabulary, guidelines, and general technical principles underlying service oriented architecture (SOA), including principles relating to functional design, performance, development, deployment, and management. 2 T erms a nd definiti ons For the purposes of this document, the followi

34、ng terms and definitions apply. 2.1 actor person or system component that interacts with the system as a whole and that provides stimulus which invokes actions SOURCE: ISO/IEC 16500-8:1999, 3.1 2.2 architecture fundamental concepts or properties of a system in its environment embodied in its element

35、s, relationships, and in the principles of its design and evolution SOURCE: ISO/IEC/IEEE 42010:2011, 3.2 2.3 choreography type 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 fo

36、r the entire (global) composition Note 1 to entry: Choreography does not require complete or perfect knowledge of the pattern of behaviour. Note 2 to entry: See ISO/IEC 18384-3:2016, 8.3. 2.4 collaboration type of composition (2.5) whose elements (2.8) interact in a non-directed fashion, each accord

37、ing to their own plans and purposes without a predefined pattern of behaviour Note 1 to entry: See ISO/IEC 18384-3:2016, 8.3. 2.5 composition result of assembling a collection of elements (2.8) for a particular purpose Note 1 to entry: See ISO/IEC 18384-3:2016, 8.2. INTERNATIONAL ST ANDARD ISO/IEC 1

38、8384-1:2016(E) ISO/IEC 2016 All rights reserved 1BS ISO/IEC 18384-1:2016ISO/IEC 18384-1:2016(E) 2.6 endpoint location at which information is received to invoke and configure interaction 2.7 effect outcome of an interaction with a service (2.20) Note 1 to entry: The effect is how a service delivers

39、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.8 element unit at a given level of abstraction and with a clearly defined boundary Note 1 to entry: An element can be any type of entity (2.9). Note 2 to entry: See ISO/IEC 18384-3

40、:2016, 5.1. 2.9 entity individual element (2.8) in a system with an identity which can act as a service provider (2.50) or service consumer (2.29) Note 1 to entry: Examples of entities are organizations, enterprises and individuals, software, and hardware. 2.10 event something that occurs to which a

41、n element (2.8) may choose to respond Note 1 to entry: Any element can generate (emit) or respond to an event. Note 2 to entry: See ISO/IEC 18384-3:2016, Clause 10. 2.11 execution context set of technical and business elements (2.8) needed by those with needs and capabilities to permit service provi

42、ders (2.50) and service consumers (2.29) instantiation and communication Note 1 to entry: The execution context of a service interaction (2.37) is the set of infrastructure elements, process entities, policy assertions, and agreements that are identified as part of an instantiated service interactio

43、n, and thus forms a path between those with needs and those with capabilities. Note 2 to entry: See Reference 8. 2.12 human actor actor (2.1) restricted to a person 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.

44、2. 2.13 human task task (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.14 interface shared boundary between two functional units, defined by various characteristics pertaining to the functions, physical interconnections,

45、 signal exchanges, and other characteristics, as appropriate SOURCE: ISO/IEC 2382:2015, 2121308 2.15 loose coupling principle where dependencies between elements (2.8) of a SOA solution (2.56) are intentionally reduced 2.16 orchestration type of composition (2.5) where one particular element (2.8) i

46、s used by the composition to oversee and direct the other elements Note 1 to entry: The element that directs an orchestration is not part of the orchestration (Composition instance) itself. Note 2 to entry: See ISO/IEC 18384-3:2016, 8.3. 2.17 policy statement that an entity (2.9) intends to follow o

47、r intends that another entity should follow Note 1 to entry: See ISO/IEC 18384-3:2016, Clause 9). 2.18 process type of composition (2.5) whose elements (2.8) are composed into a sequence or flow of activities and interactions with the objective of carrying out certain work Note 1 to entry: A process

48、 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.19 real-world effect change relevant to and experienced by specific stakeholders Note 1 to entry: See Reference 8. 2.20 service logical representation of a set of activi

49、ties that has specified outcomes, is self-contained, may be composed of other services, and is a “black box” to consumers of the service Note 1 to entry: The word “activity” in the “service” definition 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.21 service broker element (2.8) that enables the communication