Search

Työssä tutkittiin CORBA-spesifikaation määrittelemää ohjelmistoarkkitehtuuria, sen toteutuksia sekä soveltuvuutta pehmeiden reaaliaikajärjestelmien ohjaukseen. Tarkastelun alla oli erityisesti joustavan valmistusjärjestelmän perusohjelmiston toteuttaminen CORBA-yhteensopivalla ohjelmistolla. Ohjelmistojen koon ja niiden välisten integrointien lukumäärän kasvaminen hankalasti hallittaviksi on aiheuttanut tarvetta kehittää yhtenäisiä rajapintoja käyttäviä ohjelmia sekä laajennettavia ja uudelleenkäytettäviä ohjelmistoarkkitehtuureja ja menettelytapoja. Ongelmien välttämiseksi ohjelmiston eri osat tulisi saada mahdollisimman riippumattomiksi toisistaan ja riippuvuussuhteet tulisi kuvata standardilla tavalla, jotta muutokset yhteen osaan ohjelmistoa vaikuttaisivat mahdollisimman vähän ohjelmiston muihin osiin. CORBA tarjoaa selkeän komponenttiperustaisen arkkitehtuurin ja piilottaa verkkotason ohjelmoinnin. Lisäksi se mahdollistaa ohjelmiston rajapintojen kuvaamisen yhtenäisellä tavalla, mikä vähentää ohjelmistojen integrointityötä. CORBAn käyttöönotto vaatii kuitenkin panostusta koulutukseen, eikä sen kaupallisten toteutusten suorituskyky vielä täytä kovien reaaliaikajärjestelmien asettamia vaatimuksia. Tämän työn yhteydessä tehty joustavan valmistusjärjestelmän perusohjelmisto toteutettiin kaupallisella ORB-toteutuksella (Orbix) ja oliotietokannalla (Objectivity). Sitä kokeiltiin todellisessa toimintaympäristössä, missä käyttöjärjestelmänä oli Windows NT 4.0 ja siirtomediana Ethernet-lähiverkko.

Työssä tutkittiin CORBA-spesifikaation määrittelemää ohjelmistoarkkitehtuuria, sen toteutuksia sekä soveltuvuutta pehmeiden reaaliaikajärjestelmien ohjaukseen. Tarkastelun alla oli erityisesti joustavan valmistusjärjestelmän perusohjelmiston toteuttaminen CORBA-yhteensopivalla ohjelmistolla. Ohjelmistojen koon ja niiden välisten integrointien lukumäärän kasvaminen hankalasti hallittaviksi on aiheuttanut tarvetta kehittää yhtenäisiä rajapintoja käyttäviä ohjelmia sekä laajennettavia ja uudelleenkäytettäviä ohjelmistoarkkitehtuureja ja menettelytapoja. Ongelmien välttämiseksi ohjelmiston eri osat tulisi saada mahdollisimman riippumattomiksi toisistaan ja riippuvuussuhteet tulisi kuvata standardilla tavalla, jotta muutokset yhteen osaan ohjelmistoa vaikuttaisivat mahdollisimman vähän ohjelmiston muihin osiin. CORBA tarjoaa selkeän komponenttiperustaisen arkkitehtuurin ja piilottaa verkkotason ohjelmoinnin. Lisäksi se mahdollistaa ohjelmiston rajapintojen kuvaamisen yhtenäisellä tavalla, mikä vähentää ohjelmistojen integrointityötä. CORBAn käyttöönotto vaatii kuitenkin panostusta koulutukseen, eikä sen kaupallisten toteutusten suorituskyky vielä täytä kovien reaaliaikajärjestelmien asettamia vaatimuksia. Tämän työn yhteydessä tehty joustavan valmistusjärjestelmän perusohjelmisto toteutettiin kaupallisella ORB-toteutuksella (Orbix) ja oliotietokannalla (Objectivity). Sitä kokeiltiin todellisessa toimintaympäristössä, missä käyttöjärjestelmänä oli Windows NT 4.0 ja siirtomediana Ethernet-lähiverkko.

