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

《BS ISO IEC 18384-3-2016 Information technology Reference Architecture for Service Oriented Architecture (SOA RA) Service Oriented Architecture ontology《信息技术 面向服务架构用参考架构 (S.pdf》由会员分享，可在线阅读，更多相关《BS ISO IEC 18384-3-2016 Information technology Reference Architecture for Service Oriented Architecture (SOA RA) Service Oriented Architecture ontology《信息技术 面向服务架构用参考架构 (S.pdf（88页珍藏版）》请在麦多课文档分享上搜索。

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

2、 This British Standard is the UK implementation of ISO/IEC 18384-3: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.

3、This publication 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 81295 8 ICS 35.100.05 Compliance with a British Standard cannot c

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

5、ure for Service Oriented Architecture (SOA RA) Part 3: Service Oriented Architecture ontology Technologie de linformation Architecture de rfrence pour larchitecture oriente service (SOA RA) Partie 3: Ontologie de larchitecture oriente service INTERNATIONAL STANDARD ISO/IEC 18384-3 Reference number I

6、SO/IEC 18384-3:2016(E) First edition 2016-0 7-01 ISO/IEC 2016 BS ISO/IEC 18384-3: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 othe

7、rwise in any form or by 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

8、 Ch. de Blandonnet 8 CP 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-3:2016(E)BS ISO/IEC 18384-3:2016ISO/IEC 18384-3:2016(E)Foreword vi Introduction vii 1 Scope . 1 2 Normative references 1 3 T erms, definitions and ab

9、br e viat ed t erms 1 3.1 Terms and definitions . 1 3.2 Abbreviated terms . 1 4 Notations. 2 5 Conventions . 2 6 Conformance . 2 7 SOA Ontology Overview . 3 7.1 At a Glance 3 7.2 Intended Use . 5 7.3 Applications . 5 8 System and Element 5 8.1 Overview 5 8.2 The Element Class 6 8.3 The uses and used

10、By Properties . 6 8.4 Element Organizational Example 7 8.5 The System Class . 7 8.6 System Examples . 8 8.6.1 Organizational Example. 8 8.6.2 Service composition Example. 8 8.6.3 Car wash Example . 8 8.7 The represents and representedBy Properties . 9 8.8 The represents and representedBy Examples 10

11、 8.8.1 Organizational Example10 8.8.2 Car Wash Example .10 9 HumanActor and Task 11 9.1 Overview .11 9.2 The HumanActor Class 11 9.3 HumanActor Examples 12 9.3.1 The uses and usedBy Properties Applied to HumanActor 12 9.3.2 The represents and representedBy Properties Applied to HumanActor .12 9.3.3

12、Organizational Example12 9.3.4 Car Wash Example .13 9.4 The Task Class .13 9.5 The does and doneBy Properties .13 9.6 Task Examples .14 9.6.1 The uses and usedBy Properties Applied to Task 14 9.6.2 The represents and representedBy Properties Applied to Task 14 9.6.3 Organizational Example14 9.6.4 Ca

13、r Wash Example .15 10 Service, ServiceContract, and ServiceInterface .15 10.1 Overview .15 10.2 The Service Class 16 10.3 The performs and performedBy Properties .16 10.4 Service Consumers and Service Providers.17 10.5 Service Examples 17 10.5.1 The uses and usedBy properties Applied to Service 17 I

14、SO/IEC 2016 All rights reserved iii Contents PageBS ISO/IEC 18384-3:2016ISO/IEC 18384-3:2016(E)10.5.2 The represents and representedBy Properties Applied to Service .18 10.5.3 Exemplifying the Difference Between Doing a Task and Performing a Service 18 10.5.4 Car Wash Example .18 10.6 The ServiceCon

15、tract Class 18 10.7 The interactionAspect and legalAspect Datatype Properties 19 10.8 The hasContract and isContractFor Properties .20 10.9 The involvesParty and isPartyTo Properties 20 10.10 The Effect Class 21 10.11 The specifies and isSpecifiedBy Properties 22 10.12 ServiceContract Examples 22 10

16、.12.1 Service-level Agreements 22 10.12.2 Service Sourcing 23 10.12.3 Car Wash Example .23 10.13 The ServiceInterface Class .23 10.14 The Constraints Datatype Property .24 10.15 The hasInterface and isInterfaceOf Properties 25 10.16 The InformationType Class .25 10.17 The hasInput and isInputAt Prop

17、erties 26 10.18 The hasOutput and isOutputAt Properties 26 10.19 Examples .26 10.19.1 Interaction Sequencing .26 10.19.2 Car wash example 27 11 C omposition and its Subclasses .27 11.1 Overview .27 11.2 The Composition Class 27 11.3 The compositionPattern Datatype Property 28 11.3.1 Overview 28 11.3

18、.2 The Orchestration Composition Pattern 29 11.3.3 The Choreography Composition Pattern .29 11.3.4 The Collaboration Composition Pattern .29 11.4 The orchestrates and orchestratedBy Properties 31 11.5 The ServiceComposition Class .32 11.6 The Process Class .32 11.7 Service Composition and Process Ex

19、amples 33 11.7.1 Simple Service Composition Example 33 11.7.2 Process Example .33 11.7.3 Process and Service Composition Example .34 11.7.4 Car Wash Example .34 12 Policy 34 12.1 Overview .34 12.2 The Policy Class .34 12.3 The appliesTo and isSubjectTo Properties .35 12.4 The setsPolicy and isSetBy

20、Properties 35 12.5 Examples .36 12.5.1 Car Wash Example .36 13 Event .36 13.1 Overview .36 13.2 The Event Class 36 13.3 The generates and generatedBy Properties37 13.4 The respondsTo and respondedToBy Properties .37 Annex A (informative) Complete Car Wash Example 39 Annex B (informative) Internet Pu

21、rchase Example .44 Annex C (normative) The O WL Definition of the SO A Ont ology 46 Annex D (informative) Class Relationship Matrix 55 iv ISO/IEC 2016 All rights reservedBS ISO/IEC 18384-3:2016ISO/IEC 18384-3:2016(E)Annex E (informative) Terms Mapping Between the SOA RA Parts .59 Bibliogr aph y .74

22、ISO/IEC 2016 All rights reserved vBS ISO/IEC 18384-3:2016ISO/IEC 18384-3:2016(E) Foreword 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 IS

23、O or IEC participate in the development of International Standards through technical committees 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 organization

24、s, 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 committee, ISO/IEC JTC 1. The procedures used to develop this document and those intended for its further maintenance

25、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 accordance with the editorial rules of the ISO/IEC Directives, Part 2 (see www.iso.org/directives). Attention is dra

26、wn 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 rights. Details of any patent rights identified during the development of the document will be in the Introduction an

27、d/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 constitute an endorsement. For an explanation on the meaning of ISO specific terms and expressions related to conformity

28、 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 information The committee responsible for this document is ISO/IEC JTC 1, Information technology, Subcommittee SC 38, Cloud Computing

29、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 and concepts for SOA Part 2: Reference Architecture for SOA Solutions Part 3: Service Oriented Architecture Ontolog

30、yvi ISO/IEC 2016 All rights reservedBS ISO/IEC 18384-3:2016ISO/IEC 18384-3:2016(E) Introduction Service 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

31、a logical representation of a set of activities that has specified outcomes, is self-contained, 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 t

32、hat 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 SOA architectural style can improve the efficiency of developing information systems and integrating and reusing I

33、T resources. In addition, using the SOA architectural style can help enable rapid response of information systems to ever-changing business needs. This International Standard is intended to be a single set of SOA technical principles, specific norms, and standards for the world-wide market to help r

34、emove confusion about SOA and improve the standardization and quality of solutions. This International Standard defines the terminology, technical principles, reference architecture and the ontology for SOA. ISO/IEC 18384 can be used to introduce SOA concepts, as a guide to the development and manag

35、ement of SOA solutions, as well as be referenced by business and industry standards. This International Standard contains three parts: 1) ISO/IEC 18384-1 which defines the terminology, basic technical principles and concepts for SOA. 2) ISO/IEC 18384-2 which defines the detailed SOA reference archit

