WO2007122119A1 - Production and management method for changes to interface libraries - Google Patents

Production and management method for changes to interface libraries Download PDF

Info

Publication number
WO2007122119A1
WO2007122119A1 PCT/EP2007/053615 EP2007053615W WO2007122119A1 WO 2007122119 A1 WO2007122119 A1 WO 2007122119A1 EP 2007053615 W EP2007053615 W EP 2007053615W WO 2007122119 A1 WO2007122119 A1 WO 2007122119A1
Authority
WO
WIPO (PCT)
Prior art keywords
interface
model
workshop
meta
designer
Prior art date
Application number
PCT/EP2007/053615
Other languages
French (fr)
Inventor
Gilles Merlet
Riana Ralambomanana
Bruno Girard
Original Assignee
Thales
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Thales filed Critical Thales
Priority to EP07728081A priority Critical patent/EP2008177A1/en
Publication of WO2007122119A1 publication Critical patent/WO2007122119A1/en

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G06F8/30—Creation or generation of source code

Definitions

  • the present invention relates to a method for producing and maintaining libraries of interfaces between at least two devices communicating with each other.
  • Interface libraries implement data structures representing messages and message encoding / decoding functions, but also message consistency checking and registration services. Test sets to validate the product code are also generated.
  • the production of the interface libraries was until now carried out according to a conventional software development process. From a descriptive document of the messaging, phases of design, coding and unit tests made it possible to produce the source code. This solution was expensive in development time and especially in terms of maintenance. Modification of the source code required replaying all or part of the unit tests. Since the nature of messaging required to control the physical representation of data to the nearest bit, the implementation was very often dependent on the target platform. Finally, the source code was written in a given computer language, requiring a complete re-development in case of change of language.
  • Code generators were also available, but their use remained complex and required in-depth specific knowledge of computer science. Another disadvantage of these tools is their lack of genericity; that is, they have been designed for the generation of a specific interface and require major changes for the generation of another interface. In addition, the generated code is linked to a particular language, is not necessarily complete and in this case requires human intervention after the generation step.
  • the present invention relates to a method for simplifying and automating the production and management of the evolution of libraries of interfaces between at least two devices communicating with each other.
  • the method according to the invention is characterized by the fact that it is implemented by two actors, the designer who builds the modeling and generation workshop, and the user who models his interface library and generates it. using this workshop, and this method is characterized in that it comprises the following steps: the designer defines the interface model description language called the interface meta-model, this language resulting from an analysis the different interface specifications that can be used and all their common characteristics identified, the designer uses a predefined configuration of a tool that automatically generates the implementation of this model description language and the associated man-machine interface , - the designer writes the "patterns" or transformation rules to generate a library, the designer, by assembling the implementation
  • the description of the interface model description language, the associated human-machine interface, the generation patterns, at the core of the tool produces a generic interface library production workshop that can be used as it is. user for any library.
  • the user then uses the library production workshop as a "black box" in which he models the interfaces he wishes to implement and selects the transformation rules that will enable the tool to be used. to generate his libraries.
  • FIG. 1 is a simplified block diagram of the various components and involved in the process
  • Fig. 2 is an example of a description of an interface meta-model as can be used by the present invention
  • Fig. 3 is a simplified block diagram illustrating the generation of the implementation of the meta-model by the designer
  • Figure 4 is a simplified block diagram of a user interface production workshop, as may be implemented by the invention.
  • Figure 1 shows the different components of a modeling and generic generation workshop based on the method of the invention.
  • Meta-model (4) is the description language of a model. It is defined by the designer (1) of the workshop and itself respects a predetermined description language.
  • the kernel (3) provides the generic functions of manipulation of models and meta-models, the functions of generation of code by relying on a engine of generation by "templates" (patterns), for example the engine “Velocity” rM , the main window of the tool on which will integrate the human-machine interface (5) provided to the user (2) for entering the model and basic commands such as the opening of the help, configuration and execution of the generation, for example.
  • the transformation rules (6) specify the expected form of the generated code according to the syntax defined by the build engine.
  • Fig. 2 is an exemplary description of an interface meta-model (10) using the UML formalism as may be used by the present invention.
  • This meta-model is the key to the interface library production workshop, in that it can generically describe any type of messaging. It is the result of the analysis of the different interface specifications that can be used and all their common characteristics identified, such as: an interface (represented by the MessageLibrary class), composed of a set of messages, these messages consist of different fields and possibly extensions, the fields can be elementary fields or a set of elementary fields ("Records"). Conditions may also be associated with them to determine their presence.
  • the elementary fields can be of different predefined types such as: numeric, enumerated, string of characters, floating ...
  • FIG. 3 represents the workshop (12) for creating and generating meta-models used by the designer (1) to enter his interface meta-model (10), for example that represented in FIG. 2, and to generate his implemen- tation and the associated human-machine interface (1 1), which will be integrated in the interface library production workshop.
  • This workshop of creation and generation of meta-model is a configuration of the tool dedicated to the designer (1) and is used by it as a "black box”.
  • This workshop includes: a "meta-meta-model", a metamodel input HMI, the kernel and transformation rules dedicated to generating an implementation of a meta-model and an input HMI of models.
  • Figure 4 illustrates the user interface library production plant (2).
  • the designer (1) uses the implementation of the interface meta-model and the associated human-machine interface (1 1) that were generated by the creation and generation workshop. of meta-model (12) to integrate it into the core of the tool.
  • the designer (1) has also defined the various transformation rules (13) for generating libraries (15) comprising: source code, documentation and tests. These transformation rules (13) are also integrated into the tool's kernel and are valid with any model entered by the user (2).
  • the user (2) uses the interface library production workshop as a "black box” in which he enters his interface model (14) via the man-machine interface (11) and selects the rules of the interface. transformation (13) that it wishes to apply among those available. By executing the transformation, he obtains the various libraries (15) resulting from the rules he has selected.
  • the solution of the invention has, in particular, the following advantages:
  • the interface library is produced entirely from the modeling of the messaging, itself carried out thanks to a suitable human-machine interface. No software development skills for model capture and library production are required. The development time and the maintenance operations are considerably reduced,
  • Portability (language, wound-shape target) is acquired by adapting the transformation rules, without the need to modify the model,
  • the reliability of the interface library is improved by automating code generation, without any manual intervention on the product code.
  • the scalability of the workshop (thanks to the metamodel generator) makes it possible to take into account new specificities without having to intervene on the source code of the tool.
  • the user of the tool does not need any specific computer skills, because it is reserved for the designer.