Based on the lessons on a software implementation called ADAM, that is presented in this paper, we address the question of the title by : EXPENSIVE !Starting from two scenarios, we first try to characterize the costs of a distributed approach versus a centralized approach for the program supervision in a distributed environment. Then we describe ADAM's technical realization, and conclude on a discussion pointing out the granularity problems in the (Software) Agent concept.; En tirant les leçons de l'implantation d'un logiciel ADAM, qui est décrit dans cet article, nous répondons à la question du titre par : CHER !Partant de scénarios, puis en nous plaçant dans le cadre plus général de pilotage de programmes en environnement hétérogène réparti, nous confrontons les coûts d'une approche centralisée par rapport à une approche distribuée. Suite à une description des moyens techniques, nous terminons par une discussion mettant à jour les problèmes de granularité dans le concept d'Agent (Logiciel).

In this paper, we present our work-in-progress on developing an automated deployment planner for the composition of Web services as software components using the Reo coordination middleware in a distributed environment. Web services refer to accessing services over the Web. Reo is an exogenous coordination model for compositional construction of component connectors based on a calculus of mobile channels that has been developed at CWI (the Netherlands). Reo has a strong theoretical underpinning which makes it a good candidate model for coordinating the work of Web services participating in a composition. Suppose a new Web application has been developed by composing a number of Web services with different requirements and constraints. To run the application, it is required to deploy it on a number of hosts with different computational capabilities available to the application in the distributed environment (e.g., Internet) so that all constraints and requirements are satisfied. Because of the many parameters and constraints in such a deployment problem, it is difficult to do it manually. Thus, an automated deployment planner is required for this purpose.

Application of model checking to isolated software components is not directly possible because a component does not form a complete program - the problem of missing environment occurs. A solution is to create an environment of some form for the component subject to model checking. As the most general environment can cause model checking of the component to be infeasible, we model the environment on the basis of a particular context the component is to be used in. More specifically, our approach exploits hierarchical component architecture and component behavior specification defined via behavior protocols, all that provided in ADL. This way, the environment represents the behavior of the rest of the particular application with respect to the target component. We present an algorithm for computing the model of environment's behavior that is based on syntactical expansion and substitution of behavior protocols.

In the domain of software engineering, the use of software components is now a well established approach. However, it raises problems about the dynamic adaptation of these components to particular users demands. Indeed, these components have been developed with the intent to have a wide range of use, and so they implement functionalities which perhaps do not match precisely enough the demands of specific users.Therefore, we address the adaptation of the coordination between components by means of so-called Moderators. A Moderator is itself a coordination component managing interactions that are described and formalized using Petri nets. More precisely, we study the dynamic adaptation of the coordination rules by means of specific transformations of the Petri nets used to describe a Moderator.Safety properties must be enforced to maintain a consistent cooperation among participants with respect to the requested evolutions of the coordination rules. In particular, an adaptation of the Moderator can be considered safe if it cannot be detected by the participants. We present a computable criterion which enables to check such a satefy property automatically.We illustrate our approach in the context of a computer aided learning system, by adapting the coordination rules for controlling accesses to documents during an examination.

We explore the question of the composition of invariance specifications in a context of concurrent and reactive systems. Depending on how compositionality is stated and how invariants are defined, invariance specifications may or may not be compositional. This article first examines two classic forms of invariants and their compositional properties. After pointing out what we see as deficiencies of these two kinds of invariants, two new forms are defined and shown to have useful compositional properties that the more classic forms do not enjoy. The last form, in particular, is shown to be well suited to situations where none of the other three is adapted.

Although the term software component has become commonplace, there is no universally accepted definition of the term, nor does there exist a common foundation for specifying various kinds of components and their compositions. We propose such a foundation. The Piccola calculus is a process calculus, based on the asynchronous π-calculus, extended with explicit namespaces. The calculus is high level, rather than minimal, and is consequently convenient for expressing and reasoning about software components, and different styles of composition. We motivate and present the calculus, and outline how it is used to specify the semantics of Piccola, a small composition language. We demonstrate how the calculus can be used to simplify compositions by partial evaluation, and we briefly outline some other applications of the calculus to reasoning about compositional styles.

