The Specifications Exchange Service of an RM-ODP Framework

Size: px
Start display at page:

Download "The Specifications Exchange Service of an RM-ODP Framework"

Transcription

1 The Specifications Exchange Service of an RM-ODP Framework X. Blanc (*+), M-P. Gervais(*), J. Le Delliou(+) (*)Laboratoire d'informatique de Paris 6-8 rue du Capitaine Scott F75015 PARIS (+)EDF Research Division - 1, av du Gnl De Gaulle F92141 CLAMART Cedex Xavier.Blanc@lip6.fr, Marie-Pierre.Gervais@lip6.fr, Juliette.Le-Delliou@edf.fr Abstract LIP6 and EDF have started to develop an RM-ODP framework for building open distributed systems. The first concern of this development was the construction of the Specification Exchange Service. This service, the socalled Backbone, enables the exchanges of RM-ODP specifications over any ORB or file systems. This article presents the functionalities of the Backbone in the RM-ODP framework and it explains how meta-modeling standards such as MOF and XMI have been used to create it. 1. Introduction The rapid evolution of new technologies has raised some of the weakness of the traditional IT systems. Mergers and acquisitions between companies require fusion of their IT systems but frequently, these cannot easily evolve because of lack of opening. Then they have to be rebuilt. New technologies are now used to build a robust, competitive and open IT system. Most of them allow to consider the system as a part of the company, especially by providing enterprise modeling techniques that encompass aspects related to the IT system along with some related to enterprise itself. However, these techniques are quite young and not strongly experimented, then they are not used on a large scale yet. Among the various enterprise modeling methods and approaches, some of them come from the software engineering area while others come from other areas such as the distributed systems, e.g., the RM-ODP standard [1]. LIP6 1 and EDF 2 aim to promote the use of this standard for the enterprise modeling since it provides consistent and rigorous concepts. The objective is to build enterprise specifications in considering RM-ODP as the modeling language. Thus, an RM-ODP framework is under construction. This will enable to build open systems according to the RM-ODP standard principles by providing a set of services. The framework is then 1 2 Laboratoire d'informatique de Paris 6 Electricité de France designed as a set of modules offering services. These are used by the various actors involved in the system development. Some interactions among the modules or the actors in the system development cycle take place in the form of specifications exchange. Therefore, a service supporting these exchanges must be developed, which is the core element of the framework. A first step in the production of our framework was to developed such a service, the so-called "Backbone". As it provides a support for the RM-ODP specifications exchange, the Backbone encompasses two aspects, one related to the structure of a specification and the other one that deals with the encoding of a specification. The Backbone is then designed as a mould in which users fit their specifications. Aspects related to the specification structure are taking into account by the use of metamodeling techniques provided by the MOF standard [3]. We first have defined an RM-ODP meta-model according to the MOF architecture. Together with this standard are provided associated techniques such as IDL interfaces generation. Moreover, the MOF standard interworks with the XMI standard [4]. Thus, XML files structures can be derived from a meta-model. We gained by using these facilities in order to address the aspects related to the encoding of a specification. Therefore, the Backbone supports two different ways to encode a specification, respectively as a set of objects obtained from IDL interfaces and as an XML file. Specifications can then be exchanged by use of either an ORB or a file system. In order to build the Backbone, we have developed M3J, a tool that implement most of the MOF and XMI functionalities. This article presents the Backbone, i.e., the specifications exchange service of our RM-ODP framework. It first introduces our motivation for choosing RM-ODP as modeling language and describes the scope of our framework. The Part 3 is devoted to the Backbone presentation, namely its functionality and construction. Details are provided on the techniques used to provide the specification structuring and encoding. We partly describe the RM-ODP meta-model we defined. We explain the IDL interfaces and XML files structure generation from this meta-model. In Part 4, we present M3J, the tool we developed to build the Backbone. Finally, we provide some concluding remarks.

2 2. RM-ODP as a modeling language This part briefly presents the ISO RM-ODP standard and some of its concepts in order to explain why we have chosen it as a modeling language [1]. This enables to introduce the scope of our framework Presentation of RM-ODP RM-ODP is an ISO standard. It gives concepts and structuring rules to establish specifications of open distributed systems. RM-ODP proposes to partition the specification of a system according to five viewpoints. A specification of an RM-ODP system is then composed of five specifications, one for each of the five viewpoints. The five viewpoints are the enterprise viewpoint, the computational viewpoint, the information viewpoint, the engineering viewpoint and the technology viewpoint. Each of the viewpoint's specification focuses on a particular aspect of the system. The enterprise viewpoint focuses on the purpose, the scope and the policies that apply to the system. The computational viewpoint focuses on the functionalities performed by the system. The information viewpoint focuses on the information managed by the system. The engineering viewpoint focuses on the architecture of the system. And finally, the technology viewpoint focuses on the technology used by the system. These five viewpoints are autonomous in the sense of all information related to a particular viewpoint is included in the viewpoint's specification; there is no need of the other viewpoints. For example, all information related to the purpose and the scope of the system is included in the enterprise viewpoint's specification. However, viewpoints are not independent, all are linked by correspondences rules. These rules explain the constraints that link information contained in a viewpoint's specification to information contained in another one. For example, there are correspondences rules that explain that information specified according to the information viewpoint are managed by operations specified according to the computational viewpoint. These correspondences rules maintain the coherence of the whole ODP specification, consisting of the union of the five viewpoint's specifications. The RM-ODP provides general concepts that exist in all the viewpoints. For example, RM-ODP defines that an "object" is a model of something of the real world. The concept of "object" is shared between the viewpoints. There are objects in the enterprise, information, computational, engineering and technology viewpoints; all these objects are models of elements of the real world. RM-ODP provides also specific concepts for each of the viewpoints. For example, RM-ODP defines that a "community" is a configuration of objects formed to meet an objective. The concept of "community" is only an enterprise concept, which is not used in the other viewpoints Advantages We aim to provide a framework for building open systems. For this, we have decided to build models of open systems using RM-ODP as the modeling language. This choice can be justified by these following reasons. RM-ODP provides concepts that are consistent, rigorous and completeness. These concepts are the result of several years of research made by international experts on open distributed systems. Since we worked with RM- ODP, we think that the concepts are perfectly adapted to all of the aspects of the phases of the construction of open systems. RM-ODP viewpoints provide a partitioning that is very interesting. Partitioning we used to work with in our company is very close to the RM-ODP one. Then people have no problem to adapt to RM-OP viewpoints. Moreover, we think that the correspondences rules linking the viewpoints are very useful. They guarantee the specification consistency. RM-ODP does not force the use of any notation. This is an advantage because we think that notations give constraints. For example, a very simple notation can be easily used by a lot of people but it has not the same power of expression as a language. In another hand, a very complex notation has the same power of expression as the language but only few people can used it. When a language does not depend on a notation, it can be associated with several notations, one for each use, and then it is not constrained by any of them. RM-ODP does not provide any method. There is no sequence between viewpoints, i.e., a modeler can start his model by building any viewpoint's specification. Moreover, in each viewpoint, RM-ODP does not provide any method. We really think that it is an advantage. Each company frequently uses its own methods, which are well suited to its business. These are not often easily adaptable to other business, and people do not understand that someone forces them to use a method that does not fit to their business. RM-ODP is an international ISO standard. This means that the concepts will not change with the next version beta 2. The viewpoints, concepts, structuring rules and correspondences rules are the RM-ODP foundations, which are stable. Moreover, everybody learning this standard can easily understand any RM-ODP specifications and this contributes to the openness of the systems. RM-ODP is one of the standards that deal with enterprise concepts. The enterprise viewpoint focuses on the "enterprise". It defines concepts such as policy, objective, and community that are very useful when performing enterprise modeling Drawbacks

