Statische Codemetriken sind wichtige Indikatoren für die Qualität eines Softwaresystems. Sie beleuchten dabei unterschiedliche Aspekte eines Softwaresystems. Deshalb ist es notwendig, mehrere Codemetriken zu nutzen, um die Qualität eines Softwaresystems in seiner Gesamtheit bewerten zu können. Wünschenswert wäre zudem eine Darstellung, die die Struktur des Gesamtsystems und die Bewertung einzelner Elemente eines Softwaresystems in einer Darstellung kombiniert. Die Arbeit untersucht deshalb, welche Metaphern geeignet sind, um eine solche Darstellung zu ermöglichen. Ein zweites Ziel der Arbeit war es, eine solche Visualisierung automatisch erzeugen zu können. Dafür wurde ein Generator entwickelt, der diese Anforderung erfüllt. Zur Konzeption dieses Generators kamen Techniken aus der generativen Softwareentwicklung zum Einsatz. Bei der Umsetzung des Generators wurde auf Techniken aus der modellgetriebenen Softwareentwicklung zurückgegriffen, vor allem auf Techniken aus dem openArchitectureWare-Framework. Der Generator kann in Eclipse eingebunden werden und ist in der Lage, aus einem Java-Projekt die Struktur und die Metrikwerte automatisch zu extrahieren. Diese Werte werden daraufhin in ein dreidimensionales Modell überführt, das auf dem offenen Extensible 3D Standard basiert. Der Generator ermöglichte zudem die Evaluierung zweier unterschiedlicher Metaphern, die im Rahmen der Arbeit durchgeführt wurde.