In order to define a real-world model problem for research work in the area of predictable assembly of certifiable software components, this paper introduces the substation automation domain, as a representative for the wide spectrum of data acquisition and process control systems. Special emphasis in the paper is put on those aspects of the application area, which make its employment as a model problem provider attractive. First, the compositions are required to meet several well defined quality requirements besides functionality and must therefore allow for the prediction of these qualities before the final system is assembled and is undergoing a potentially costly factory and/or onsite acceptance test. Second, the upcoming IEC61850 standard defines agreed upon domain models and quality attribute requirements on system operations. Third, the substation automation domain is comfortable with the notion of certification. Utilities require that such systems and their products be compliant with international standards and thus possess certificates issued by independent certification authorities. In order to make this problem domain attractive to research in the area of compositional reasoning of component assemblies, this paper provides the needed step of relating the domain models and the domain`s quality attribute requirements to software components and assembly properties.

This report is the first deliverable of WP4 “Technology Support” of the CLARITY project, funded by the EU’s Horizon 2020 Programme under Grant Agreement number 730355. WP4 intends to provide the technological backbone of the CLARITY Climate Service Information System (CSIS) by tailoring the technological background foreseen in the CLARITY work package descriptions to project needs. For this, WP4 will integrate and adapt all required and existing (background) tools and services that are necessary for realisation of the CLARITY reference scenarios (Demonstration Cases) and implementation of the EU-GL into the CLARITY Climate Services. The aim of this deliverable is to provide an initial plan for the WP4 work per task, taking into account the input from D1.1 “Initial Workshops and the CLARITY Development Environment”: T4.2 "Catalogue of elements at risk and adaptation options" provides a catalogue that will serve as repository of element at risk types and adaptation options and a dedicated Catalogue of Data Sources and Simulation Models that makes climate-related information accessible and discoverable. T4.3 "Scenario Management" will offer the Scenario Management tool which supports and enforces first and foremost the standardised workflows of the EU-GL for each of the distinct planning steps, a Data Dashboard that provides an overview of all the different datasets that are used, produced, ordered, collected, requested, exchanged etc. by an end user and a Data Package Export and Import Tool for exporting any data that is directly available in the CSIS. T4.4 "Scenario Transferability" provides a Map Component for clear and easy visualization of different maps and layers as well as the Scenario Transferability Component that offers general matchmaking functionality by means of graphical user interfaces (e.g. map visualisations) for side-by-side comparison of alternate (adaptation) scenarios. T4.5 Scenario Analysis, Decision Support and Report Generation provides software that will support the analysis and comparison of scenario candidates (options) regarding performance indicators that can be defined by the end user. Detailed information for each of the WP4 tasks is provided as a separate section in this document. Annex 1 also provides an overview of the tools that are inherited from previous projects and explains the initial plan for using and/or extending these inputs in CLARITY.

Computer-based emotion recognition is a growing field which develops new needs in terms of software modeling and integration of existing models. This thesis describes a conceptual framework for designing emotionally-aware interactive software. Our approach is based upon conceptual results from the field of multimodal interaction: we redefine the concepts of modality and multimodality within the frame of passive emotion recognition. We then describe a component-based conceptual model relying on this redefinition. The emotion branch facilitates the design, development and maintenance of emotionally-aware systems. A multimodal, interactive, gesture-based emotion recognition software based on the emotion branch was developed. This system was integrated within an augmented reality system to augment a ballet dance show according to the dancer's expressed emotions., La reconnaissance d'émotions est un domaine jeune mais dont la maturité grandissante implique de nouveaux besoins en termes de modélisation et d'intégration dans des modèles existants. Ce travail de thèse expose un modèle conceptuel pour la conception d'applications interactives sensibles aux émotions de l'utilisateur. Notre approche se fonde sur les résultats conceptuels issus de l'interaction multimodale: nous redéfinissons les concepts de modalité et de multimodalité dans le cadre de la reconnaissance passive d'émotions. Nous décrivons ensuite un modèle conceptuel à base de composants logiciels s'appuyant sur cette redéfinition: la branche émotion, facilitant la conception, le développement et le maintien d'applications reconnaissant l'émotion de l'utilisateur. Une application multimodale de reconnaissance d'émotions par la gestuelle a été développée selon le modèle de la branche émotion et intégrée dans un système d'augmentation de spectacle de ballet sensible aux émotions d'un danseur.

Ambient intelligence aims to provide to human users applications and services that are personalized and adapted to the current situation. The ambient environment which surrounds the human consists of a set of connected objects and software components that are bricks used for the construction of applications by composition. The availability of these components can vary dynamically, in case of mobility for example. In addition, their appearance or disappearance is usually unanticipated. Moreover, in these dynamic and open environments, the user needs are not stable nor always well defined.To build these applications, and provide the user with “the right applications at the right time”, our team explores an original approach called "opportunistic software composition" : the idea is to build applications on the fly by assembling software components present in the environment at the time, without relying on explicit user needs or predefined applications models. Here, it is the availability of the components that triggers opportunistically the on the-fly building of applications. It is controlled by an intelligent system, called opportunistic composition engine, which decides on the “right” compositions to be made without user input. In such a way, the applications “emerge” dynamically from the ambient environment.Thus, emerging applications can be unexpected or unknown to the user. At the center of the system, the latter must be informed of these applications. On the first hand, she/he must be able to control them, i.e. accept or reject them, and if she/he has the required skills, modify them or eventually build applications herself/himself by assembling software components present in the ambient environment. However, in the control tasks, the user must be assisted as well as possible. On the other hand, in order for the opportunistic composition engine to build relevant assemblies in the absence of explicit needs, it must receive information from the user.In this thesis, we propose an approach based on Model Driven Engineering (MDE) in order to put the user "at the center of the loop". The objective is to present the emerging applications to the user, to assist him in his interventions and to extract useful feedback data to provide to the "intelligent" composition engine.Our solution is based on a metamodel for assembling software components, on different domain-specific languages (DSL) that support application descriptions, and on a graphical editor for editing applications and capturing user feedback. Different methods for model transformations are used to generate structural and semantic application descriptions for different users, from the applications models build by the intelligent engine. In addition, the descriptions can be easily adjusted to a particular human, by changing or adapting the DSL and the model transformations to the user’s profile. Unlike the traditional use of MDE where tools and techniques are used by engineers to develop software and generate code, the focus in our approach is on the end users.The entire solution has been implemented and works coupled with the engine. That is to say, our solution is able to intercept the applications models built by the engine, to transform them into presentable models that can be understood and modified by the user, and finally to capture the user feedback and give it back to the engine to update its knowledge.; L’intelligence ambiante vise à offrir à un utilisateur humain des applications et des services personnalisés et adaptés à la situation courante. L’environnement ambiant dans lequel cet humain est plongé est composé d’un ensemble d’objets connectés et de composants logicielsqui sont des briques de base pour la construction d’applications par composition. La disponibilité de ces composants peut varier dynamiquement, en cas de mobilité par exemple. Ceux-ci peuvent apparaître ou disparaître de manière non anticipée. De plus, dans ces environnements dynamiques et ouverts, le besoin de l’utilisateur humain n’est pas stable ni toujours bien défini.Pour construire des applications dans un tel contexte, et fournir à l’utilisateur “les bonnes applications au bon moment”, notre équipe explore une approche originale appelée “composition logicielle opportuniste” : l’idée est de construire des applications à la volée par assemblage de composants logiciels présents dans l’environnement sur le moment, sans se baser sur des besoins explicites ni sur des schémas de construction prédéfinis. C’est l’opportunité qui déclenche la construction des applications à la volée. Elle est contrôlée par un système intelligent, appelé moteur de composition opportuniste, qui doit décider des “bonnes” compositions à effectuer sans contribution explicite de l’utilisateur. Ainsi, les applications “émergent” dynamiquement.Les applications émergentes peuvent être imprévues ou inconnues de l’utilisateur. Au centre du système, ce dernier doit être en informé. Il doit pouvoir les contrôler, c’est-à-dire les accepter ou les rejeter, et s’il a les compétences requises, les modifier ou même construire lui-même des applications en assemblant des composants logiciels présents dans l’environnement ambiant. Dans les tâches de contrôle, l’utilisateur doit être assisté au mieux. D’autre part, pour que le moteur de composition opportuniste construise des assemblages pertinents en l’absence de besoins explicites, il doit recevoir des informations de l’utilisateur. Ceci ne doit cependant pas entraîner, pour l’utilisateur, une surcharge d’information ou d’opérations à effectuer.Dans cette thèse, nous proposons une approche basée sur l’ingénierie dirigée par les modèles (IDM) afin de mettre l’utilisateur “au centre de la boucle”. Il s’agit de lui présenter les applications émergentes, de l’assister dans son contrôle et d’extraire des données de feedback utiles à fournir au moteur de composition “intelligent”.Notre solution repose sur un métamodèle d’assemblage de composants logiciels, des langages spécifiques à un domaine (DSL) qui supportent la description des applications, un éditeur graphique qui permet d’éditer les applications et de capturer le feedback de l’utilisateur.Différentes transformations de modèle permettent l’interfaçage avec le moteur de composition et la génération de différentes formes de descriptions structurelles et sémantiques des applications pour des utilisateurs différents. En outre, les descriptions peuvent être facilement ajustées à un humain particulier, en changeant ou en adaptant les DSL et les transformations de modèle au profil de l’utilisateur.Dans notre approche, contrairement à l’utilisation classique de l’IDM où les outils et les techniques sont utilisés par les ingénieurs pour développer des logiciels et générer du code, le focus est sur les utilisateurs finaux qui prennent la place des ingénieurs.L’ensemble de la solution a été implémentée et fonctionne de manière couplée avec le moteur de composition opportuniste : notre solution prend en entrée les applications proposées par le moteur, les transforme en des modèles présentables, compréhensibles et modifiables par l’utilisateur, et enfin capture le feedback

International audience; While the use of components grows in software development, building effective component directories becomes a critical issue as architects need help to search components in repositories. During the life-cycle of component-based software, several tasks, such as construction from scratch or component substitution, would benefit from an efficient component classification and retrieval. In this paper, we analyze how we can build a classification of components using their technical description (i.e. functions and interfaces) in order to help automatic as well as manual composition and substitution. The approach is implemented in the CoCoLa prototype, which is dedicated to Fractal component directory management and validated through a case study.

Automatic program specialization can derive efficient implementations from generic components, thus reconciling the often opposing goals of genericity and efficiency. This technique has proved useful within the domains of imperative, functional, and logical languages, but so far has not been explored within the domain of object-oriented languages. We present experiments in the specialization of Java programs. We demonstrate how to construct a program specializer for Java programs from an existing specializer for C programs and a Java-to-C compiler. Specialization is managed using a declarative approach that abstracts over the optimization process and masks implementation details. Our experiments show that program specialization provides a four-time speedup of an image-filtering program. Based on these experiments, we identify optimizations of object-oriented programs that can be carried out by automatic program specialization. We argue that program specialization is useful in the field of software components, allowing a generic component to be specialized to a specific configuration.

Software developing organizations nowadays have a wide choice when it comes to sourcing software components. This choice ranges from developing or adapting in-house developed components via buying closed source components to utilizing open source components. This study aims at structured decision support in this type of decision. As a basis for this study an initial set of criteria is taken, that has been identified and validated in a particular software development environment in a previous study on the subject (Kusters et al, 2016). In the paper at hand we report on the results of the application and validation of the initial set of sourcing criteria in a completely different case study environment, namely a software environment in that. medical embedded software is being developed. In addition, and based on the outcomes of our case study, a further step is made towards structured decision support for sourcing decisions by the development of an initial sourcing criteria framework.

This report is the first deliverable of WP4 “Technology Support” of the CLARITY project, funded by the EU’s Horizon 2020 Programme under Grant Agreement number 730355. WP4 intends to provide the technological backbone of the CLARITY Climate Service Information System (CSIS) by tailoring the technological background foreseen in the CLARITY work package descriptions to project needs. For this, WP4 will integrate and adapt all required and existing (background) tools and services that are necessary for realisation of the CLARITY reference scenarios (Demonstration Cases) and implementation of the EU-GL into the CLARITY Climate Services. The aim of this deliverable is to provide an initial plan for the WP4 work per task, taking into account the input from D1.1 “Initial Workshops and the CLARITY Development Environment”: T4.2 "Catalogue of elements at risk and adaptation options" provides a catalogue that will serve as repository of element at risk types and adaptation options and a dedicated Catalogue of Data Sources and Simulation Models that makes climate-related information accessible and discoverable. T4.3 "Scenario Management" will offer the Scenario Management tool which supports and enforces first and foremost the standardised workflows of the EU-GL for each of the distinct planning steps, a Data Dashboard that provides an overview of all the different datasets that are used, produced, ordered, collected, requested, exchanged etc. by an end user and a Data Package Export and Import Tool for exporting any data that is directly available in the CSIS. T4.4 "Scenario Transferability" provides a Map Component for clear and easy visualization of different maps and layers as well as the Scenario Transferability Component that offers general matchmaking functionality by means of graphical user interfaces (e.g. map visualisations) for side-by-side comparison of alternate (adaptation) scenarios. T4.5 Scenario Analysis, Decision Support and Report Generation provides software that will support the analysis and comparison of scenario candidates (options) regarding performance indicators that can be defined by the end user. Detailed information for each of the WP4 tasks is provided as a separate section in this document. Annex 1 also provides an overview of the tools that are inherited from previous projects and explains the initial plan for using and/or extending these inputs in CLARITY.

For a software system to be perceived as a success, or even just as properly functioning, many quality attributes, besides functionality, need to be at an acceptable level. However, current software development processes focus on the functional aspects of a system to be developed. They hardly help to systematically engineer for quality attributes other than functionality. It is a system`s architecture by which such quality requirements are satisfied. In particular, software components are an incarnation of architectural means, which have come into being to better cope with the variety of quality aspects of software systems. Unfortunately, architectural artifacts appear somewhat magically sometimes, and so do components. Hence, components are not a major extension to OO in the programming language or conceptual modeling sense, but a basis to address many of the quality requirements, be they discernable or non-discernable at system runtime. CBSE, being the discipline of engineering with components, is a promising basis to more explicitly and systematically design with and for quality attributes. After defining the context and classifying quality attributes, we first illustrate the important relationship of quality attributes to use case realizations. Second, we argue for components as the fulcrum point for the realization of functional and extra-functional roles. Third, we identify ongoing research directions that we consider conducive towards a software engineering process that supports the design for functional and extra-functional requirements.

