Dissertations / Theses on the topic 'UML2'

Submitted by Silvana Teresinha Dornelles Studzinski (sstudzinski) on 2015-10-28T12:29:05Z No. of bitstreams: 1 Vivian Teresinha Pedó da Silva_.pdf: 3694100 bytes, checksum: ce6e15fc4bf10c3f2a81dfbdb083b1b7 (MD5)
Made available in DSpace on 2015-10-28T12:29:05Z (GMT). No. of bitstreams: 1 Vivian Teresinha Pedó da Silva_.pdf: 3694100 bytes, checksum: ce6e15fc4bf10c3f2a81dfbdb083b1b7 (MD5) Previous issue date: 2015-06-16
UNISINOS - Universidade do Vale do Rio dos Sinos
A presente tese descreve e analisa os discursos que constituem os currículos de formação de professores, problematizando o campo da Educação Especial como locus de formação de professor para surdos. Para tanto, analisa sete currículos de cursos de formação de professores, desenvolvidos entre os anos de 1962 e 2009 na Universidade Federal de Santa Maria (RS). Utiliza como ferramenta teórico-metodológica o conceito de discurso, inspirada nos estudos foucaultianos em educação. A partir da pesquisa, foi possível constatar três grandes ênfases discursivas nos currículos de formação de professores analisados; são elas: do campo da saúde (início em 1962), da Pedagogia (início em 1973) e da Educação Especial (início em 1984). Em cada ênfase, é possível observar a recorrência de discursos sobre a deficiência e diferença/diversidade. Destaca-se, a partir de 2004, a forte presença dos discursos da diversidade e da inclusão. Conclui-se que os discursos da diversidade, articulados aos da Educação Especial, são condição de possibilidade para a existência da diferença/identidade surda nos cursos de Educação Especial em Santa Maria. Também se conclui que o currículo em vigor iniciado em 2004, comparativamente aos outros currículos, evidencia uma ampliação dos discursos pedagógicos, a diminuição dos discursos das deficiências e a ampliação dos discursos da surdez como diferença. A tese defendida é que os currículos, ao modificarem-se para serem atualizados, contemplam a diversidade e não a diferença surda. Pesquisadores e profissionais da indústria reconhecem a importância do desenvolvimento de sistemas cientes de contexto, visto que tais sistemas cada vez mais fazem parte da vida cotidiana das pessoas. Para projetar, comunicar decisões de projeto e representar os aspectos estruturais e comportamentais destes sistemas, os desenvolvedores comumente utilizam a Linguagem de Modelagem Unificada (UML), a qual é amplamente reconhecida como linguagem padrão de modelagem de software. Porém, dada a crescente diversidade de técnicas de modelagem e a incapacidade da UML em representar os conceitos de sistemas cientes de contexto, é particularmente desafiante para os desenvolvedores objetivamente projetar e comunicar decisões de projetos de tais sistemas. Consequentemente, os desenvolvedores geralmente não dispõem de ferramentas que facilitem a representação de contexto de uma forma adequada, ao passo que propõem notações para contornar o problema, agravando ainda mais o problema da heterogeneidade das técnicas de modelagem atuais. O problema central é que a UML é imprecisa para representar o conceito de contexto e rígida para incorporar novos conceitos. Outro problema é que as ferramentas acadêmicas e comerciais de modelagem atuais - incluindo IBM RSA, Astah, Borland Together - não dão suporte à representação e à validação de modelos de contexto. Este trabalho, portanto, propõe uma extensão da UML para modelagem de contexto, a qual visa não só permitir a representação e validação dos principais aspectos de contexto, como também potencializar uma melhor comunicação de decisões de projeto de sistemas cientes de contexto. Também é proposto um ambiente de modelagem específico de domínio para tornar possível a modelagem de sistemas cientes de contexto, o qual foi implementado como um plug­in da plataforma Eclipse utilizando os frameworks GMF, EMF e UML2tool. Este ambiente permite não só representar o conceito de contexto seguindo a abordagem proposta, bem como avaliar a corretude dos modelos criados. A extensão e a ferramenta proposta foram avaliadas através de um questionário abordando a modelagem proposta comparada com modelagens que utilizam a UML pura. Essa avaliação permitiu determinar os reais benefícios do trabalho desenvolvido e onde os resultados sugerem que a modularização das informações de contexto em um novo conceito chamado de UML2Context traz benefícios, quando comparada com a decomposição de tais informações com a UML Pura. Os resultados apontaram que a UML2Context aumentou a taxa de respostas corretas em 28,41%, reduziu o esforço de interpretação em 61,03% e melhorou a interpretação dos modelos de contexto em 35,98%, se mostrando eficaz para modelagem de sistemas ubíquos.
Researchers and industry professionals recognize the importance of developing context-aware systems, as these systems increasingly are part of everyday life of people. To design, communicate design decisions and represent the structural and behavioral aspects of these systems, developers commonly use the Unified Modeling Language (UML), which is widely recognized as the standard language of software modeling. However, given the increasing diversity of modeling techniques and UML's inability to represent the concepts of context-aware systems, is particularly challenging for developers to design and objectively communicate design decisions of such systems. Usually developers don’t have the tools to facilitate the representation of context in an appropriate manner, whereas propose notations to solve the problem, further aggravating the problem of heterogeneity of current modeling techniques. The main problem is that UML is inaccurate to represent the concept of context and rigid to incorporate new concepts. Another problem is that academic and commercial tools of current modeling - including IBM RSA, Astah, Borland Together - do not support the representation and validation of context models. This paper therefore proposes an extension of UML for modeling context, which aims not only to allow the representation and validation of the key aspects of context, but also enhance communication of project decision of context aware systems. It also proposes a domain specific modeling environment that enable the modeling of context-aware systems, which was implemented as an Eclipse platform plugin using the GMF frameworks, EMF and UML2tool. This environment will not only represent the concept of context following the proposed approach and to evaluate the correctness of the models. The extent and the proposed tool was evaluated through a questionnaire addressing the proposed model compared with modelings that using the standard UML. This avaliation allowed us to evaluate the real benefits of work and where the results suggest that the modularization of context information in a new concept called UML2Context brings benefits compared with the decomposition of such information with the pure UML. The results link that UML2Context increased the rate of correct answers in 28.41%, reduced the effort of interpretation in 61,03% and improved the interpretation of context models in 35.98%, proving effective for modeling ubiquitous systems.

The recent version of UML 2.0 (in year 2006) specifies activities and actions, which allow describing low level behavior of software system being modeled, in implementation independent fashion. This work analyzes suitability of UML 2.0 activities and actions for generating full program code (or as many as possible). It also proposes a method for generating program code from UML 2.0 activities and actions, which consists of a way to express UML activities with concurrently executing actions in a sequential execution scenario and a way to determine the exact code template (among the few possible) for UML activity elements based on identifying the particular context of element in question.