36、ecture layers, including a metamodel, capabilities, architectural building blocks, as well as types of services in SOA solutions. 3) ISO/IEC 18384-3 which defines the core concepts of SOA and their relationships in the Ontology. The targeted audience of this International Standard includes, but is n

37、ot limited to, standards organizations, architects, architecture methodologists, system and software designers, business people, SOA service providers, SOA solution and service developers, and SOA service consumers who are interested in adopting and developing SOA. Users of this International Standa

38、rd will find it useful to read ISO/IEC 18384-1 for an understanding of SOA basics. ISO/IEC 18384-1 should be read before reading or applying ISO/IEC 18384-2. For those new to the SOA reference architecture in ISO/IEC 18384-2:2016, Clause 4 provides a high level understanding of the reference archite

39、cture for SOA solutions. The remaining clauses provide comprehensive details of the architectural building blocks and tradeoffs needed for a SOA Solution. This part of ISO/IEC 18384 contains the SOA Ontology, which is a formalism of the core concepts and terminology of SOA, with mappings to both UML

40、 and OWL. The SOA Ontology can be used independent of or in conjunction with ISO/IEC 18384-1 and ISO/IEC 18384-2. The purpose of this part of ISO/IEC 18384 is to contribute to developing and fostering common understanding of service-oriented architecture (SOA) in order to improve alignment between t