Tesis por compendio / [ES] La investigación desarrollada en esta tesis representa un marco novedoso para capturar requisitos de usabilidad durante el desarrollo de un sistema software. Estos requisitos, están representados como alternativas de diseños de Interfaces de Usuario (IU). El objetivo es desarrollar un proceso de captura de requisitos de usabilidad basado en entrevistas estructuradas con el apoyo de una herramienta que ayude a resolver problemas como: (1) la omisión de la usabilidad desde las primeras etapas de desarrollo, en general, las características de usabilidad solo se tienen en cuenta al diseñar las interfaces en las últimas etapas de desarrollo; (2) resulta tedioso la captura de requisitos para analistas que no son expertos en usabilidad; (3) los métodos y herramientas que se utilizan para desarrollar software no admiten la elicitación de requisitos de usabilidad. A partir de estos problemas encontrados en la literatura se definen las preguntas de investigación: ¿Es posible capturar requisitos de usabilidad en etapas iniciales de desarrollo al mismo tiempo que los requisitos funcionales? Para responder a esta pregunta, la tesis ha definido un método de elicitación de requisitos de usabilidad llamado UREM (por sus siglas en inglés, Usability Requirements Elicitation Method) y ha propuesto un método para tratarlo dentro de entornos MDD. El desarrollo de este trabajo de investigación se ha llevado a cabo siguiendo la metodología Design Science. Esta metodología considera dos ciclos: el primer ciclo es un ciclo de ingeniería en el que se diseña un método para incluir requisitos de usabilidad durante el proceso de elicitación de requisitos. El segundo ciclo corresponde a la validación del método propuesto mediante una evaluación empírica dentro de un contexto académico. La propuesta de captura de requisitos de usabilidad mediante UREM consiste en la definición de una estructura de un árbol donde las guías de usabilidad y las guías de diseño de IU están almacenadas. El árbol se define como un grafo conectado sin ciclos y una raíz; compuesto de 4 elementos: pregunta, respuesta, grupo de preguntas y diseño. Las preguntas y las alternativas de diseño (respuestas) son extraídas de las guías de usabilidad y de diseño, y marcan el camino por el cual el analista navega hasta llegar a los nodos hoja que son los diseños de la interfaz de usuario que se han alcanzado durante el proceso de captura de requisitos de usabilidad. Son los usuarios finales quienes eligen la alternativa más adecuada dependiendo de sus requisitos y/o siguiendo las recomendaciones ya preestablecidas en la estructura del árbol. La construcción del árbol la lleva a cabo un experto en usabilidad y puede ser utilizado en reiteradas ocasiones, generando así diversas alternativas de diseño de interfaz de usuario. La tesis presenta el trabajo relacionado en tres áreas: elicitación de requisitos de usabilidad, uso de guías de usabilidad e ingeniería empírica de software. / [CA] La investigació desenvolupada en aquesta tesi representa un marc nou per a capturar requisits d'usabilitat durant el desenvolupament d'un sistema programari. Aquests requisits, estan representats com a alternatives de dissenys d'Interfícies d'Usuari (IU). L'objectiu és desenvolupar un procés de captura de requisits d'usabilitat basat en entrevistes estructurades amb el suport d'una eina que ajude a resoldre problemes com: (1) l'omissió de la usabilitat des de les primeres etapes de desenvolupament, en general, les característiques d'usabilitat només es tenen en compte en dissenyar les interfícies en les últimes etapes de desenvolupament; (2) resulta tediós la captura de requisits per a analistes que no són experts en usabilitat; (3) els mètodes i eines que s'utilitzen per a desenvolupar programari no admeten l'elicitació de requisits d'usabilitat. A partir d'aquests problemes trobats en la literatura es defineixen les preguntes d'investigació: És possible capturar requisits d'usabilitat en etapes inicials de desenvolupament al mateix temps que els requisits funcionals? Per a respondre a aquesta pregunta, la tesi ha definit un mètode d'elicitació de requisits d'usabilitat anomenat UREM (per les seues sigles en anglés, Usability Requirements Elicitation Method) i ha proposat un mètode per a tractar-lo dins d'entorns MDD. El desenvolupament d'aquest treball de recerca s'ha dut a terme seguint la metodologia Design Science. Aquesta metodologia considera dos cicles: el primer cicle és un cicle d'enginyeria en el qual es dissenya un mètode per a incloure requisits d'usabilitat durant el procés d' elicitació de requisits. El segon cicle correspon a la validació del mètode proposat mitjançant una avaluació empírica dins d'un context acadèmic. La proposta de captura de requisits d'usabilitat mitjançant UREM consisteix en la definició d'una estructura d'un arbre on les guies d'usabilitat i les guies de disseny d'IU estan emmagatzemades. L'arbre es defineix com un graf connectat sense cicles i una arrel; compost de 4 elements: pregunta, resposta, grup de preguntes i disseny. Les preguntes i les alternatives de disseny (respostes) són extretes de les guies d'usabilitat i de disseny, i marquen el camí pel qual l'analista navega fins a arribar als nodes fulla que són els dissenys de la interfície d'usuari que s'han aconseguit durant el procés de captura de requisits d'usabilitat. Són els usuaris finals els qui trien l'alternativa més adequada depenent dels seus requisits i/o seguint les recomanacions ja preestablides en l'estructura de l'arbre. La construcció de l'arbre la duu a terme un expert en usabilitat i pot ser utilitzat en reiterades ocasions, generant així diverses alternatives de disseny d'interfície d'usuari. La tesi presenta el treball relacionat en tres àrees: elicitació de requisits d'usabilitat, ús de guies d'usabilitat i enginyeria empírica de programari. / [EN] The research developed in this thesis represents a novel framework for capturing usability requirements during the development of a software system. These requirements are represented as alternative User Interface (UI) designs. The objective is to develop a usability requirements capture process based on structured interviews with the support of a tool that helps solve problems such as: (1) the omission of usability from the early stages of development, in general, the characteristics of Usability is only taken into account when designing interfaces in the later stages of development; (2) it is tedious to capture requirements for analysts who are not usability experts; (3) the methods and tools used to develop software do not support the elicitation of usability requirements. Based on these problems found in the literature, the research questions are defined: Is it possible to capture usability requirements in initial stages of development at the same time as functional requirements? To answer this question, the thesis has defined a usability requirements elicitation method called UREM (Usability Requirements Elicitation Method) and has proposed a method to treat it within MDD environments. The development of this research work has been carried out following the Design Science methodology. This methodology considers two cycles: the first cycle is an engineering cycle in which a method is designed to include usability requirements during the requirements elicitation process. The second cycle corresponds to the validation of the proposed method through an empirical evaluation within an academic context. The proposal to capture usability requirements through UREM consists of the definition of a tree structure where the usability guides and UI design guides are stored. The tree is defined as a connected graph without cycles and a root; composed of 4 elements: question, answer, group of questions and design. The questions and design alternatives (answers) are extracted from the usability and design guides, and mark the path along which the analyst navigates until reaching the leaf nodes, which are the user interface designs that have been achieved. during the usability requirements capture process. It is the end users who choose the most appropriate alternative depending on their requirements and/or following the recommendations already pre-established in the tree structure. The construction of the tree is carried out by a usability expert and can be used repeatedly, thus generating various user interface design alternatives. The thesis presents related work in three areas: usability requirements elicitation, use of usability guides, and empirical software engineering. / This work has been developed with the support of MICINN (PROS-Req TIN2010-19130-C02- 02), UV (UV-INV-PRECOMP13-115032), GVA (ORCA PROMETEO/2009/015), and cofinanced with ERDF. We also acknowledge the support of the Intra European Marie Curie Fellowship Grant 50911302 PIEF-2010. We acknowledge also the support from the National University of San Antonio Abad of Cusco under the program Yachayninchis Wiñarinanpaq CONCYTEC and FONDECYT, the support of Generalitat Valenciana with CoMoDID (CIPROM/2021/023) and GENI (CIAICO/2022/229), as well as the support of the Spanish Ministry of Science and Innovation co-financed by FEDER in the project SREC (PID2021-123824OB-I00) / Ormeño Ayala, YI. (2023). Marco para la captura de requisitos de usabilidad en entornos de MDD [Tesis doctoral]. Universitat Politècnica de València. https://doi.org/10.4995/Thesis/10251/202630 / Compendio