Les systèmes informatiques envahissent de plus en plus notre quotidien, en allant de la plus simple application de lecture des fichiers audio, à la plus critique comme les voitures et les avions. Dans les systèmes critiques, la validation par vérification formelle s'impose. Cette thèse s'inscrit dans ce cadre et tend à doter le langage UML, langage de modélisation standard de facto, d'une sémantique formelle pour des finalités de vérification. En premier lieu, nous avons analysé et révisé le fondement théorique des principales approches de formalisation et de vérification issues de la littérature et se focalisant sur le langage UML, ses profils et les concepts des réseaux de Petri (RdPs). En deuxième lieu, nous avons proposé une nouvelle approche hiérarchique de formalisation des diagrammes globaux d'interactions (IOD). En se basant sur ce point, nous avons développé des formalismes temporels et temporisés des diagrammes de Timing UML2 (TD), appliqués par des exemples d'illustration. Ensuite, nous avons conçu une approche de vérification sur les approches développées, s'intéressant aux Systèmes Temps Réel (STRs), utilisant l'extension temporelle du langage des contraintes objets OCL/Temps Réel (OCL TR), le profil UML MARTE et la logique temporelle temporisée (TCTL), exploitée d'une technique de vérification automatique après la transformation du modèle (Model Checking). Enfin, nous avons appliqué les formalismes proposés sur une étude de cas, afin de garantir leurs efficacités logique et temporelle
The computer systems have increasingly invaded our daily lives from the simplest application as audio files reading to the most critical one as cars and airplanes. For critical systems, the validation by the formal verification is required. This Thesis concerns this area of research and aims to ensure the betterment of UML language, which is the de facto standard, with formal semantics for verification finality. For the first part, we have analyzed and revised the theoretical foundations the existing formal verification methods used UML, their profiles and the basic concepts of the Petri nets (PNs). For the second part, we have created a novel hierarchical approach to formalize the Interaction Overview Diagrams (IOD). Based on this idea, we have developed temporal formalisms based on the UML2 Timing Diagrams (TD), applied by illustration examples. Then, we have proposed a Formal Verification approach based on last formalisms which are interested in Real Time Systems (RTS) and employ the temporal extension of the Object Constraints language (OCL/Real Time) (OCL TR), the UML MARTE profile and the timed computation Tree logic (TCTL), given by the Model Checking technique after the model's transformation. Finally, we have applied all the proposed formalisms through a case study, in order to ensure its logical and temporal efficiency

Deficiencies in software design or architecture can severely impede and slow down the software development and maintenance progress. Bad smells and anti-patterns can be an indicator for poor software design and suggest for refactoring the affected source code fragment. In recent years, multiple techniques and tools have been proposed to assist software engineers in identifying smells and guiding them through corresponding refactoring steps. However, these detection tools only cover a modest amount of smells so far and also tend to produce false positives which represent conscious constructs with symptoms similar or identical to actual bad smells (e.g., design patterns). These and other issues in the detection process demand for a code or design review in order to identify (missed) design smells and/or re-assess detected smell candidates. UML diagrams are the quasi-standard for documenting software design and are often available in software projects. In this position paper, we investigate whether (and to what extent) UML diagrams can be used for identifying and assessing design smells. Based on a description of difficulties in the smell detection process, we discuss the importance of design reviews. We then investigate to what extent design documentation in terms of UML2 diagrams allows for representing and identifying software design smells. In particular, 14 kinds of design smells and their representability in UML class and sequence diagrams are analyzed. In addition, we discuss further challenges for UML-based identification and assessment of bad smells.

La réalisation de systèmes complexes de mesures, de contrôle et de surveillance nécessite une méthodologie de conception rigoureuse et des outils adaptés pour aboutir à un système sans faute. La démarche méthodologique proposée vise à aider à la conception d'un système complexe dédié à la gestion intelligente du confort et à la sécurité des personnes au sein de l'habitat. Cette démarche s'intègre dans un processus d'Ingénierie Système et s'appuie sur les standards UML et SYSML, mais également sur le formalisme HiLes, développé par le LAAS et adapté à la conception de modèle commande, la vérification formelle et la simulation numérique. Ces travaux de thèse présentent les méthodes et les outils de conception préconisés pour un habitat intelligent intégrant les objectifs de confort et de sécurité. Deux expérimentations sont décrites utilisant une commande auto-adaptative basée sur l'apprentissage des habitudes des utilisateurs dans leur environnement de vie et implémentés sur site réel.

L'Internet du futur aura a transporter les donnees de nouvelles applications avec des garanties de qualite de service (QdS). De ce besoin resulte la necessite d'en re-concevoir l'architecture. Par ailleurs, la structure de l'Internet, compose de domaines independants vis a vis de la gestion de la QdS, pose le probleme de la continuite du service lors de la traversee de plusieurs domaines. Face a ces deux problematiques, la these soutenue est celle d'un systeme de communication offrant des garanties de QdS par flux applicatif dans un environnement Internet multi domaines. Son architecture integre un plan communication comportant plusieurs services/protocoles aux niveaux Transport et IP, et un plan signalisation assurant la gestion des ressources a la frontiere des domaines. Nos contributions sont les suivantes. Nous proposons un modele de caracterisation des services IP et Transport, etaye par : (1) des mesures realisees sur une plate forme nationale, (2) une etude en simulation (ns-2) et (3) des mesures realisees sur une plate-forme emulant (Dummynet) un Internet multi domaines. Nous etendons l'architecture de communication proposee dans des travaux anterieurs de facon a abstraire le niveau applicatif de la complexite du choix des services Transport et IP, et a optimiser l'utilisation des ressources du reseau. Nous specifions en UML et implementons en Java notre proposition d'architecture de signalisation permettant d'assurer la continuite du service offert aux applications sur tous les domaines traverses. Enfin, nous testons le systeme de communication avec deux types d'applications multimedias sur une plate-forme emulant le comportement de plusieurs domaines DiffServ.

1 EINFÜHRUNG Der Beitrag diskutiert ein Vorgehensmodell zur Übertragung eines Vernetzungsansatzes für sehr kleine Wertschöpfungseinheiten, vornehmlich aus dem Maschinenbau, in die Domäne Dezentrale Energieversorgung. Es handelt sich dabei um den kompetenzzellenbasierten Vernetzungsansatz (KVA), ein Artefakt des DFG-Forschungsprojektes „Hierarchielose regionale Produktionsnetze“ (Sonderforschungsbereich 457). Das Lernen setzt die Analyse sowie das Erkennen und Verstehen des Forschungsgegenstandes KVA voraus. Von besonderem Interesse sind die Forschungsergebnisse zu den aufbau- und ablauforganisatorischen Grundbetrachtungen über die Zusammenarbeit von Kompetenzzellen. Können diese Ergebnisse einen wissenschaftlichen und praktischen Nutzen für die Organisation von Anbietergemeinschaften aus Stromerzeugern und -verbrauchern stiften? Dazu werden das Gestaltungskonzept Zwei-Ebenen-Kooperation und das Konzept der Kompetenzzelle untersucht. Für die Übertragung wird die Modellierungssprache Unified Modeling Language 2 (UML2) zur Beschreibung von Struktur, Funktion und Organisation vorgeschlagen.

One of the inevitable negative effects of software evolution is design erosion. Refactoring is a technique that aims at counteracting this phenomenon by successively improving the design of software without changing its observable behaviour. Design erosion occurs also in the context of executable UML models, i.e. models that are detailed enough to be automatically compiled to executable applications. This thesis presents results of a study on applying refactoring to the area of maintenance of executable UML models. It contains an overview of recent approaches to UML model refactoring and to executable modelling, followed by identification of refactoring areas in models built in Telelogic TAU, a state-of-the art UML CASE tool. It proposes a systematic approach to specification of both executable UML model refactorings as well as associated bad smells in models. Additionally, it shows how refactorings can be implemented in Telelogic TAU.

As the amount of accessible and shareable knowledge increases, it is figured out that learning platforms offering the same context and learning path to all users can not meet the demands of learners. This issue brings out the necessity of designing and developing adaptive hypermedia systems. This study describes an agent-based adaptive learning framework whose goal is to implement effective tutoring system with the help of Artificial Intelligence (AI) techniques and cognitive didactic methods into Adaptive Educational Hypermedia Systems (AEHS) in the domain of Unified Modeling Language (UML). There are three main goals of this study. First goal is to explore how supportive agents affect student&rsquo
s learning achievement in distance learning. Second goal is to examine the interaction between supportive agents and learners with the help of experiments in Human Computer Interaction laboratories and system analysis. The effects of the methodology that agents give misleading hints which are common mistakes of other learners are also investigated. Last goal is to deliver effective feedback to students both from IAs and tutors. In order to assess that UML-ALF has accomplished its objectives, we followed an experimental procedure. Experimental groups have taken the advantage of adaptive and intelligent techniques of the UML-ALF and control groups have used the traditional learning techniques. The results show that there is a positive correlation between variables practice score and number of agent suggestion which means, as the participants benefit from supportive agents, they get higher scores.