3 Despite of all the advantages described in the previous Section, RM-ODP has some disadvantages. The goal of our framework is to face these drawbacks. A lot of definitions of RM-ODP concepts are crossed definitions. So it is very difficult to understand them. This is a big disadvantage and maybe one of the reasons for which a lot of people have just heard about RM-ODP. One of the goals of our framework is to introduce smoothly the RM-ODP concepts. RM-ODP does not provide any notation. We already mentioned this as an advantage, but it is also a disadvantage. If no notation exists, nobody can build a specification. In fact, some notations are provided but only to illustrate some examples, i.e., they are not complete and they are not usable. A goal of our framework is to provide at least one notation. RM-ODP does not provide any method. Once again, on one hand, it is an advantage and on the other hand, no provision of at least one method is a disadvantage. Moreover, a method could help to learn RM-ODP concepts. The goal of our framework is to provide at least one method; while being open to host any other methods. From these drawbacks can be deduced another one: no tools exist for RM-ODP. This is an important point because no tools associated with a standard means that nobody will use this standard. The goal of our work is to provide a framework that will host some tools. 3. The Backbone Our RM-ODP framework will offer several services for building RM-ODP systems. It will be composed of modules, for example a module for the generation of RM- ODP specifications, another one for the automatic generation of code and so on. Most of these modules will have to manage RM-ODP specifications. The interactions between these modules will be based on exchanges of specifications. Specifications are built for several reasons. Either the modeler wants to lead the development of the new system, or he wants to explain to the users how the system works, or he wants to explain to another modeler the architecture of the system. We consider all these cases as exchanges of specifications. A modeler exchanges specifications with the developers, with the users or with other modelers. Thus, the first step in the provision of our framework for building ODP systems is to build services that support the exchange of specifications between either modules or users. These services are provided by the socalled "Backbone", the core of the framework. We first define the functionalities of the Backbone and then we explain its construction. 3.1 The Backbone Functionality The Backbone is the core element of the framework, needed for exchanging RM-ODP specifications. It addresses two major issues that are raised when exchanging specifications. The first issue is related to the "What", i.e., what an RM-ODP specification is in terms of semantics and structure. The second issue is related to the "How", i.e., how the specifications must be encoded in order to be exchanged. The Backbone deals with these two aspects by providing a service of "Specification Structuring" and a service of "Specification Encoding". When a user wants to use the Backbone for exchanging an RM-ODP specification, verification must be done to check if his specification is really an RM-ODP specification. The Specification Structuring service is used to check the conformity with the RM-ODP specification's structure. If the conformity is correct, the specification must be encoded into the Backbone format. The Specification Encoding service is used to encode a specification. Then the specification can be exchanged. In fact, the Backbone provides a mould. If users want to exchange specifications, they only must fit their specifications into the mould. This mould realizes both the Specification Structuring and the Specification Encoding services. 3.2 The Backbone Construction In order to provide these services, the Backbone has been built as follows. In the Backbone, the structure of a specification is described by using meta-modeling techniques. We have built an RM-ODP meta-model by using the OMG's MOF standard [3]. A meta-model is a model of model; it defines the structure of a set of models. Then the RM- ODP meta-model defines the structure of all the RM-ODP models. In this way, the Backbone offers the Specification Structuring service. The Specification Encoding service offered by the Backbone is twofold, coming from the use of the MOF standard. This defines rules for generating IDL interfaces that reflect the structure defined by a meta-model. Thus, thanks to these interfaces, a model can be represented by objects. Moreover, the MOF standard interworks with the OMG's XMI standard that defines rules for generating the structure of XML documents reflecting the structure defined by a meta-model [4]. The structure of an XML document is a DTD (Document Type Definition). Thanks to a DTD, a model can be represented by an XML document.

4 Building the Backbone consists of implementing these services provided to the users as a mould. Actually, three moulds are built to realize the various services and they constitute the Backbone (figure 1): A first mould is dedicated to the realization of the Specification Structuring service. It is an abstract mould since it corresponds to the RM-ODP metamodel that defines the structure of all the RM- ODP specifications. It cannot be used as it is but it represents the semantics of RM-ODP specifications. Another mould realizes the part of the Specification Encoding service related to the objects representation of a model. As we said previously, the IDL interfaces generated by the MOF standard's rules reflect the structure defined by a meta-model. Applying these rules to the RM-ODP meta-model provides IDL interfaces that reflect the structure defined by the RM-ODP metamodel, i.e., the structure of all the RM-ODP specifications. These interfaces represent a concrete mould, which is derived from the abstract one since these interfaces reflect the structure of the RM-ODP meta-model. This mould expresses a syntax of an RM-ODP specification. More precisely, this mould is composed of these interfaces and their implementation classes. Implementation classes are realized with CORBA. That's why this encoding uses all the CORBA services. Last, but not least, a mould realizes the other part of the Specification Encoding service related to the XML representation of a model. As mentioned previously, DTD generated by the XMI standard's rules reflect the structure defined by a meta-model. Applying these rules to the RM-ODP meta-model provides a DTD that reflects the structure defined by the RM-ODP meta-model, i.e. the structure of all the RM-ODP specifications. This DTD represents another concrete mould, also derived from the abstract mould. We detail in the next sections this process of construction and the techniques we use. Exchange of RM-ODP specifications What? How? RM-ODP meta-model XMI IDL Fig 1: The construction of the Backbone 3.3. The MOF architecture The MOF standard defines an architecture to classify models in four layers, called the four layer architecture. Let us start with the lowest layer. This layer includes the elements of the real world, which are the elements of the universe of discourse. It does not include any models since it only includes the elements to be modeled, which are data. Thus, this low layer, called M0, is composed of data, also called MOF Objects. The goal of any model is to describe these MOF objects. The layer that includes all the elements modeling data of the M0 layer is called M1 layer. It is composed of models and components of model. The components of models are also called MOF meta-objects. The M0 and M1 layers are layers commonly used in modeling, as they correspond respectively to the universe of discourse and to the model. However, the MOF standard does not define only these two layers since it considers models as a kind of data. So, there are models of models. Then the MOF standard defines the M2 layer that contains all elements modeling elements of M1 layer. In the MOF standard vocabulary, the models of models are called meta-models and they are composed of MOF Classes. To sum up, meta-models belong to M2 layer, they model models and they are composed of MOF classes. Right now, we have presented three of the four layer architecture. From this, it appears that the relationship between two adjacent layers is always the same: "The elements of an M n layer model the elements of an M n-1 layer". Applying several times this process could lead to a n layer architecture, so the question is: when does this process stop? The MOF standard defines that the highest layer is the M3 layer. This layer is composed of models of models of models, i.e., meta-meta-models. In fact, there is only one meta-meta-model in the M3 layer, which is the MOF model and which models all meta-models. The MOF model models itself, that s why the M3 layer is the highest layer The RM-ODP meta-model The figure 2 shows RM-ODP in the context of the four layer architecture. RM-ODP enables to specify distributed systems, those being data that belong to the M0 layer. An RM-ODP specification is a model of a system, so it belongs to the M1 layer. All RM-ODP specifications have the same structure, for example, all of them are composed of five viewpoint s specifications. BACKBONE