Les travaux présentés dans cette thèse s’inscrivent dans le cadre du développement logiciel des systèmes temps réel embarqués. Nous définissons dans ce travail une méthodologie nommée DRIM. Cette méthodologie permet de guider le déploiement des applications temps réel sur différents RTOS en suivant la ligne de l’IDM et en assurant le respect des contraintes de temps après le déploiement. L’automatisation de la méthodologie DRIM montre sa capacité à détecter les descriptions non-implémentables de l’application, réalisées au niveau conception, pour un RTOS donné, ce qui présente l’avantage de réduire le temps de mise sur le marché d’une part et de guider l’utilisateur pour un choix approprié de l’RTOS cible d’autre part. / The main purpose of this Phd is to contribute to the software development of real-time embedded systems. We define in this work a methodology named DRIM: Design Refinement toward Implementation Methodology. This methodology aims to guide the deployment of a real-time application on to different RTOS while respecting MDE principals and ensuing that the timing properties are still met after deployment. The automation of DRIM shows its ability to detect non-implementable design models describing the real-time application, on aparticular RTOS, which permits to reduce the time-to-market on the one hand and guide the user to the selection of the appropriate RTOS from the other hand.

Die Telekommunikation und die ihr zuliefernde Industrie stellen einen softwareintensiven Bereich dar - der durch einen sehr hohen Anteil von Eigenentwicklungen gekennzeichnet ist. Eine wesentliche Ursache dafür sind spezielle Anforderungen an Telekommunikationssoftwaresysteme, die i.allg. nicht durch Standardsoftwareprodukte sichergestellt werden können. Diese Anforderungen ergeben sich aus den besonderen Eigenschaften solcher Softwaresysteme wie die Verteilung der Komponenten von Softwaresystemen sowie die Verteilung der Entwicklung dieser Komponenten, die Heterogenität der Entwicklungs- und Einsatzumgebungen für diese Komponenten und die Komplexität der entwickelten Softwaresysteme hinsichtlich nichtfunktionaler Charakteristika. Die industrielle Entwicklung von Telekommunikationssoftwaresystemen ist ein schwieriger und bisher nicht zufriedenstellend gelöster Prozeß. Aktuelle Forschungsarbeiten thematisieren Softwareentwicklungsprozesse und -techniken sowie unterstützende Werkzeuge zur Erstellung und Integration wiederverwendbarer Softwarekomponenten ("Componentware"). Das Ziel dieser Dissertation besteht in der Unterstützung der industriellen Entwicklung offener, verteilter Telekommunikationssoftwaresysteme. Dazu wird die Entwicklungstechnik Objektorientierte Modellierung mit dem Einsatz von Komponentenarchitekturen durch die automatische Ableitung von Softwarekomponenten aus Modellen zusammengeführt. Die zentrale Idee ist dabei eine präzise Definition der zur Entwicklung von verteilten Softwaresystemen einsetzbaren Modellierungskonzepte in Form eines Metamodells. Von diesem Metamodell ausgehend werden dann zur Konstruktion und Darstellung objektorientierter Entwurfsmodelle eine graphische und eine textuelle Notation definiert. Da die Notationen die Konzepte des Meta- Modells visualisieren, haben sie diesem gegenüber einen sekundären Charakter. Für die Transformation von Entwurfsmodellen in ausführbare Applikationen wurde auf der Grundlage von CORBA eine Komponentenplattform realisiert, die zusätzlich zu Interaktionen zwischen verteilten Softwarekomponenten auch Entwicklungs-, Deployment- und Ausführungsaspekte unterstützt. Wiederum ausgehend vom Metamodell wird durch die Anwendung wohldefinierter Ableitungsregeln die automatische Überführung von Entwurfsmodellen in Softwarekomponenten des zu entwickelnden Systems ermöglicht. Die von den Autoren erarbeiteten Konzeptionen und Vorgehensweisen wurden praktisch in eine Werkzeugumgebung umgesetzt, die sich bereits erfolgreich in verschiedenen Softwareentwicklungsprojekten bewährt hat. / The telecommunication industry and their suppliers form a software intensive domain. In addition, a high percentage of the software is developed by the telecommunication enterprises themselves. A main contributing factor for this situation are specific requirements to telecommunication software systems which cannot be fulfilled by standard off-the-shelf products. These requirements result from particular properties of those software systems, e.g. distributed development and execution of their components, heterogeneity of execution and development environments and complex non-functional characteristics like scalability, reliability, security and manageability. The development of telecommunication software systems is a complex process and currently not satisfactory realized. Actual research topics in this arena are software development processes and development techniques as well as tools which support the creation and integration of reusable software components (component ware). The goal of this thesis work is the support of the industrial development and manufacturing of open distributed telecommunication software systems. For that purpose, the development technique object oriented modelling and the implementation technique usage of component architectures are combined. The available modelling concepts are precisely defined as a metamodel. Based on that metamodel, graphical and textual notations for the presentation of models are developed. To enable a smooth transition from object oriented models into executable components a component architecture based on CORBA was also developed as part of the thesis. This component architecture covers besides the interaction support for distributed components deployment and execution aspects. Again on the basis of the metamodel code generation rules are defined which allow to automate the transition from models to components. The development techniques described in this thesis have been implemented as a tool chain. This tool chain has been successfully used in several software development projects.

