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

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

1、BS ISO/IEC 18384-3:2016Information technology Reference Architecture forService Oriented Architecture(SOA RA)Part 3: Service Oriented ArchitectureontologyBSI Standards PublicationWB11885_BSI_StandardCovs_2013_AW.indd 1 15/05/2013 15:06BS ISO/IEC 18384-3:2016 BRITISH STANDARDNational forewordThis Bri

2、tish Standard is the UK implementation of ISO/IEC18384-3: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 publicatio

3、n does 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 81295 8ICS 35.100.05Compliance with a British Standard cannot confer immunity fromle

4、gal obligations.This British Standard was published under the authority of theStandards Policy and Strategy Committee on 31 July 2016.Amendments/corrigenda issued since publicationDate T e x t a f f e c t e dBS ISO/IEC 18384-3:2016Information technology Reference Architecture for Service Oriented Ar

5、chitecture (SOA RA) Part 3: Service Oriented Architecture ontologyTechnologie de linformation Architecture de rfrence pour larchitecture oriente service (SOA RA) Partie 3: Ontologie de larchitecture oriente serviceINTERNATIONAL STANDARDISO/IEC18384-3Reference numberISO/IEC 18384-3:2016(E)First editi

6、on2016-07-01 ISO/IEC 2016BS ISO/IEC 18384-3: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, elec

7、tronic 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 officeCh. de Blandonnet 8 CP 401CH-1214 Vernie

8、r, Geneva, SwitzerlandTel. +41 22 749 01 11Fax +41 22 749 09 47copyrightiso.orgwww.iso.orgISO/IEC 18384-3:2016(E)BS ISO/IEC 18384-3:2016ISO/IEC 18384-3:2016(E)Foreword viIntroduction vii1 Scope . 12 Normative references 13 Terms, definitions and abbreviated terms 13.1 Terms and definitions . 13.2 Ab

9、breviated terms . 14 Notations. 25 Conventions . 26 Conformance . 27 SOA Ontology Overview . 37.1 At a Glance 37.2 Intended Use . 57.3 Applications . 58 System and Element 58.1 Overview 58.2 The Element Class 68.3 The uses and usedBy Properties . 68.4 Element Organizational Example 78.5 The System C

10、lass . 78.6 System Examples . 88.6.1 Organizational Example. 88.6.2 Service composition Example. 88.6.3 Car wash Example . 88.7 The represents and representedBy Properties . 98.8 The represents and representedBy Examples 108.8.1 Organizational Example 108.8.2 Car Wash Example .109 HumanActor and Tas

11、k 119.1 Overview . 119.2 The HumanActor Class 119.3 HumanActor Examples 129.3.1 The uses and usedBy Properties Applied to HumanActor 129.3.2 The represents and representedBy Properties Applied to HumanActor .129.3.3 Organizational Example 129.3.4 Car Wash Example .139.4 The Task Class . 139.5 The do

12、es and doneBy Properties . 139.6 Task Examples . 149.6.1 The uses and usedBy Properties Applied to Task 149.6.2 The represents and representedBy Properties Applied to Task 149.6.3 Organizational Example 149.6.4 Car Wash Example .1510 Service, ServiceContract, and ServiceInterface .1510.1 Overview .

13、1510.2 The Service Class 1610.3 The performs and performedBy Properties . 1610.4 Service Consumers and Service Providers. 1710.5 Service Examples 1710.5.1 The uses and usedBy properties Applied to Service 17 ISO/IEC 2016 All rights reserved iiiContents PageBS ISO/IEC 18384-3:2016ISO/IEC 18384-3:2016

14、(E)10.5.2 The represents and representedBy Properties Applied to Service .1810.5.3 Exemplifying the Difference Between Doing a Task and Performing a Service 1810.5.4 Car Wash Example .1810.6 The ServiceContract Class 1810.7 The interactionAspect and legalAspect Datatype Properties 1910.8 The hasCont

15、ract and isContractFor Properties .2010.9 The involvesParty and isPartyTo Properties 2010.10 The Effect Class 2110.11 The specifies and isSpecifiedBy Properties 2210.12 ServiceContract Examples 2210.12.1 Service-level Agreements 2210.12.2 Service Sourcing 2310.12.3 Car Wash Example .2310.13 The Serv

16、iceInterface Class . 2310.14 The Constraints Datatype Property . 2410.15 The hasInterface and isInterfaceOf Properties 2510.16 The InformationType Class . 2510.17 The hasInput and isInputAt Properties 2610.18 The hasOutput and isOutputAt Properties 2610.19 Examples . 2610.19.1 Interaction Sequencing

17、 .2610.19.2 Car wash example 2711 Composition and its Subclasses .2711.1 Overview . 2711.2 The Composition Class 2711.3 The compositionPattern Datatype Property 2811.3.1 Overview 2811.3.2 The Orchestration Composition Pattern 2911.3.3 The Choreography Composition Pattern .2911.3.4 The Collaboration

18、Composition Pattern .2911.4 The orchestrates and orchestratedBy Properties 3111.5 The ServiceComposition Class . 3211.6 The Process Class . 3211.7 Service Composition and Process Examples 3311.7.1 Simple Service Composition Example 3311.7.2 Process Example .3311.7.3 Process and Service Composition E

