XDtools is a plugin originally used in the NeOn Toolkit ontology editor. XDtools is used as a tool for the ontology engineer when designing new ontologies or to add new parts to existing ontologies. The XDtools plugin was partially ported to another ontology editor, Protégé. This thesis describes the implementation and design choices made during the work with porting the plugin. A description of the parts that have been ported can be found in the report. It also contains the result of the testing and user study made after the implementation. Conclusions of those results and proposed changes to the plugin are also found in the report.

Design patterns describe solutions that can be used in a particular context for commonly recurring problems at the detailed design level of a software system. Patterns have become an important concept in object-oriented development and their usage is a widely accepted practice. This thesis investigates issue of tool support for design patterns usage that can be offered by UML modelling tools, and proposes UML based method and notation for specification of the patterns, and documentation of their instances in a design model, facilitating such support. Different ways of such support are presented and classified, and comparison of tools offering assistance for patterns usage is depicted. UML profile supporting specification of structural aspects of solutions proposed by design patterns, and documentation of their instances is specified in the thesis.

Saab Aerosystems, a part of Saab AB, has the overall responsibility for the development of the fourth generation fighter aircraft JAS 39 Gripen. When planning a mission for one or more aircrafts, a computer program called Mission Support System is used. Some of the data from the planning is then transferred to the actual aircraft. Today there are some unwanted restrictions in the planning software. One of these restrictions is about the fact that a number of parameters that controls the output from a planned mission are not configurable runtime, i.e. a reinstallation at customers location is needed to change this. The main purpose of this thesis was to propose a new design and a new framework that solves the inflexibility described above. The design should also be validated by a test implementation. A number of different designs were proposed and four of these were selected to be candidates for being implemented. An important tool used when developing the designs was the theory of design patterns. To choose one of the four a ranking system, based on both measurable metrics and non-measurable experience, was used. One design was selected to be the best and after implementing of the design it was considered to be valid. Future work can consist of rewriting all modules in the software to use the new framework.

This paper works as an assignment from the Video On Demand Company Headweb, who wanted aninterface analysis of their own and their competitors VOD services. The purpose is to help Headwebwith their own interface by studying theirs and others interfaces and make an analysis on how theyfunction, how they look and how good the usability is with every service, with hope to findsomething that could make the VOD service of Headweb better.I have also studied how the interfaces of the VOD services look on different platforms, to see howthey are designed as a whole. This has been an expert analysis where I have studied the differentVOD-services by myself, without any external users.To find advantages and disadvantages with the services and their platforms, I have used differenttheories, models and design patterns to frame areas such as filmsearch, categorization, registrationand navigation. I have compared the VOD services with each other and drew conclusions for eacharea to see how the interfaces differ between the services, but also between platforms.My analysis has shown that all VOD services in this project have a very unique interface, eventhough they all have the same goal, to allow the user to control their viewing of film. They usevarious functions and structure and use their own page names and categorizations. In this project, Ihave also found a number of changes that I recommend that Headweb does to their service toenhance the usability.

Design patterns document a field's systematic knowledge derived from experiences. Despite the vast body of work in the field of multi-agent systems (MAS), design patterns for MAS are not popular among software practitioners. As MAS have features that are widely considered as key to engineering complex distributed applications, for example in manufacturing, robotics, ecommerce, traffic control and coordination, science simulations, it is important to provide a clear overview of existing patterns to make this knowledge accessible. To that end, a systematic literature review was performed covering the main publication venues of the field since 1998, resulting in 206 patterns. The study shows that (1) there is a lack of a standard template for documenting design patterns for MAS, which hampers the use of patterns by practitioners, (2) associations between patterns are poorly described, which results in a lack of overview of the pattern space, (3) patterns for MAS have been used for a variety of application domains, which underpins their high potential for practitioners, and (4) classifications of design patterns for MAS are bounded to specific pattern catalogs, a more holistic view on the pattern space is missing. From the study, a number of guidelines is outlined that are important for future work on design patterns for MAS and their adoption in practice.

This master thesis deals with the presentation layer and its framework support for the web applications. The thesis is divided into theoretical and practical part. First of all, the presentation layer is described; followed by the depiction of the particular basic technologies running within the web browsers. Communication with the server is one of the topics mentioned as well. The thesis analyzes the AJAX techniques and from a theoretical perspective focuses on the server part of the presentation layer by means of the design patterns. Afterwards, theoretical findings are analyzed with three different frameworks (Zend, PRADO, Nette) while the practical example shows all the options offered by each framework. The final conclusion summarizes the particular experiences observed. Therefore, the reader is expected to obtain information regarding the presentation layer from all the points of view. Moreover, the practical comparisons are provided in order to help the reader to choose an efficient framework for development.

Following the success of software engineering design patterns, security patterns are a promising approach to aid in the design and development of more secure software systems. At the same time, recent work on aspect-oriented programming (AOP) suggests that the cross-cutting nature of software security concerns makes it a good candidate for AOP techniques. This work uses a set of software metrics to evaluate and compare object-oriented and aspect-oriented implementations of five security patterns--Secure Base Action, Intercepting Validator, Authentication Enforcer, Authorization Enforcer, and Secure Logger. Results show that complete separation of concerns was achieved with the aspect-oriented implementations and the modularity of the base application was improved, but at a cost of increased complexity in the security pattern code. In most cases the cohesion, coupling, and size metrics were improved for the base application but worsened for the security pattern package. Furthermore, a partial aspect-oriented solution, where the pattern code is decoupled from the base application but not completely encapsulated by the aspect, demonstrated better modularity and reusability than a full aspect solution. This study makes several contributions to the fields of aspect-oriented programming and security patterns. It presents quantitative evidence of the effect of aspectization on the modularity of security pattern implementations. It augments four existing security pattern descriptions with aspect-oriented solution strategies, complete with new class and sequence diagrams based on proposed aspect-oriented UML extensions. Finally, it provides a set of role-based refactoring instructions for each security pattern, along with a proposal for three new basic generalization refactorings for aspects.