CCS (Communicating and Concurrent Systems) is the process algebra to specify and verify concurrent and communicating systems. This work proposes a transformation guide of the CCS equations into to the UML-RT (Unified Modeling Language for Real-Time) model and a transformation guide of the UML-RT model into a set of CCS equations. The UML-RT model is a software design language, which supports code generation and the construction of executable systems. The UML-RT is an UML extension, and it does not have a formal semantics; therefore it is not possible to verify UMLRT models. The transformation guide of UML-RT models into CCS equations allows verifying the models. We argue that the transformation of CCS models into UML-RT models allows an alternative way of correctly building systems. This work details the transformation guides from CCS equations to UML-RT models and from UML-RT models to CSS equations and it discusses the limitations and benefits.

Analyzing software contains two different tasks. First of all we are analyzing the software and try to calculate some metrics for software quality. Then those results have to be presented to the software engineers. VizzAnalyzer is a tool for analysis and visualization of software. It visualization allow not for a standardized diagram representation. Therefore it is difficult for others to understand, and we need to explain the meaning of our non-standard diagram elements. The solution is to use a standardized representation which can be understood by both sides. UML is such a collection of intuitively diagrams with standardized elements. Their meaning is clear to most software engineers.

We extended our analysis tool, the VizzAnalyzer, allowing it to view software systems as UML Class diagrams. We reused the existing plug-in architecture to connect our analysis tool with yEd, a graph visualization program. This plug-in is responsible for exchanging the data between the two applications.

We solve this conversion defining an UML Class Diagram Model and the mapping function between this model and the Common Meta-Model used by VizzAnalyzer and our Class Diagram Model. After that, we export this Class Diagram Model to a format suitable for yEd to display.

Now we can generate Class Diagrams with the VizzAnalyzer tool. This will allow a better communication of the results derived by different analysis with the software engineers.

This thesis describes the evolution of different alternatives and the design and implementation of our solution.

Made available in DSpace on 2013-08-07T18:42:52Z (GMT). No. of bitstreams: 1 000404134-Texto+Completo-0.pdf: 1945170 bytes, checksum: b8a0273e017edb542534fd86a3d269e2 (MD5) Previous issue date: 2008
With the success of Model Driven Architecture (MDA) and Unified Modeling Language (UML), models are replacing code as the first software development artifact. In MDA, model transformation and model composition are essential activities. While model transformation has been well researched and documented, model composition needs more investigation. With MDA arise three challenges, such as: (i ) create domain specific modeling languages (DSMLs); (ii ) merge DSML; and (iii ) merge models expressed in DSML. The UML allows building DSML through UML profiles, however it does not provide an adequate mechanism to merge such profiles. With this in mind, this work proposes a UML profiles composition mechanism based on merge rules, model transformation rules, composition strategy, match strategy and match rules. A formalization of this mechanism was built using the Alloy formal language and automatic analysis were accomplished using Alloy Analyzer. Moreover, a model composition tool was developed to evaluate the mechanism and automate the approach.
Com o sucesso da MDA (Model Driven Architecture) e da UML (Unified Modeling Language), modelos estão substituindo código como o principal artefato de desenvolvimento de software. Em MDA, a transformação e a composição de modelos são duas atividades essenciais. Enquanto a transformação de modelos tem sido amplamente pesquisada e documentada, a composição de modelos precisa de mais investigação. Com a MDA, surgiram três desafios: (i) criar linguagens de modelagem específicas de domínios (DSML); (ii) compor DSML; (iii) compor modelos representados em DSML. A UML permite a construção de DSML através de UML profiles, porém não oferece um mecanismo adequado para tais profiles. Neste contexto, o presente trabalho apresenta uma proposta de mecanismo de composição de UML profiles fundamentado em regras de composição, regras de transformação de modelos, estratégias de composição, estratégia de comparação e regras de comparação. Um modelo formal deste mecanismo foi construído utilizando a linguagem de modelagem formal Alloy e foi realizada uma análise automática do modelo usando Alloy Analyzer. Além disso, uma ferramenta de software foi construída com o objetivo de validar o mecanismo e automatizar a abordagem.

The Unified Modeling Language (UML) is a visual modeling language for documenting and specifying software. It is gaining popularity as a language for a variety of purposes. It was designed as a result of a unifying activity in the last decade. Since this general purpose language cannot suit all possible needs, it has built-in mechanisms for providing extensibility for specific purposes. One such mechanism is the notion of stereotype, which is a means of branding the existing model element with a new semantics. Such extended elements can then act as new model elements as if they were standard model elements. This notion is only one of the possible ways of customizations of the language. The other, more powerful technique is metamodeling, which enables to change UML by directly changing its specification. The thesis investigates the notion of stereotype in UML both from theoretical and practical perspectives. It examines the notion of stereotype as it originally appeared in object-oriented software development as a means of branding objects according to their secondary classification in the system. The initial intent behind stereotypes is compared with the view of stereotypes in UML and similar languages, which later on provides a basis for an understanding of a stereotype in the thesis. The thesis elaborates on a classification of stereotypes from the perspective of their usage. The classification categorizes different usages of stereotypes in different situations. Based on the classification, one such usage is evaluated in an empirical way. The evaluation is done in the form of an experiment on how the stereotypes influence the understanding of UML models. An example of a customization of UML for a conceptual database model is presented. It is a basis for a study on the expressiveness of stereotypes in the context of persistency modeling in objectoriented software. Two ways of the introduction of the stereotypes into the software development process (dependent and independent of UML tools) are outlined.The thesis contains also a presentation of how the knowledge expressed as ontology can be imported into domain models expressed in UML. This research can be seen as a further study on the customization of UML towards usage of ontology-based knowledge.

La médecine est un domaine caractérisé par une terminologie spéci que. C’est pour cela qu’elle a une position très spéciale, non seulement en raison du nombre impressionnant de termes mis en jeu, mais aussi par les efforts internationaux déjà consacrés pour établir des terminologies standardisées. Ces terminologies, créées principalement de forme manuelle, jouent un rôle clé dans le traitement de l’information et des connaissances médicales. Pour le portugais, il n’existe qu’une seule grande terminologie standardisée, et ce, pour la variante brésilienne. C’est pour cette raison que notre travail consiste à créer et à maintenir (semi-)automatiquement un dictionnaire électronique uni é et évolutif pour le portugais luso-africain, à partir de diverses terminologies collectées sur la toile, également de forme (semi-)automatique. Le codage de ces terminologies selon un même langage informatique de balisage générique a relevé plusieurs dif cultés qui ont dû être résolues, a n de pouvoir faire l’uni cation intra-terminologique. Cette étape a souligné plusieurs problèmes que nous avons résolu de diverses formes en fonction du type de problème : soit par l’application des règles du Nouvel Accord Orthographique, soit par une distance d’édition. Ce n’est qu’après être passé par ces différentes étapes que nous pouvons alors fusionner nos données a n de corriger les problèmes d’uni cation inter-terminologiques alors apparus lors de la fusion. C’est ainsi que nous obtenons le plus grand dictionnaire médical luso-africain de plus de 81.000 termes, où sont également précisées, quand disponibles, les variantes brésiliennes

This thesis presents an in-depth investigation into the practical use of 3D for software visualisation. This work presents the first comprehensive user-centred study which examines the software engineering tasks users undertake currently, the issues that 3D addresses and a measure of benefit of the 3D solution compared to traditional approaches. This thesis also presents a mechanism for creating 3D software visualisations, a refined evaluation methodology and visualisation heuristics that together provide a valuable resource for further research into this area. The research results have been structured so they are directly applicable to industry and as such are already undergoing industrial adoption. This has been achieved through the following: Firstly the research augments current and accepted software visualisation approaches by basing the visual notation on the Unified Modelling Language (UML). This has enabled the current visual software engineering tasks to be studied and for representative user tasks to be captured and quantified. The 3D visualisations then complement the current working practices by solving