Abstract

This invention relates to a method for production and maintenance of interface libraries between at least two items of equipment communicating with each other, and it is characterized by the fact that it is used by two players, the designer (1) who builds up the modelling and generation workshop (7), and the user (2) who models his interface library and generates the library that he wishes using this workshop, and characterised in that it comprises the following steps: the designer defines the interface model description language called the interface meta-model (4), this language resulting from an analysis of the different interface specifications that could be used and including all their identified common characteristics, the designer uses a predefined configuration of the workshop (12) automatically generating an implementation of this model description language and the associated man-machine interface, the designer writes “patterns” or transformation rules (6) to generate a library, and the designer assembles the implementation of the interface model description language, the associated man-machine interface, generation patterns, with the tool core, and makes a generic interface library production workshop (16) at the core of the tool, that the user can use as is for any library.

Description

PROCEDE DE PRODUCTION ET DE GESTION DES EVOLUTIONS DE PROCESS FOR PRODUCING AND MANAGING EVOLUTIONS OF
LIBRAIRIES D'INTERFACESLIBRARY OF INTERFACES
La présente invention se rapporte à un procédé de production et de maintenance de librairies d'interfaces entre au moins deux équipements communiquant entre eux.The present invention relates to a method for producing and maintaining libraries of interfaces between at least two devices communicating with each other.
Les librairies d'interfaces implémentent les structures de données représentant les messages et les fonctions d'encodage / décodage des messages, mais également des services de vérification de cohérence de messages et d'enregistrement. Des jeux de tests permettant la validation du code produit sont également générés.Interface libraries implement data structures representing messages and message encoding / decoding functions, but also message consistency checking and registration services. Test sets to validate the product code are also generated.
Ces librairies peuvent être amenées à évoluer et sont susceptibles d'être incorporées à des logiciels écrits dans différents langages, fonctionnant sur différentes machines cibles. Les difficultés de réalisation de ces librairies résident dans :These libraries may have to evolve and are likely to be incorporated into software written in different languages, operating on different target machines. The difficulties of realization of these libraries reside in:
- la généricité requise (utilisation de l'atelier en l'état pour tout type de messagerie)- the required generality (use of the workshop as is for any type of messaging)
- l'automatisation complète de la production (pas d'intervention manuelle sur le code source, la documentation, les jeux de tests, ...) - l'utilisation de l'atelier sans connaissance de langages spécifiques.- the complete automation of the production (no manual intervention on the source code, the documentation, the test sets, ...) - the use of the workshop without knowledge of specific languages.
Selon les procédés connus, la production des librairies d'interface était jusqu'alors réalisée suivant un processus de développement logiciel classique. A partir d'un document descriptif de la messagerie, des phases de conception, codage et tests unitaires permettaient de produire le code source. Cette solution était coûteuse en temps de développement et surtout en termes de maintenance. La modification du code source nécessitait de rejouer tout ou partie des tests unitaires. Les messageries imposant par nature de maîtriser la représentation physique des données au bit près, l'implémentation était très souvent dépendante de la plate-forme cible. Enfin, le code source était écrit dans un langage informatique donné, nécessitant un re-développement complet en cas de changement de langage.According to the known methods, the production of the interface libraries was until now carried out according to a conventional software development process. From a descriptive document of the messaging, phases of design, coding and unit tests made it possible to produce the source code. This solution was expensive in development time and especially in terms of maintenance. Modification of the source code required replaying all or part of the unit tests. Since the nature of messaging required to control the physical representation of data to the nearest bit, the implementation was very often dependent on the target platform. Finally, the source code was written in a given computer language, requiring a complete re-development in case of change of language.
Des générateurs de code étaient également disponibles mais leur utilisation restait complexe et nécessitait une connaissance spécifique approfondie en informatique. Un autre inconvénient de ces outils est leur manque de généricité ; c'est à dire qu'ils ont été conçus pour la génération d'une interface spécifique et nécessitent des évolutions majeures pour la génération d'une autre interface. De plus, le code généré est lié à un langage en particulier, n'est pas forcément complet et dans ce cas nécessite une intervention humaine après l'étape de génération.Code generators were also available, but their use remained complex and required in-depth specific knowledge of computer science. Another disadvantage of these tools is their lack of genericity; that is, they have been designed for the generation of a specific interface and require major changes for the generation of another interface. In addition, the generated code is linked to a particular language, is not necessarily complete and in this case requires human intervention after the generation step.
La présente invention a pour objet un procédé visant à simplifier et à automatiser la production ainsi que la gestion de l'évolution de librairies d'interfaces entre au moins deux équipements communiquant entre eux.The present invention relates to a method for simplifying and automating the production and management of the evolution of libraries of interfaces between at least two devices communicating with each other.
Le procédé conforme à l'invention est caractérisé par le fait qu'il est mis en œuvre par deux acteurs, le concepteur qui construit l'atelier de modélisation et de génération, et l'utilisateur qui modélise sa librairie d'interface et la génère à l'aide de cet atelier, et ce procédé est caractérisé en ce qu'il comporte les étapes suivantes : le concepteur définit le langage de description des modèles d'interfaces appelé méta-modèle d'interfaces, ce langage résultant d'une analyse des différentes spécifications d'interfaces susceptibles d'être utilisées et reprenant toutes leur caractéristiques communes identifiées, le concepteur utilise une configuration prédéfinie d'un outil générant automatiquement l'implémentation de ce langage de description de modèle ainsi que l'interface homme -machine associée, - le concepteur écrit les « patrons » ou règles de transformation permettant de générer une librairie, le concepteur, en assemblant l'implémentation du langage de description des modèles d'interfaces, l'interface homme-machine associée, les patrons de génération, au noyau de l'outil, réalise un atelier de production de librairies d'interfaces générique, utilisable en l'état par l'utilisateur pour toute librairie.The method according to the invention is characterized by the fact that it is implemented by two actors, the designer who builds the modeling and generation workshop, and the user who models his interface library and generates it. using this workshop, and this method is characterized in that it comprises the following steps: the designer defines the interface model description language called the interface meta-model, this language resulting from an analysis the different interface specifications that can be used and all their common characteristics identified, the designer uses a predefined configuration of a tool that automatically generates the implementation of this model description language and the associated man-machine interface , - the designer writes the "patterns" or transformation rules to generate a library, the designer, by assembling the implementation The description of the interface model description language, the associated human-machine interface, the generation patterns, at the core of the tool, produces a generic interface library production workshop that can be used as it is. user for any library.
Selon une autre caractéristique de l'invention, l'utilisateur utilise ensuite l'atelier de production de librairies comme une « boite noire » dans laquelle il modélise les interfaces qu'il désire implémenter et sélectionne les règles de transformations qui permettront à l'outil de lui générer ses librairies.According to another characteristic of the invention, the user then uses the library production workshop as a "black box" in which he models the interfaces he wishes to implement and selects the transformation rules that will enable the tool to be used. to generate his libraries.
Selon l'invention, on utilise les principes de transformation de modèles au sens du « Model Driven Architecture » (MDA) de l'0MG (Object Management Group), afin de substituer au développement classique, une modélisation de l'interface, suivie d'une génération automatique de « librairies ». Cette solution repose sur la méthode itérative de création et sur l'évolutivité de l'atelier de modélisation et de génération . Par « librairies » ou « librairies d'interface », on entend, en particulier, au sens de la présente invention, du code source, de la documentation et des tests.According to the invention, the principles of model transformation the Object Management Group (MDM) "Model Driven Architecture" (MDA), in order to replace conventional development with interface modeling, followed by automatic generation of "libraries". This solution is based on the iterative method of creation and scalability of the modeling and generation workshop. By "libraries" or "interface libraries" is meant, in particular, within the meaning of the present invention, source code, documentation and tests.
La présente invention sera mieux comprise à la lecture de la description détaillée d'un mode de réalisation, pris à titre d'exemple non limitatif et illustré par le dessin annexé, sur lequel : la figure 1 est un bloc-diagramme simplifié des différents composants et acteurs impliqués dans le procédé, la figure 2 est un exemple de description d'un méta-modèle d'interface tel que pouvant être utilisé par la présente invention, - la figure 3 est un bloc-diagramme simplifié illustrant la génération de l'implémentation du méta-modèle par le concepteur, la figure 4 est un bloc-diagramme simplifié d'un atelier de production d'interfaces par l'utilisateur, tel que pouvant être mis en œuvre par l'invention. La figure 1 montre les différents composants d'un atelier de modélisation et de génération générique basé sur le procédé de l'invention.The present invention will be better understood on reading the detailed description of an embodiment, taken by way of non-limiting example and illustrated by the appended drawing, in which: FIG. 1 is a simplified block diagram of the various components and involved in the process, Fig. 2 is an example of a description of an interface meta-model as can be used by the present invention; Fig. 3 is a simplified block diagram illustrating the generation of the implementation of the meta-model by the designer, Figure 4 is a simplified block diagram of a user interface production workshop, as may be implemented by the invention. Figure 1 shows the different components of a modeling and generic generation workshop based on the method of the invention.
Le méta-modèle (4) constitue le langage de description d'un modèle. Il est défini par le concepteur (1) de l'atelier et respecte lui même un langage de description prédéterminé. Le noyau (3) fournit les fonctions génériques de manipulation de modèles et de méta-modèles, les fonctionnalités de génération de code en s'appuyant sur un moteur de génération par « templates » (patrons), par exemple le moteur « Velocity»rM , la fenêtre principale de l'outil sur laquelle va s'intégrer l'interface homme-machine (5) fournie à l'utilisateur (2) pour la saisie du modèle ainsi que les commandes de base telles que l'ouverture de l'aide, la configuration et l'exécution de la génération, par exemple. Les règles de transformation (6) spécifient la forme attendue du code généré en suivant la syntaxe définie par le moteur de génération.Meta-model (4) is the description language of a model. It is defined by the designer (1) of the workshop and itself respects a predetermined description language. The kernel (3) provides the generic functions of manipulation of models and meta-models, the functions of generation of code by relying on a engine of generation by "templates" (patterns), for example the engine "Velocity" rM , the main window of the tool on which will integrate the human-machine interface (5) provided to the user (2) for entering the model and basic commands such as the opening of the help, configuration and execution of the generation, for example. The transformation rules (6) specify the expected form of the generated code according to the syntax defined by the build engine.
L'ensemble de ces éléments (3) à (6) constitue un atelier de modélisation et de génération (7). La figure 1 permet également de comprendre la distinction entre les rôles du concepteur (1) et de l'utilisateur (2) de l'outil. Le concepteur (1) crée et modifie le méta-modèle et les règles de transformation (6) qui composent l'atelier, tandis que l'utilisateur (2) saisit ou modifie son modèle (8), en étant uniquement assisté par une IHM (Interface Homme-Machine) de saisie (5) dépendant du méta-modèle (4) utilisé. Cette IHM se présente comme un formulaire dont l'utilisateur remplit les champs correspondant à ses besoins. C'est également l'utilisateur qui active la génération des librairies en accord avec les règles de transformation (6).All of these elements (3) to (6) constitute a modeling and generation workshop (7). Figure 1 also makes it possible to understand the distinction between the roles of the designer (1) and the user (2) of the tool. The designer (1) creates and modifies the meta-model and the transformation rules (6) that make up the workshop, while the user (2) enters or modifies his model (8), being only assisted by an HMI (Man-Machine Interface) input (5) depending on the meta-model (4) used. This HMI is presented as a form whose user fills in the fields corresponding to his needs. It is also the user who activates the generation of the libraries in accordance with the transformation rules (6).
La figure 2 est un exemple de description d'un méta-modèle d'interface (10) utilisant le formalisme UML tel que pouvant être utilisé par la présente invention. Ce méta-modèle est la clé de l'atelier de production de librairies d'interfaces, en ce sens qu'il permet de décrire de manière générique tout type de messagerie. Il est le résultat de l'analyse des différentes spécifications d'interfaces susceptibles d'être utilisées et reprend toutes leur caractéristiques communes identifiées, telles que : une interface (représenté par la classe MessageLibrary), composée d'un ensemble de messages, ces messages sont constitués de différents champs et éventuellement d'extensions, les champs peuvent être des champs élémentaires ou un ensemble de champs élémentaires (« Records »). Des conditions peuvent également leur être associées afin de déterminer leur présence. les champs élémentaires peuvent être de différents types prédéfinis tels que : numérique, énuméré, chaîne de caractères, flottants... une interface est également définie par son format d'encodage tel que « Little Endian » ou « Big Endian ». La figure 3 représente l'atelier (12) de création et de génération de méta- modèles utilisé par le concepteur (1) pour saisir son méta-modèle d'interface (10), par exemple celui représenté en figure 2, et générer son implémcntation et l'interface homme-machine associée (1 1), qui seront intégrés dans l'atelier de production de librairies d'interfaces. Cet atelier de création et de génération de méta-modèle est une configuration de l'outil dédié au concepteur (1) et est utilisé par celui-ci comme une « boite noire ». Cet atelier comporte : un « méta-méta-modèle », une IHM de saisie de méta-modèles, le noyau et des règles de transformation dédiées à la génération d'une implémentation d'un méta-modèle et d'une IHM de saisie de modèles. La figure 4 illustre l'atelier de production de librairies d'interfaces mis en oeuvre par l'utilisateur (2) . Afin de construire cet atelier, le concepteur (1) se sert de l' implémentation du méta-modèle d'interface et de l'interface homme-machine associée (1 1) qui ont été générés par l'atelier de création et de génération de méta- modèle (12) pour l'intégrer au noyau de l'outil. Le concepteur (1) a également défini les différentes règles de transformation (13) permettant de générer des librairies (15) comportant: du code source, de la documentation et des tests. Ces règles de transformation (13) sont également intégrées au noyau de l'outil et sont valables avec tout modèle saisi par l'utilisateur (2).Fig. 2 is an exemplary description of an interface meta-model (10) using the UML formalism as may be used by the present invention. This meta-model is the key to the interface library production workshop, in that it can generically describe any type of messaging. It is the result of the analysis of the different interface specifications that can be used and all their common characteristics identified, such as: an interface (represented by the MessageLibrary class), composed of a set of messages, these messages consist of different fields and possibly extensions, the fields can be elementary fields or a set of elementary fields ("Records"). Conditions may also be associated with them to determine their presence. the elementary fields can be of different predefined types such as: numeric, enumerated, string of characters, floating ... an interface is also defined by its encoding format such as "Little Endian" or "Big Endian". FIG. 3 represents the workshop (12) for creating and generating meta-models used by the designer (1) to enter his interface meta-model (10), for example that represented in FIG. 2, and to generate his implemen- tation and the associated human-machine interface (1 1), which will be integrated in the interface library production workshop. This workshop of creation and generation of meta-model is a configuration of the tool dedicated to the designer (1) and is used by it as a "black box". This workshop includes: a "meta-meta-model", a metamodel input HMI, the kernel and transformation rules dedicated to generating an implementation of a meta-model and an input HMI of models. Figure 4 illustrates the user interface library production plant (2). In order to build this workshop, the designer (1) uses the implementation of the interface meta-model and the associated human-machine interface (1 1) that were generated by the creation and generation workshop. of meta-model (12) to integrate it into the core of the tool. The designer (1) has also defined the various transformation rules (13) for generating libraries (15) comprising: source code, documentation and tests. These transformation rules (13) are also integrated into the tool's kernel and are valid with any model entered by the user (2).
L'utilisateur (2) utilise l'atelier de production de librairies d'interfaces comme une « boite noire » dans laquelle il saisit son modèle d'interface (14) via l'interface homme-machine (11) et sélectionne les règles de transformation (13) qu'il désire appliquer parmi celles disponibles. En exécutant la transformation, il obtient les différentes librairies(15) résultants des règles qu'il a sélectionnées.The user (2) uses the interface library production workshop as a "black box" in which he enters his interface model (14) via the man-machine interface (11) and selects the rules of the interface. transformation (13) that it wishes to apply among those available. By executing the transformation, he obtains the various libraries (15) resulting from the rules he has selected.
La solution de l'invention présente, en particulier, les avantages suivants : - La librairie d'interface est produite entièrement à partir de la modélisation de la messagerie, elle-même réalisée grâce à une interface homme-machine adaptée. Aucune compétence en développement logiciel pour la saisie du modèle et la production des librairies n'est requise. Le temps de développement et les opérations de maintenance en sont considérablement réduits,The solution of the invention has, in particular, the following advantages: The interface library is produced entirely from the modeling of the messaging, itself carried out thanks to a suitable human-machine interface. No software development skills for model capture and library production are required. The development time and the maintenance operations are considerably reduced,
La portabilité (langage, plaie-forme cible) est acquise en adaptant les règles de transformation, sans qu'il soit besoin de modifier le modèle, La fiabilité de la librairie d'interface est améliorée par l'automatisation de la génération de code, sans aucune intervention manuelle sur le code produit. L'évolutivité de l'atelier (grâce au générateur de méta-modèle) permet de prendre en compte des nouvelles spécificités sans avoir à intervenir sur le code source de l'outil.Portability (language, wound-shape target) is acquired by adapting the transformation rules, without the need to modify the model, The reliability of the interface library is improved by automating code generation, without any manual intervention on the product code. The scalability of the workshop (thanks to the metamodel generator) makes it possible to take into account new specificities without having to intervene on the source code of the tool.
L'utilisateur de l'outil n'a besoin d'aucune compétence spécifique en informatique, car celle-ci est réservée au concepteur. The user of the tool does not need any specific computer skills, because it is reserved for the designer.