5 This structure is modeled in the RM-ODP meta-model, which belongs to the M2 layer and which is modeled by the MOF Model. Behaviour Identifies Role The figure 2 also shows how another standard can be added in the four layer architecture. In the MOF standard, UML is provided as an example; here XXX could be replaced by UML. Action Performs Object MOF Model M3 Layer Fig 3: A part of the RM-ODP Part 2 meta-model. RM-ODP Meta-model RM-ODP Model RM-ODP Model Data Data XXX Meta-model XXX Model Data M2 Layer Fig 2: RM-ODP in the four layer architecture. M1 Layer M0 Layer The RM-ODP meta-model does not exist yet. A part of it should be presented in the next normative part of the RM-ODP standard. It will describe all the concepts needed to build an RM-ODP specification. It should be noted that the RM-ODP meta-model is not equivalent to the RM-ODP standard, it should be considered as a part of the standard. The meta-model will only describe the M1 layer concepts. For example, it will not describe the entity that is specified as an element of the universe of discourse. We are defining an RM-ODP meta-model and a first version is now available. This meta-model is composed of six different parts, one for each viewpoint and one for the common definitions from Part 2 of the RM-ODP standard. As Part 2 defines concepts that are used by all the viewpoints, the five viewpoints meta-models will depend on the Part 2 meta-model. The figure 3 shows a part of our RM-ODP Part 2 meta-model. This part defines four RM-ODP Part 2 concepts. It illustrates that a Behaviour is composed of Action, a Role identifies a Behaviour and an Object performs Action. This illustration is just a piece of our complete version of the Part2 meta-model. In particular, multiplicity, role name and other elements are hidden. The figure 4 shows a part of the RM-ODP enterprise viewpoint meta-model [2]. This part of the enterprise meta-model defines three concepts. It illustrates that a Community is composed of Role and Object, and it shows that an Object fulfils a Role. Once again, this part is just an example, it is not complete; multiplicity, role name and other elements are hidden. The enterprise meta-model depends on the part 2 metamodel, thus the Role concept defined in the enterprise meta-model depends on the Role concept defined in the Part 2 meta-model. In fact, the enterprise meta-model teaches us that an object belonging to a community must fulfill a role of the community and then, the Part 2 meta-model teaches us that this object performs the actions of the behaviour identified by this role. Community Object fulfils Role Fig 4: A part of the RM-ODP enterprise meta-model 3.5. Encoding a model into objects The MOF standard defines rules for the generation of IDL interfaces that reflect the structure defined by a metamodel. These interfaces are used to represent a model with objects. A meta-model defines the structure of a set of models. A model having a structure defined by a meta-model is said to be an instance of this meta-model. The elements that compose the model have types that are defined by the meta-model. For example, if a meta-model defines the concepts "Community" and "Role" then a model that is an instance of this meta-model is composed of elements of type "Community" and "Role". The IDL interfaces generated by the rules defined in the MOF standard represent these types. Thus, objects

6 that have the type defined by these interfaces represent instances of the meta-model (figure 5). Metamodel Metamodel Model Fig 5: The IDL interfaces generation The figure 5 shows a meta-model that defines the structure of a model; the model is an instance of the metamodel. IDL interfaces have been generated; they reflect the structure defined in this meta-model. The interfaces and the meta-model are equivalent. Objects that have the type defined in the IDL interface represent the model. The objects are equivalent to the model; it is just a syntactic transformation Encoding a model into an XML file XMI defines rules for the encoding of a model in an XML file. The rules defined in XMI apply to MOF metamodels. The XMI philosophy is very close to one defined in the MOF standard for the generation of IDL interfaces. The XMI standard defines rules for generating a DTD that reflects the structure defined by a meta-model. Thus, models can be represented by XML files that are in conformance with the DTD. The figure 6 shows the relationship between these rules and MOF meta-models. It should be noted that rules for the DTD generation are only a part of XMI, which is the only one we are interested in for the Backbone. Model rules IDL interface rules DTD XML Implementation Class M2 Layer M1 Layer objects M2 Layer M1 Layer Fig 6: The XMI generation The figure 6 shows a meta-model and an instance of this meta-model. The rules defined in the XMI standard reflect the structure defined in the meta-model. Then, a XML file in conformance with that DTD represents the model. Once again, the XML file and the model are equivalent; it is just a syntactic transformation Conclusion The construction of the Backbone can be sum up in three points. Building the RM-ODP meta-model that is the abstract mould. This mould is the base of the others. Generating the IDL interfaces, building implementation classes of these interfaces and building some tools to manipulate them. This is a concrete mould. Generating the DTD and building some tools for manipulating XML documents those are in conformance with this DTD. This is another concrete mould. Using the Backbone to exchange specifications means choosing one of the concrete moulds of the Backbone and fitting it with the specification to be exchanged. This realizes both the Specification Structuring and the Specification Encoding services (figure 7). Finally, in case of a set of objects, any ORB can be used to physically realize the exchange. In case of XML files, any file system can be suitable. Spec Abstract mould IDL moul d XML moul d specification represented with objects specification Backbon represented with XML files Fig 7: The steps of the specification exchange 4. M3J, a tool implementing MOF and XMI functionalities In order to construct the Backbone, we needed to build the RM-ODP meta-model, to generate its IDL interfaces and implementation classes and to define its DTD. So, we developed M3J (Meta-Meta-Model in Java) that realizes most of the functionalities defined in the MOF and XMI standards. O R B File system

7 We have used M3J for generating the Backbone and it is still used in the construction of our framework. M3J has been totally developed in Java M3J Functionalities M3J mainly provides four sets of functions. The first one is related to the graphic edition of a meta-model. The figure 8 shows the user interface of M3J. Here we can see the part of the meta-model of the enterprise viewpoint. The top window shows the class editor, used to describe all the characteristics of the class. The bottom window shows the graphic interface with some buttons to create new classes or new associations. is the meta-model the harder is the implementation. M3J provides basic implementations of these interfaces as a default option. This is a very helpful starting point for developing complex implementations The Backbone construction with M3J M3J was used for the creation of three moulds of the Backbone, i.e., to build the RM-ODP meta-model, to generate the IDL interfaces and the DTD. The abstract mould The abstract mould is the basis for the construction of the two concrete ones as they derive from it. Then we started in building it. This mould is the RM-ODP metamodel that we defined. We used M3J to draw it. The resulting schema is the abstract mould. The concrete mould for IDL Fig 8: M3J (Meta-meta-model in Java) This interface allows the user to build a meta-model. This meta-model will be the source of other services provided by M3J. The second service that M3J provides is the generation of the IDL interfaces as defined by the MOF standard. This service is compliant with the rules defined in the MOF standard for the generation of IDL interfaces. The interfaces generated for the RM-ODP enterprise metamodel are shown in part 4.2. The third service that M3J provides is the generation of the XML format as defined by the XMI standard. M3J provides the DTD of a meta-model as defined in the XMI standard. This DTD defines the structure of XML documents that represent models. The XML file generated for the RM-ODP enterprise meta-model is shown in part 4.2. The last service that M3J provides is the implementation of the IDL interfaces. The standard MOF defines rules for the generation of IDL interfaces. But these interfaces must be implemented to be useful. Implementing these interfaces is quite easy but the bigger As we said in part 3.5, the MOF standard defines rules for the generation of IDL interfaces that reflect the structure defined by a meta-model. These interfaces and their implementations are one of the two concrete moulds. Parts of these rules are defined as follows: For each class defined in the meta-model, an interface is generated. For each association defined in the meta-model, an interface is generated. Applying these rules to the part of the RM-ODP metamodel described in figure 4 gives us six interfaces; the meta-model defines three classes (Community, Object and Role) and three associations (Community contains Role, Community contains Object, Object fulfills Role). The figure 9 presents a part of the IDL interface of the Community: Interface Community { RoleBag roles(); void add_roles(in Role new_element); ObjectBag objects(); void remove_objects(in Object); } Fig 9: A part of the "Community" IDL interface The mould is composed of these interfaces and their implementations. The figure 10 presents a part of the implementation of the "Community" interface: Public class ComImpl extends _CommunityImplBase { Vector _roles; Vector _objects;

8 } Object[] objects() { Object[] _res = new Object[]; } Fig 10: A part of the implementation of the "Community" interface. When a user wants to use the Backbone with the IDL encoding, he must create his specification using these interfaces and classes. For example, if his specification is composed of one community (let us say the "Fishmonger" Community) he must create a new object of type Community: Community _fishmonger = new ComImpl(); Then, if this community is composed of one object, he must create this object and link it to the community. Object _object1 = new ObjImpl(); _ fishmonger.add_objects(_object1); M3J was used for the generation of IDL interfaces and a basic implementation. It should be noted that this mould is more complex as it provides additional facilities for the specification management. The concrete mould for XML As we said in part 3.6, XMI standard provides rules for the generation of a DTD that reflects the structure defined by a meta-model. Applying these rules for the RM-ODP model gives us the RM-ODP DTD. This DTD defines the structure of XML documents that represent RM-ODP specifications. The figure 11 shows an XML document structured according to this DTD. It represents the specification of the Fishmonger community composed of one object (object1). <Community> <Name> FishMonger </Name> <CommunityCompositions> <Community.objects> <Object> <Name>object1 </Name> </Object> </Community.objects> </CommunityCompositions> </Community> Fig 11: A specification composed of a community with one object encoded with XML. The DTD defines that an XML file representing an RM-ODP specification must begin with the tag <Community>, and then the tag <Name> etc M3J was used for the generation of this DTD. As well as the mould for IDL, this is also more complex as it provides tools to manage such files Other tools More and more tools become available, which provide the MOF and XMI functionalities. dmof is one of them provided by the DSTC [6]. It provides the generation of the IDL interfaces and their implementation. Soon, it will provide the XMI functionalities. dmof does not provide any graphic interface for building meta-model, but a language named MDL. Univers@lys is a tool provided by France Telecom R&D [7]. Although it is not MOF compliant, it offers equivalent services. 5. Further works The Backbone supports services that offer mechanisms for exchanging RM-ODP specification. It is the core element of a framework dedicated to the ODP systems building. Our works now focus on the construction of this framework. Two issues are addressed. The first issue is related to the specification notation. Our RM-ODP framework will provide a notation for building RM-ODP specifications. We could use the XML format as a notation, but we think that this is too complex and not suitable to be used by designers. Our choice is to use UML or to provide a graphical notation such as an UML-like. The second issue is related to methods for creating specifications. The RM-ODP framework must be free from method in the sense that any method must be suitable when using it. However, it must provide at least one method. Works for defining a methodology based on RM-ODP have been realized [5]. On the other hand, we are currently defining a methodology for designing multiagent systems [8]. These could help out and might be adapted to our framework. 6. Conclusion In order to build open distributed systems, we aim to provide an RM-ODP framework designed as a set of services. The major one is the Specification Exchange Service, called the Backbone. This paper has presented it. For its building, we have used facilities providing from the MOF and XMI standards. The Backbone can then offer two various ways for exchanging specifications, either as a set of objects or as an XML file. Therefore, the exchanges can be done with any ORB when using the IDL encoding or with any file systems when using the XML encoding. Moreover, the Backbone guarantees that