Since Web applications are very complex, compared to traditional client/server applications, Web application design with the UML can be obtrusively hard for a modeller. The grounds are that the UML does not define the correct semantics to be able to visualize a web application correctly. This is a qualitative reduction study where we have used interviews and our own experience during the redesign of a UML-modelled e-commerce application with WAE-UML. Using the flow of a case study we have tried to see if we can improve three quality attributes of a complete design. Stakeholder communication reflects the need of unambiguous design artefacts that are easy to understand and that mediate the real message of the use-case. The condition of the design artefacts should provide artefacts that resemble reality and that not are misleading and provide for verification and validation of the requirements. The last attribute maintainability should provide means for easy maintenance and updates. We found that WAE-UML can improve these quality attributes in a design but the impact it has on them is dependent on two major aspects. The first aspect concerns the designers’ judgment of detail in a design. A detailed design can be good considering requirements and use-case traceability and verification, but prohibit communication. Maintainability can also be improved in a detailed design because the diagrams are less abstract and a truer picture of the application. The second aspect is that it depends on the knowledge possessed of the semantics by the people in contact with the design documents. Due to the time aspect the people working in the industry that we interviewed were reluctant to modelling a Web application at all. They thought it would take a long time to learn WAE-UML but also for executing a design phase.
Contact e-mail: miga02@student.bth.se, hean01@student.bth.se

The goal of this research is to provide a tool to unobtrusively introduce the design metrics D,, and Di into existing engineering practices. To that goal, different methods for visualizing the UML design metrics were explored. A small survey was conducted to determine which of the different visualizations is most attractive. The results of this survey were used to guide the design of the Design Metrics Visualization Plugin (Design MVP), which was developed as a plugin for the open-source UML tool Dia. This plugin allows for the calculation, and more importantly, visualization of the UML metrics during UML class diagram modeling.
Department of Computer Science