19、xample .3411.7.4 Car Wash Example .3412 Policy 3412.1 Overview . 3412.2 The Policy Class . 3412.3 The appliesTo and isSubjectTo Properties . 3512.4 The setsPolicy and isSetBy Properties 3512.5 Examples . 3612.5.1 Car Wash Example .3613 Event .3613.1 Overview . 3613.2 The Event Class 3613.3 The gener

20、ates and generatedBy Properties 3713.4 The respondsTo and respondedToBy Properties .37Annex A (informative) Complete Car Wash Example 39Annex B (informative) Internet Purchase Example .44Annex C (normative) The OWL Definition of the SOA Ontology 46Annex D (informative) Class Relationship Matrix 55iv

21、 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 .59Bibliography .74 ISO/IEC 2016 All rights reserved vBS ISO/IEC 18384-3:2016ISO/IEC 18384-3:2016(E)ForewordISO (the International Organization for Standardizat

22、ion) 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 established by the respective organization to

23、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 the field of information technology, ISO and

24、 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 needed for the different types of document shoul

25、d 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. ISO and IEC shall not be held responsible

26、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 in this document is information given for the

27、 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 Barriers to Trade (TBT) see the following URL: For

28、eword Supplementary informationThe 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 Reference Architecture for Service Oriented Archit

29、ecture (SOA RA): Part 1: Terminology and concepts for SOA Part 2: Reference Architecture for SOA Solutions Part 3: Service Oriented Architecture Ontologyvi ISO/IEC 2016 All rights reservedBS ISO/IEC 18384-3:2016ISO/IEC 18384-3:2016(E)IntroductionService oriented architecture (SOA) is an architectura

30、l 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, it may be composed of other services but consumers of

31、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 businesses without needing to specify aspects of any par

32、ticular 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 enable rapid response of information systems to ever-changing business needs.This

33、International Standard 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 and improve the standardization and quality of solutions.This International Standard defines the terminology, technical princi

34、ples, reference architecture and the ontology for SOA. ISO/IEC 18384 can be used to introduce SOA concepts, as a guide to the development and management of SOA solutions, as well as be referenced by business and industry standards.This International Standard contains three parts:1) ISO/IEC 18384-1 w

35、hich defines the terminology, basic technical principles and concepts for SOA.2) 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.3) ISO/IEC 18384-3 which de

36、fines the core concepts of SOA and their relationships in the Ontology.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 so

37、lution and service developers, and SOA service consumers who are interested in adopting and developing SOA.Users of this International Standard 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. F

38、or those new to the SOA reference architecture in 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 tradeoffs needed for a SOA Solution. This

39、 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 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 t

40、o contribute to developing and fostering common understanding of service-oriented architecture (SOA) in order to improve alignment between the business and information technology communities and facilitate SOA adoption.The SOA Ontology defines the concepts, terminology, and semantics of SOA in both

41、business and technical terms, in order to create a foundation for further work in domain-specific areas, enable communications between business and technical people, enhance the understanding of SOA concepts in the business and technical communities, provide a means to state problems and opportuniti

42、es clearly and unambiguously to promote mutual understanding, and ISO/IEC 2016 All rights reserved viiBS ISO/IEC 18384-3:2016ISO/IEC 18384-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 STANDA

43、RD ISO/IEC 18384-3:2016(E)Information technology Reference Architecture for Service Oriented Architecture (SOA RA) Part 3: Service Oriented Architecture ontology1 ScopeThis part of ISO/IEC 18384 defines a formal ontology for service-oriented architecture (SOA), an architectural style that supports s

44、ervice orientation. The terms defined in this ontology are key terms from the vocabulary in ISO/IEC 18384-1.2 Normative referencesThe following documents, in whole or in part, are normatively referenced in this document and are indispensable for its application. For dated references, only the editio

45、n cited applies. For undated references, the latest edition of the referenced document (including any amendments) applies.ISO/IEC 18384-1, Information technology Reference Architecture for Service Oriented Architecture (SOA RA) Part 1 Terminology and concepts for SOA3 Terms, definitions and abbrevia

46、ted terms3.1 Terms and definitionsFor the purposes of this document, the terms and definitions given in ISO/IEC 18384-1 and the following apply.3.1.1opaquehaving no internal structure that is visible to an external observer3.1.2ontologymodel that represents a domain and is used to reason about the o

47、bjects in that domain and the relations between themNote 1 to entry: This part of ISO/IEC 18384 is high level and not meant to be used for formal reasoning.SOURCE: ISO/IEC/TR 24800-1:2007, 2.1.93.2 Abbreviated termsFor the purposes of this document, the following abbreviated terms apply.ABB Architec

48、ture Building BlockBPMN Business Process Model and NotationEA Enterprise ArchitectureESB Enterprise Service BusIT Information Technology ISO/IEC 2016 All rights reserved 1BS ISO/IEC 18384-3:2016ISO/IEC 18384-3:2016(E)OWL Web Ontology LanguageRA Reference ArchitectureRDF Resource Definition Framework

49、SLA Service Level AgreementSOA Service Oriented ArchitectureUML Unified Modeling Language4 NotationsThe ontology is represented in the web ontology language (OWL) defined by the World Wide Web Consortium. OWL has three increasingly expressive sub-languages: OWL-Lite, OWL-DL, and OWL-Full (see Reference 10 for a definition of these three dialects of OWL). This ontology uses OWL-DL, the sub-language that provides the greatest expressiveness possible while retaining computational completeness and decidability.The