1、 Collection of SANS standards in electronic format (PDF) 1. Copyright This standard is available to staff members of companies that have subscribed to the complete collection of SANS standards in accordance with a formal copyright agreement. This document may reside on a CENTRAL FILE SERVER or INTRA
2、NET SYSTEM only. Unless specific permission has been granted, this document MAY NOT be sent or given to staff members from other companies or organizations. Doing so would constitute a VIOLATION of SABS copyright rules. 2. Indemnity The South African Bureau of Standards accepts no liability for any
3、damage whatsoever than may result from the use of this material or the information contain therein, irrespective of the cause and quantum thereof. ISBN 978-0-626-23161-3 SANS 15414:2009Edition 1 ISO/IEC 15414:2006Edition 2 SOUTH AFRICAN NATIONAL STANDARD Information technology Open distributed proce
4、ssing Reference model Enterprise language This national standard is the identical implementation of ISO/IEC 15414:2006, and is adopted with the permission of the International Organization for Standardization and the International Electrotechnical Commission. Published by SABS Standards Division 1 D
5、r Lategan Road Groenkloof Private Bag X191 Pretoria 0001Tel: +27 12 428 7911 Fax: +27 12 344 1568 www.sabs.co.za SABS SANS 15414:2009 Edition 1 ISO/IEC 15414:2006 Edition 2 Table of changes Change No. Date Scope National foreword This South African standard was approved by National Committee SABS SC
6、 71C, Information technology Systems and software engineering, in accordance with procedures of the SABS Standards Division, in compliance with annex 3 of the WTO/TBT agreement. This SANS document was published in October 2009. Reference numberISO/IEC 15414:2006(E)ISO/IEC 2006INTERNATIONAL STANDARD
7、ISO/IEC15414Second edition2006-06-15Information technology Open distributed processing Reference model Enterprise language Technologies de linformation Traitement rparti ouvert Modle de rfrence Langage dentreprise SANS 15414:2009This s tandard may only be used and printed by approved subscription an
8、d freemailing clients of the SABS .ISO/IEC 15414:2006(E) PDF disclaimer 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 co
9、mputer performing the editing. In downloading this file, parties accept 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 cr
10、eate this PDF file can be found in the General Info relative to the 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 t
11、he Central Secretariat at the address given below. ISO/IEC 2006 All 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 e
12、ither ISO at the address below 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 2006 All rights reservedSANS 15414:2009T
13、his s tandard may only be used and printed by approved subscription and freemailing clients of the SABS .ISO/IEC 15414:2006(E) ISO/IEC 2006 All rights reserved iiiCONTENTS Page Introduction . v 0.1 RM-ODP. v 0.2 Overview and motivation v 1 Scope . 1 2 Normative references 1 2.1 Identical ITU-T Recom
14、mendations | International Standards 1 3 Terms and definitions 2 3.1 Definitions from ODP standards 2 3.2 Definitions from ODP standards extended in this specification. 3 4 Abbreviations 3 5 Conventions 4 6 Concepts. 4 6.1 System concepts . 4 6.2 Community concepts . 4 6.3 Behaviour concepts . 4 6.4
15、 Policy concepts. 5 6.5 Accountability concepts . 5 7 Structuring rules. 6 7.1 Overall structure of an enterprise specification 6 7.2 Contents of an enterprise specification 6 7.3 Community rules 7 7.4 Enterprise object rules 9 7.5 Common community types . 9 7.6 Lifecycle of a community . 9 7.7 Obje
16、ctive rules . 10 7.8 Behaviour rules. 11 7.9 Policy rules 12 7.10 Accountability rules. 15 8 Compliance, completeness and field of application 16 8.1 Compliance 16 8.2 Completeness . 16 8.3 Field of application 17 9 Enterprise language compliance 17 10 Conformance and reference points . 17 11 Consis
17、tency rules 17 11.1 Viewpoint correspondences. 18 11.2 Enterprise and information specification correspondences. 18 11.3 Enterprise and computational specification correspondences 19 11.4 Enterprise and engineering specification correspondences. 20 11.5 Enterprise and technology specification corres
18、pondence . 20 Annex A Model of the enterprise language concepts (This annex does not form an integral part of this Recommendation | International Standard) 21 Annex B Explanations and examples (This annex does not form an integral part of this Recommendation | International Standard) 24 B.1 First ex
19、ample Specification of an e-commerce system 24 B.2 Second example Specification of a library . 33 INDEX 40 SANS 15414:2009This s tandard may only be used and printed by approved subscription and freemailing clients of the SABS .ISO/IEC 15414:2006(E) iv ISO/IEC 2006 All rights reservedForeword ISO (t
20、he 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 committees
21、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. I
22、n 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 technical committee is to prepare International Standar
23、ds. 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 elements
24、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 jointly by Joint Technical Committee ISO/IEC JTC 1, Information technology, Subcommittee SC 7, Software and system engineering, in
25、 collaboration with ITU-T. The identical text is published as ITU-T Rec. X.911. This second edition cancels and replaces the first edition (ISO/IEC 15414:2002), which has been technically revised. SANS 15414:2009This s tandard may only be used and printed by approved subscription and freemailing cli
26、ents of the SABS .ISO/IEC 15414:2006(E) ISO/IEC 2006 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 Reference Model provides a coordinating framework for the standardization of
27、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. The Reference Model of Open Distributed Processing is based on precise con
28、cepts 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 extends the definition of how ODP systems are specified from the enterpr
29、ise 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 overview of ODP, giving scoping, justification and explanation of key concepts
30、, 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 categorization of required areas of standardization expressed in terms of th
31、e reference points for conformance identified in ITU-T Rec. X.903 | ISO/IEC 10746-3. This part is informative. Part 2: ITU-T Rec. X.902 | ISO/IEC 10746-2: Foundations: which contains the definition of the concepts and analytical framework for normalized description of (arbitrary) distributed process
32、ing 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 requirements for new specification techniques. This part is normative. Part 3:
33、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 shall conform. It uses the descriptive techniques from ITU-T Rec. X.902 | ISO/IEC 10746-2.
34、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 formalization is achieved by interpreting each concept in terms of the construc
35、ts 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 Overview and motivation Part 3 of the Reference Model, ITU-T Rec. X.903 | ISO/IEC 10746-3, d
36、efines 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 of ODP systems; 2) a viewpoint language for each viewpoint, defining concepts and rules for s
37、pecifying 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 10746-3 to enable full enterprise viewpoint specification of an ODP system; Explain the correspond
38、ences 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 languages, is suitable for the specification of a concrete application architecture to fill a specifi
39、c business need. This Recommendation | International Standard uses concepts taken from ITU-T Recs X.902 | ISO/IEC 10746-2 and X.903 | ISO/IEC 10746-3 and structuring rules taken from clause 5 of ITU-T Rec. X.903 | ISO/IEC 10746-3; it introduces refinements of those concepts, additional viewpoint-spe
40、cific concepts, and prescriptive structuring rules for enterprise viewpoint specifications. The additional viewpoint-specific concepts are defined using concepts from ITU-T Recs X.902 | ISO/IEC 10746-2 and X.903 | ISO/IEC 10746-3. SANS 15414:2009This s tandard may only be used and printed by approve
41、d subscription and freemailing clients of the SABS .ISO/IEC 15414:2006(E) vi ISO/IEC 2006 All rights reservedThis Recommendation | International Standard provides a common language (set of terms and structuring rules) to be used in the preparation of an enterprise specification capturing the purpose
42、, scope and policies for an ODP system. An enterprise specification is a part of the specification of an ODP system using viewpoints defined by ITU-T Recommendation X.903 | ISO/IEC 10746-3. The specification of the ODP system can describe any or all of: an existing system within its environment; an
43、anticipated future structure or behaviour of that existing system within the same or an anticipated future environment; a system to be created within some environment. The primary audience for this Recommendation | International Standard is those who prepare and use such specifications. The audience
44、 includes ODP system owners and users, including subject manager experts, and developers and maintainers of ODP system, tools, and methodologies. The motivation for the enterprise language is to support standardized techniques for specification. This improves communication and helps create consisten
45、t specifications. The preparation of specifications often falls into the category referred to as analysis or requirement specification. There are many approaches used for understanding, agreeing and specifying systems in the context of the organizations of which they form a part. The approaches can
46、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 completeness needed for thorough specification. The audiences of the specifications also vary. For agreement between the potentia
47、l 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 terms directly related to system realization. The use of enterprise specifications can be wider than the early phases of sof
48、tware engineering process. A current trend is to integrate existing systems into global networks, where the functionality of interest spans multiple organizations. The enterprise language provides a means to specify the joint agreement of common behaviour of the ODP systems within and between these
49、organizations. The enterprise specification can also be used at other 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, 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 development of software engineering metho