Cette thèse s'inscrit dans le cadre de la mise en œuvre de l'ingénierie dirigée par les modèles (IDM) pour le développement des systèmes embarquées. Ces systèmes ayant généralement des ressources limitées (mémoire et/ou calculs), exigent que le code généré soit le plus optimisé possible. L'objectif de cette thèse est de produire à partir d'un modèle spécifié dans le langage UML, un code assembleur plus compact que le code assembleur produit par les compilateurs de code. Malgré l'évolution croissante des compilateurs optimisés, les compilateurs les plus répandus comme le GCC (Gnu Compiler Collection) sont incapables d'effectuer certains types d'optimisations qu'il est possible d'effectuer à un plus haut niveau d'abstraction dans une phase de pré-génération de code. En effet, certaines informations (liées à la sémantique d'exécution du langage UML) sont perdues lors de la génération de code. Ces informations, utiles pour les optimisations de haut niveau, sont invisibles par le compilateur de code vue qu'il prend toutes les informations liées au système modélisé à partir du code généré. Nous proposons ainsi une nouvelle approche dirigée par les modèles pour le développement des systèmes à ressources limitées, qui élimine l'étape de la génération de code en remplaçant cette étape par une compilation directe des modèles. Nous avons développé le premier compilateur de modèles UML (GUML : le front-end UML pour le compilateur GCC) qui génère directement de l'assembleur (sans passer par un langage de programmation) à partir des modèles UML. GUML permet de compiler les classes, les activités et les machines à états UML. Il permet de générer, en compilant certaines machines à états, un code assembleur plus compact que le code assembleur produit par GCC. Deux optimisations de GCC sont améliorées : l'élimination de code mort et l'élimination des expressions redondantes.

Effectiveness of system testing, in specific phases such as design verification, requirements validation, test planning and generation, system integration and system testing are considered. Software as well as hardware test issues are reviewed. Metrics related to system testing are specified. The current system testing processes in a large Turkish military electronic systems manufacturer are reviewed, specific problems are identified and UML-based behavioral testing is proposed as an improved process. The current process and the proposed process are compared in terms of test coverage, test effectiveness and test effort metrics.

Software development process encounter productivity obstacles, which are affected by an arise of new technologies. Object Management Group (OMG) proposed model driven architecture (MDA) supposed to minimize effect of new technologies arrival into a process of software development. One of the most important aspects in MDA is meta-model, which is used to specify MDA style transformations. Theses present meta-model of PLA model and XSL transformations, used to retrieve PLA simulation model. Example of creating oil terminal simulation model is presented as well.

Projektavimas naudojant UML kalbą tampa vis populiaresniu, todėl šios srities įrankių gausa vis didėja. Tampa tikra problema išsirinkti tinkamą UML įrankį. Šiame darbe yra analizuojami UML kalbos projektavimo įrankiai pagal jų galimybes. Yra išnagrinėti 10 pasirinktų UML įrankių, apibūdintos pagrindinės jų charakteristikos, bei palyginti pagal pasirinktus kriterijus. UML įrankių palyginimui buvo sudarytos ir pateiktos lentelės su išvardintais įrankiais bei kriterijais. Remiantis duomenimis iš lentelių, buvo sudaryti UML įrankių palyginimo grafikai. Pateiktas pagrindinių sąvokų detalus aprašymas. Suprojektuota ir sukurta mokomoji svetainė pagal išrinktą UML įrankį. Sukurtas vartotojo vadovas video formatu. Pateiktos rekomendacijos UML įrankio pasirinkimui.
According to the results of the research the design while using UML becomes considerably more popular due to this reason the great variety of tools of this sphere are also increased. Therefore, it goes naturally, that it became a real problem in order a suitable tool of UML to be closen properly. In this work the tools of the projecting of the language are analyzed and also the 10 chosen UML tools are represented while describing their main particularities, they are also compared according to the chosen criteria. In order the comparison of the UML to be carried out properly the tables with mentioned tools and their criterias to be represented. According to the date from the tables the graphs of the comparison of the tools of UML are made and the detailed description of the main conception is presented as well. The educational website according to the chosen appropriate UML tool is projected and created. The guidance of a user is also created in the video format. According to the analysis of UML tools there are given the certain recommendations in order the appropriate tool to be chosen appropriately. Also there are given the aspects with the help of which the choise of a suitable tool of a user can be carried out in the dependency on the desirable project. Acceding to the analysis of the commercial and non-commercial tools the certain recommendations are given.

Active technology in database management systems (DBMS) enables the movement of behaviour dependent on the system’s state, from the application software to a rule base in the DBMS. With active technology in database systems, the problem of how to design active behaviour has become an important issue. Modelling processes do not foresee support for design of active rules which can lead to conflicts between the event-condition-action (ECA) rules representing the active behaviour and the application systems, using the active DBMS. The unified modelling language (UML) is a widely used notation language and is the main subject in this project. Its features will be investigated to acknowledge to what extend UML modelling diagrams provide information that can be used to formulate ECA rules.

To achieve this, two methods where developed. One of the methods was applied on use-case UML modelling diagrams. The use-case models were developed by means of reflecting a real-life organisation. The results from applying the method on the use-case models were that there are features in UML that can be expressed with ECA rules.

Active technology in database management systems (DBMS) enables the movement of behaviour dependent on the system’s state, from the application software to a rule base in the DBMS. With active technology in database systems, the problem of how to design active behaviour has become an important issue. Modelling processes do not foresee support for design of active rules which can lead to conflicts between the event-condition-action (ECA) rules representing the active behaviour and the application systems, using the active DBMS. The unified modelling language (UML) is a widely used notation language and is the main subject in this project. Its features will be investigated to acknowledge to what extend UML modelling diagrams provide information that can be used to formulate ECA rules.

To achieve this, two methods where developed. One of the methods was applied on use-case UML modelling diagrams. The use-case models were developed by means of reflecting a real-life organisation. The results from applying the method on the use-case models were that there are features in UML that can be expressed with ECA rules.

The Unified Modelling Language (UML) is intended to express complex ideas in an intuitive and easily understood way. It is important because it is widely used in software engineering and other disciplines. Although an official definition document exists, there is much debate over the precise meaning of UML models. ¶ In response, the academic community have put forward many different proposals for formalising UML, but it is not at all obvious how to decide between them. Indeed, given that UML practitioners are inclined to reject formalisms as non-intuitive, it is not even obvious that the definition should be “formal” at all. Rather than searching for yet another formalisation of UML, our main aim is to determine what would constitute a good definition of UML. ¶ The first chapter sets the UML definition problem in a broad context, relating it to work in logic and the philosophy of science. More specific conclusions about the nature of model driven development are reached in the beginning of Chapter 2. We then develop criteria for a definition of UML. Applying these criteria to the existing definition, we find that it is lacking in clarity. We then set out to test the precision of the definition. The test is to take an apparently inconsistent model, and determine whether it really is inconsistent according to the definition. ¶ Many people have proposed that UML models are graphs, but few have justified this choice using the official definition of UML. We begin Chapter 3 by arguing from the official definition that UML models are graphs and that instantiation is a graph homomorphism into an interpretation functor. The official definition of UML defines the semantics against its abstract syntax, which is in turn defined by a UML model. Chapters 3 and 4 prepare for our test by resolving this apparent circularity. The result is a semantics for the metamodel fragment of the language. ¶ In Chapter 5, we find, contrary to popular belief, that the official definition does provide sufficient semantics to classify the example model as inconsistent. Moreover, the sustained study of the semantics in Chapters 3 to 5 confirms our initial argument that the semantic domain is graphs. The Actions are the building blocks of UML’s prescriptive dynamics. We see that they can be naturally defined as graph transformation rules. Sequence diagrams are the main example of descriptive dynamics, but we find that their official semantics are broken. The “recorded history” approach should be replaced, we suggest, by a graph-oriented dynamic logic. ¶ Chapter 6 presents our early work on dynamic logic for UML sequence diagrams and further explores the proposed semantic repairs. In Chapter 7, guided by the criteria developed in Chapter 2, we critically survey the UML formalisation literature and conclude that an existing body of graph transformation based work known as “dynamic metamodelling” is very close to what is required. ¶ The final chapter draws together our conclusions. It proposes a category theoretic construction to merge models of the syntax and semantic domain, yielding a type graph for the graph transformation system which defines the dynamic semantics of the language. Finally, it outlines the further work required to realise a satisfactory definition of UML.

Thesis (M.S.)--School of Computing and Engineering. University of Missouri--Kansas City, 2007.
"A thesis in computer science." Typescript. Advisor: Yijie Han. Vita. Title from "catalog record" of the print edition Description based on contents viewed Nov. 13, 2007. Includes bibliographical references (leaves 46-48). Online version of the print edition.

Unified Modeling Language (UML) allows software engineers to use a standard way of expressing a design approach at a high level. The benefits of system modeling are well accepted in the software development community. Modeling of Very High Speed Integrated Circuit Hardware Description Language (VHDL) designs, for synthesizing into hardware, is a common practice also. The research herein looks at system modeling of a design using UML, in which there are both software and hardware components. The idea is to explore modeling of the system with the ability to abstract whether the implementation of a particular function is realized in software or hardware. The designer can then model/evaluate a given system design approach and later allocate functions to software and hardware, as appropriate to meet constraints such as performance, cost, schedule. Since using UML for software is a standard approach, this research investigates the UML to hardware path via VHDL.
Department of Computer Science

Made available in DSpace on 2015-04-14T14:49:00Z (GMT). No. of bitstreams: 1 404134.pdf: 1945170 bytes, checksum: b8a0273e017edb542534fd86a3d269e2 (MD5) Previous issue date: 2008-02-28
Com o sucesso da MDA (Model Driven Architecture) e da UML (Unified Modeling Language), modelos est?o substituindo c?digo como o principal artefato de desenvolvimento de software. Em MDA, a transforma??o e a composi??o de modelos s?o duas atividades essenciais. Enquanto a transforma??o de modelos tem sido amplamente pesquisada e documentada, a composi??o de modelos precisa de mais investiga??o. Com a MDA, surgiram tr?s desafios: (i) criar linguagens de modelagem espec?ficas de dom?nios (DSML); (ii) compor DSML; (iii) compor modelos representados em DSML. A UML permite a constru??o de DSML atrav?s de UML profiles, por?m n?o oferece um mecanismo adequado para tais profiles. Neste contexto, o presente trabalho apresenta uma proposta de mecanismo de composi??o de UML profiles fundamentado em regras de composi??o, regras de transforma??o de modelos, estrat?gias de composi??o, estrat?gia de compara??o e regras de compara??o. Um modelo formal deste mecanismo foi constru?do utilizando a linguagem de modelagem formal Alloy e foi realizada uma an?lise autom?tica do modelo usando Alloy Analyzer. Al?m disso, uma ferramenta de software foi constru?da com o objetivo de validar o mecanismo e automatizar a abordagem.

Made available in DSpace on 2014-06-12T15:52:01Z (GMT). No. of bitstreams: 1 license.txt: 1748 bytes, checksum: 8a4605be74aa9ea9d79846c1fba20a33 (MD5) Previous issue date: 2008
A integração de métodos formais com notações semi-formais visuais é uma tendência em engenharia de software. Métodos formais apresentam uma semântica precisa e permitem verificação de propriedades. No entanto, não são considerados intuitivos. Por outro lado, notações semi-formais visuais, como UML, são facilmente integradas no processo de desenvolvimento de software. Assim, métodos formais e semi-formais visuais são complementares. CSP e UML-RT são, respectivamente, exemplos de notação formal e diagramática usados para especificar e projetar sistemas concorrentes e distribuídos. CSP é um método formal no qual processos representam unidades comportamentais que se comunicam através de canais de comunicação, utilizando passagem de mensagem. UML-RT é uma extensão conservativa de UML na qual cápsulas são unidades comportamentais que se comunicam através de portas de comunicação. Portas realizam protocolos os quais especificam os sinais que podem ser enviados e recebidos através de uma porta, e a ordem na qual os sinais podem ser comunicados. Em um trabalho anterior, Ferreira apresentou um conjunto de regras que sistematizam o mapeamento de CSP para UML-RT, mas uma prova formal deste mapeamento não foi apresentada. Assim, para garantir consistência no desenvolvimento de sistemas concorrentes e distribuídos utilizando este mapeamento, a prova formal do mesmo é indispensável, uma vez que não faz sentido o esforço dedicado à especificação do sistema em CSP e a verificação de propriedades e refinamentos, se uma ou mais regras de mapeamento estiverem incorretas. No entanto, UMLRT não possui uma semântica formal padrão. Entre outras propostas de semântica formal, Ramos propõe uma semântica para UML-RT utilizando OhCircus (uma combinação de CSP e Z com características adicionais de orientação a objetos) como modelo semântico. Neste trabalho, é proposta uma variação da semântica de Ramos para UML-RT usando CSP como modelo semântico. Com base nesta semântica, é apresentada a prova do mapeamento de CSP para UML-RT, considerando o modelo de falhas e divergências de CSP. Assim, este trabalho consolida a integração de CSP e UML-RT proposta por Ferreira, no desenvolvimento de sistemas críticos, concorrentes e distribuídos. Um resultado interessante foi observar que, estritamente, as regras propostas por Ferreira não preservam a semântica de CSP, essencialmente com relação a aspectos de terminação dos processos

Made available in DSpace on 2014-06-12T16:01:17Z (GMT). No. of bitstreams: 2 arquivo7289_1.pdf: 2013918 bytes, checksum: e3f26e432c831b7c299664b62269fd01 (MD5) license.txt: 1748 bytes, checksum: 8a4605be74aa9ea9d79846c1fba20a33 (MD5) Previous issue date: 2005
Petróleo Brasileiro S.A.
Como outros métodos visuais orientados a objetos, UML tem influenciado tremendamente a prática de modelagem na engenharia de software com ricos mecanismos de estruturação. Porém, apesar de suas vantagens e adoção em larga escala, na prática, a falta de uma semântica formal tem dificultado o desenvolvimento rigoroso baseado em modelos de aplicações não triviais (aplicações que por sua natureza necessitam de ênfase na especificação e na verificação de seus componentes). A razão para isto é que transformações de modelos podem não preservar a semântica e, como conseqüência, o comportamento do modelo. Este problema é ainda mais sério em transformações que envolvem diferentes visões do modelo. Limitações similares podem ser encontradas durante o desenvolvimento com UML-RT. Esta linguagem é uma extensão conservativa de UML que provê a noção de objetos ativos (objetos com um comportamento próprio, independente do fluxo de execução do restante do sistema) para descrever aplicações concorrentes e distribuídas. Neste tipo de desenvolvimento, transformações devem lidar simultaneamente com as diferentes visões estáticas e dinâmicas do modelo, representadas por seus diagramas e propriedades. Por estes motivos, este trabalho propõe uma semântica para UML-RT, mapeando suas construções em OhCircus, uma linguagem formal, orientada a objetos, que combina CSP e Z, e que suporta o cálculo de refinamentos de Morgan. A partir desta semântica, bem como das noções e leis de refinamentos de OhCircus, é possível propor leis de transformação de modelos passíveis de demonstração e que preservam o comportamento do sistema. Estas leis de transformação são propostas em duas categorias: a primeira delas é um conjunto abrangente de leis básicas que expressam pequenas mudanças nas principais visões do modelo, como a declaração ou remoção de elementos do modelo; já a segunda representa leis de transformação de maior granularidade, derivadas a partir da composição de leis básicas, como a decomposição de uma cápsulas em cápsulas operando em paralelo. Tais transformações derivadas podem ser vistas como refatoramentos (refactorings) corretos sobre o modelo, facilmente aplicáveis durante um processo de desenvolvimento rigoroso, sem que o desenvolvedor tenha conhecimento do formalismo que o suporta. Finalmente, a abrangência deste conjunto de leis é discutida particularmente através dos principais passos de uma estratégia de redução de modelos UML-RT a um modelo UML estendido com um único objeto ativo, responsável por todas as interações com o ambiente e por conservar o comportamento dinâmico do sistema modelado. Este modelo UML estendido pode ser visto como uma forma normal, e, portanto, nossa estratégia pode ser vista como uma contribuição para uma estratégia mais global de completude capturada por redução a esta forma normal

This master's thesis describes the analysis, design and implementation of an application for automatic generation of UML class diagram. Application is designed as a web service, which provides remote access, especially permanent actuality of generated class diagram. Input of the service is a compiled application written for C# .NET or Java platform. The reader is acquainted with basics of reverse engineering of mentioned platforms and with structure of UML class diagram. Then are these knowledge applied in design and implementation of the service. The main goal is to facilitate and accelerate the activities of software development team members.

Klientsidesrenderade webbapplikationer med JavaScript-ramverk har blivit vanligt inom den moderna programutvecklingen. Modelleringsunderlag för dessa webbapplikationer kan vara relevant inom IT-industrin eftersom modellering är relevant för utveckling av mjukvara. För att ta fram detta underlag genomförs en fallstudie där modelleringsexempel med UML tas fram för en klientsidesrenderad webbapplikation som även implementeras. Detta resultat ger ett exempel för hur modellering av klientsidesrenderad webbapplikation kan utföras med UML- utökning för designmodeller och implementationsmodell. Baserat på resultatet dras slutsatser om att modellering med UML- utökning för klientsidesrenderad webbapplikation kan underlätta implementation av webbapplikationen och göra den underhållbar.
Client side rendered web applications with JavaScript frameworks have become common in modern software development. Modelling support for these web applications could be relevant for people in the IT industry since modelling is relevant for development of software. For producing this modelling support a case study is done where modelling examples with UML are made for a client side rendered web application that also gets implemented. This result gives an example for how modelling of client side rendered web application can be performed with UML extension for design models and implementation model. Based on the result conclusions are drawn that modelling with UML extension for client side rendered web application can ease implementation of the web application and make it maintainable.

Abstract During object-oriented system development, programming should be preceded by analysis and design to assure that the system fulfils the demands of the customer and simplify during the development phase and documentation. When modeling the analysis and design phases, several different notations may be used. One of these is the UML (Unified Modeling Language) which this thesis will cover. The aim is to compare the use of the UML i practice versus what is said in the literature. The investigation is built upon interviews at different companies to receive their reflections about the UML. Questions at issue are why and when the selected companies use the UML and what diagrams they use. We also investigate whether they strictly follow the UML notation or complement it with another kind of notation. Moreover two companies not using the UML was interviewed to find out why they have chosen not to. The thesis starts with an introduction to object-oriented system development with analysis and design followed by the history of the UML and its most common diagrams according to Larman [1]. These diagrams are use case, conceptual model, system-sequence diagram, contract, interaction diagram, class diagram and state diagram. Each diagram is explained with text and graphics. The most important results are that the UML is considered being adequate to the system developers. They use a number of the most common diagrams. Furthermore the CASE-tools showed not to meet the demands of the developers. We believe that inadequate tools hinders the future diffusion of the UML on the market. Improved tools for modeling and documentation are desired for all of the interviewed companies.

Eftersom databaser blir allt vanligare och används mer och mer inom allt större områden är det viktigt att finna modelleringsspråk som kan modellera egenskaperna för databashanteringssystemen under analys och design fasen. Aktiva databashanteringssystem har egenskapen att automatiskt kunna reagera på händelser som uppkommer. Aktiva databashanteringssystem klarar av att hantera s.k. ECA-regler. ECA-regler består av händelse, villkor och handling. För att kunna modellera aktiva databashanteringssystem krävs att det är möjligt att modellera ECA-regler. Ett modelleringsspråk som anses kunna modellera ECA-regler är UML. Berndtsson och Calestam (2001) anser dock att det finns brister i UML och har därför skapat en extension UML-A som bättre klarar av att uttrycka ECA-regler.

Detta arbete undersöker ifall det finns några semantiska skillnader mellan UML och UML-A. Jämförelsen sker genom att ett antal exempelregler skapas och att dessa modelleras i både UML-A och UML. Modellerna utvärderas både semantiskt och grafiskt för att se ifall skillnader kan påvisas mellan modelleringsspråken. Resultaten som kommit fram i detta arbete är att det finns klara semantiska skillnader mellan UML och UML-A när det gäller ECA-regler. De brister som funnits hos UML har inte kunnat identifieras i UML-A vilket tyder på att UML-A mycket väl skulle kunna användas för att modellera ECA-regler och därmed även aktiva databashanteringssystem.

In this master thesis the advanced design methodology is presented by which information systems requirements represented with precise UML models are transformed to project. The first section describes a research of five existing MDA tools comparison according to evaluation criteria. This criteria covers model to model and model to code transformations approach, platform of generated code and integration with UML CASE tools abilities. For requirements model transformation to design, plug-in for CASE tool MagicDraw is created according MDA standards. Model transformation plug-in takes system requirement model as input and generates design model. In this way it is possible to implement design methods that have explicit design rules. Created plug-in requirements, functional specification and architecture described in Project section. The investigation section describes investigation of the developed plug-in. In this section were investigate the working efficiency of designer increasing and the quality of design models ensuring with create MagicDraw plug-in.

Darbo tikslas – sukurti specializuotą modeliavimo aplinką, skirtą organizacijos struktūros specifikavimui. Tipinė organizacija yra suskirstyta į padalinius, kuriuose dirba darbuotojai, kuriems priskirta viena ar kita pareigybė ir atlieka įvairius vaidmenis organizacijos projektuose. Analitinė modeliavimo kalbų ir įrankių apžvalga parodė, kad vieningo būdo specifikuoti organizacijos struktūrą nėra. Daugeliu atveju organizacijos struktūra modeliuojama neformaliomis diagramomis, kurias sudėtinga analizuoti ir atnaujinti. Darbe siūlomas nesudėtingas organizacijos struktūros meta modelis bei jo realizacija UML profiliu. Naudojantis MagicDraw UML įrankio funkcinėmis savybėmis – stereotipų adaptavimu, validavimo taisyklėmis bei ataskaitų generavimu – sukurta specializuota organizacijų struktūros modeliavimo aplinka. Praktinė sukurtos aplinkos vertė pademonstruota taikant ją konkrečios organizacijos UAB “Baltijos programinė įranga” struktūros modeliavimui.
The goal of this thesis is to create a specialized modeling environment for defining organization structures. A typical organization defines some organization units, has a number of employees that are assigned to a specific organization unit, play a specific role in an organization and may be involved in projects to play different roles. The research of modeling tools and languages shows that there is no single dominant approach to modeling organization structure, and in most cases it is modeled informally, which makes it difficult to analyze and maintain. This thesis proposes a simple meta-model covering the most important organization structure concepts and their mappings to UML profile. A specialized environment for modeling organization structures is created using MagicDraw UML tool features – stereotype customizations, validation rules, and report generation. For demonstrating the practical value of the created environment, modeling the structure of a real organization Baltijos programine iranga is presented.

In the end of the 80´s the area of system development moved into a new era. As a consequence many new methods and development models emerged which in many cases resulted in problems when choosing system development models and methods. As a result of these problems the today standardized modeling language UML (Unified Modeling Language) was created. UML is tailored to support many different types of projects. This is possible because of UML’s capacity to be adjusted and adapted to a specific company environment.

The purpose of this bachelor thesis is to investigate how and why companies use UML and what experiences and opinions those who use UML have of using UML in practice. To fulfill our purpose we have chosen to carry out a qualitative study with semistandardized interviews. The interviews were accomplished on four companies in Jönköping. The result of the research shows that the primary reason for companies to carry out modeling is because it results in good documentation which makes development, administration and operation easier. Furthermore, the study has shown that the reason that companies have chosen UML is because it is a standard which is suited for various different projects and also for the development model used in the company. The standardization is also, according to all companies, the primary strength with UML.

Weaknesses in UML are considered to be the lack of process diagrams and standardized syntax in modeling tools. There was found to be an increase in the number of diagrams used the longer the companies have used UML. The diagrams applied by all companies are: use case diagram, class diagram and sequence diagram. Moreover, the use of diagrams for a specific project is dependent on the project type and size. However, none of the companies utilize the flexibility to adjust the syntax. All companies combine UML with RUP or business customized development models with characteristics from RUP. There is, however, a difference in how companies use the diagrams in combination with the development models. This probably depends on the companies’ iterative way of working where the diagrams are involved in the whole system development process.

I slutet av 80-talet gick systemutvecklingen in i ett nytt skede. Detta fick som följd att många nya metoder och utvecklingsmodeller för systemutveckling skapades vilket i flera fall ledde till problem vid val av systemutvecklingsmetod och modell. Till följd av detta skapades det idag standardiserade modelleringsspråket UML (Unified Modeling Language). UML är anpassat för att stödja många olika typer av projekt eftersom det tillåter företagsspecifika anpassningar och förändringar.

Syftet med studien är att undersöka hur och varför företag använder sig av UML samt vilka erfarenheter och uppfattningar de som arbetar med UML har av att tillämpa det i praktiken. För att uppfylla syftet har vi valt att genomföra en kvalitativ studie med semistandardiserade intervjuer. Intervjuerna utfördes på fyra företag i Jönköpingsregionen.

Resultatet av studien visar att den främsta anledningen till att företag modellerar är att det ger en bra dokumentation vilket underlättar utveckling, förvaltning och drift. Vidare har studien visat att UML har valts på grund av att det är en standard som lämpar sig för många olika projekt samt för att UML passar den utvecklingsmodell som tillämpas på företaget. Standardiseringen är även enligt samtliga företag den främsta styrkan med UML. Svagheter i UML anses vara avsaknaden av processdiagram samt bristen på standardiserad syntax i verktygen.

Ju längre UML har använts på företagen desto fler diagram används. De diagram som tillämpas av samtliga företag är användningsfallsdiagram, klassdiagram och sekvensdiagram. I övrigt beror användningen av diagram för ett specifikt projekt på projektets typ och storlek. Däremot utnyttjar inget av företagen UML:s flexibilitet att anpassa syntaxen.

Samtliga företag kombinerar i någon utsträckning UML med RUP eller egenutvecklade utvecklingsmodeller med liknande egenskaper som RUP. Det skiljer sig dock i hur företagen använder diagrammen i samband med utvecklingsmodellerna. Detta beror troligtvis på det iterativa sätt företagen arbetar efter där diagrammen följer med i hela systemutvecklingsprocessen.

The Unified Modelling Language (UML) is widely accepted as the standard notation for Object-Oriented methods. However, one of its major problem is its lack of formal semantics. The development of the Object Constraints Language (OCL) in the last few years seems to be the answer to this problem, but some argue that it is difficult to use. In addition, inadequate information and lack of precise definitions of UML models [31] are the two main reasons why current existing 00 supporting tools do not emphasis on the standard input syntax or format used with UML models. In this thesis, the author attempts to provide answers to some of these questions by developing a set of transformation rules from UML to ) VDM++ and then develops an architecture for a CASE tool to support the transformation process.