Na ultima década o paradigma de computação orientada a serviços (SOC - Service Oriented Computing) tem ganhado cada vez mais espaço na indústria e na academia, a fim de solucionar o problema da falta de comunicação entre os diversos sistemas de informação presentes dentro de um ambiente corporativo. Graças aos recentes avanços da chamada \"Web 2.0\" um novo estilo arquitetural chamado de Arquitetura orientada a Web (WOA - Web Oriented Architecture) foi proposto a fim de garantir uma maneira simples de conectar os componentes de software dinamicamente. Esse estilo tem como um dos princípios o uso de serviços Web RESTful, a fim de conseguir uma interface funcional simples e uniforme. Este trabalho apresenta um ambiente colaborativo de apoio ao desenvolvimento de serviços Web RESTful utilizando o paradigma de desenvolvimento orientado a modelos (MDD - Model Driven Development). Pretende-se mostrar os benefícios do MDD aplicado a Engenharia Web e também as vantagens apresentadas pela colaboração nesse cenário. Foi realizado ainda um experimento a fim de comprovar a eficiência do ambiente colaborativo e benefícios alcançados por ele / In the last decade the paradigm of Service Oriented Computing has gained more attention in industry and academia in order to solve the problem of lack of communication between different information systems present within a corporate environment. Due to recent advances in Web 2.0 a new architectural style called Web Oriented Architecture is proposed to ensure a simple way to connect software components dynamically. This style has as a principle the use of RESTful Web Services in order to achieve a uniform interface simple and functional. This paper presents a collaborative environment to support the development of RESTful Web Services using the Model Driven Development paradigm. It is intended to show the benefits of MDD applied to Web Engineering and also the advantages presented by collaboration in this scenario. It was also performed a experiment to prove the efficiency of the collaborative environment and benefits achieved by the same