O presente documento tem por objetivo apresentar o desenvolvimento de uma ferramenta computacional para auxiliar profissionais da área de otimização na implementação de métodos e resolução de problemas. O projeto foi desenvolvido como tema de dissertação no Programa de Mestrado em Ciência da Computação e Matemática Computacional do ICMC/USP. A ferramenta pode ser enquadrada como um ambiente de desenvolvimento (framework) e será chamada de ProOF - Professional Optimization Framework. O ProOF tem como foco principal nortear a implementação computacional de métodos variados para problemas de otimização, utilizando como paradigma a programação orientada a objetos. Esse framework incorpora as principais características encontradas por outras ferramentas propostas na literatura. Além disso, procura facilitar a implementação de métodos e resolução de problemas ao permitir alto reuso de códigos, dar suporte a geração de códigos em diferentes linguagens de programação e gerar uma Graphical User Interface (GUI) automática para parametrização dos métodos inseridos pelo usuário. Alguns trabalhos publicados recentemente utilizaram versões em desenvolvimento do ProOF e serão citados como estudo de caso para atestar a robustez do framework proposto. Por fim, uma comparação será realizada entre o ProOF e outros frameworks existentes na literatura / This paper aims to present the development of a computational tool to assist professionals in the optimization field in implementation of methods and problem solving. The project was developed as dissertation topic in the Masters Program in Computer Science and Computational Mathematics at ICMC/USP. The tool can be considered as a development environment (framework) and will be called ProOF - Professional Optimization Framework. The ProOF is mainly focused on guiding the implementation of various computational methods for optimization problems using as a paradigm the object-oriented programming. This framework incorporating the principal features found in other tools proposed in the literature. Moreover, seeks to facilitate the implementation of methods and problem resolution by allowing high code reuse, give support to code generation in different programming languages and generate a Graphical User Interface (GUI) automatic for parameter setting of methods implemented by the user. Some recently published studies have used previous versions of the ProOF and they will be cited as a case study to attest the robustness of the proposed framework. Finally, a comparison will be made between the ProOF and other existing frameworks in the literature

Les systèmes d'aide à la conduite gèrent un grand volume de données qui doivent être mises à jour régulièrement. Cependant, ces systèmes ne permettent, ni de les stocker, ni de les gérer d'une manière efficace. Pour ces raisons, nous proposons l'intégration d'un système de bases de données temps réel (TR) dans les systèmes d'aide à la conduite. Cela permet d'améliorer la tolérance aux fautes, de réduire le nombre de transactions et de réduire leur temps de réponse. La gestion d'un grand volume de données et leurs contraintes TR rend ces systèmes plus complexes, ce qui rend leur modélisation plus difficile. Pour remédier à cette complexité, nous avons proposé trois patrons de conception en nous basant sur un processus de création de patrons. Ce processus permet de définir les étapes à suivre pour déterminer les fonctionnalités et les exigences du domaine d'aide à la conduite, d'une part, et de définir les règles d'unification pour générer les diagrammes UML de classes et de séquence, d'autre part. Pour représenter ces patrons, nous avons proposé le profil UML-RTDB2, pour tenir compte : (i) de l'expression de la variabilité des patrons, (ii) de la représentation des contraintes TR et des aspects non fonctionnels et (iii) des éléments instanciés à partir des patrons lors de la modélisation d'une application cible. Une fois les patrons créés, ils peuvent être réutilisés par les concepteurs pour modéliser des systèmes spécifiques. Pour cela, nous avons proposé un processus de réutilisation pour guider les concepteurs d'applications lors de la réutilisation des solutions de patrons. Enfin, nous avons procédé à l'évaluation de ces patrons en utilisant deux catégories de métriques. / Advanced Driver Assistance Systems (ADAS) manage an important volume of data that must be updated regularly. However, ADAS don't store, nor manage efficiently these data. For these reasons, we propose to integrate a real-time (RT) database system into ADAS. The integration of the RT database system allows improving the fault tolerance, reducing the number of transactions and minimizing their response time. The management of a lot of data makes these systems complex, thus, their design is highly difficult. To tackle this problem, we have proposed three patterns based on the pattern development process. This process allows defining the steps to follow in order to determine the functionalities and the requirements of the driver assistance domain on one hand, and defining the unification rules for the generation of the UML class and sequence diagrams, on the other hand. In order to represent these patterns, we have proposed UML-RTDB2 profile, which allows (i) expressing the variability of patterns, (ii) representing the real time constraints and the non functional properties and (iii) identifying the role played by each pattern element in a pattern instance. Once the proposed patterns are created, they can be reused by designers to model a specific application. For this reason, we have proposed a process to assist the applications designers when instantiating the patterns solutions. Finally, we have evaluated these patterns based on two categories of metrics.

In ubiquitous environments, users are exposed to public spaces and places where they are supposed to interact and provide also private information. In order to enhance user acceptance of such ubiquitous appliances they have to be designed to consider trust and trustworthiness already in the design phase. We focus on regarding trust in early phases and provide tools for designers by describing trust issues through patterns which are made available through design repositories. Such patterns help designers of ubiquitous applications to create designs quicker based on the availability of already proven solutions they can rely on.