Claims

REVENDICATIONS
1. Procédé de production et de maintenance de librairies d'interfaces entre au moins deux équipements communiquant entre eux, caractérisé par le fait qu'il est mis en œuvre par deux acteurs, le concepteur (1) qui construit l'atelier (7) de modélisation et de génération, et l'utilisateur (2) qui modélise sa librairie d'interface et génère la librairie qu'il désire à l'aide de cet atelier, et caractérisé en ce qu'il comporte les étapes suivantes : le concepteur définit le langage de description des modèles d'interfaces appelé méta-modèle d'interfaces (4), ce langage résultant d'une analyse des différentes spécifications d'interfaces susceptibles d'être utilisées et reprenant toutes leur caractéristiques communes identifiées, le concepteur utilise une configuration prédéfinie d'un outil (3) générant automatiquement l'implémentation de ce langage de description de modèle ainsi que l'interface homme -machine associée, le concepteur écrit les « patrons » ou règles de transformation (6) permettant de générer une librairie, le concepteur, en assemblant l'implémentation du langage de description des modèles d'interfaces, l'interface homme-machine associée, les patrons de génération, au noyau de l'outil, réalise un atelier (7) de production de librairies d'interfaces générique, utilisable en l'état par l'utilisateur pour toute librairie.1. A method for producing and maintaining libraries of interfaces between at least two devices communicating with each other, characterized in that it is implemented by two actors, the designer (1) who builds the workshop (7) model and generation, and the user (2) who models his interface library and generates the desired library using this workshop, and characterized in that it comprises the following steps: the designer defines the description language of the interface models called meta-model of interfaces (4), this language resulting from an analysis of the various interface specifications that can be used and with all their common characteristics identified, the designer uses a predefined configuration of a tool (3) automatically generating the implementation of this model description language and the associated man-machine interface, the designer writes the "patterns or transformation rules (6) to generate a library, the designer, by assembling the implementation of the interface model description language, the associated human-machine interface, the generation patterns, to the tool's core , carries out a workshop (7) for producing generic interface libraries, usable by the user for the entire library.
2. Procédé selon la revendication 1 , caractérisé en ce que l'utilisateur utilise ensuite l'atelier de production de librairies comme une « boite noire » dans laquelle il modélise les interfaces qu'il désire implémenter et sélectionne les règles de transformations qui permettront à l'outil de lui générer ses librairies.2. Method according to claim 1, characterized in that the user then uses the library production workshop as a "black box" in which he models the interfaces he wants to implement and selects the transformation rules that will allow the tool to generate his libraries.
3. Procédé selon la revendication 1 ou 2, caractérisé en ce qu'il est mis en œuvre pour réaliser une librairie d'interface pour une messagerie. 3. Method according to claim 1 or 2, characterized in that it is implemented to produce an interface library for messaging.
4. Atelier de production de librairies (7) pour la mise en œuvre du procédé selon !a revendication 2, caractérisé en ce qu'il comporte un moteur de génération par patrons (3), un méta-modèle (4), un interface homme-machine de saisie de modèle (5) et des règles de transformation (6).4. A library production workshop (7) for implementing the method according to claim 2, characterized in that it comprises an engine of generation by patterns (3), a meta-model (4), a man-machine interface for model input (5) and transformation rules (6).
5. Atelier selon la revendication 4, caractérisé en ce que lorsqu'il est utilisé par le concepteur, le méta-modèle (4) est un méta-modèle d'interfaces servant à créer des méta-modèles (méta-méta-modèle).5. Workshop according to claim 4, characterized in that when used by the designer, the meta-model (4) is a meta-model of interfaces used to create meta-models (meta-meta-model). .
6. Atelier selon la revendication 4 ou 5, caractérisé en ce que lorsqu'il est utilisé par l'utilisateur, le méta-modèle est une implémentation du méta- modèle d'interface. 6. Workshop according to claim 4 or 5, characterized in that when used by the user, the meta-model is an implementation of the interface meta-model.
PCT/EP2007/053615 2006-04-14 2007-04-13 Production and management method for changes to interface libraries WO2007122119A1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
EP07728081A EP2008177A1 (en) 2006-04-14 2007-04-13 Production and management method for changes to interface libraries

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
FR0603354A FR2899987A1 (en) 2006-04-14 2006-04-14 METHOD FOR PRODUCING AND MANAGING INTERFACE LIBRARY EVOLUTIONS
FR0603354 2006-04-14