A reutilização de software busca aumentar a qualidade e produtividade no desenvolvimento de software, evitando a duplicação do esforço e reaproveitando o máximo possível das experiências de projetos passados. Apesar de simples, esta idéia não é facilmente colocada em prática, principalmente de maneira sistemática e controlada. Técnicas de engenharia de domínio e linhas de produtos de software buscam facilitar esta tarefa, porém ainda existem outros fatores que dificultam a adoção da prática da reutilização. Entre estes, destacam-se os problemas inerentes ao desenvolvimento de software da maneira como é conduzido atualmente, baseado em código-fonte. Estes problemas têm suas origens na crescente demanda por software cada vez mais complexo e afetam negativamente a capacidade de reutilizar software. O desenvolvimento orientado a modelos surge como uma alternativa atraente neste cenário, elevando a importância de modelos dentro do ciclo de vida do software, incorporando-os como parte integrante do produto final por meio de técnicas de modelagem e geração de código. Com isto, parte da complexidade do software fica escondida dentro dos geradores, protegendo os desenvolvedores, reduzindo a incidência de erros, aumentando a produtividade, qualidade, interoperabilidade e manutenibilidade dos artefatos produzidos. Nesta dissertação defende-se a tese de que o desenvolvimento orientado a modelos pode efetivamente aumentar e/ou melhorar a reutilização de software, e que para isso ela deve ser tratada de forma consistente dentro de um processo de engenharia de domínio. Para demonstrar esta tese, é apresentada uma abordagem orientada a modelos para reutilização de software, com atividades que guiam o desenvolvedor durante a análise, projeto e implementação do domínio. São também apresentados os resultados de uma avaliação envolvendo três estudos empíricos, realizados em ambiente acadêmico e industrial, que buscou determinar a viabilidade da abordagem e os benefícios que podem ser alcançados com a combinação de técnicas do desenvolvimento orientado a modelos e da reutilização de software. Os resultados mostram que a abordagem pode trazer diferentes benefícios para organizações de software, incluindo aumento da quantidade e qualidade da reutilização, e reduzindo a complexidade de desenvolvimento e configuração de produtos / Software reuse aims at increasing quality and productivity in software development, avoiding effort duplication and reusing all past experiences possible. Although it is a simple idea, it is not easy to put reuse in practice, especially in a systematic and controlled way. Domain engineering and software product lines techniques try to make this task easier, but there are many other factors that difficult the reuse adoption. Among these factors are the problems that are inherent to software development in the way it is conducted today, based on source code. These problems arise from the growing demand for increasingly complex software, negatively affecting the ability to reuse. Model-driven development is an attractive alternative in this scenario, leveraging the importance of models in the software life cycle, incorporating them as part of the final product through modeling and code generation techniques. As a result, part of the software complexity becomes hidden inside the generators, shielding the developers, reducing errors, increasing the productivity, quality, interoperability and maintainability of the produced assets. In this dissertation is presented the thesis that model-driven development can effectively increase and/or improve software reuse, and that to achieve this goal it must be treated in a consistent way inside a domain engineering process. To demonstrate this thesis, a model-driven software reuse approach is presented, with activities that guide the developer during domain analysis, design and implementation. The results of an evaluation involving three empirical studies are also presented. The studies were performed in both academic and industrial environments, and aimed at determining the viability of the approach and the benefits that can be achieved with the combination of model-driven development and software reuse techniques. The results showed that the approach can bring different benefits to software organizations, such as software reuse quantity and quality improvements, and complexity reduction in product development and configuration tasks