The Unified Modeling Language (UML) has become the standard language for the design of object-oriented software systems over the past decade. Even though there exist various tools which claim to support design with UML, their functionality is usually focused on drawing UML diagrams and generating code from the UML model. The task of choosing a suitable design which fulfils the requirements still has to be accomplished by the human designer alone. The aim of this thesis is to develop concepts for UML design tools which assist the modeller in improving the system design and requirements incrementally. For this approach a variant of formal games called exploration games is introduced as underlying technique. Exploration games can be defined on the basis of incomplete and imprecise UML models as they occur frequently in practice. The designer repeatedly plays an exploration game to detect flaws or incompleteness in the design and its specification, which are both incorporated in the game definition. At any time the game definition can be incremented by the modeller which allows him to react to the discoveries made during a play and experiment with new design solutions. Exploration games can be applied to UML in different variants. For each variant must be specified how the UML diagrams are used to set up the game and how the semantic variation points of UML should be interpreted. Furthermore some parts of the game definition may not be contained in the UML model and have to be provided separately. The emphasis of this thesis is on game variants which make use of UML diagrams for modelling system behaviour, especially state machines and activity diagrams. A prototypical implementation demonstrates how the concepts developed in this thesis can be put into practice. The tool supports the user in defining, playing and incrementing a game. Moreover it can compute winning strategies for the players and may act as opponent of the modeller. As example a game variant based on UML state machines has been implemented. The architecture that has been chosen for the tool leaves room for extension by additional game variants and alternative algorithms.