Publications (1)

Publication Number Publication Date
WO2007122119A1 true WO2007122119A1 (en) 2007-11-01

Family

ID=37496738

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/EP2007/053615 WO2007122119A1 (en) 2006-04-14 2007-04-13 Production and management method for changes to interface libraries

Country Status (3)

Country Link
EP (1) EP2008177A1 (en)
FR (1) FR2899987A1 (en)
WO (1) WO2007122119A1 (en)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102929598A (en) * 2012-09-25 2013-02-13 中国核电工程有限公司 Man-machine interface design method for improving safety of nuclear power station

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1202167A1 (en) * 2000-10-27 2002-05-02 Interactive Objects Software GmbH Method for model based object oriented development of external interfaces for distributed software systems
EP1343078A1 (en) * 2002-01-07 2003-09-10 Interactive Objects Software GmbH Modelling system and generation of software generating systems
EP1387260A1 (en) * 2002-07-25 2004-02-04 The Rationalizer Intelligent Software AG Method and system for software development
DE10233971A1 (en) * 2002-07-25 2004-02-19 The Rationalizer Intelligent Software Ag Software generating method for a software-controlled device uses a software model implemented as data in a computer to derive software program code automatically from the model
US20050160401A1 (en) * 1999-10-16 2005-07-21 Computer Associates Think, Inc. System and method for adding user-defined objects to a modeling tool

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20050160401A1 (en) * 1999-10-16 2005-07-21 Computer Associates Think, Inc. System and method for adding user-defined objects to a modeling tool
EP1202167A1 (en) * 2000-10-27 2002-05-02 Interactive Objects Software GmbH Method for model based object oriented development of external interfaces for distributed software systems
EP1343078A1 (en) * 2002-01-07 2003-09-10 Interactive Objects Software GmbH Modelling system and generation of software generating systems
EP1387260A1 (en) * 2002-07-25 2004-02-04 The Rationalizer Intelligent Software AG Method and system for software development
DE10233971A1 (en) * 2002-07-25 2004-02-19 The Rationalizer Intelligent Software Ag Software generating method for a software-controlled device uses a software model implemented as data in a computer to derive software program code automatically from the model

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
GIUSEPPE NACCARATO: "Template-Based Code Generation with Apache Veloctiy, Part 1", ONJAVA.COM, 5 May 2004 (2004-05-05), pages 1 - 10, XP002411583, Retrieved from the Internet <URL:http://www.onjava.com/pub/a/onjava/2004/05/05/cg-vel1.html> [retrieved on 20061213] *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102929598A (en) * 2012-09-25 2013-02-13 中国核电工程有限公司 Man-machine interface design method for improving safety of nuclear power station

