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. ICS 35.100.01 ISBN 0-626-14977-0 SANS 10746-4:2003 Edition 1 and ISO/IEC amdt 1 ISO/IEC 10746-4:1998 Edition 1 and amdt 1 SOUTH AFRICAN NATIONAL STANDARD
4、 Information technology Open distributed processing Reference model: Architectural semantics This national standard is the identical implementation of ISO/IEC 10746-4:1998 and amendment 1, and is adopted with the permission of the International Organization for Standardization and the International
5、Electrotechnical Commission. Published by Standards South Africa 1 dr lategan road groenkloof private bag x191 pretoria 0001 tel: 012 428 7911 fax: 012 344 1568 international code + 27 12 www.stansa.co.za Standards South Africa 2003 SANS 10746-4:2003 Edition 1 and ISO/IEC amdt 1 ISO/IEC 10746-4:1998
6、 Edition 1 and amdt 1 Table of changes Change No. Date Scope ISO/IEC amdt 1 2001 Amended to change: a) “viewpoint languages“ to “computational viewpoint language“ throughout the text b) the publication date for ITU-T Recommendation Z.100 from “1993“ to “1999“ in the normative reference clause c) the
7、 title of 3.3 from “Definitions from the Z-Base Standard“ to “Definitions from the Z notation“ Amended to include: a) a new annex on computational formalization (annex A) b) the relationship of annex A (Computational formalization) to the main text of the standard c) a reference in the introduction
8、to clause 7 of ITU-T Rec. X.903 | ISO/IEC 10746-3 d) a normative reference to ISO/IEC 13568, and a reference to “Z Notation, ISO/IEC JTC1 SC 22 WG 19 Advanced Working Draft 2.C, July 13th1999“ Amended to update: a) the list of definitions from ITU-T Recommendation in Z.100 in 3.2 b) the list of defi
9、nitions in 3.3 National foreword This South African standard was approved by National Committee STANSA SC 71C, Information Technology: ICT systems and software engineering, in accordance with procedures of Standards South Africa, in compliance with annex 3 of the WTO/TBT agreement. Reference number
10、ISO/IEC 10476-4:1998/Amd.1:2001(E)ISO/IEC 2001 INTERNATIONAL STANDARD ISO/IEC10746-4First edition1998-12-15AMENDMENT 12001-12-15Information technology Open Distributed Processing Reference Model: Architectural semantics AMENDMENT 1: Computational formalization Technologies de linformation Traitement
11、 rparti ouvert Modle de rfrence: Smantique architecturale AMENDEMENT 1: Formalisation informatique ISO/IEC 10746-4:1998/Amd.1:2001(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 un
12、less the typefaces which are embedded are licensed to and installed on the computer 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 tradema
13、rk 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 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.
14、In the unlikely event that a problem relating to it is found, please inform the Central Secretariat at the address given below. ISO/IEC 2001 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 mechanica
15、l, including photocopying and microfilm, without permission in writing from either 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.ch Web www.iso.ch P
16、ublished by ISO in 2002 Printed in Switzerland ii ISO/IEC 2001 All rights reserved ISO/IEC 10746-4:1998/Amd.1:2001(E) ISO/IEC 2001 All rights reserved iiiCONTENTSPage1) Introduction 12) Clause 1 Scope . 13) Clause 2 Normative references . 24) Subclause 3.2 Definitions from ITU-T Recommendation Z.100
17、 25) Subclause 3.3 Definitions from the Z-Base Standard 26) Annex A 3Annex A Computational Formalization. 3A.1 Formalization of the Computational Viewpoint Language in LOTOS 3A.2 Formalization of the Computational Viewpoint Language in SDL. 12A.3 Formalization of the Computational Viewpoint Language
18、 in Z . 20A.4 Formalization of the Computational Viewpoint Language in ESTELLE 28ISO/IEC 10746-4:1998/Amd.1:2001(E) iv ISO/IEC 2001 All rights reserved Foreword ISO (the International Organization for Standardization) and IEC (the International Electrotechnical Commission) form the specialized syste
19、m 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 deal with particular fields of technical activity. ISO and IEC technical committees col
20、laborate 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 IEC have established a joint technical committee, ISO/IEC JTC 1. International Standar
21、ds 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 Standards. Draft International Standards adopted by the joint technical committee are circulated to national bodies for voting. Publication
22、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 of this Amendment may be the subject of patent rights. ISO and IEC shall not be held responsible for identifying any or all such pate
23、nt rights. Amendment 1 to International Standard ISO/IEC 10746-4:1998 was prepared by Joint Technical Committee ISO/IEC JTC 1, Information technology, Subcommittee SC 7, Software engineering, in collaboration with ITU-T. The identical text is published as ITU-T Rec. X.904/Amd.1. ISO/IEC 10746-4:1998
24、/Amd.1:2001 (E)ITU-T Rec. X.904/Amd.1 (2000 E) 1INTERNATIONAL STANDARDISO/IEC 10746-4:1998/Amd.1:2001 (E)ITU-T Rec. X.904/Amd.1 (2000 E)ITU-T RECOMMENDATIONINFORMATION TECHNOLOGY OPEN DISTRIBUTED PROCESSING REFERENCE MODEL: ARCHITECTURAL SEMANTICSAMENDMENT 1Computational formalization1) Introduction
25、Replace the lst paragraph of the introductionThis Recommendation | International Standard is an integral part of the ODP Reference Model. It contains aformalisation of the ODP modelling concepts defined in ITU-T Rec. X.902 | ISO/IEC 10746-2, clauses 8 and 9. Theformalisation is achieved by interpret
26、ing each concept in terms of the constructs of the different standardised formaldescription techniques.withThis Recommendation | International Standard is an integral part of the ODP Reference Model. It contains aformalization of the ODP modelling concepts defined in ITU-T Rec. X.902 | ISO/IEC 10746
27、-2, clauses 8 and 9 and inITU-T Rec. X.903 | ISO/IEC 10746-3, clause 7 (Computational Language). The formalization is achieved by interpretingeach concept in terms of the constructs of the different standardized formal description techniques.2) Clause 1 ScopeReplace the fourth bullet under The RM-OD
28、P consists ofITU-T Rec. X.904 | ISO/IEC 10746-4: Architectural Semantics: contains a formalisation of the ODP modellingconcepts defined in ITU-T Rec. X.902 | ISO/IEC 10746-2, clauses 8 and 9, and a formalisation of the viewpointlanguages of ITU-T Rec. X.903 | ISO/IEC 10746-3. The formalisation is ac
29、hieved by interpreting each concept in termsof the constructs of the different standardised formal description techniques. This text is normative.withITU-T Rec. X.904 | ISO/IEC 10746-4: Architectural Semantics: contains a formalization of the ODP modellingconcepts defined in ITU-T Rec. X.902 | ISO/I
30、EC 10746-2, clauses 8 and 9, and a formalization of the computationalviewpoint language of ITU-T Rec. X.903 | ISO/IEC 10746-3. The formalization is achieved by interpreting each conceptin terms of the constructs of the different standardized formal description techniques. This text is normative.Repl
31、ace the fourth paragraphThe purpose of this Recommendation | International Standard is to provide an architectural semantics for ODP. Thisessentially takes the form of an interpretation of the basic modelling and specification concepts of ITU-T Rec. X.902 |ISO/IEC 10746-2 and the viewpoint languages
32、 of ITU-T Rec. X.903 | ISO/IEC 10746-3, using the various features ofdifferent formal specification languages. An architectural semantics is developed in four different formal specificationlanguages: LOTOS, ESTELLE, SDL and Z. The result is a formalisation of ODPs architecture. Through a process ofi
33、terative development and feedback, this has improved the consistency of ITU-T Rec. X.902 | ISO/IEC 10746-2 andITU-T Rec. X.903 | ISO/IEC 10746-3.withThe purpose of this Recommendation | International Standard is to provide an architectural semantics for ODP. Thisessentially takes the form of an inte
34、rpretation of the basic modelling and specification concepts of ITU-T Rec. X.902 |ISO/IEC 10746-2 and the computational viewpoint language of ITU-T Rec. X.903 | ISO/IEC 10746-3, using the variousfeatures of different formal specification languages. An architectural semantics is developed in four dif
35、ferent formal2 ITU-T Rec. X.904/Amd.1 (2000 E)specification languages: LOTOS, ESTELLE, SDL and Z. The result is a formalization of ODPs architecture. Through aprocess of iterative development and feedback, this has improved the consistency of ITU-T Rec. X.902 |ISO/IEC 10746-2 and ITU-T Rec. X.903 |
36、ISO/IEC 10746-3.Add the following paragraph at the end of Scope:Annex A shows one way in which the computational viewpoint language of ITU-T Rec. X.903 | ISO/IEC 10746-3 can berepresented in the formal languages LOTOS, SDL, Z and Estelle. This Recommendation | International Standard alsomakes use of
37、 the concepts defined in ITU-T Rec. X.902 | ISO/IEC 10746-2.3) Clause 2 Normative referencesChange publication date for ITU-T Recommendation Z.100 from (1993) to (1999).ISO/IEC 13568:Add the following reference:Z Notation, ISO/IEC JTC 1 SC 22 WG 19 Advanced Working Draft 2.C, July 13th 1999.4) Subcl
38、ause 3.2 Definitions from ITU-T Recommendation Z.100Replace the list with the following terms:active, adding, all, alternative, and, any, as, atleast, axioms, block, call, channel, comment, connect, connection,constant, constants, create, dcl, decision, default, else, endalternative, endblock, endch
39、annel, endconnection,enddecision, endgenerator, endnewtype, endoperator, endpackage, endprocedure, endprocess, endrefinement, endselect,endservice, endstate, endsubstructure, endsyntype, endsystem, env, error, export, exported, external, fi, finalized, for,fpar, from, gate, generator, if, import, im
40、ported, in, inherits, input, interface, join, literal, literals, map, mod, nameclass,newtype, nextstate, nodelay, noequality, none, not, now, offspring, operator, operators, or, ordering, out, output,package, parent, priority, procedure, process, provided, redefined, referenced, refinement, rem, rem
41、ote, reset, return,returns, revealed, reverse, save, select, self, sender, service, set, signal, signallist, signalroute, signalset, spelling, start,state, stop, struct, substructure, synonym, syntype, system, task, then, this, timer, to, type, use, via, view, viewed, virtual,with, xor.5) Subclause
42、3.3 Definitions from the Z-Base StandardChange subclause title to:3.3 Definitions from the Z Notation.Replace the list with following terms:axiomatic description, data refinement, hiding, operation refinement, overriding, schema (operation, state, framing),schema calculus, schema composition, sequen
43、ce, type.ISO/IEC 10746-4:1998/Amd.1:2001 (E)ISO/IEC 10746-4:1998/Amd.1:2001 (E)ITU-T Rec. X.904/Amd.1 (2000 E) 36) Annex AAdd a new Annex A as follows:Annex AComputational FormalizationA.1 Formalization of the Computational Viewpoint Language in LOTOSA.1.1 ConceptsThe formalization of the computatio
44、nal language in LOTOS uses the concepts defined in the formalization of the basicmodelling and structuring rules given in ITU-T Rec. X.902 | ISO/IEC 10746-2 clauses 8 and 9.Elementary Structures Associated with Operational and Signal InterfacesTo formalize the computational language in LOTOS it is n
45、ecessary to introduce certain elementary structures. Theseinclude parameters that might be associated with certain computational interfaces and a basic model of information thatmight be used in a stream flow.To formalize parameters it is necessary to introduce two concepts: names for things and type
46、s for things. Names aresimply labels. As we shall see, the computational viewpoint requires that checks, e.g. for equality, are done on theselabels when interfaces are constructed. We may represent names generally by:type Name is Booleansorts Nameopns newName: - NameanotherName: Name - Name_eq_,_ne_
47、: Name, Name - Boolendtype(*Name*)For brevity sake we omit the equations, which are expected to be obvious. It is possible to be more prescriptive here, e.g.using character strings from the LOTOS library. The only thing we are interested in regarding names is that we candetermine their equality or i
48、nequality.As discussed in this Recommendation | International Standard, a type in the ODP sense may not be interpreted directly inthe process algebra part of LOTOS. It is however possible to model types through the Act One part of LOTOS.Unfortunately, whilst Act One was designed specifically for rep
49、resenting types, it is limited in the ways in which typesand types relationships are checked. For example, it is not possible to check subtyping or equivalence up to isomorphismbetween types due to type equality in Act One being based on name equivalence of sorts. As a basis for reasoning herewe introduce an elementary notion of types that allows us to test for equality, inequality and subtyping.type AnyType is Booleansorts AnyTypeopns newType: - AnyTypeanotherType: AnyType - AnyType_eq_,_isSubtype_: AnyType, AnyType - Boolend