9 the specification to be exchanged is in conformance with the RM-ODP. The Backbone has been built by use of M3J, a tool we developed and that implements most of the MOF and XMI standards functionalities. M3J as well as the Backbone are not dedicated to RM- ODP in the sense that they can be used to create any meta-model from which IDL interfaces and their implementation or XML files structures will be derived. Several sets of three moulds can be created, each set corresponding to a meta-model. Actually, the Backbone can include as many sets of three moulds as is necessary, one set per meta-model. 7. References [1] ISO/IEC IS x ITU-T Rec. X90x, ODP Reference Model Part x, [2] ISO/IEC JTC1/SC7 CD 15414, ODP Reference Model : Enterprise Viewpoint, January [3] OMG, MOF Specification v1.3, July [4] OMG, XML Metadata Interchange (XMI) v1.0, October ad/ [5] J.M. Cornily, M. Belaunde, E. Debeau: Specifying distributed object applications Using the Reference Model for Open Distributed Processing and the Unified Modeling Language In Proceedings of the 3rd International Enterprise Distributing Object Computing Conference (EDOC'99), IEEE Press, Mannheim, Germany, September [6] dmof: [7] M. Belaunde A Pragmatic Approach for Building a User-friendlyand Flexible UML Model Repository ; UML'99 [8] J. F. Dauchez and M. P. Gervais, Specifying and Verifying the Behaviour of Telecommunications Services, In Proceedings of the 6th International Conference on Intelligence in Networks (ICIN'2000), Arcachon, France, January 2000, pp

An introduction to MOF MetaObject Facility.

An introduction to MOF MetaObject Facility. An introduction to MOF MetaObject Facility pierre-alain.muller@irisa.fr About The MetaObject Facility Specification is the foundation of OMG's industry-standard standard environment where models can be

More information

Rich Hilliard 20 February 2011

Rich Hilliard 20 February 2011 Metamodels in 42010 Executive summary: The purpose of this note is to investigate the use of metamodels in IEEE 1471 ISO/IEC 42010. In the present draft, metamodels serve two roles: (1) to describe the

More information

METADATA INTERCHANGE IN SERVICE BASED ARCHITECTURE

METADATA INTERCHANGE IN SERVICE BASED ARCHITECTURE UDC:681.324 Review paper METADATA INTERCHANGE IN SERVICE BASED ARCHITECTURE Alma Butkovi Tomac Nagravision Kudelski group, Cheseaux / Lausanne alma.butkovictomac@nagra.com Dražen Tomac Cambridge Technology

More information

ISO/IEC FDIS INTERNATIONAL STANDARD FINAL DRAFT. Information technology Open Distributed Processing Type Repository Function ISO/IEC JTC 1

ISO/IEC FDIS INTERNATIONAL STANDARD FINAL DRAFT. Information technology Open Distributed Processing Type Repository Function ISO/IEC JTC 1 FINAL DRAFT INTERNATIONAL STANDARD ISO/IEC FDIS 4769 ISO/IEC JTC Secretariat: ANSI Voting begins on: 2000-08-3 Voting terminates on: 2000-0-3 Information technology Open Distributed Processing Type Repository

More information

ISO/IEC JTC1/SC7 /N3016

ISO/IEC JTC1/SC7 /N3016 ISO/IEC JTC1/SC7 Software and Systems Engineering Secretariat: CANADA (SCC) ISO/IEC JTC1/SC7 /N3016 2004-04-07 Document Type Title Source Framework Framework for ISO/IEC System and Software Engineering

More information

Utilisation de UML pour exprimer les concepts entreprise de ODP

Utilisation de UML pour exprimer les concepts entreprise de ODP 6 LABORATOIRE D'INFORMATIQUE DE PARIS 6 Systèmes Répartis et Coopératifs Utilisation de UML pour exprimer les concepts entreprise de ODP X. Blanc, M.-P. Gervais, R. Le-Delliou LIP6 1999 / 024 novembre

More information

ISO/IEC INTERNATIONAL STANDARD

ISO/IEC INTERNATIONAL STANDARD INTERNATIONAL STANDARD This is a preview - click here to buy the full publication ISO/IEC 19500-3 First edition 2012-04-15 Information technology Object Management Group Common Object Request Broker Architecture

More information

TWO APPROACHES IN SYSTEM MODELING AND THEIR ILLUSTRATIONS WITH MDA AND RM-ODP

TWO APPROACHES IN SYSTEM MODELING AND THEIR ILLUSTRATIONS WITH MDA AND RM-ODP TWO APPROACHES IN SYSTEM MODELING AND THEIR ILLUSTRATIONS WITH MDA AND RM-ODP Andrey Naumenko, Alain Wegmann Laboratory of Systemic Modeling, Swiss Federal Institute of Technology - Lausanne, EPFL-I&C-LAMS,1015

More information

From Models to Components. Rapid Service Creation with

From Models to Components. Rapid Service Creation with From Models to Components Rapid Service Creation with Marc Born, Olaf Kath {born kath}@ikv.de Evolutions in Software Construction C O M P L E X I T Y Model Driven Architectures Meta Object Facility and

More information

Second OMG Workshop on Web Services Modeling. Easy Development of Scalable Web Services Based on Model-Driven Process Management

Second OMG Workshop on Web Services Modeling. Easy Development of Scalable Web Services Based on Model-Driven Process Management Second OMG Workshop on Web Services Modeling Easy Development of Scalable Web Services Based on Model-Driven Process Management 88 solutions Chief Technology Officer 2003 Outline! Introduction to Web Services!

More information

From Object Composition to Model Transformation with the MDA

From Object Composition to Model Transformation with the MDA From Object Composition to Transformation with the MDA Jean Bézivin University of Nantes 2, rue de la Houssinière, BP 92208 44322 Nantes cedex 3, France Jean.Bezivin@sciences.univ-nantes.fr Abstract The

More information

AN INTEGRATED COMPONENT-BASED APPROACH TO ENTERPRISE SYSTEM SPECIFICATION AND DEVELOPMENT

AN INTEGRATED COMPONENT-BASED APPROACH TO ENTERPRISE SYSTEM SPECIFICATION AND DEVELOPMENT AN INTEGRATED COMPONENT-BASED APPROACH TO ENTERPRISE SYSTEM SPECIFICATION AND DEVELOPMENT Zoran Stojanovic, Ajantha Dahanayake Faculty of Information Technology and Systems, Delft University of Technology,

More information

Use of Models and Modelling Techniques for Service Development

Use of Models and Modelling Techniques for Service Development Appears in M.J. Mendes, R. Suomi and C. Passos (eds.). Digital Communities in a Networked Society: ecommerce, egovernment and ebusiness, Kluwer Academic Publishers, 2004. Use of Models and Modelling Techniques

More information

The Eclipse Modeling Framework and MDA Status and Opportunities

The Eclipse Modeling Framework and MDA Status and Opportunities The Eclipse Modeling Framework and MDA Status and Opportunities David Frankel Consulting df@davidfrankelconsulting.com www.davidfrankelconsulting.com Portions adapted from the book Model Driven Architecture:

More information

Ingegneria del Software Corso di Laurea in Informatica per il Management. Introduction to UML

Ingegneria del Software Corso di Laurea in Informatica per il Management. Introduction to UML Ingegneria del Software Corso di Laurea in Informatica per il Management Introduction to UML Davide Rossi Dipartimento di Informatica Università di Bologna Modeling A model is an (abstract) representation

More information

INTERNATIONAL TELECOMMUNICATION UNION. SERIES X: DATA NETWORKS AND OPEN SYSTEM COMMUNICATIONS Open distributed processing

INTERNATIONAL TELECOMMUNICATION UNION. SERIES X: DATA NETWORKS AND OPEN SYSTEM COMMUNICATIONS Open distributed processing INTERNATIONAL TELECOMMUNICATION UNION ITU-T X.911 TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU (10/2001) SERIES X: DATA NETWORKS AND OPEN SYSTEM COMMUNICATIONS Open distributed processing Information

More information

Computation Independent Model (CIM): Platform Independent Model (PIM): Platform Specific Model (PSM): Implementation Specific Model (ISM):

Computation Independent Model (CIM): Platform Independent Model (PIM): Platform Specific Model (PSM): Implementation Specific Model (ISM): viii Preface The software industry has evolved to tackle new approaches aligned with the Internet, object-orientation, distributed components and new platforms. However, the majority of the large information

More information

Event Metamodel and Profile (EMP) Proposed RFP Updated Sept, 2007

Event Metamodel and Profile (EMP) Proposed RFP Updated Sept, 2007 Event Metamodel and Profile (EMP) Proposed RFP Updated Sept, 2007 Robert Covington, CTO 8425 woodfield crossing boulevard suite 345 indianapolis in 46240 317.252.2636 Motivation for this proposed RFP 1.

More information

RM-ODP: The ISO Reference Model for Open Distributed Processing

RM-ODP: The ISO Reference Model for Open Distributed Processing RM-ODP: The ISO Reference Model for Open Distributed Processing Antonio Vallecillo ETSI Informática. Universidad de Málaga av@lcc.uma.es 1. Introduction As software technology becomes a core part of business

More information

Outline. A little history. Outline. The Unified Modeling Language Opportunities and Challenges for Formal Methods

Outline. A little history. Outline. The Unified Modeling Language Opportunities and Challenges for Formal Methods Outline The Unified Modeling Language Opportunities and Challenges for Formal Methods An update on UML Language definition Tools A precise OO meta-modeling facility - MMF Stuart Kent University of Kent

More information

WHY WE NEED AN XML STANDARD FOR REPRESENTING BUSINESS RULES. Introduction. Production rules. Christian de Sainte Marie ILOG

WHY WE NEED AN XML STANDARD FOR REPRESENTING BUSINESS RULES. Introduction. Production rules. Christian de Sainte Marie ILOG WHY WE NEED AN XML STANDARD FOR REPRESENTING BUSINESS RULES Christian de Sainte Marie ILOG Introduction We are interested in the topic of communicating policy decisions to other parties, and, more generally,

More information

A state-based 3-way batch merge algorithm for models serialized in XMI

A state-based 3-way batch merge algorithm for models serialized in XMI A state-based 3-way batch merge algorithm for models serialized in XMI Aron Lidé Supervisor: Lars Bendix Department of Computer Science Faculty of Engineering Lund University November 2011 Abstract With

More information

Executive Summary. Round Trip Engineering of Space Systems. Change Log. Executive Summary. Visas

Executive Summary. Round Trip Engineering of Space Systems. Change Log. Executive Summary. Visas Reference: egos-stu-rts-rp-1002 Page 1/7 Authors: Andrey Sadovykh (SOFTEAM) Contributors: Tom Ritter, Andreas Hoffmann, Jürgen Großmann (FHG), Alexander Vankov, Oleg Estekhin (GTI6) Visas Surname - Name

More information

Metamodeling. Janos Sztipanovits ISIS, Vanderbilt University

Metamodeling. Janos Sztipanovits ISIS, Vanderbilt University Metamodeling Janos ISIS, Vanderbilt University janos.sztipanovits@vanderbilt.edusztipanovits@vanderbilt edu Content Overview of Metamodeling Abstract Syntax Metamodeling Concepts Metamodeling languages

More information

Object Management Group Model Driven Architecture (MDA) MDA Guide rev. 2.0 OMG Document ormsc/

Object Management Group Model Driven Architecture (MDA) MDA Guide rev. 2.0 OMG Document ormsc/ Executive Summary Object Management Group Model Driven Architecture (MDA) MDA Guide rev. 2.0 OMG Document ormsc/2014-06-01 This guide describes the Model Driven Architecture (MDA) approach as defined by

More information

Future Directions for SysML v2 INCOSE IW MBSE Workshop January 28, 2017

Future Directions for SysML v2 INCOSE IW MBSE Workshop January 28, 2017 Future Directions for SysML v2 INCOSE IW MBSE Workshop January 28, 2017 Sanford Friedenthal safriedenthal@gmail.com 1/30/2017 Agenda Background System Modeling Environment (SME) SysML v2 Requirements Approach

More information

Generalized Document Data Model for Integrating Autonomous Applications

Generalized Document Data Model for Integrating Autonomous Applications 6 th International Conference on Applied Informatics Eger, Hungary, January 27 31, 2004. Generalized Document Data Model for Integrating Autonomous Applications Zsolt Hernáth, Zoltán Vincellér Abstract

More information

TINA-CAT WorkGroup Request For Proposals

TINA-CAT WorkGroup Request For Proposals TINA-CAT WorkGroup Request For Proposals TINA Conformance Testing Framework Document information Title: TINA Conformance Testing Framework RfP Version: 1.0: Approved and Released Date: July 19, 1999 1.

More information

Chapter 3 Research Method

Chapter 3 Research Method Chapter 3 Research Method 3.1 A Ontology-Based Method As we mention in section 2.3.6, we need a common approach to build up our ontologies for different B2B standards. In this chapter, we present a ontology-based

More information

Model Driven Development Unified Modeling Language (UML)

Model Driven Development Unified Modeling Language (UML) Model Driven Development Unified Modeling Language (UML) An Overview UML UML is a modeling notation standardized by OMG (proposal 1997, ver.1.1 in 1998, ver. 2.0 in 2004) now in 2.4.1 mature based on notations

More information

Model Driven Architecture

Model Driven Architecture Model Driven Architecture Vision VS Reality EDOC 2001 September 4-7, Seattle, USA Sridhar Iyengar Unisys Fellow Member, OMG Architecture Board sridhar.iyengar2@unisys.com Slide 1 Model Driven Architecture

More information

SUMMARY: MODEL DRIVEN SECURITY

SUMMARY: MODEL DRIVEN SECURITY SUMMARY: MODEL DRIVEN SECURITY JAN-FILIP ZAGALAK, JZAGALAK@STUDENT.ETHZ.CH Model Driven Security: From UML Models to Access Control Infrastructres David Basin, Juergen Doser, ETH Zuerich Torsten lodderstedt,

More information

Sequence Diagram Generation with Model Transformation Technology

Sequence Diagram Generation with Model Transformation Technology , March 12-14, 2014, Hong Kong Sequence Diagram Generation with Model Transformation Technology Photchana Sawprakhon, Yachai Limpiyakorn Abstract Creating Sequence diagrams with UML tools can be incomplete,

More information

Methods for the Development

Methods for the Development Methods for the Development Of Dependable and Adaptive Information Systems Carolina Gomez Hernandez Index of Contents History of Modeling Methods for the Development of DAIS: Model Driven Architecture

More information

OMG Specifications for Enterprise Interoperability

OMG Specifications for Enterprise Interoperability OMG Specifications for Enterprise Interoperability Brian Elvesæter* Arne-Jørgen Berre* *SINTEF ICT, P. O. Box 124 Blindern, N-0314 Oslo, Norway brian.elvesater@sintef.no arne.j.berre@sintef.no ABSTRACT:

More information

Model Driven Production of Domain-Specific Modeling Tools

Model Driven Production of Domain-Specific Modeling Tools Model Driven Production of Domain-Specific Modeling Tools Bassem KOSAYBA, Raphaël MARVIE, Jean-Marc GEIB Laboratoire d Informatique Fondamentale de Lille UMR CNRS 8022 59655 Villeneuve d Ascq {kosayba,marvie,geib}@lifl.fr

More information

An UML-XML-RDB Model Mapping Solution for Facilitating Information Standardization and Sharing in Construction Industry

An UML-XML-RDB Model Mapping Solution for Facilitating Information Standardization and Sharing in Construction Industry An UML-XML-RDB Model Mapping Solution for Facilitating Information Standardization and Sharing in Construction Industry I-Chen Wu 1 and Shang-Hsien Hsieh 2 Department of Civil Engineering, National Taiwan

More information

Model-Driven QoS Provisioning Techniques for CCM DRE Systems

Model-Driven QoS Provisioning Techniques for CCM DRE Systems Model-Driven QoS Provisioning Techniques for CCM DRE Systems Stoyan Paunov, Gan Deng, Douglas C. Schmidt, and Anirudha Gokhale ISIS, Vanderbilt University Motivation for QoS-enabled Middleware Trends!

More information

Model-Based Social Networking Over Femtocell Environments

Model-Based Social Networking Over Femtocell Environments Proc. of World Cong. on Multimedia and Computer Science Model-Based Social Networking Over Femtocell Environments 1 Hajer Berhouma, 2 Kaouthar Sethom Ben Reguiga 1 ESPRIT, Institute of Engineering, Tunis,

More information

On the link between Architectural Description Models and Modelica Analyses Models

On the link between Architectural Description Models and Modelica Analyses Models On the link between Architectural Description Models and Modelica Analyses Models Damien Chapon Guillaume Bouchez Airbus France 316 Route de Bayonne 31060 Toulouse {damien.chapon,guillaume.bouchez}@airbus.com

More information

Standard Business Rules Language: why and how? ICAI 06

Standard Business Rules Language: why and how? ICAI 06 Standard Business Rules Language: why and how? ICAI 06 M. Diouf K. Musumbu S. Maabout LaBRI (UMR 5800 du CNRS), 351, cours de la Libération, F-33.405 TALENCE Cedex e-mail: {diouf, musumbu, maabout}@labri.fr

More information

Meta Architecting: Towered a New Generation of Architecture Description Languages

Meta Architecting: Towered a New Generation of Architecture Description Languages Journal of Computer Science 1 (4): 454-460, 2005 ISSN 1549-3636 Science Publications, 2005 Meta Architecting: Towered a New Generation of Architecture Description Languages Adel Smeda, Tahar Khammaci and

More information

A TESTING METHODOLOGY FOR AN OPEN SOFTWARE E-LEARNING PLATFORM

A TESTING METHODOLOGY FOR AN OPEN SOFTWARE E-LEARNING PLATFORM A TESTING METHODOLOGY FOR AN OPEN SOFTWARE E-LEARNING PLATFORM Ana Cavalli, Stéphane Maag, Sofia Papagiannaki and Georgios Verigakis GET / Institut National des Télécommunications Laboratoire SAMOVAR /

More information

Fundamentals to Creating Architectures using ISO/IEC/IEEE Standards

Fundamentals to Creating Architectures using ISO/IEC/IEEE Standards Fundamentals to Creating Architectures using ISO/IEC/IEEE Standards What to Architect? How to Architect? IEEE Goals and Objectives Chartered by IEEE Software Engineering Standards Committee to: Define

More information

Software Language Engineering of Architectural Viewpoints

Software Language Engineering of Architectural Viewpoints Software Language Engineering of Architectural Viewpoints Elif Demirli and Bedir Tekinerdogan Department of Computer Engineering, Bilkent University, Ankara 06800, Turkey {demirli,bedir}@cs.bilkent.edu.tr

More information

It s all Done with Mirrors Patterns and OCL. KMF Kent Modelling Framework D.H.Akehurst and O.Patrascoiu

It s all Done with Mirrors Patterns and OCL. KMF Kent Modelling Framework D.H.Akehurst and O.Patrascoiu It s all Done with Mirrors Patterns and OCL KMF Kent Modelling Framework D.H.Akehurst and O.Patrascoiu Goal Model Implementation MDA Goal Meta-Model Specification Tool Code Generation Is a Transformation

More information

ISO/IEC JTC1/SC7 /N3209

ISO/IEC JTC1/SC7 /N3209 ISO/IEC JTC1/SC7 Software and Systems Engineering Secretariat: CANADA (SCC) ISO/IEC JTC1/SC7 /N3209 2005-05-17 Document Type Title Liaison Documents Liaison statements from ITU-T SG 17 Source ITU-T SG

More information

Beginning To Define ebxml Initial Draft

Beginning To Define ebxml Initial Draft Beginning To Define ebxml Initial Draft File Name Version BeginningToDefineebXML 1 Abstract This document provides a visual representation of how the ebxml Architecture could work. As ebxml evolves, this

More information

OCL Support in MOF Repositories

OCL Support in MOF Repositories OCL Support in MOF Repositories Joachim Hoessler, Michael Soden Department of Computer Science Technical University Berlin hoessler@cs.tu-berlin.de, soden@cs.tu-berlin.de Abstract From metamodels that

More information

Introduction. Chapter 1. What Is Visual Modeling? The Triangle for Success. The Role of Notation. History of the UML. The Role of Process

Introduction. Chapter 1. What Is Visual Modeling? The Triangle for Success. The Role of Notation. History of the UML. The Role of Process Quatrani_Ch.01.fm Page 1 Friday, October 27, 2000 9:02 AM Chapter 1 Introduction What Is Visual Modeling? The Triangle for Success The Role of Notation History of the UML The Role of Process What Is Iterative

More information

Spemmet - A Tool for Modeling Software Processes with SPEM

Spemmet - A Tool for Modeling Software Processes with SPEM Spemmet - A Tool for Modeling Software Processes with SPEM Tuomas Mäkilä tuomas.makila@it.utu.fi Antero Järvi antero.jarvi@it.utu.fi Abstract: The software development process has many unique attributes

More information

Design of Telecommunication Services Based on Software Agent Technology and Formal Methods

Design of Telecommunication Services Based on Software Agent Technology and Formal Methods Design of Telecommunication Services Based on Software Agent Technology and Formal Methods Marie-Pierre GERVAIS(*) and Nicolas RUFFEL Université René Descartes(*) - Université Pierre et Marie Curie Laboratoire

More information

DITA for Enterprise Business Documents Sub-committee Proposal Background Why an Enterprise Business Documents Sub committee

DITA for Enterprise Business Documents Sub-committee Proposal Background Why an Enterprise Business Documents Sub committee DITA for Enterprise Business Documents Sub-committee Proposal Background Why an Enterprise Business Documents Sub committee Documents initiate and record business change. It is easy to map some business

More information

ISO/IEC INTERNATIONAL STANDARD. Information technology Open Distributed Processing Interface references and binding

ISO/IEC INTERNATIONAL STANDARD. Information technology Open Distributed Processing Interface references and binding INTERNATIONAL STANDARD ISO/IEC 14753 First edition 1999-07-15 Information technology Open Distributed Processing Interface references and binding Technologies de l'information Traitement distribué ouvert

More information

Metamodeling with Metamodels. Using. UML/MOF including OCL

Metamodeling with Metamodels. Using. UML/MOF including OCL Metamodeling with Metamodels Using UML/MOF including OCL Introducing Metamodels (Wikipedia) A metamodel is a model of a model An instantiation of metamodel gives a model Metamodeling is the process of

More information

ISO/IEC INTERNATIONAL STANDARD. Information technology Open Distributed Processing Unified Modeling Language (UML) Version 1.4.

ISO/IEC INTERNATIONAL STANDARD. Information technology Open Distributed Processing Unified Modeling Language (UML) Version 1.4. INTERNATIONAL STANDARD ISO/IEC 19501 First edition 2005-04-01 Information technology Open Distributed Processing Unified Modeling Language (UML) Version 1.4.2 Technologies de l'information Traitement distribué

More information

Developing Software Applications Using Middleware Infrastructure: Role Based and Coordination Component Framework Approach

Developing Software Applications Using Middleware Infrastructure: Role Based and Coordination Component Framework Approach Developing Software Applications Using Middleware Infrastructure: Role Based and Coordination Component Framework Approach Ninat Wanapan and Somnuk Keretho Department of Computer Engineering, Kasetsart

More information

Modelling in Enterprise Architecture. MSc Business Information Systems

Modelling in Enterprise Architecture. MSc Business Information Systems Modelling in Enterprise Architecture MSc Business Information Systems Models and Modelling Modelling Describing and Representing all relevant aspects of a domain in a defined language. Result of modelling

More information

MDA Journal. BPMI and OMG: The BPM Merger A BPT COLUMN. David S. Frankel Lead Standards Architect - Model Driven Systems SAP Labs.

MDA Journal. BPMI and OMG: The BPM Merger A BPT COLUMN. David S. Frankel Lead Standards Architect - Model Driven Systems SAP Labs. A BPT COLUMN MDA Journal December 2005 David S. Frankel Lead Standards Architect - Model Driven Systems SAP Labs David.Frankel@SAP.com https://www.sdn.sap.com/irj/sdn/ weblogs?blog=/pub/u/55914 Contents

More information

Proposed Revisions to ebxml Technical. Architecture Specification v1.04

Proposed Revisions to ebxml Technical. Architecture Specification v1.04 Proposed Revisions to ebxml Technical Architecture Specification v1.04 Business Process Team 11 May 2001 (This document is the non-normative version formatted for printing, July 2001) Copyright UN/CEFACT

More information

UML 2.5: Specification Simplification

UML 2.5: Specification Simplification A division of Data Access Technologies, Inc. UML 2.5: Specification Simplification Presented at the Third Biannual Workshop on Eclipse Open Source Software and OMG Open Specifications Ed Seidewitz Timeline

More information

Meta Object Facility (MOF) Specification

Meta Object Facility (MOF) Specification Date: July 2005 Meta Object Facility (MOF) Specification Version 1.4.1 formal/05-05-05 This version is also available from ISO as ISO/IEC 19502. Contents Foreword... ix Introduction... xi 1 Scope...1

More information

Meta-Modeling and Modeling Languages

Meta-Modeling and Modeling Languages member of Meta-Modeling and Modeling Languages Models and Modelling Model A reproduction of the part of reality which contains the essential aspects to be investigated. Modelling Describing and Representing

More information

ISO INTERNATIONAL STANDARD. Financial services Universal financial industry message scheme Part 8: ASN.1 generation

ISO INTERNATIONAL STANDARD. Financial services Universal financial industry message scheme Part 8: ASN.1 generation INTERNATIONAL STANDARD ISO 20022-8 First edition 2013-05-01 Financial services Universal financial industry message scheme Part 8: ASN.1 generation Services financiers Schéma universel de messages pour

More information

ISO/IEC JTC 1/SC 32 N 2018

ISO/IEC JTC 1/SC 32 N 2018 ISO/IEC JTC 1/SC 32 N 2018 Date: 2010-07-15 REPLACES: ISO/IEC JTC 1/SC 32 Data Management and Interchange Secretariat: United States of America (ANSI) Administered by Farance Inc. on behalf of ANSI DOCUMENT

More information

BLU AGE 2009 Edition Agile Model Transformation

BLU AGE 2009 Edition Agile Model Transformation BLU AGE 2009 Edition Agile Model Transformation Model Driven Modernization for Legacy Systems 1 2009 NETFECTIVE TECHNOLOGY -ne peut être copiésans BLU AGE Agile Model Transformation Agenda Model transformation

More information

ADT: Eclipse development tools for ATL

ADT: Eclipse development tools for ATL ADT: Eclipse development tools for ATL Freddy Allilaire (freddy.allilaire@laposte.net) Tarik Idrissi (tarik.idrissi@laposte.net) Université de Nantes Faculté de Sciences et Techniques LINA (Laboratoire

More information

Coral: A Metamodel Kernel for Transformation Engines

Coral: A Metamodel Kernel for Transformation Engines Coral: A Metamodel Kernel for Transformation Engines Marcus Alanen and Ivan Porres TUCS Turku Centre for Computer Science Department of Computer Science, Åbo Akademi University Lemminkäisenkatu 14, FIN-20520

More information

Model Driven Architecture Targets Middleware Interoperability Challenges

Model Driven Architecture Targets Middleware Interoperability Challenges Model Driven Architecture Targets Middleware Interoperability Challenges by Richard Soley Chairman and Chief Executive Officer Object Management Group and the OMG Staff Strategy Group "CORBA was a powerful

More information

3rd Lecture Languages for information modeling

3rd Lecture Languages for information modeling 3rd Lecture Languages for information modeling Agenda Languages for information modeling UML UML basic concepts Modeling by UML diagrams CASE tools: concepts, features and objectives CASE toolset architecture

More information

An Ontological Analysis of Metamodeling Languages

An Ontological Analysis of Metamodeling Languages An Ontological Analysis of Metamodeling Languages Erki Eessaar and Rünno Sgirka 2 Department of Informatics, Tallinn University of Technology, Estonia, eessaar@staff.ttu.ee 2 Department of Informatics,

More information

Using UML To Define XML Document Types

Using UML To Define XML Document Types Using UML To Define XML Document Types W. Eliot Kimber ISOGEN International, A DataChannel Company Created On: 10 Dec 1999 Last Revised: 14 Jan 2000 Defines a convention for the use of UML to define XML

More information

MythoLogic: problems and their solutions in the evolution of a project

MythoLogic: problems and their solutions in the evolution of a project 6 th International Conference on Applied Informatics Eger, Hungary, January 27 31, 2004. MythoLogic: problems and their solutions in the evolution of a project István Székelya, Róbert Kincsesb a Department

More information

Proposed Revisions to ebxml Technical Architecture Specification v ebxml Business Process Project Team

Proposed Revisions to ebxml Technical Architecture Specification v ebxml Business Process Project Team 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 Proposed Revisions to ebxml Technical Architecture Specification v1.0.4 ebxml Business Process Project Team 11

More information

MDA and Integration of Legacy Systems: An Industrial Case Study

MDA and Integration of Legacy Systems: An Industrial Case Study MDA and Integration of Legacy Systems: An Industrial Case Study Parastoo Mohagheghi 1, Jan Pettersen Nytun 2, Selo 2, Warsun Najib 2 1 Ericson Norway-Grimstad, Postuttak, N-4898, Grimstad, Norway 1 Department

More information

This paper is more intended to set up a basis for a constructive discussion than to offer definitive answers and closed solutions.

This paper is more intended to set up a basis for a constructive discussion than to offer definitive answers and closed solutions. The TopModL Initiative Pierre-Alain Muller pa.muller@uha.fr INRIA/Irisa Université de Rennes France Cédric Dumoulin cedric.dumoulin@lifl.fr LIFL Université de Lille France Frédéric Fondement frederic.fondement@epfl.ch

More information

Metadata Repository Support for Legacy Knowledge Discovery in Public Administrations

Metadata Repository Support for Legacy Knowledge Discovery in Public Administrations Metadata Repository Support for Legacy Knowledge Discovery in Public Administrations Adriana Maria C.M. Figueiredo 1, Aqueo Kamada 1, Luciano L. Damasceno 1, Marcos Antonio Rodrigues 1, and Manuel de Jesus

More information

The Unified Modelling Language. Example Diagrams. Notation vs. Methodology. UML and Meta Modelling

The Unified Modelling Language. Example Diagrams. Notation vs. Methodology. UML and Meta Modelling UML and Meta ling Topics: UML as an example visual notation The UML meta model and the concept of meta modelling Driven Architecture and model engineering The AndroMDA open source project Applying cognitive

More information

Semantic Information Modeling for Federation (SIMF)

Semantic Information Modeling for Federation (SIMF) Purpose Semantic Information Modeling for Federation (SIMF) Overview V0.2-04/21/2011 The Architecture Ecosystem SIG of the Object Management Group (OMG) is in the process of drafting an RFP focused on

More information

Introduction to Software Engineering 10. Software Architecture

Introduction to Software Engineering 10. Software Architecture Introduction to Software Engineering 10. Software Architecture Roadmap > What is Software Architecture? > Coupling and Cohesion > Architectural styles: Layered Client-Server Blackboard, Dataflow,... >

More information

Christian Doppler Laboratory

Christian Doppler Laboratory Christian Doppler Laboratory Software Engineering Integration For Flexible Automation Systems AutomationML Models (in EMF and EA) for Modelers and Software Developers Emanuel Mätzler Institute of Software

More information

UML big picture. Perdita Stevens. School of Informatics University of Edinburgh

UML big picture. Perdita Stevens. School of Informatics University of Edinburgh UML big picture Perdita Stevens School of Informatics University of Edinburgh Plan Whence UML? Parts of UML How it all fits together UML as a language Consistency: what does it mean, do we need it? Defining

More information

Semantic Web Domain Knowledge Representation Using Software Engineering Modeling Technique

Semantic Web Domain Knowledge Representation Using Software Engineering Modeling Technique Semantic Web Domain Knowledge Representation Using Software Engineering Modeling Technique Minal Bhise DAIICT, Gandhinagar, Gujarat, India 382007 minal_bhise@daiict.ac.in Abstract. The semantic web offers

More information

UML Framework for Intensive Signal Processing Embedded Applications

UML Framework for Intensive Signal Processing Embedded Applications LIFL 2002-n 07 Juillet 2002 Publication LIFL 2002-n 07 UML Framework for Intensive Signal Processing Embedded Applications Cédric Dumoulin, Jean-Luc Dekeyser Laboratoire d'informatique Fondamentale de

More information

ISO/IEC TR TECHNICAL REPORT. Information technology Procedures for achieving metadata registry (MDR) content consistency Part 1: Data elements

ISO/IEC TR TECHNICAL REPORT. Information technology Procedures for achieving metadata registry (MDR) content consistency Part 1: Data elements TECHNICAL REPORT ISO/IEC TR 20943-1 First edition 2003-08-01 Information technology Procedures for achieving metadata registry (MDR) content consistency Part 1: Data elements Technologies de l'information

More information

ITU-T Y Next generation network evolution phase 1 Overview

ITU-T Y Next generation network evolution phase 1 Overview I n t e r n a t i o n a l T e l e c o m m u n i c a t i o n U n i o n ITU-T Y.2340 TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU (09/2016) SERIES Y: GLOBAL INFORMATION INFRASTRUCTURE, INTERNET PROTOCOL

More information

Oral Questions. Unit-1 Concepts. Oral Question/Assignment/Gate Question with Answer

Oral Questions. Unit-1 Concepts. Oral Question/Assignment/Gate Question with Answer Unit-1 Concepts Oral Question/Assignment/Gate Question with Answer The Meta-Object Facility (MOF) is an Object Management Group (OMG) standard for model-driven engineering Object Management Group (OMG)

More information

The Model-Driven Semantic Web Emerging Standards & Technologies

The Model-Driven Semantic Web Emerging Standards & Technologies The Model-Driven Semantic Web Emerging Standards & Technologies Elisa Kendall Sandpiper Software March 24, 2005 1 Model Driven Architecture (MDA ) Insulates business applications from technology evolution,

More information

SC32 WG2 Metadata Standards Tutorial

SC32 WG2 Metadata Standards Tutorial SC32 WG2 Metadata Standards Tutorial Metadata Registries and Big Data WG2 N1945 June 9, 2014 Beijing, China WG2 Viewpoint Big Data magnifies the existing challenges and issues of managing and interpreting

More information

Specifying QoS Structural Constraints in RM- ODP

Specifying QoS Structural Constraints in RM- ODP , July 6-8, 2011, London, U.K. Specifying QoS Structural Constraints in RM- ODP Jalal Laassiri, Member, IAENG, Salah-ddine Krit, Said El Hajji and Mohamed Bouhdadi Abstract QoS already forms an important

More information

A Formal V&V Framework for UML Models Based on Model Transformation Techniques

A Formal V&V Framework for UML Models Based on Model Transformation Techniques A Formal V&V Framework for UML Models Based on Model Transformation Techniques Soon-Kyeong Kim and David Carrington Information Technology and Electrical Engineering The University of Queensland, St. Lucia,

More information

ISO/IEC INTERNATIONAL STANDARD

ISO/IEC INTERNATIONAL STANDARD INTERNATIONAL STANDARD ISO/IEC 19500-2 This is a preview of "ISO/IEC 19500-2:2012". Click here to purchase the full version from the ANSI store. Second edition 2012-04-15 Information technology Object

More information

Reusable Object-Oriented Model

Reusable Object-Oriented Model e-informatica Software Engineering Journal, Volume 7, Issue 1, 2013, pages: 35 44, DOI 10.5277/e-Inf130104 Reusable Object-Oriented Model Jaroslav Žáček, František Huňka Faculty of Science, University

More information

Impacts of changes in enterprise software construction for telecommunications

Impacts of changes in enterprise software construction for telecommunications Project Report Impacts of changes in enterprise software construction for telecommunications Model Driven Architecture Assessments of relevant technologies Editor: Olaf Kath, IKV++ Technologies AG DRAFT

More information

COSC 3351 Software Design. An Introduction to UML (I)

COSC 3351 Software Design. An Introduction to UML (I) COSC 3351 Software Design An Introduction to UML (I) This lecture contains material from: http://wps.prenhall.com/esm_pfleeger_softengtp_2 http://sunset.usc.edu/classes/cs577a_2000/lectures/05/ec-05.ppt

More information

ISO/IEC INTERNATIONAL STANDARD. Information technology Metamodel framework for interoperability (MFI) Part 1: Reference model

ISO/IEC INTERNATIONAL STANDARD. Information technology Metamodel framework for interoperability (MFI) Part 1: Reference model INTERNATIONAL STANDARD ISO/IEC 19763-1 First edition 2007-02-01 Information technology Metamodel framework for interoperability (MFI) Part 1: Reference model Technologies de l'information Cadre du métamodèle

More information

!MDA$based*Teaching*and* Research*in*Software*Engineering*!

!MDA$based*Teaching*and* Research*in*Software*Engineering*! Plan!MDA$based*Teaching*and* Research*in*Software*Engineering*! Ludwik!Kuźniarz! Blekinge*Institute*of*Technology* School*of*Computing* Sweden*! Myself! Driven Architecture! MDA based Reaserch! Sample

More information

Conceptual Modeling and Specification Generation for B2B Business Processes based on ebxml

Conceptual Modeling and Specification Generation for B2B Business Processes based on ebxml Conceptual Modeling and Specification Generation for B2B Business Processes based on ebxml HyoungDo Kim Professional Graduate School of Information and Communication, Ajou University 526, 5Ga, NamDaeMoonRo,

More information

Automation of Semantic Web based Digital Library using Unified Modeling Language Minal Bhise 1 1

Automation of Semantic Web based Digital Library using Unified Modeling Language Minal Bhise 1 1 Automation of Semantic Web based Digital Library using Unified Modeling Language Minal Bhise 1 1 Dhirubhai Ambani Institute for Information and Communication Technology, Gandhinagar, Gujarat, India Email:

More information

Workpackage 15: DBE Business Modeling Language. Deliverable D15.5: BML Editor Final Release

Workpackage 15: DBE Business Modeling Language. Deliverable D15.5: BML Editor Final Release Contract n 507953 Workpackage 15: DBE Business Modeling Language Deliverable D15.5: BML Editor Final Release Project funded by the European Community under the Information Society Technology Programme

More information