With the high demand for renovation of legacy systems, their evolution is becoming an urgent need. Although some approaches have been introduced to evolving legacy systems, they are not sufficient for understanding legacy code. In this thesis, development/environment-specific models of domain-specific legacy systems are acquired, based on their characteristics and operations. The development/environment-specific model of COBOL legacy systems is based on the characteristics and operations of COBOL, and is a procedure-based model comprising a graph that describes the calling and being-called relationships of those procedures in COBOL legacy systems. It has four types: linear, branch, joint, and synthetic procedure-based models. The link-based model of HTML legacy systems uses a graph that describes the importing or imported relationships of webs in a legacy system. It has three types: sequential, cyclical, and compositive link-based models. The development/environment-specific model of the SQL legacy system comprises association, generation and composition database-based models based on the basic operations of SQL and the two main relationships of generation and association between the databases in an SQL legacy system. The structural stage of UML extraction in this thesis contains class realisation. The classification of classes from COBOL legacy system is two, which are procedure class and variable class. Every procedure in COBOL legacy system is defined as one procedure class. Variable class is based on the program slicing techniques with two stages of pseudo class and real class extraction from COBOL legacy system. The variable of the sliced criterion is defined as the class name, and the variables contained in its slicing criterion are defined as the attributes of that variable class. Because the behavioural analysis of domain-specific legacy systems is behind the analysis of structural analysis, the operations in variable class are not described. The classification of classes of HTML legacy system is based on the web pages and their blocks. The classification of SQL legacy system is two, which is procedure class and database class. Selected UML diagrams are used to describe the static aspect of domain-specific legacy systems. The behavioural stage of UML extraction in this thesis focuses on the operations and activities of domain-specific legacy systems. When understanding the operations and activities of domain-specific legacy code, their preconditions and post-conditions must be presented from the source code. Then those operations and activities are ordered according to the time and sequence they are executed by. At last, the operation and activity arraies are presented. Selected UML diagrams describing the dynamic aspect of domain-specific legacy systems are realised based on those operation and activity arraies. The major contribution of this thesis is the presentation of development/ environment-specific models of domain-specific legacy systems and an approach towards software evolution of domain-specific legacy systems using UML diagrams.

