ITU-T Z 130-2003 Extended Object Definition Language (eODL) Techniques for distributed software component development – Conceptual foundation notations and technology mappings SERIOR.pdf

1、 INTERNATIONAL TELECOMMUNICATION UNION ITU-T Z.130TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU (07/2003) SERIES Z: LANGUAGES AND GENERAL SOFTWARE ASPECTS FOR TELECOMMUNICATION SYSTEMS Formal description techniques (FDT) Extended Object Definition Language (eODL) Extended Object Definition Languag

2、e (eODL): Techniques for distributed software component development Conceptual foundation, notations and technology mappings ITU-T Recommendation Z.130 ITU-T Z-SERIES RECOMMENDATIONS LANGUAGES AND GENERAL SOFTWARE ASPECTS FOR TELECOMMUNICATION SYSTEMS FORMAL DESCRIPTION TECHNIQUES (FDT) Specificatio

3、n and Description Language (SDL) Z.100Z.109 Application of formal description techniques Z.110Z.119 Message Sequence Chart (MSC) Z.120Z.129 Extended Object Definition Language (eODL) Z.130Z.139 Testing and Test Control Notation (TTCN) Z.140Z.149 User Requirements Notation (URN) Z.150Z.159 PROGRAMMIN

4、G LANGUAGES CHILL: The ITU-T high level language Z.200Z.209 MAN-MACHINE LANGUAGE General principles Z.300Z.309 Basic syntax and dialogue procedures Z.310Z.319 Extended MML for visual display terminals Z.320Z.329 Specification of the man-machine interface Z.330Z.349 Data-oriented human-machine interf

5、aces Z.350Z.359 Human-computer interfaces for the management of telecommunications networks Z.360Z.369 QUALITY Quality of telecommunication software Z.400Z.409 Quality aspects of protocol-related Recommendations Z.450Z.459 METHODS Methods for validation and testing Z.500Z.519 MIDDLEWARE Distributed

6、processing environment Z.600Z.609 For further details, please refer to the list of ITU-T Recommendations. ITU-T Rec. Z.130 (07/2003) i ITU-T Recommendation Z.130 Extended Object Definition Language (eODL): Techniques for distributed software component development Conceptual foundation, notations and

7、 technology mappings Summary This Recommendation is intended for designers, implementers and managers of distributed systems, and tool developers that provide tools to support distributed systems. This Recommendation specifies the ITU Extended Object Definition Language (ITU-eODL). ITU-eODL is used

8、for a component-oriented development of distributed systems from the perspectives of four different but related views: the computational, implementation, deployment, and target environment view. Each view is connected with a specific modelling goal expressed by dedicated abstraction concepts. Comput

9、ational object types with (operational, stream, signal) interfaces and ports are the main computational view concepts which describe distributed software components abstractly in terms of their potential interfaces. Artefacts as abstractions of concrete programming language contexts and their relati

10、ons to interfaces form the implementation view. The deployment view describes software entities (software components) in binary representation and the computational entities realized by them. The target environment view provides modelling concepts of a physical network onto which the deployment of t

11、he software components shall be made. All concepts of the views are related to each other. These relations form an essential base for techniques and tools that support the software development process from design via implementation and integration to deployment. The test phase is not yet captured by

12、 this Recommendation. ITU-eODL is an extension of the ITU Object Definition Language ITU-ODL 1 and supersedes it. Originally ITU-ODL was designed as an extension of ODP-IDL 9 and defined computational concepts based on ODP 2, 3 terminology. eODL follows this principle. However, definitions are based

13、 on a metamodel rather than the traditional abstract syntax approach. One advantage of the metamodel approach is to allow use of MOF 4 related tools to support the automation of model transitions between the different software development phases. Another benefit is the ability to instantiate concret

14、e models from the metamodel, which can be represented by existing languages, so an integration of different design approaches can be achieved. The readers of this Recommendation are expected to be familiar with IDL 5, UML 11, MOF. The definition of eODL is supported by the following annexes and appe

