BS ISO IEC 15414-2015 Information technology Open distributed processing Reference model Enterprise language《信息技术 开放型分布式处理 标准模式 企业语言》.pdf

《BS ISO IEC 15414-2015 Information technology Open distributed processing Reference model Enterprise language《信息技术 开放型分布式处理 标准模式 企业语言》.pdf》由会员分享，可在线阅读，更多相关《BS ISO IEC 15414-2015 Information technology Open distributed processing Reference model Enterprise language《信息技术 开放型分布式处理 标准模式 企业语言》.pdf（56页珍藏版）》请在麦多课文档分享上搜索。

1、BSI Standards Publication BS ISO/IEC 15414:2015 Information technology Open distributed processing Reference model Enterprise languageBS ISO/IEC 15414:2015 BRITISH STANDARD National foreword This British Standard is the UK implementation of ISO/IEC 15414:2015. It supersedes BS ISO/IEC 15414:2006 whi

2、ch is withdrawn. The UK participation in its preparation was entrusted to Technical Committee IST/15, Software and systems engineering. A list of organizations represented on this committee can be obtained on request to its secretary. This publication does not purport to include all the necessary pr

3、ovisions of a contract. Users are responsible for its correct application. The British Standards Institution 2015. Published by BSI Standards Limited 2015 ISBN 978 0 580 89939 3 ICS 35.080 Compliance with a British Standard cannot confer immunity from legal obligations. This British Standard was pub

4、lished under the authority of the Standards Policy and Strategy Committee on 30 April 2015. Amendments/corrigenda issued since publication Date T e x t a f f e c t e dBS ISO/IEC 15414:2015Reference number ISO/IEC 15414:2015(E) ISO/IEC 2015INTERNATIONAL STANDARD ISO/IEC 15414 Third edition 2015-04-15

5、 Information technology Open distributed processing Reference model Enterprise language Technologies de linformation Traitement rparti ouvert Modle de rfrence Langage dentreprise BS ISO/IEC 15414:2015 ISO/IEC 15414:2015(E) COPYRIGHT PROTECTED DOCUMENT ISO/IEC 2015 All rights reserved. Unless otherwi

6、se specified, no part of this publication may be reproduced or utilized otherwise 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 bel

7、ow 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.iso.org Published in Switzerland ii ISO/IEC 2015 All rights reservedBS ISO/IEC 15414:2015Rec. ITU-T X.911 (09/20

8、14) iii CONTENTS Page 0.1 RM-ODP . v 0.2 Overview and motivation v 1 Scope 1 2 Normative references 1 2.1 Identical ITU-T Recommendations | International Standards . 1 2.2 Additional References . 1 3 Terms and definitions . 2 3.1 Definitions from ODP standards . 2 4 Abbreviations . 3 5 Conventions 4

9、 6 Concepts . 4 6.1 System concepts 4 6.2 Community concepts . 4 6.3 Behaviour concepts . 4 6.4 Deontic concepts . 5 6.5 Policy concepts 6 6.6 Accountability concepts 6 7 Structuring rules . 7 7.1 Overall structure of an enterprise specification . 7 7.2 Contents of an enterprise specification 7 7.3

10、Community rules . 8 7.4 Enterprise object rules . 10 7.5 Common community types . 10 7.6 Life cycle of a community 11 7.7 Objective rules 11 7.8 Behaviour rules . 12 7.9 Policy rules 16 7.10 Accountability rules 18 8 Compliance, completeness and field of application . 19 8.1 Compliance . 19 8.2 Comp

11、leteness 19 8.3 Field of application . 19 9 Enterprise language compliance . 20 10 Conformance and reference points . 20 11 Consistency rules 20 11.1 Viewpoint correspondences 20 11.2 Enterprise and information specification correspondences . 21 11.3 Enterprise and computational specification corres

12、pondences . 22 11.4 Enterprise and engineering specification correspondences . 22 11.5 Enterprise and technology specification correspondence 23 Annex A Model of the enterprise language concepts . 24 Annex B Explanations and examples . 28 B.1 First example Enterprise specification of an e-commerce s

