Spelling suggestions: "subject:"modeldriven 8oftware devevelopment"" "subject:"modeldriven 8oftware agentdevelopment""
1 |
Automatic Generation of Trace Links in Model-driven Software DevelopmentGrammel, Birgit 02 December 2014 (has links) (PDF)
Traceability data provides the knowledge on dependencies and logical relations existing amongst artefacts that are created during software development. In reasoning over traceability data, conclusions can be drawn to increase the quality of software.
The paradigm of Model-driven Software Engineering (MDSD) promotes the generation of software out of models. The latter are specified through different modelling languages. In subsequent model transformations, these models are used to generate programming code automatically. Traceability data of the involved artefacts in a MDSD process can be used to increase the software quality in providing the necessary knowledge as described above.
Existing traceability solutions in MDSD are based on the integral model mapping of transformation execution to generate traceability data. Yet, these solutions still entail a wide range of open challenges. One challenge is that the collected traceability data does not adhere to a unified formal definition, which leads to poorly integrated traceability data. This aggravates the reasoning over traceability data. Furthermore, these traceability solutions all depend on the existence of a transformation engine.
However, not in all cases pertaining to MDSD can a transformation engine be accessed, while taking into account proprietary transformation engines, or manually implemented transformations. In these cases it is not possible to instrument the transformation engine for the sake of generating traceability data, resulting in a lack of traceability data.
In this work, we address these shortcomings. In doing so, we propose a generic traceability framework for augmenting arbitrary transformation approaches with a traceability mechanism. To integrate traceability data from different transformation approaches, our approach features a methodology for augmentation possibilities based on a design pattern. The design pattern supplies the engineer with recommendations for designing the traceability mechanism and for modelling traceability data.
Additionally, to provide a traceability mechanism for inaccessible transformation engines, we leverage parallel model matching to generate traceability data for arbitrary source and target models. This approach is based on a language-agnostic concept of three similarity measures for matching. To realise the similarity measures, we exploit metamodel matching techniques for graph-based model matching. Finally, we evaluate our approach according to a set of transformations from an SAP business application and the domain of MDSD.
|
2 |
Software architectures for cloud robotics : the 5 view Hyperactive Transaction Meta-Model (HTM5) / Architectures logicielles pour la robotique en nuageNagrath, Vineet 15 January 2015 (has links)
Le développement de logiciels pour les robots connectés est une difficulté majeure dans le domaine du génie logiciel. Les systèmes proposés sont souvent issus de la fusion de une ou plusieurs plates-formes provenant des robots, des ordinateurs autonomes, des appareils mobiles, des machines virtuelles, des caméras et des réseaux. Nous proposons ici une approche orientée agent permettant de représenter les robots et tous les systèmes auxiliaires comme des agents d’un système. Ce concept de l’agence préserve l’autonomie sur chacun des agents, ce qui est essentiel dans la mise en oeuvre logique d’un nuage d’éléments connectés. Afin de procurer une flexibilité de mise en oeuvre des échanges entre les différentes entités, nous avons mis en place un mécanisme d’hyperactivité ce qui permet de libérer sélectivement une certaine autonomie d’un agent par rapport à ces associés.Actuellement, il n’existe pas de solution orientée méta-modèle pour décrire les ensembles de robots interconnectés. Dans cette thèse, nous présentons un méta-modèle appelé HTM5 pour spécifier a structure, les relations, les échanges, le comportement du système et l’hyperactivité dans un système de nuages de robots. La thèse décrit l’anatomie du méta-modèle (HTM5) en spécifiant les différentes couches indépendantes et en intégrant une plate-forme indépendante de toute plateforme spécifique. Par ailleurs, la thèse décrit également un langage de domaine spécifique pour la modélisation indépendante dans HTM5. Des études de cas concernant la conception et la mise en oeuvre d’un système multi-robots basés sur le modèle développé sont également présentés dans la thèse. Ces études présentent des applications où les décisions commerciales dynamiques sont modélisées à l’aide du modèle HTM5 confirmant ainsi la faisabilité du méta-modèle proposé. / Software development for cloud connected robotic systems is a complex software engineeringendeavour. These systems are often an amalgamation of one or more robotic platforms, standalonecomputers, mobile devices, server banks, virtual machines, cameras, network elements and ambientintelligence. An agent oriented approach represents robots and other auxiliary systems as agents inthe system.Software development for distributed and diverse systems like cloud robotic systems require specialsoftware modelling processes and tools. Model driven software development for such complexsystems will increase flexibility, reusability, cost effectiveness and overall quality of the end product.The proposed 5-view meta-model has separate meta-models for specifying structure, relationships,trade, system behaviour and hyperactivity in a cloud robotic system. The thesis describes theanatomy of the 5-view Hyperactive Transaction Meta-Model (HTM5) in computation independent,platform independent and platform specific layers. The thesis also describes a domain specificlanguage for computation independent modelling in HTM5.The thesis has presented a complete meta-model for agent oriented cloud robotic systems and hasseveral simulated and real experiment-projects justifying HTM5 as a feasible meta-model.
|
3 |
Automatic Generation of Trace Links in Model-driven Software DevelopmentGrammel, Birgit 17 February 2014 (has links)
Traceability data provides the knowledge on dependencies and logical relations existing amongst artefacts that are created during software development. In reasoning over traceability data, conclusions can be drawn to increase the quality of software.
The paradigm of Model-driven Software Engineering (MDSD) promotes the generation of software out of models. The latter are specified through different modelling languages. In subsequent model transformations, these models are used to generate programming code automatically. Traceability data of the involved artefacts in a MDSD process can be used to increase the software quality in providing the necessary knowledge as described above.
Existing traceability solutions in MDSD are based on the integral model mapping of transformation execution to generate traceability data. Yet, these solutions still entail a wide range of open challenges. One challenge is that the collected traceability data does not adhere to a unified formal definition, which leads to poorly integrated traceability data. This aggravates the reasoning over traceability data. Furthermore, these traceability solutions all depend on the existence of a transformation engine.
However, not in all cases pertaining to MDSD can a transformation engine be accessed, while taking into account proprietary transformation engines, or manually implemented transformations. In these cases it is not possible to instrument the transformation engine for the sake of generating traceability data, resulting in a lack of traceability data.
In this work, we address these shortcomings. In doing so, we propose a generic traceability framework for augmenting arbitrary transformation approaches with a traceability mechanism. To integrate traceability data from different transformation approaches, our approach features a methodology for augmentation possibilities based on a design pattern. The design pattern supplies the engineer with recommendations for designing the traceability mechanism and for modelling traceability data.
Additionally, to provide a traceability mechanism for inaccessible transformation engines, we leverage parallel model matching to generate traceability data for arbitrary source and target models. This approach is based on a language-agnostic concept of three similarity measures for matching. To realise the similarity measures, we exploit metamodel matching techniques for graph-based model matching. Finally, we evaluate our approach according to a set of transformations from an SAP business application and the domain of MDSD.
|
4 |
Generative und modellgetriebene Softwarevisualisierung am Beispiel der StadtmetapherZilch, Denise 17 September 2015 (has links) (PDF)
Für den Visualisierungsgenerator der Forschungsgruppe „Softwarevisualisierung in drei Dimensionen und virtueller Realität“ soll eine Stadtmetapher zur Darstellung von Software implementiert werden. Als Vorlage dient „CodeCity“, dessen Umsetzung der Stadtmetapher auf den Generator übertragen werden soll. Die Anforderungsermittlung basiert auf der Analyse beider Bestandteile, um ein strukturiertes Vorgehen zu gewährleisten. Die Implementierung der Generatorartefakte erfolgt mittels Xtext zur Erstellung eines Metamodells, das die Entitäten der neuen Metapher beschreibt, und Xtend, das genutzt wird um die Datenmodelle zu modifizieren und in Quelltext umzuwandeln. Darauf aufbauend folgt abschließend die Abstraktion zu einem Prozessmodell für die generative und modellgetriebene Softwarevisualisierung, das als Leitfaden für zukünftige Implementierungen dienen soll.
|
5 |
Designing Round-Trip Systems by Change Propagation and Model PartitioningSeifert, Mirko 26 July 2011 (has links) (PDF)
Software development processes incorporate a variety of different artifacts (e.g., source code, models, and documentation). For multiple reasons the data that is contained in these artifacts does expose some degree of redundancy. Ensuring global consistency across artifacts during all stages in the development of software systems is required, because inconsistent artifacts can yield to failures. Ensuring consistency can be either achieved by reducing the amount of redundancy or by synchronizing the information that is shared across multiple artifacts. The discipline of software engineering that addresses these problems is called Round-Trip Engineering (RTE).
In this thesis we present a conceptual framework for the design RTE systems. This framework delivers precise definitions for essential terms in the context of RTE and a process that can be used to address new RTE applications. The main idea of the framework is to partition models into parts that require synchronization - skeletons - and parts that do not - clothings. Once such a partitioning is obtained, the relations between the elements of the skeletons determine whether a deterministic RTE system can be built. If not, manual decisions may be required by developers. Based on this conceptual framework, two concrete approaches to RTE are presented.
The first one - Backpropagation-based RTE - employs change translation, traceability and synchronization fitness functions to allow for synchronization of artifacts that are connected by non-injective transformations. The second approach - Role-based Tool Integration - provides means to avoid redundancy. To do so, a novel tool design method that relies on role modeling is presented. Tool integration is then performed by the creation of role bindings between role models.
In addition to the two concrete approaches to RTE, which form the main contributions of the thesis, we investigate the creation of bridges between technical spaces. We consider these bridges as an essential prerequisite for performing logical synchronization between artifacts. Also, the feasibility of semantic web technologies is a subject of the thesis, because the specification of synchronization rules was identified as a blocking factor during our problem analysis.
The thesis is complemented by an evaluation of all presented RTE approaches in different scenarios. Based on this evaluation, the strengths and weaknesses of the approaches are identified. Also, the practical feasibility of our approaches is confirmed w.r.t. the presented RTE applications.
|
6 |
Designing Round-Trip Systems by Change Propagation and Model PartitioningSeifert, Mirko 28 June 2011 (has links)
Software development processes incorporate a variety of different artifacts (e.g., source code, models, and documentation). For multiple reasons the data that is contained in these artifacts does expose some degree of redundancy. Ensuring global consistency across artifacts during all stages in the development of software systems is required, because inconsistent artifacts can yield to failures. Ensuring consistency can be either achieved by reducing the amount of redundancy or by synchronizing the information that is shared across multiple artifacts. The discipline of software engineering that addresses these problems is called Round-Trip Engineering (RTE).
In this thesis we present a conceptual framework for the design RTE systems. This framework delivers precise definitions for essential terms in the context of RTE and a process that can be used to address new RTE applications. The main idea of the framework is to partition models into parts that require synchronization - skeletons - and parts that do not - clothings. Once such a partitioning is obtained, the relations between the elements of the skeletons determine whether a deterministic RTE system can be built. If not, manual decisions may be required by developers. Based on this conceptual framework, two concrete approaches to RTE are presented.
The first one - Backpropagation-based RTE - employs change translation, traceability and synchronization fitness functions to allow for synchronization of artifacts that are connected by non-injective transformations. The second approach - Role-based Tool Integration - provides means to avoid redundancy. To do so, a novel tool design method that relies on role modeling is presented. Tool integration is then performed by the creation of role bindings between role models.
In addition to the two concrete approaches to RTE, which form the main contributions of the thesis, we investigate the creation of bridges between technical spaces. We consider these bridges as an essential prerequisite for performing logical synchronization between artifacts. Also, the feasibility of semantic web technologies is a subject of the thesis, because the specification of synchronization rules was identified as a blocking factor during our problem analysis.
The thesis is complemented by an evaluation of all presented RTE approaches in different scenarios. Based on this evaluation, the strengths and weaknesses of the approaches are identified. Also, the practical feasibility of our approaches is confirmed w.r.t. the presented RTE applications.
|
7 |
Model-Driven Technical Space Integration Based on a Mapping Approach / Приступ интеграцији техничких простора заснован на пресликавањима иинжењерству вођеном моделима / Pristup integraciji tehničkih prostora zasnovan na preslikavanjima iinženjerstvu vođenom modelimaDimitrieski Vladimir 30 March 2018 (has links)
<p>In order to automate development of integration adapters in industrial<br />settings, a model-driven approach to adapter specification is devised. In this<br />approach, a domain-specific modeling language is created to allow<br />specification of mappings between integrated technical spaces. Also<br />proposed is the mapping automation engine that comprises reuse and<br />alignment algorithms. Based on mapping specifications, executable adapters<br />are automatically generated and executed. Results of approach evaluations<br />indicate that it is possible to use a model-driven approach to successfully<br />integrate technical spaces and increase the automation by reusing domainspecific<br />mappings from previously created adapters.</p> / <p>За потребе повећања степена аутоматизације развоја адаптера за<br />интеграцију у индустријском окружењу, осмишљен је моделом вођен<br />приступ развоју адаптера. У оквиру овог приступа развијен је наменски<br />језик за спецификацију пресликавања између техничких простора који су<br />предмет интеграције. Приступ обухвата и алгоритме за поравнање и<br />поновно искориштење претходно креираних пресликавања са циљем<br />аутоматизације процеса спецификације. На основу креираних<br />пресликавања, могуће je аутоматски генерисати извршиви код адаптера.<br />У испитивањима приступа, показано је да је могуће успешно применити<br />моделом вођен приступ у интеграцији техничких простора као и да је<br />могуће успешно повећати степен аутоматизације поновним<br />искоришћењем претходно креираних пресликавања.</p> / <p>Za potrebe povećanja stepena automatizacije razvoja adaptera za<br />integraciju u industrijskom okruženju, osmišljen je modelom vođen<br />pristup razvoju adaptera. U okviru ovog pristupa razvijen je namenski<br />jezik za specifikaciju preslikavanja između tehničkih prostora koji su<br />predmet integracije. Pristup obuhvata i algoritme za poravnanje i<br />ponovno iskorištenje prethodno kreiranih preslikavanja sa ciljem<br />automatizacije procesa specifikacije. Na osnovu kreiranih<br />preslikavanja, moguće je automatski generisati izvršivi kod adaptera.<br />U ispitivanjima pristupa, pokazano je da je moguće uspešno primeniti<br />modelom vođen pristup u integraciji tehničkih prostora kao i da je<br />moguće uspešno povećati stepen automatizacije ponovnim<br />iskorišćenjem prethodno kreiranih preslikavanja.</p>
|
8 |
Integrierte und hybride Konstruktion von Software-ProduktlinienDinger, Ulrich 10 September 2009 (has links) (PDF)
Die Konzepte zur Erstellung von Software-Produktlinien dienen der ingenieurmäßigen, unternehmensinternen Wiederverwendung existierender Software-Artefakte. Existierende Ansätze nutzen von Hand erstellte und gewartete Kompositionsprogramme zum Assemblieren der Produkte entsprechend einer Variantenauswahl. Der Einsatz einer automatischen Planungskomponente sowie eines einfachen, erweiterbaren Komponenten-Meta-Modells hilft dabei, die dabei anfallenden Daten computergestützt zu verarbeiten. Die Integration beider Konzepte zu einem hybriden Ansatz ermöglicht die Neuerstellung von Produkten, die nicht von Anfang an als Produktlinie konzipiert sind, ohne eine spätere Umarbeitung unter Nutzung der automatischen Planungskomponente unnötig zu erschweren.
|
9 |
Component-Based Model-Driven Software DevelopmentJohannes, Jendrik 07 January 2011 (has links) (PDF)
Model-driven software development (MDSD) and component-based software development are both paradigms for reducing complexity and for increasing abstraction and reuse in software development. In this thesis, we aim at combining the advantages of each by introducing methods from component-based development into MDSD. In MDSD, all artefacts that describe a software system are regarded as models of the system and are treated as the central development artefacts. To obtain a system implementation from such models, they are transformed and integrated until implementation code can be generated from them. Models in MDSD can have very different forms: they can be documents, diagrams, or textual specifications defined in different modelling languages. Integrating these models of different formats and abstraction in a consistent way is a central challenge in MDSD.
We propose to tackle this challenge by explicitly separating the tasks of defining model components and composing model components, which is also known as distinguishing programming-in-the-small and programming-in-the-large. That is, we promote a separation of models into models for modelling-in-the-small (models that are components) and models for modelling-in-the-large (models that describe compositions of model components). To perform such component-based modelling, we introduce two architectural styles for developing systems with component-based MDSD (CB-MDSD).
For CB-MDSD, we require a universal composition technique that can handle models defined in arbitrary modelling languages. A technique that can handle arbitrary textual languages is universal invasive software composition for code fragment composition. We extend this technique to universal invasive software composition for graph fragments (U-ISC/Graph) which can handle arbitrary models, including graphical and textual ones, as components. Such components are called graph fragments, because we treat each model as a typed graph and support reuse of partial models.
To put the composition technique into practice, we developed the tool Reuseware that implements U-ISC/Graph. The tool is based on the Eclipse Modelling Framework and can therefore be integrated into existing MDSD development environments based on the framework.
To evaluate the applicability of CB-MDSD, we realised for each of our two architectural styles a model-driven architecture with Reuseware. The first style, which we name ModelSoC, is based on the component-based development paradigm of multi-dimensional separation of concerns. The architecture we realised with that style shows how a system that involves multiple modelling languages can be developed with CB-MDSD. The second style, which we name ModelHiC, is based on hierarchical composition. With this style, we developed abstraction and reuse support for a large modelling language for telecommunication networks that implements the Common Information Model industry standard.
|
10 |
MARISA-MDD: uma abordagem para transforma??es entre modelos orientados a aspectos: dos requisitos ao projeto detalhadoMedeiros, Ana Luisa Ferreira de 09 June 2008 (has links)
Made available in DSpace on 2014-12-17T15:47:47Z (GMT). No. of bitstreams: 1
AnaLFM.pdf: 903790 bytes, checksum: 70d26a43bc5418b76d2ecdc1716d862c (MD5)
Previous issue date: 2008-06-09 / Aspect Oriented approaches associated to different activities of the software development process are, in general, independent and their models and artifacts are not aligned and inserted in
a coherent process. In the model driven development, the various models and the correspondence between them are rigorously specified. With the integration of aspect oriented software development (DSOA) and model driven development (MDD) it is possible to automatically propagate models from one activity to another, avoiding the loss of information and important decisions established in each activity. This work presents MARISA-MDD, a strategy based on models that integrate aspect-oriented requirements, architecture and detailed design, using the languages AOV-graph, AspectualACME and aSideML, respectively. MARISA-MDD defines, for each activity, representative models (and corresponding metamodels) and a number of transformations between the models of each language. These transformations have been specified and implemented in ATL (Atlas Definition Language), in the Eclipse environment. MARISA-MDD allows the automatic propagation between AOV-graph, AspectualACME, and aSideML models. To validate the proposed approach two case studies, the Health Watcher and the Mobile Media have been used in the MARISA-MDD environment for the automatic
generation of AspectualACME and aSideML models, from the AOV-graph model / As abordagens orientadas a aspectos relacionadas a diferentes atividades do processo de desenvolvimento de software s?o, em geral, independentes e os seus modelos e artefatos n?o
est?o alinhados ou inseridos em um processo coerente. No desenvolvimento orientado a, modelos, os diversos modelos e a correspond?ncia entre eles s?o especificados com rigor. Com a
integra??o do desenvolvimento orientado a aspectos (DSOA) e o desenvolvimento baseado em modelos (MDD) pode-se automaticamente propagar modelos de uma atividade para outra
atividade, evitando a perda de informa??es e de decis?es importantes estabelecidas em cada atividade. Este trabalho apresenta MARISA-MDD, uma estrat?gia baseada em modelos que integra as atividades de requisitos, arquitetura e projeto detalhado orientado a aspectos, usando as linguagens AOV-graph, AspectualACME e aSideML, respectivamente. MARISA-MDD define, para cada atividade, modelos representativos (e metamodelos correspondentes) e um
conjunto de transforma??es entre os modelos de cada linguagem. Tais transforma??es foram especificadas e implementadas em ATL (Atlas Definition Language), no ambiente Eclipse. MARISA-MDD permite a propaga??o autom?tica entre modelos AOV-graph, AspectualACME e aSideML. Para validar a abordagem proposta dois estudos de caso, o Health Watcher e o
Mobile Media foram usados no ambienteMARISA-MDD para gera??o autom?tica dos modelos AspectualACME e aSideML, a partir do modelo AOV-graph
|
Page generated in 0.0605 seconds