15、ndices: Annex A introduces a textual syntax for eODL, intended to be used for the representation of eODL specifications. The syntax is defined using the EBNF style. Annex B defines the mapping between the eODL metamodel and the textual syntax defined in Annex A. Annex C provides a mapping from eODL

16、to ITU SDL-2000 that allows an eODL model to be automatically transformed to a SDL-2000 model. Annex D contains a software reference to the XML representation 12 of the eODL metamodel according to the XML meta interchange format (XMI) 6. It is provided in a separate file in order to allow import and

17、 processing of the eODL metamodel by UML tools. Clause 1 provides an overview of how eODL is used by designers, implementers and managers of a distributed system. A concrete example of the use is given in Appendix I. Appendix II describes the overall development process when using eODL and possible

18、tool support. Source ITU-T Recommendation Z.130 was approved on 22 July 2003 by ITU-T Study Group 17 (2001-2004) under the ITU-T Recommendation A.8 procedure. ii ITU-T Rec. Z.130 (07/2003) FOREWORD The International Telecommunication Union (ITU) is the United Nations specialized agency in the field

19、of telecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. The World

20、 Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. In s

21、ome areas of information technology which fall within ITU-Ts purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. NOTE In this Recommendation, the expression “Administration“ is used for conciseness to indicate both a telecommunication administration and a recogni

22、zed operating agency. Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure e.g. interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words

23、 “shall“ or some other obligatory language such as “must“ and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. INTELLECTUAL PROPERTY RIGHTS ITU draws attention to the possibility that t

24、he practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation

25、 development process. As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementors are cautioned that this may not represent the latest information and are

26、therefore strongly urged to consult the TSB patent database. ITU 2004 All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. ITU-T Rec. Z.130 (07/2003) iii CONTENTS Page 1 Scope 1 2 References. 3 3 Abbreviations 3 4 D

27、efinitions 4 5 Metamodel 6 5.1 Definitions and conventions. 7 5.2 Naming and scoping. 8 5.3 Computational concepts . 9 5.4 Implementation concepts 19 5.5 Deployment concepts . 21 5.6 Target environment concepts . 23 6 Bibliography . 27 Annex A Syntax of eODL. 28 A.1 Introduction 28 A.2 Lexical conve

28、ntions and grammar base . 28 A.3 Computational view 28 A.4 Configuration view. 30 A.5 Implementation view 30 A.6 Deployment view 31 A.7 Target environment 34 A.8 Syntax of eODL 34 Annex B Metamodel to syntax mapping. 42 B.1 Introduction 42 B.2 Signal and Signal Parameter. 43 B.3 Medium Type, Medium,

29、 Media Set . 44 B.4 Consume and Produce 45 B.5 Sink and Source 46 B.6 Interface Type. 46 B.7 CO Types, Supports and Requires 47 B.8 Provided and Used Port 48 B.9 Artefact and Instantiation Pattern. 49 B.10 Implements Relation. 49 B.11 Implementation Element 50 B.12 Software Component 51 B.13 Assembl

30、y and Initial Configuration . 52 B.14 Constraints and Properties 53 B.15 Target Environment, Node and NodeLink . 54 B.16 InstallationMap. 55 iv ITU-T Rec. Z.130 (07/2003) Page B.17 InstantiationMap. 56 B.18 Deployment Plan 57 B.19 Extern type 57 Annex C Mapping to SDL-2000. 58 C.1 Introduction 58 C.

31、2 The package eodl 58 C.3 Structure . 58 C.4 Scoped names . 59 C.5 Mapping of computational concepts 59 C.6 Mapping of configuration view concepts. 65 C.7 Mapping of implementation concepts 66 C.8 Omitting automatically generated behaviour . 72 C.9 Not mapped eODL concepts 72 C.10 Predefined eodl pa

32、ckage. 72 Annex D eODL metamodel XML representation. 75 Appendix I Example: Dining Philosophers 75 I.1 Introduction 75 I.2 Description . 76 I.3 Example in eODL. 77 I.4 Example in SDL-2000 79 Appendix II Information processing and tool support 100 II.1 Introduction 100 II.2 Modelling tool issues 101