13、ystem 28 B.2 Second example Specification of a library . 34 Annex C An operational semantics for enterprise behaviour . 41 C.1 A semantics for basic behaviour . 41 C.2 Frames and markings 41 C.3 Calculating the utility of possible courses of action 41 C.4 Use of utility to prioritize possible behavi

14、ours 41 INDEX 43 BS ISO/IEC 15414:2015 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 ISO or IEC participate in the development of

15、 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 organizations, governmental and non-governmental, in l

16、iaison 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. International Standards are drafted in accordance with the rules given in the ISO/IEC Directives, Part 2. The main task of the joint t

17、echnical committee is to prepare International 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. Attention

18、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 rights. ISO/IEC 15414 was prepared by Joint Technical Committee ISO/IEC JTC 1, Information technology, Subcommi

19、ttee SC 7, Software and systems engineering, in collaboration with ITU-T. The identical text is published as ITU-T X.911 (09/2014). This third edition cancels and replaces the second edition (ISO/IEC 15414:2006), which has been technically revised. iv Rec. ITU-T X.911 (09/2014) BS ISO/IEC 15414:2015

20、 Rec. ITU-T X.911 (09/2014) v Introduction The rapid growth of distributed processing led to the adoption of the Reference Model of Open Distributed Processing (RM-ODP). This Reference Model provides a coordinating framework for the standardization of open distributed processing (ODP). It creates an

21、 architecture within which support of distribution, interworking and portability can be integrated. This architecture provides a framework for the specification of ODP systems. The Reference Model of Open Distributed Processing is based on precise concepts derived from current distributed processing

22、 developments and, as far as possible, on the use of formal description techniques for specification of the architecture. This Recommendation | International Standard refines and extends the definition of how ODP systems are specified from the enterprise viewpoint, and is intended for the developmen

23、t or use of enterprise specifications of ODP systems. 0.1 RM-ODP The RM-ODP consists of: Part 1: Rec. ITU-T X.901 | ISO/IEC 10746-1: Overview: This contains a motivational overview of ODP, giving scoping, justification and explanation of key concepts, and an outline of the ODP architecture. It conta

24、ins explanatory material on how the RM-ODP is to be interpreted and applied by its users, who may include standards writers and architects of ODP systems. It also contains a categorization of required areas of standardization expressed in terms of the reference points for conformance identified in I

25、TU-T Rec. X.903 | ISO/IEC 10746-3. This part is informative. Part 2: Rec. ITU-T X.902 | ISO/IEC 10746-2: Foundations: This contains the definition of the concepts and analytical framework for normalized description of (arbitrary) distributed processing systems. It introduces the principles of confor

26、mance to ODP standards and the way in which they are applied. This is only to a level of detail sufficient to support Rec. ITU-T X.903 | ISO/IEC 10746-3 and to establish requirements for new specification techniques. This part is normative. Part 3: Rec. ITU-T X.903 | ISO/IEC 10746-3: Architecture: T

27、his contains the specification of the required characteristics that qualify distributed processing as open. These are the constraints to which ODP standards shall conform. It uses the descriptive techniques from Rec. ITU-T X.902 | ISO/IEC 10746-2. This part is normative. Part 4: Rec. ITU-T X.904 | I

28、SO/IEC 10746-4: Architectural semantics: This contains a formalization of the ODP modelling concepts defined in Rec. ITU-T X.902 | ISO/IEC 10746-2 clauses 8 and 9. The formalization is achieved by interpreting each concept in terms of the constructs of one or more of the different standardized forma

29、l description techniques. This part is normative. Rec. ITU-T X.911 | ISO/IEC 15414: Enterprise language: this Recommendation | International Standard. 0.2 Overview and motivation Part 3 of the Reference Model, Rec. ITU-T X.903 | ISO/IEC 10746-3, defines a framework for the specification of ODP syste

30、ms comprising: 1) five viewpoints, called enterprise, information, computational, engineering and technology, which provide a basis for the specification of ODP systems; 2) a viewpoint language for each viewpoint, defining concepts and rules for specifying ODP systems from the corresponding viewpoin

31、t. The purpose of this Recommendation | International Standard is to: Refine and extend the enterprise language defined in Rec. ITU-T X.903 |ISO/IEC 10746-3 to enable full enterprise viewpoint specification of an ODP system. Explain the correspondences of an enterprise viewpoint specification of an

