ITUT X.911 ISO/IEC 15414
Date:01-03-03
RM-ODP Enterprise Language FCD with NB Comments
Helsinki 2001 Input
ISO/IEC JTC 1/SC 7
Software Engineering
Secretariat: Canada (SCC)
Doc Type:Final Committee Draft
Title:Information Technology—Open Distributed Processing—
Reference Model—Enterprise Language
ISO/IEC 15414 | ITUT Recommendation X.911
Source:Project Editor
Project:1.07.77
Status:FCD with NB Comments, Helsinki 2001 Input
Action:For Info
Distribution:SC 7/WG17
Medium:E
Number of Pages:39
Version:303
Address reply to:
ISO/IEC JTC1/SC7 Secretariat
Bell Canada
1050 Beaver Hall Hill 2nd floor
Montréal Québec H2Z 1S4
CANADA
Tel: +1 514 391 8286
Fax: +1 514 870 2246
INTERNATIONAL STANDARD
ISO/IEC 15414 : Committee Draft
ITU-T Rec. X.911 (Committee Draft)
ITU-T RECOMMENDATION
/ INTERNATIONAL TELECOMMUNICATION UNIONITU-T / X.911
TELECOMMUNICATION
STANDARDIZATION SECTOR
OF ITU / (Final Committee Draft 7/00)
COMMON TEXT DRAFT PUBLICATION
Information Technology—
Open Distributed Processing—Reference Model—
Enterprise Language
ITU-T Recommendation X.911
Version 303
Committee Draft ISO/IEC 15414 (ITU-T X.911)
CONTENTS
Page
0Introduction
0.1RMODP
0.2This Recommendation | International Standard
1Scope
2 Normative references
Identical ITUT Recommendations | International Standards
3Definitions
3.1Definitions from ODP standards
3.1.1Modelling concept definitions
3.1.2Viewpoint language definitions
3.2Definitions from ODP standards refined or extended in this standard
4Abbreviations
5Overview and motivation
6Concepts
6.1General concepts
6.2Role concepts
6.3Policy concepts
6.4Force concepts
7Structuring Rules
7.1 Overall structure of an enterprise specification
7.2 Contents of an enterprise specification
7.3Community rules
7.3.1Specification of a community
7.3.2Relationships between communities
7.4Enterprise object rules
7.5Common community types
7.5.1 Domain community type
7.5.2 Federation community type
7.5.3Ownership Community Type
7.6Lifecycle of a community
7.6.1Establishing a community
7.6.2Changes in a community
7.6.3Terminating a community
7.7Objective rules
7.8Behaviour rules
7.8.1Roles and processes
7.8.2Role rules
7.8.3Interface roles and interactions between communities
7.8.4Enterprise objects and actions
7.8.5Process rules
7.9Policy rules
7.9.1General policy rules
7.9.2Obligations, permissions and prohibitions
7.9.3Nesting of policy frameworks
7.9.4Policy violations
7.9.5Organisation of policy
7.10Force rules
7.10.1 Delegation rules
7.10.2 Authority rules
7.10.3 Commitment rules
7.10.4 Declaration rules
7.10.5 Prescription rules
8Consistency rules
8.1 Viewpoint correspondences
8.2 Enterprise and information specification correspondences
8.2.1 Concepts related by correspondences
8.2.2 Required correspondences
8.2.3 Required correspondence statements
8.3 Enterprise and computational specification correspondences
8.3.1 Concepts related by correspondences
8.3.2 Required correspondences
8.3.3 Required correspondence statements
8.4 Enterprise and engineering specification correspondences
8.4.1 Concepts related by correspondences
8.4.2 Required correspondences
8.4.3 Required correspondence statements
9Relations between standards and product development
9.1 Compliance, conformance, testing and consistency
9.2 Completeness
9.3 Scoping statement
10Enterprise Language Compliance
11Conformance and reference points
Annex AOverall structure of an enterprise specification
Index
Foreword
This is the initial final committee draft of ITU | ISO/IEC Common Text for Recommendation X.911 | International Standard 15414: Information Technology—Open Distributed Processing—Reference Model—Enterprise Language. It is the draft output of the May-June 2000 Madrid meeting.
The draft is in the format prescribed for ITU | ISO/IEC Common Text.
The work on this draft Recommendation | International Standard is done by ISO/IEC JTC 1/SC 7/WG 17, originally chartered by SC 21 as a project in SC 21/WG 7, and lately known as SC 33/WG 5 and SC 7/WG 3.
TEMPORARY NOTES The draft includes temporary notes, specified by the working group, for the information of National Bodies, which appear in a smaller font, indented as is this paragraph. These are not part of the text of the draft.
Editor’s notes The draft includes editor’s notes, which appear in a smaller font, deeply indented as is this paragraph; these are not part of the text of the draft.
References This document contains references to Parts 2 and 3 of RM-ODP; for example, [35.1] is a reference to Part 3, subclause 5.1. These references are not part of the text of the draft.
Numbering Each line and page of this document is numbered, for the convenience of national bodies commenting on the document.
IMPORTANT: When referring to line and page numbers, use the numbers on the Portable Document Format (PDF) version of this document. The numbers on other versions of the document may change depending on the software or on the printer chosen while viewing the document.
Indexing The project editor requests suggestions for indexing this document.
It is the project editor’s faith that a good index is an index prepared by a professional indexer.
Changes to ITU template; these must be changed back:
- Addition of style, Editors Note
- Addition of Keep lines together to Paragraph Line and Page Breaks
- Font
ITU-T Rec. X.911 (Committee Draft)1
Committee Draft ISO/IEC 15414 (ITU-T X.911)
FIN1GSummary of concernsInconsistent use of terminology
Problems
Part 2 terminology is not explained enough for readers to follow the discussion
Cobehaviour missing
Implementation objects vs. modeling world at different levels of abstraction still mixed especially when trying to match processes with role
Audiences and usage examples not clear
Force concepts form not a full set, other similar groups of concepts have not been spelled out this way – language is extensible.
Proposal
Suggestions in FIN9, FIN11, FIN14, FIN23, FIN68
ES 30EAnnex BExamples
Rationale
Having into consideration the intended audience of this document, we feel that some explanatory examples would be of much interest and help to them.
Proposal
Include a second annex with some explanatory text and examples of enterprise specifications. There were some examples in a previous version of this document. We suggest including them, or some modified versions of them.
UK1Cat GTitle
Rationale:
The title of the standard on the cover page of the standard is given as “Information Technology – Open Distributed Processing – Reference Model – Enterprise Viewpoint” although it has been agreed by several meetings of WG 17 and its predecessor bodies that the title is “Information Technology – Open Distributed Processing – Reference Model – Enterprise Language.
Proposal:
The SC 7 Secretariat should be requested (yet again) to note the change of title and to make any consequent changes to the project information.
UK2Cat GThe meaning of the term “enterprise specification”
Rationale:
The terms “enterprise specification” and “enterprise model” are both used, apparently interchangeably, in the current text. If the two terms are considered to be equivalent then only one should be used, if they are considered to be different then their uses should be clearly distinguished.
Proposal:
The terms “enterprise specification” and “specification” should be used in accordance with their use in the RM-ODP Part 3.
The terms “enterprise model” and “model” should only be used to refer to what is expressed by an “enterprise specification” or “specification” respectively.
Editorial changes are proposed in comments below where these are made necessary by this principle.
USA 1 Ethroughout
Rationale
This is a relatively heavyweight method of making minor editorial comments. We understand that the working group does not wish the project editor to make such changes on his own.
Proposal
The USA proposes to take the liberty of suggesting minor editorial changes during the editing meeting.
0Introduction
The rapid growth of distributed processing has led to the adoption of the Reference Model of Open Distributed Processing (RMODP). This Reference Model provides a co-ordinating framework for the standardisation 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.
FIN7E0, line 6, page 1Spelling
Rationale
Missing word.
Proposal
Replace “Open Distributed” with “Open Distributed Processing”.
The Reference Model of Open Distributed 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 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.
JP1EPage 1-2, 0.2, line 9This Recommendation | International Standard
Rationale
Missing page numbers and a word.
Proposal
Add page numbers and make the sentence readable.
Add page numbers “1” and “2” to each page, and replace “… text ITU-T” by “… text from ITU-T …”, line 9 on the second page.
0.1RMODP
The RMODP consists of:
ITUT Recommendation X.901 | ISO/IEC 107461: Overview: which contains a motivational overview of ODP, giving scoping, justification and explanation of key concepts, and an outline of the ODP architecture. It contains explanatory material on how the RMODP is to be interpreted and applied by its users, who may include standards writers and architects of ODP systems. It also contains a categorisation of required areas of standardisation expressed in terms of the reference points for conformance identified in ITUT Recommendation X.903 | ISO/IEC 107463. This part is not normative.
ITUT Recommendation X.902 | ISO/IEC 107462: Foundations: which contains the definition of the concepts and analytical framework for normalised 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 ITUT Recommendation X.903 | ISO/IEC 107463 and to establish requirements for new specification techniques. This part is normative.
ITUT Recommendation X.903 | ISO/IEC 107463: 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 uses the descriptive techniques from ITUT Recommendation X.902 | ISO/IEC 107462. This part is normative.
ITUT Recommendation X.904 | ISO/IEC 107464: Architectural semantics: which contains a formalisation of the ODP modelling concepts defined in ITUT Recommendation X.902 | ISO/IEC 107462 clauses 8 and 9. The formalisation is achieved by interpreting each concept in terms of the constructs of one or more of the different standardised formal description techniques. This part is normative.
ITUT Recommendation X.911 | ISO/IEC 15414: Enterprise language: this Recommendation | International Standard.
0.2This Recommendation | International Standard
ITU-T Recommendation 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 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 Recommendation 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 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 specific business need.
This ITUT Recommendation X.911 | ISO/IEC IS 15414 uses concepts taken from ITUT Recommendations X.902 and X.903 | ISO/IEC 107462 and 107463, and introduces refinements of those concepts, additional viewpointspecific concepts, and prescriptive rules for enterprise viewpoint specifications. The additional viewpointspecific concepts are defined using concepts from ITUT Recommendations X.902 and X.903 | ISO/IEC 107462 and 107463.
This Recommendation | International Standard contains, for the convenience of the reader, some text taken verbatim from clauses5 and 10 of ITUT Recommendation X.903 | ISO/IEC 107463: Part3: Architecture. Such text is marked by a reference like this: [35.9], which indicates text taken from part3, subclause5.9 of RMODP. In the event of any discrepancies in these cases, the text of ITUT Recommendation X.903 | ISO/IEC 107463 is authoritative.
This Recommendation | International Standard also contains some text which is a modification of text ITUT Recommendation X.903 | ISO/IEC 107463: Part3: Architecture. Such text is marked by a reference like this: [see also 35.9]. The modifications are authoritative with respect to the enterprise language.
This Recommendation | International Standard contains these annexes:
Annex A: Overall structure of an enterprise specification
This annex is not normative.
1
Committee Draft ISO/IEC 15414 (ITU-T X.911)
INTERNATIONAL STANDARD
ISO/IEC 0001 : 1996 (E)
ITU-T Rec. A.1000 (1996 E)
ITU-T RECOMMENDATION
INFORMATION TECHNOLOGY—OPEN DISTRIBUTED PROCESSING—
REFERENCE MODEL—ENTERPRISE LANGUAGE
1Scope
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 ITU-T Recommendation X.903 |ISO/IEC 10746-3);
b) rules which establish correspondences between the enterprise language and the other viewpoint languages (defined in ITU-T Recommendation X.903 |ISO/IEC 10746-3) to ensure the overall consistency of a specification.
The language is specified to a level of detail sufficient to enable the determination of the compliance of any ODP modelling language to this Recommendation | International Standard and to establish requirements for new specification techniques.
JP2TLPage 3, 1, forth paragraph, lines 15Scope
Rationale
Whether modelling language is “ODP modelling language” or just a “modelling language” should be dependent on the results of conformance testing (if we do have it). If the modelling language is called ODP modelling language, then it should be compliant, and the text seems inappropriate.
Also what is important here is not a modelling language but models created with modelling languages.
Proposal
Remove reference to ODP.
Remove “ODP” from “… compliance of any ODP modelling language …” and make it more general.
This Recommendation | International Standard is a refinement and extension of ITUT Recommendation X.903 | ISO/IEC 107463, clauses 5 and 10, but does not replace them.
This standard is intended for use in preparing enterprise viewpoint specifications of ODP systems, and in developing notations and tools to support such specifications.
As specified in clause 5 of ITUT Recommendation X.903 | ISO/IEC 107463, an enterprise viewpoint specification defines the purpose, scope and policies of an ODP system. [35.0]
2 Normative references
The following ITUT Recommendations | International Standards contain provisions which, through reference in this text, constitute provisions of this Recommendation | International Standard. At the time of publication, the editions indicated were valid. All Recommendations | International Standards are subject to revision, and parties to agreements based on this Recommendation | International Standard are encouraged to investigate the possibility of applying the most recent editions of the Recommendations | International Standards listed below. Members of IEC and ISO maintain registers of currently valid International Standards. The ITUT Secretariat maintains a list of the currently valid ITUT Recommendations.
FIN8E2, page 3, line25Spelling
Proposal
Replace “con tain” with “contain”.
Identical ITUT Recommendations | International Standards
–ITUT Recommendation X.902 (1995) | ISO/IEC 107462: 1994, Information technology – Open Distributed Processing – Reference Model – Foundations
–ITUT Recommendation X.903 (1995) | ISO/IEC 107463: 1994, Information technology – Open Distributed Processing – Reference Model – Architecture
–ITUT Recommendation X.904 (1997) | ISO/IEC 107464: 1997, Information technology – Open Distributed Processing – Reference Model – Architectural semantics
3Definitions
3.1Definitions from ODP standards
3.1.1Modelling concept definitions
This Recommendation | International Standard makes use of the following terms as defined in ITUT Recommendation X.902 | ISO/IEC 107462
1
Committee Draft ISO/IEC 15414 (ITU-T X.911)
-- action;
-- behaviour (of an object) ;
-- composite object;
-- composition;
-- configuration (of objects) ;
-- conformance;
-- conformance point;
-- contract;
-- <X> domain;
-- entity;
-- environment contract;
-- environment (of an object) ;
-- epoch;
-- establishing behaviour;
-- incremental modification;
-- instance (of a type) ;
-- instantiation (of an <X> template) ;
-- interface;
-- internal action;
-- interworking reference point;
-- invariant;
-- liaison;
-- location in space;
-- location in time;
-- object;
-- obligation;
-- ODP standards;
-- ODP system;
-- perceptual reference point;
-- permission;
-- policy;
-- postcondition;
-- precondition;
-- programmatic reference point;
-- prohibition;
-- proposition;
-- quality of service;
-- reference point;
-- refinement;
-- responding object;
-- role;
-- state (of an object) ;
-- subtype;
-- system;
-- <X> template;
-- terminating behaviour;
-- type (of an <X>);
-- viewpoint (on a system).
1
Committee Draft ISO/IEC 15414 (ITU-T X.911)
3.1.2Viewpoint language definitions
This Recommendation | International Standard makes use of the following terms as defined in ITUT Recommendation X.903 | ISO/IEC 107463
1
Committee Draft ISO/IEC 15414 (ITU-T X.911)
-- community;
-- computational interface;
-- computational viewpoint;
-- dynamic schema;
-- engineering viewpoint;
-- enterprise viewpoint;
-- <X> federation
-- information viewpoint;
-- invariant schema;
-- <viewpoint> language;
-- static schema;
-- technology viewpoint.
.
1
Committee Draft ISO/IEC 15414 (ITU-T X.911)
3.2Definitions from ODP standards refined or extended in this standard
This Recommendation | International Standard refines or extends the definitions of the following terms originally defined in ITUT X.902 | ISO/IEC 107462 (the refined or extended definitions are in clause 6):
1
Committee Draft ISO/IEC 15414 (ITU-T X.911)
-- policy
1
Committee Draft ISO/IEC 15414 (ITU-T X.911)
4Abbreviations
ODPopen distributed processing
RMODPReference Model of Open Distributed Processing
(ITUT Recommendations X.901 to X.904 | ISO/IEC IS 10746)
5Overview and motivation
FIN9THclause 5induced rewrite of clause 5
Rationale
Collected together the comments on the audience of this standard, on the exploitation scenarios for this standard, and the clarity and spelling of clause 5 (FIN9-FIN14) induce the following rewrite of clause 5.
Proposal
5. Motivation and overview
The purpose of this Recommendation | International Standard is to provide a common language (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. Such an enterprise specification forms a part of the specification of and ODP system in terms of the set of viewpoints defined by ITU-T Recommendation X.903 | ISO/IEC 10746-3.
The primary audience for the document consists of those who prepare and use such specifications. The motivation for a standard enterprise language is to support standardised techniques for specification. This improves communication and helps create consistent overall specifications.
The preparation of specifications often falls into the category referred to as analysis of requirement specification. There are many approaches used for understanding, agreeing and specifying systems in the context of the organisations of which they form a part. The approaches can provide useful insights into both the organisation 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 potential clients of an ODP system and the provider of that system, there may be needed 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 software engineering process. Current trend is to integrate existing systems into global networks, where the functionality of interest spans multiple organisations. The enterprise language provides means to specify the joint agreement of common behaviour of the ODP systems within and between these organisations. 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 contact structure. Enterprise viewpoint specifications may contain rules for inter-organisational behaviour.