33、II.3 Generator tool issues 101 II.4 Deployment tool issues. 102 ITU-T Rec. Z.130 (07/2003) 1 ITU-T Recommendation Z.130 Extended Object Definition Language (eODL): Techniques for distributed software component development Conceptual foundation, notations and technology mappings 1 Scope The provision

34、 of efficient techniques and of tool support for the development and engineering of distributed systems is a key enabling factor for the further evolution of Information Technology. Telecommunication systems are special distributed systems consisting of components which are distributed across networ

35、ks and have to cope with concurrency, autonomy, synchronization, and communication aspects. The development of highly efficient and scalable systems is a complex and complicated task, where tools have to support all phases of the development process from requirements capturing over design and implem

36、entation to integration, test and deployment. Code generation out of object-oriented design models leads to reusable, executable components. Such components integrate runtime environment and middleware platform technology dependent aspects with the enterprise specific object-oriented design model. E

37、ach software component has a physical representation (e.g., binary file), which has to be available for execution on a special node of a distributed system. The main focus of this Recommendation is the design of such components. Techniques for the development of distributed systems contribute signif

38、icantly to a reduction of the time to market of distributed applications and telecommunication services. An appropriate treatment of all kinds of communication aspects lies in the very nature of the targeted application domain. These aspects span from transactional requirements on object interaction

39、s over quality of service issues to security policies. Taking into account the broad acceptance of object middleware technology, middleware platforms provide an ideal implementation environment for such designs. Of these are plain CORBA 5, CORBA Components 7 and other distributed processing platform

40、s. This Recommendation is targeted to all software development processes addressing the following phases of the software life cycle: design phase; implementation phase; integration phase; operational phase. This Recommendation does not address the requirement capturing phase. The special emphasis of

41、 this Recommendation lies on the technological support of the transitions between phases to achieve their automation. The key technology is a model driven approach which is based on a well-defined metamodel (see 11). This metamodel allows integration of several existing design languages like SDL 8,

42、UML and CORBA-IDL. The metamodel is the definition of the concepts for the addressed phases of the software lifecycle. The models being instantiated on the basis of the metamodel can be represented using the existing languages. Since some concepts are not covered by an existing language, this Recomm

43、endation also defines a concrete syntax: eODL (Extended ODL). The metamodel-based approach replaces the well-known abstract syntax approach for the definition of languages. ITU-eODL is a revision of ITU-ODL. The syntax definition is given by Annex A. Consequently, the metamodel is independent of a s

44、pecific design notation. Design models can be developed applying different notations, but are based on the same concepts. Design information can be exchanged on the basis of the metamodel. Both the notation and the metamodel are independent 2 ITU-T Rec. Z.130 (07/2003) of a specific runtime environm

45、ent. The same design can be mapped onto different target environments. This enables high flexibility and is also important for the aspect of reuse of component design models. The integration of this Recommendation in software development processes is depicted in Figure 1. Starting with a precise req

46、uirements definition, a design model is specified. This Recommendation defines concepts which enable different views of the design model. Each view covers different aspects of the system to be developed. The concepts of the metamodel allow development of models powerful enough to derive software com

47、ponent skeletons automatically. The skeletons form the starting point of the implementation phase, where they have to be completed by the business logic. In the integration phase the completed software components have to be integrated in the target environment. Z.130_F01RequirementsdefinitionImpleme

48、ntation phase: Real software components (SCOs)with code modulesUse of software componentsDesign phase: SpecificationAutomatic derivation of software component skeletonsManual transitionOperationSCO ASCO B SCO CIntended software systemComputational view Computational objects (COs) with interfacesDepl

49、oyment viewAssemblies with initial configurations ofCOsImplementation viewArtefacts with ImplementationelementsComparison of intention and resultsAutomatic derivationof integration anddeployment descriptionsIntegration phase: Deployed and integrated components Target environment view Nodes, node links, and servicesReal software systemIntegration supportFigure 1/Z.130 Software development This Recommendation also contains concepts that allow the description of the topology and properties of the target envi