32、ODP system to other viewpoint specifications of that system. Ensure that the enterprise language, when used together with the other viewpoint languages, is suitable for the specification of a concrete application architecture to fill a specific business need. This Recommendation | International Stan

33、dard uses concepts taken from Recs ITU-T X.902 | ISO/IEC 10746-2 and X.903 | ISO/IEC 10746-3 and structuring rules taken from clause 5 of Rec. ITU-T X.903 | ISO/IEC 10746-3; it introduces refinements of those concepts, additional viewpoint-specific concepts, and prescriptive structuring rules for en

34、terprise viewpoint specifications. The additional viewpoint-specific concepts are defined using concepts from Recs ITU-T X.902 | ISO/IEC 10746-2 and X.903 | ISO/IEC 10746-3. BS ISO/IEC 15414:2015 Rec. ITU-T X.911 (09/2014) v i This Recommendation | International Standard provides a common language (

35、set of terms and structuring rules) to be used in the preparation of an enterprise specification capturing the purpose, scope and policies for an ODP system. An enterprise specification is a part of the specification of an ODP system using viewpoints defined by Recommendation ITU-T X.903 | ISO/IEC 1

36、0746-3. The specification of the ODP system can describe any or all of: an existing system within its environment; an anticipated future structure or behaviour of that existing system within an existing or an anticipated future environment; a system to be created within some environment. The primary

37、 audience for this Recommendation | International Standard is those who prepare and use such specifications. The audience includes ODP system owners and users, including subject management experts, and developers and maintainers of ODP systems, tools and methodologies. The motivation for the enterpr

38、ise language is to support standardized techniques for specification. This improves communication and helps create consistent specifications. The preparation of specifications often falls into the category referred to as analysis or requirement specification. There are many approaches used for under

39、standing, agreeing and specifying systems in the context of the organizations of which they form a part. The approaches can provide useful insights into both the organization under consideration and the requirements for systems to support it, but they generally lack the rigour, consistency and compl

40、eteness needed for thorough specification. The audiences of the specifications also vary. For agreement between the potential users of an ODP system and the provider of that system, it may be necessary to have different presentations of the same system one in terms understood by clients, and one in

41、terms directly related to system realization. The use of enterprise specifications can be wider than the early phases of the software engineering process. A current trend is to integrate existing systems into global networks, where the functionality of interest spans multiple organizations. The ente

42、rprise language provides a means to specify the joint agreement of common behaviour of the ODP systems within and between these organizations. The enterprise specification can also be used in other phases of the system life cycle. The specification can, for example, be used at system run-time to con

43、trol agreements between the system and its users, and to establish new agreements according to the same contract structure. Enterprise viewpoint specifications may contain rules for inter-organizational behaviour. This Recommendation | International Standard also provides a framework for the develop

44、ment of software engineering methodologies and tools exploiting ODP viewpoint languages, and a set of concepts for the development of enterprise viewpoint specification languages. For these purposes, this Recommendation | International Standard provides rules for the information content of specifica

45、tions and the grouping of that information. Further requirements on the relationships between enterprise language concepts and concepts in other viewpoints are specific to the methodologies, tools or specification languages to be developed. An enterprise specification defines the purpose, scope, and

46、 policies of an ODP system and it provides a statement of conformance for system implementations. The purpose of the system is defined by the specified behaviour of the system while policies capture further restriction on the behaviour between the system and its environment or within the system itse

47、lf related to the business decisions by the system owners. An enterprise specification also allows the specification of an ODP system that spans multiple domains and is not owned by a single party, and specification of the collective behaviour of a system that is divided into independently specified

48、 and independently working subsystems. This generality places greater emphasis on the expression of correct or normal behaviour and on the chains of responsibility involved in achieving it. For example, the advent of service oriented and cloud computing has led to the need to specify business rules

49、and behaviour in a way that clearly describes obligations, permissions, authorizations and prohibitions, as well as the accountability of each of the objects involved in an enterprise specification. This involves the expression of the so-called deontic aspects of the behaviour of the system, and of the accountability of the objects involved. Annex A presents a metamodel of the enterprise language, illustrating the key concepts of the enterprise language and their relationships. This annex is normative. Annex B provides exam