In this report, we present the application of the CADP verification toolbox to check the correctness of an industrial protocol for deploying and configuring transparently a large set of heterogeneous software components over a set of distributed computers/devices. To cope with the intrinsic complexity of this protocol, compositional verification techniques have been used, including incremental minimization and projections over automatically generated interfaces as advocated by Graf & Steffen and Krimm & Mounier. Starting from the XML description of a configuration of components to be deployed by the protocol, a translator produces a set of LOTOS descriptions, mu-calculus formulas, and the corresponding compositional verification scenario to be executed. The approach is fully automated, as formal methods and tool invocations are made invisible to the end-user, who only has to check the verification results for the configuration under study. Due to the use of compositional verification, the approach can scale to large configurations. So far, LOTOS descriptions of more than seventy concurrent processes have been verified successfully.

This paper introduces a calculus of state-based software components modelled as concrete coalgebras for some Set endofunctors, with specified initial conditions. The calculus is parametrized by a notion of behaviour, introduced as a strong (usually commutative) monad. The proposed component model and calculus are illustrated through the characterisation of a particular class of components, classified as separable, which includes the ones arising in the so-called model oriented approach to systems’ design.

Reusing software assets has many advantages and has been essential feature of all software development approaches. Component based software development has been especially inspired by reuse. In order to reuse software component, the component has to be designed and built for reusability. Since reusability is influenced by a number of different factors, there are various approaches and metrics used to measure reusability. In this paper we conducted extensive literature review in order to identify reusability metrics and factors influencing reusability. Total of 39 papers introducing reusability metrics were found and analyzed. We identified 36 different factors influencing reusability, 12 black box component metrics and more than 20 white box/glass box metrics.