41、he business and information technology communities and facilitate SOA adoption. The SOA Ontology defines the concepts, terminology, and semantics of SOA in both business and technical terms, in order to create a foundation for further work in domain-specific areas, enable communications between busi

42、ness and technical people, enhance the understanding of SOA concepts in the business and technical communities, provide a means to state problems and opportunities clearly and unambiguously to promote mutual understanding, and ISO/IEC 2016 All rights reserved viiBS ISO/IEC 18384-3:2016ISO/IEC 18384-

43、3:2016(E) provide a starting point for model-driven development of SOA solutions.viii ISO/IEC 2016 All rights reservedBS ISO/IEC 18384-3:2016INTERNATIONAL ST ANDARD ISO/IEC 18384-3:2016(E) Information technology Reference Architecture for Service Oriented Architecture (SOA RA) Part 3: Service Orient

44、ed Architecture ontology 1 Scope This part of ISO/IEC 18384 defines a formal ontology for service-oriented architecture (SOA), an architectural style that supports service orientation. The terms defined in this ontology are key terms from the vocabulary in ISO/IEC 18384-1. 2 Normative references The

45、 following documents, in whole or in part, are normatively referenced in this document and are indispensable for its application. For dated references, only the edition cited applies. For undated references, the latest edition of the referenced document (including any amendments) applies. ISO/IEC 18

46、384-1, Information technology Reference Architecture for Service Oriented Architecture (SOA RA) Part 1 Terminology and concepts for SOA 3 T erms, d efinitions and abbr e viat ed t erms 3.1 T erms and definiti ons For the purposes of this document, the terms and definitions given in ISO/IEC 18384-1 a

47、nd the following apply. 3.1.1 opaque having no internal structure that is visible to an external observer 3.1.2 ontology model that represents a domain and is used to reason about the objects in that domain and the relations between them Note 1 to entry: This part of ISO/IEC 18384 is high level and

48、not meant to be used for formal reasoning. SOURCE: ISO/IEC/TR 24800-1:2007, 2.1.9 3.2 A bbr e viat ed t erms For the purposes of this document, the following abbreviated terms apply. ABB Architecture Building Block BPMN Business Process Model and Notation EA Enterprise Architecture ESB Enterprise Se

49、rvice Bus IT Information Technology ISO/IEC 2016 All rights reserved 1BS ISO/IEC 18384-3:2016ISO/IEC 18384-3:2016(E) OWL Web Ontology Language RA Reference Architecture RDF Resource Definition Framework SLA Service Level Agreement SOA Service Oriented Architecture UML Unified Modeling Language 4 Notations The ontology is represented in the web ontology language (OWL) defined by the World Wide Web Consortium. OWL has three increasingly expressive sub-language