1、Adopted by INCITS (InterNational Committee for Information Technology Standards) as an American National Standard.Date of ANSI Approval: 12/24/2003Published by American National Standards Institute,25 West 43rd Street, New York, New York 10036Copyright 2003 by Information Technology Industry Council
2、 (ITI).All rights reserved.These materials are subject to copyright claims of International Standardization Organization (ISO), InternationalElectrotechnical Commission (IEC), American National Standards Institute (ANSI), and Information Technology Industry Council(ITI). Not for resale. No part of t
3、his publication may be reproduced in any form, including an electronic retrieval system, withoutthe prior written permission of ITI. All requests pertaining to this standard should be submitted to ITI, 1250 Eye Street NW,Washington, DC 20005.Printed in the United States of AmericaReference numberISO
4、/IEC 15414:2002(E)ISO/IEC 2002INTERNATIONAL STANDARD ISO/IEC15414First edition2002-10-15Information technology Open distributed processing Reference model Enterprise language Technologies de linformation Traitement distribu ouvert Modle de rfrence Langage dentreprise ISO/IEC 15414:2002(E) PDF discla
5、imer This PDF file may contain embedded typefaces. In accordance with Adobes licensing policy, this file may be printed or viewed but shall not be edited unless the typefaces which are embedded are licensed to and installed on the computer performing the editing. In downloading this file, parties ac
6、cept therein the responsibility of not infringing Adobes licensing policy. The ISO Central Secretariat accepts no liability in this area. Adobe is a trademark of Adobe Systems Incorporated. Details of the software products used to create this PDF file can be found in the General Info relative to the
7、 file; the PDF-creation parameters were optimized for printing. Every care has been taken to ensure that the file is suitable for use by ISO member bodies. In the unlikely event that a problem relating to it is found, please inform the Central Secretariat at the address given below. ISO/IEC 2002 All
8、 rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from either ISO at the address below or ISOs member body in the country o
9、f 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.ch Web www.iso.ch Printed in Switzerland ii ISO/IEC 2002 All rights reservedISO/IEC 15414:2002(E) ISO/IEC 2002 All rights reserved iiiCONTENTS Page 1 Scope 1 2 Nor
10、mative references 1 3 Definitions 1 3.1 Definitions from ODP standards . 1 3.2 Definitions from ODP standards extended in this specification 3 4 Abbreviations 3 5 Conventions 3 6 Concepts . 3 6.1 System concepts 4 6.2 Community concepts. 4 6.3 Behaviour concepts . 4 6.4 Policy concepts 4 6.5 Account
11、ability concepts 5 7 Structuring rules . 5 7.1 Overall structure of an enterprise specification . 5 7.2 Contents of an enterprise specification 6 7.3 Community rules . 7 7.4 Enterprise object rules . 8 7.5 Common community types 9 7.6 Lifecycle of a community 9 7.7 Objective rules. 10 7.8 Behaviour
12、rules 10 7.9 Policy rules 12 7.10 Accountability rules. 14 8 Compliance, completeness and field of application 15 8.1 Compliance 15 8.2 Completeness. 15 8.3 Field of application 15 9 Enterprise language compliance . 16 10 Conformance and reference points . 16 11 Consistency rules 16 11.1 Viewpoint c
13、orrespondences. 16 11.2 Enterprise and information specification correspondences . 17 11.3 Enterprise and computational specification correspondences . 18 11.4 Enterprise and engineering specification correspondences . 18 Index 20 ISO/IEC 15414:2002(E) iv ISO/IEC 2002 All rights reservedForeword ISO
14、 (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 International Standards through technical committe
15、es 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 liaison with ISO and IEC, also take part in the work
16、. 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 3. The main task of the joint technical committee is to prepare International Stan
17、dards. 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 is drawn to the possibility that some of the elemen
18、ts of this International Standard 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, Subcommittee SC 7, Software and system engine
19、ering, in collaboration with ITU-T. The identical text is published as ITU-T Rec. X.911. ISO/IEC 15414:2002(E) ISO/IEC 2002 All rights reserved vIntroduction The rapid growth of distributed processing has led to the adoption of the Reference Model of Open Distributed Processing (RM-ODP). This Refere
20、nce Model provides a co-ordinating framework for the standardization of open distributed processing (ODP). It creates an architecture within which support of distribution, interworking, and portability can be integrated. This architecture provides a framework for the specification of ODP systems. Th
21、e Reference Model of Open Distributed Processing is based on precise concepts derived from current distributed processing developments and, as far as possible, on the use of formal description techniques for specification of the architecture. This Recommendation | International Standard refines and
22、extends the definition of how ODP systems are specified from the enterprise viewpoint, and is intended for the development or use of enterprise specifications of ODP systems. 0.1 RM-ODP The RM-ODP consists of: Part 1: ITU-T Rec. X.901 | ISO/IEC 10746-1: Overview: which contains a motivational overvi
23、ew of ODP, giving scoping, justification and explanation of key concepts, and an outline of the ODP architecture. It contains 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 cate
24、gorization of required areas of standardization expressed in terms of the reference points for conformance identified in ITU-T Rec. X.903 | ISO/IEC 10746-3. This part is not normative. Part 2: ITU-T Rec. X.902 | ISO/IEC 10746-2: Foundations: which contains the definition of the concepts and analytic
25、al framework for normalized description of (arbitrary) distributed processing systems. It introduces the principles of conformance to ODP standards and the way in which they are applied. This is only to a level of detail sufficient to support ITU-T Rec. X.903 | ISO/IEC 10746-3 and to establish requi
26、rements for new specification techniques. This part is normative. Part 3: ITU-T Rec. X.903 | ISO/IEC 10746-3: Architecture: which contains the specification of the required characteristics that qualify distributed processing as open. These are the constraints to which ODP standards must conform. It
27、uses the descriptive techniques from ITU-T Rec. X.902 | ISO/IEC 10746-2. This part is normative. Part 4: ITU-T Rec. X.904 | ISO/IEC 10746-4: Architectural semantics: which contains a formalization of the ODP modelling concepts defined in ITU-T Rec. X.902 | ISO/IEC 10746-2 clauses 8 and 9. The formal
28、ization is achieved by interpreting each concept in terms of the constructs of one or more of the different standardized formal description techniques. This part is normative. ITU-T Rec. X.911 | ISO/IEC 15414: Enterprise language: this Recommendation | International Standard. 0.2 This Recommendation
29、 | International Standard Part 3 of the Reference Model, ITU-T Rec. X.903 | ISO/IEC 10746-3, defines a framework for the specification of ODP systems comprising: 1) five viewpoints, called enterprise, information, computational, engineering and technology, which provide a basis for the specification
30、 of ODP systems; 2) a viewpoint language for each viewpoint, defining concepts and rules for specifying ODP systems from the corresponding viewpoint. The purpose of this Recommendation | International Standard is to: Refine and extend the enterprise language defined in ITU-T Rec. X.903 |ISO/IEC 1074
31、6-3 to enable full enterprise viewpoint specification of an ODP system; Explain the correspondences of an enterprise viewpoint specification of an ODP system to other viewpoint specifications of that system; and Ensure that the enterprise language when used together with the other viewpoint language
32、s is suitable for the specification of a concrete application architecture to fill a specific business need. This Recommendation | International Standard uses concepts taken from ITU-T Recommendations X.902 and X.903 | ISO/IEC 10746-2 and 10746-3 and structuring rules taken from clause 5 of ITU-T Re
33、c. X.903 | ISO/IEC 10746-3; it introduces refinements of those concepts, additional viewpoint-specific concepts, and prescriptive structuring rules for enterprise viewpoint specifications. The additional viewpoint-specific concepts are defined using concepts from ITU-T Recommendations X.902 and X.90
34、3 | ISO/IEC 10746-2 and 10746-3. ISO/IEC 15414:2002(E) vi ISO/IEC 2002 All rights reserved0.3 Overview and motivation The purpose of this Recommendation | International Standard is to provide a common language (a set of terms and structuring rules) to be used in the preparation of an enterprise spec
35、ification capturing the purpose, scope and policies for an ODP system. Such an enterprise specification forms part of the specification of an ODP system in terms of the set of viewpoints defined by ITU-T Rec. X.903 | ISO/IEC 10746-3. The primary audience for this Recommendation | International Stand
36、ard consists of those who prepare and use such specifications. An enterprise specification is part of an ODP system specification. It can describe any or all of: an existing system; an anticipated future structure or behaviour of that existing system; a system to be created within some environment.
37、The motivation for a standard enterprise language is to support standardized techniques for specification in order to improve communication and help create specifications that are consistent overall. The enterprise language provides the terms and structuring rules to specify the purpose, scope and p
38、olicies for an ODP system in a manner that is meaningful for the stakeholders for that system, including the owners, the users, the developers and the maintainers. An enterprise specification describes the structure and behaviour of the system within its environment. It explicitly includes those asp
39、ects of the environment that influence the behaviour of the ODP system environmental constraints are captured as well as usage and management rules. Policies about potential changes in the system that may rule its future evolution may also be included. Such an environment can be a technical environm
40、ent (e.g. the software and hardware environment of a service component) or a social or business organization (e.g. a group of co-operating companies, a particular service inside a company). When preparing a specification, there are many approaches that are used for understanding, reaching agreement
41、about, and specifying systems in the context of the organizations of which they form a part. Many of these approaches fall into the categories often referred to as analysis or requirements specification. They can provide useful insights into both the organization under consideration and the requirem
42、ents for systems to support it, but they often lack the rigour, consistency and completeness needed for thorough specification. It is a key objective of this Recommendation | International Standard to provide a way of relating the commonly used concepts and underlying principles of such approaches t
43、o the modelling framework of the RM-ODP. An important objective of an enterprise specification is to support an agreement (for example, as part of the contract for the supply of a system) between the potential owners and users of an ODP system and the provider of that system. Both parties should be
44、able to write, read and discuss such a specification, the owners and users to be sure of the expected structure and behaviour of the system that they will get, and the provider to be clear about the structure and behaviour of the system being provided. Enterprise specifications can also be used at o
45、ther phases of the system life-cycle. The specification can, for example, be used at system run-time to control agreements between the system and its users, to establish new agreements according to the same contract structure and to establish federations. Finally, in the context of the current trend
46、 to integrate existing systems into global networks, where the functionality of interest spans multiple organizations, the enterprise language provides means to specify the joint agreement regarding the structure and behaviour of the ODP systems within and between these organizations. The concepts a
47、nd structuring rules this Recommendation | International Standard provides may be used for development of software engineering methodologies and tools exploiting ODP viewpoint languages, and for development of textual or graphical notations for the ODP enterprise language itself. For these purposes,
48、 this Recommendation | International Standard provides rules for the information content of an enterprise specification and the grouping of that information. Further requirements on the relationships between enterprise language concepts and their correspondences to concepts in other viewpoints are s
49、pecific to the methodologies, tools or notations to be developed. ISO/IEC 15414:2002 (E) ITU-T Rec. X.911 (10/2001) 1 INTERNATIONAL STANDARD ITU-T RECOMMENDATION Information technology Open distributed processing Reference model Enterprise language 1 Scope This Recommendation | International Standard provides: a) a language (the enterprise language) comprising concepts, structures, and rules for developing, representing, and reasoning about a specification of an ODP system from the enterprise viewpoint (as defined in