Also Published As

Publication number Publication date
FR2899987A1 (en) 2007-10-19
EP2008177A1 (en) 2008-12-31

Similar Documents

Publication Publication Date Title
US9754059B2 (en) Graphical design verification environment generator
Vanderdonckt Model-driven engineering of user interfaces: Promises, successes, failures, and challenges
Arcaini et al. A model‐driven process for engineering a toolset for a formal method
CN101996131A (en) Automatic test method and automatic test platform for graphic user interface (GUI) based on x extensive makeup language (XML) packaging key word
JP5350428B2 (en) Automatic program generation apparatus, method and computer program
EP3296866B1 (en) Method implemented by a computer that presents software-type applications based on design specifications
TW200412495A (en) A generic software testing system and mechanism
EP1387261A1 (en) Application software generation and language for software description
CN105512304A (en) Method for generating internet applications on line, system integration method and supporting platform
JP6479184B2 (en) Computer-executable model reverse engineering method and apparatus
US7519947B2 (en) Orchestration designer
Fursin Collective knowledge: organizing research projects as a database of reusable components and portable workflows with common interfaces
Lachgar et al. Modeling and generating native code for cross-platform mobile applications using DSL
CN102722601A (en) Implementation method of formal semantic integration framework for model transformation of numerical control system
Rodriguez-Echeverria et al. An LSP infrastructure to build EMF language servers for web-deployable model editors.
Sun et al. A model-driven approach to support engineering changes in industrial robotics software
US20230041718A1 (en) Automated code generation based on pseudo-code
JP2008293186A (en) Method and apparatus for automatically generating steel plant control program
EP2008177A1 (en) Production and management method for changes to interface libraries
Weyprecht et al. Model-driven development of simulation solution based on SysML starting with the simulation core.
JP2008287365A (en) Program generation device, program generation method, program, and recording medium
Bocevska et al. An example of application design using solidworks application programming interface
KR100846203B1 (en) Method for generating mobile application and record media recorded program for realizing the same
JP2007094453A (en) Program development support system, program development support method and program
KR20060120004A (en) A dialog control for dialog systems

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 07728081

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 2007728081

Country of ref document: EP

NENP Non-entry into the national phase

Ref country code: DE