In this PhD, a design support methodology and framework is proposed. It aims at supporting designer tools and methods during the overall design process, by considering the complexity of product to design as well as the unpredictability of such a process. Our framework methodology is based on software component, which enables to integrate existing simulation software without programming in order to use it in services like optimization, for instance. A visual and recursive composition software allows to compose models in the framework, as well as to define and implement design process workflow. Some of the framework applications are detailed here like three-phased voltage transformer modelling and sizing, magnetic micro-actuator design or assistance during the concurrent design of an electromagnetic plunger.; Ce travail de thèse propose une méthodologie et des outils pour un environnement d'aide à la conception. L'objectif est le support des outils et méthodes du concepteur durant le processus de conception en considérant la complexité des produits à concevoir et l'imprévisibilité de ce processus. Nous utilisons pour cela le concept de composant logiciels métiers à partir duquel il est possible, par exemple, d'intégrer des logiciels de simulation existants sans programmation, puis de les utiliser dans des services tels que l'optimisation. L'environnement dispose également d'un service de composition visuelle et récursive pour agréger les modèles, ainsi que pour définir et mettre en oeuvre le séquencement du processus de conception. Nous détaillons des applications de l'environnement pour dimensionner un transformateur de tensions triphasées, concevoir un micro-actionneur magnétique ou assister la conception collaborative d'un contacteur électromécanique.