The goal of this research is to validate the methodology used while investigating metrics directed verification of Unified Modeling Language (UML) based designs. This document is organized into five distinct sections. The topics discussed include an introduction to the UML, a discussion of available software metrics, a tutorial regarding the nature of design metrics, a discussion of available UML metrics, and the empirical study results. The empirical study presents detailed information regarding how UML class diagrams can be mapped to design metrics, a discussion on how the data was collected and verified, the results obtained during this study, what conclusions were drawn from the data, and recommendations for future research topics. Preliminary findings indicate that a correlation does exist between the external design complexity measure and the UML class diagrams.
Department of Computer Science

A UML (Unified Modeling Language) é uma linguagem de modelagem para especificar, construir e documentar artefatos de sistemas de software. A UML-RT, usada pela ferramenta Rational Rose RealTime (RoseRT), é uma extensão da UML que permite a modelagem de sistemas de tempo real distribuídos e guiados por evento. A UML-RT não possui semântica formal, logo não é possível realizar verificação formal do modelo. O presente trabalho propõe o mapeamento dos elementos de comunicação da UML-RT para a álgebra de processos p-calculus, a fim de prover semântica formal à UML-RT. Com objetivo de automatizar o mapeamento, foi desenvolvido um protótipo de tradutor que captura o modelo UML-RT especificado na ferramenta RoseRT e determina suas definições p-calculus. As definições p-calculus geradas utilizam a sintaxe da gramática do HAL-JACK, que é uma ferramenta integrada para verificação e análise de sistemas expressos em p-calculus, assim as definições p-calculus podem ser submetidas ao HAL-JACK para verificação formal de propriedades. Este trabalho detalha o mapeamento UML-RT para p-calculus, descreve o protótipo desenvolvido e apresenta alguns exemplos do mapeamento do modelo UML-RT para definições p-calculus.

Submitted by Kilvya Braga (kilvyabraga@hotmail.com) on 2018-05-16T13:28:09Z No. of bitstreams: 1 SAULO SOARES DE TOLEDO - DISSERTAÇÃO (PPGCC) 2016.pdf: 2345909 bytes, checksum: dcaa7238380f7791f922778432a5b9ea (MD5)
Made available in DSpace on 2018-05-16T13:28:09Z (GMT). No. of bitstreams: 1 SAULO SOARES DE TOLEDO - DISSERTAÇÃO (PPGCC) 2016.pdf: 2345909 bytes, checksum: dcaa7238380f7791f922778432a5b9ea (MD5) Previous issue date: 2016
Modelos UML são usados de várias formas na engenharia de software. Eles podem modelar desde requisitos até todo o software, e compreendem vários diagramas. O diagrama de classes, o mais popular dentre os diagramas da UML, faz uso de vários elementos UML e adornos, tais como abstração, interfaces, atributos derivados, conjuntos de generalização, composições e agregações. Atualmente, não há maneira fácil de encontrar este tipo de diagrama com base nestas características para a reutilização ou a aprendizagem por tarefas de exemplo. Por outro lado, Sistemas de Recomendação são ferramentas e técnicas que são capazes de descobrir os elementos mais adequados para um usuário, dentre muitos outros. Existem várias técnicas de recomendação, que usam informações dos elementos de várias maneiras, ao uso da opinião de outros usuários. Sistemas de recomendação já foram utilizadas com sucesso em vários problemas da engenharia de software, a exemplo da recomendação de partes de código para reuso (como métodos,por exemplo) e da identificação do desenvolvedor mais adequado para trabalhar em certas áreas do software. Este trabalho tem como objetivo propor e avaliar (i) uma representação baseada em conteúdo para diagramas de classe e as preferências do usuário, (ii) um novo algoritmo de recomendação baseado no conhecimento, (iii) a aplicação deste algoritmo e outros dois outros do estado da parte para a recomendação de diagramas de classe UML e (iv) uma avaliação destas abordagens contra uma sugestão aleatória. Para atingir este objetivo, foi realizado um estudo de caso com estudantes de ciência da computação e egressos. Depois de comparar os algoritmos, os nossos resultados mostram que, para o nosso conjunto de dados, todos eles são melhores do que uma recomendação aleatória.
UML models are used in several ways in the software engineering. They can model from requirements to the entire software, and comprise several diagrams. The Class diagram, the most popular among the UML diagrams, makes use of several UML elements and adornments, such as abstraction, interfaces, derived attributes, generalization sets, compositions and aggregations. Currently, there is no easy way to find this kind of diagram based on these features for reuse or learning by example’s tasks, for instance. On the other hand, Recommender Systems are powerful tools and techniques that are able to discover the most appropriate elements to an user among many others. There are several recommender techniques, from using the elements’ information in several ways, to using other users’ opinions. Recommender systems were already used successfully in several software engineering problems, as discovering pieces of code to recommend (as methods, for example) and finding the best developer to work in certain software problems. This work aims to propose and evaluate (i) a content-based Recommender System’s representation for class diagrams’ features and user’s preferences, (ii) a new knowledge-based recommender algorithm, (iii) the application this algorithm and two other state of the art content-based on esto the recommendation of UML class diagrams and (iv) an evaluation of these approaches against a random suggestion. To achieve this goal, we conducted a case study with computer science students and egresses. After comparing the algorithms, our results show that, for our dataset, all of them are better than a random recommendation.

Distributed, real-time, embedded systems development is a long and complex processwhere demand for development improvements are high. One such potentialimprovement is the implementation of code generation. Code generation refers tothe generation of source code from a model.The goal of this report is to improve the development process of a communicationalsystem component by implementing code generation for that component. The goal isalso to evaluate what improvements in time and error reduction have been achievedthrough the code generation implementation.In this report, a model is created using the UML-modeling environment Papyrus, fromwhich communication configuring source code for the publish/subscribe paradigm canbe generated automatically. To generate the code a compiler translating the model tothe corresponding source code is implemented. Through a case-study the codegenerator proved to generate the intended code and showed potential to be a toolfor improving development time and reduce the amount of errors introduced duringdevelopment.

The graphical user interface (GUI) could have a major impact on the successof an application. Like any other software component, the GUI is designedbefore being developed. The software design process usually starts with anabstract design that is illustrated via a modeling language and narrows downto more specific details during the process. However, there are not anymodeling languages that are explicitly focusing on designing the blueprint ofthe GUI. Developing a modeling language that is specialized in designing theskeleton of the graphical user interface could offer the software designers,architectures and clients the means of obtaining a better communication andunderstanding. Thus, developing a better product. In this report, thedevelopment of such a modeling language was made. The modeling languagecan illustrate the blueprint of the GUI. The development process was madeafter researching and finding the most suitable development procedures forour modeling language.

The thesis deals with the modeling of the Component Based Software (CBS) systems in the UML language and with extension of the UML language with using of meta-modeling techniques and with using of the UML Prodile technology. Thesis also deals with Component Based Development (CBD). The main part of this study deals with specifying of methodology for creating of UML Prodiles and with demonstration of this methodology on selected Component System meta-model by creating the profile including the OCL constraints and description of problems with creating of the prodile. Thesis also describes support of the UML Profile technology in existing UML CASE tools. For demonstration purposes thesis contains the case study with example which uses in this work created UML Profile. Profile is created in accordance with specification of UML version 2.3 and OCL in version 2.2. Demonstration is performed and profile itself is created using IBM Rational Software Architect version 8.0.2.