These tools are then configured during the engineering phase of using meta-models and a variety of roles (code generation, model analysis, etc.) Are awarded their operational phase. Some actors and roles involved in process operating stage also involved in engineering phase of the process. Indeed, expertise in the three areas, business areas, software engineering, process management/ methods must be present. The specification and implementation of specific models or meta-model transformations also requires the intervention of mobile recharge api an IDM player with expertise within this field. 

 

This actor IDM, playing an expert role in meta-modeling will interact with experts from the fields to choose the tools needed to develop mobile recharge api and explore their integration into the process. Similarly, it will interact with experts of software engineering to form meta-models associated with target architectures, the frameworks, platforms, etc. As an expert in model transformation he will be responsible for producing a set of model transformation necessary for linking different languages. These changes will eventually facilitate the construction of roads to be followed by the development process.

Apart from products to clean and internal engineering processes such as identifying areas, concepts and theories, etc., the products of the engineering process and used by processes are designed meta-models, transformations, tools and meta-tools configured, frameworks, and models of recharge api development the specific process. Are products of the engineering process and are considered resources in processes designed. These meta-models are designed using meta-modeling languages and therefore must conform to a meta-meta-model (MOF EMOF, KM3, etc.).

 

This raises the problem of the choice of recharge api development this meta-meta-model and a possible repository of meta-models. This item was discussed in paragraph of the state of the art. In our laboratory work has been done on how to define these meta-models functionally using language as meta-modeling the functional high-level language. The advantages of this approach is to benefit from a powerful language with a well defined semantics. The major drawback of this approach is the distance mobile recharge api between this approach and the current practices of the IDM community.

Transformation of models can be recharge api development produced in the form of models of transformations. These models can be described using language processing and are then consistent with meta-models describing these languages. These changes can also be made in the form of specific programs with specific mobile recharge api programming environments such as, or more simply by using more or less conventional languages In our laboratory work has been done on how to describe these transformations functionally using functional language. 

 

The advantage of this approach is to provide both the precise semantics of the language and delivers the power of abstraction of a modern functional language. The achievement of recharge api development specific tools using meta-tools such as MIC-GME or MetaEdit involves performing meta-models meeting these specific meta-meta-meta-tools models such FCO (First Class Object) for MIC-GME or GOPRR (Graph, Object, Property, Relationship, Role) for MetaEdit. These specific meta-meta-models can lead to problems of integration because of their conceptual distance to standards defined by the IDM community.