Esta tese apresenta um processo para a criação de um catálogo de modelos de computação para apoiar o design de DSMLs, e a primeira versão do catálogo, com atributos que ajudam a selecionar os modelos de computação mais adequados para cada desenvolvimento de DSML, e as características dos sistemas de software para os quais esses modelos de computação são mais adequados. O contexto de aplicação desse catálogo é o Model-Driven Development (MDD desenvolvimento dirigido por modelos) a abordagem em que o desenvolvimento de software é baseado em modelos gráficos que são posteriormente traduzidos (transformados) em modelos de nível mais baixo e, no final, em código de linguagens de programação, tais como Java ou C#. A aplicação do processo gerou uma versão inicial do catálogo com os seguintes modelos de computação: diagramas BPMN, diagramas de classe da UML e regras de negócio. Visa-se contribuir para popularizar a abordagem de MDD com base em DSMLs e, em particular, a elaboração do design das DSMLs a partir de modelos de domínio, para o que o uso do catálogo efetivamente contribui. / This thesis presents a process for the creation of a catalog of models of computation to support the design of Domain-Specific Modeling Languages (DSMLs), and the first version of the catalog, which comprises attributes that aim to help the selection of the most suitable models of computation for each DSML development, and characteristics of software systems for which these models of computation are more appropriate. The context for the use of the catalog is the Model-Driven Development (MDD) - the approach where software development is based on graphical models that are subsequently translated (transformed) into lower-level models and, in the end, in source code in programming languages, such as Java or C #. The process was applied to generate an initial version of the catalog with the following models of computation: BPMN diagrams, UML class diagrams and business rules. It aims to contribute to popularize the MDD approach based in DSMLs, and in particular, the development of the DSMLs design from domain models, for which the use of the catalog effectively contributes.

Model-Driven Development is a development approach which is being used frequently in the automotive context in order to design models. EAST-ADL is an architectural language which models systems according to their architectural features, whereas Simulink is a tool environment which models systems according to their behavior. In this thesis work, we propose a set of transformation rules that take into consideration the EAST-ADL architectural model details and the behavioral specifications in Simulink, and generate a formal model, which can be verified UPPAAL model checker. Moreover, we implement these proposed transformation rules in a tool that automates them. The transformation rules proposed in this thesis work would be implemented for every EAST-ADL file with Simulink behavior specifications, generated by the MetaEdit+ tool. Properties like timing constraints, triggering and hierarchy in both EAST-ADL and Simulink have been considered by the transformation rules. Finally, the Brake-by-Wire case study is used to validate the tool and assess the mapping of the elements.

Made available in DSpace on 2016-12-23T14:33:33Z (GMT). No. of bitstreams: 1 Diss ITM 1.pdf: 288787 bytes, checksum: 7ec6ca50c8c58631a8efb146dc08e482 (MD5) Previous issue date: 2013-01-25 / Aplicações sensíveis ao contexto usam informações contextuais para customizar serviços de acordo com as situações e as necessidades dos seus usuários. Um dos desafios associados ao desenvolvimento deste tipo de aplicação está em especificar os modelos conceituais que representam as situações de interesse da aplicação. O objetivo desta dissertação é propor uma metodologia orientada a modelos para auxiliar o desenvolvimento de aplicações sensíveis ao contexto, com foco na especificação e detecção de situações contextuais. Para atingir este objetivo, o trabalho propõe uma linguagem gráfica de modelagem de situações, chamada SML (Situation Modeling Language), que permite especificar diferentes tipos de situação considerando aspectos como composição de situações e inferência temporal. A fim de permitir a detecção de situações, os modelos descritos em SML podem ser utilizados para gerar uma implementação baseada em regras que observa contexto e controla o ciclo de vida das situações de interesse da aplicação. O trabalho descreve como os elementos especificados em SML são transformados em código a ser executado pela máquina de regras Drools. Finalmente, para apoiar o desenvolvimento de aplicações sensíveis ao contexto, são propostas ferramentas que auxiliam o processo de modelagem e de transformação do modelo em código. Os conceitos envolvidos na construção de SML e na geração automática de código são exemplificados por meio de um cenário de detecção de fraudes bancárias / Context-aware applications manipulate context information to adapt services according to the users current situation and needs. One of the challenges of developing context-aware applications refers to the specification of the conceptual models that represent the situations of interest. The objective of this thesis is to propose a model-driven methodology to assist the development of context-aware applications, focusing on the specification and the detection of contextual situations. To achieve this goal, the work proposes a graphical language for modeling situations, coined SML (Situation Modeling Language), which allows the user to specify situation types considering aspects such as composition of situations and their temporal reasoning. In order to allow situation detection, the models described in SML can be used to generate a rule-based implementation, which is capable of observing context and controlling situations lifecycle. The work describes how the elements specified in SML are transformed into code to be executed in the Drools rule engine. Finally, to support the development of applications, we propose tools to assist the modeling phase, as well as the implementation phase, by means of code generation. The concepts involved in the design of SML and the transformations of SML models to Drools code are exemplified by means of a banking scenario for detecting fraudsusceptible behavior

Esta tese apresenta um processo para a criação de um catálogo de modelos de computação para apoiar o design de DSMLs, e a primeira versão do catálogo, com atributos que ajudam a selecionar os modelos de computação mais adequados para cada desenvolvimento de DSML, e as características dos sistemas de software para os quais esses modelos de computação são mais adequados. O contexto de aplicação desse catálogo é o Model-Driven Development (MDD desenvolvimento dirigido por modelos) a abordagem em que o desenvolvimento de software é baseado em modelos gráficos que são posteriormente traduzidos (transformados) em modelos de nível mais baixo e, no final, em código de linguagens de programação, tais como Java ou C#. A aplicação do processo gerou uma versão inicial do catálogo com os seguintes modelos de computação: diagramas BPMN, diagramas de classe da UML e regras de negócio. Visa-se contribuir para popularizar a abordagem de MDD com base em DSMLs e, em particular, a elaboração do design das DSMLs a partir de modelos de domínio, para o que o uso do catálogo efetivamente contribui. / This thesis presents a process for the creation of a catalog of models of computation to support the design of Domain-Specific Modeling Languages (DSMLs), and the first version of the catalog, which comprises attributes that aim to help the selection of the most suitable models of computation for each DSML development, and characteristics of software systems for which these models of computation are more appropriate. The context for the use of the catalog is the Model-Driven Development (MDD) - the approach where software development is based on graphical models that are subsequently translated (transformed) into lower-level models and, in the end, in source code in programming languages, such as Java or C #. The process was applied to generate an initial version of the catalog with the following models of computation: BPMN diagrams, UML class diagrams and business rules. It aims to contribute to popularize the MDD approach based in DSMLs, and in particular, the development of the DSMLs design from domain models, for which the use of the catalog effectively contributes.