<p>A process for the analysis and collection of information of software systems has been defined. It extracts relevant information of project source files from an online repository and stores that meta-information in a database for further processing. Then, according to the meta-information in the database, it downloads the source files and writes the feedback information back to the database as well. Now the data can be used as input for various analysis tools, in our case a tool called VizzAnalyzer, which reads the project source code and performs a series of software quality analyses.</p><p>But actually, the process, which is mentioned above needs, a lot of manual work, makes the work inefficient and the analysis of large numbers of projects impossible.</p><p>Thus, a series of thesis projects has been devised to automate the whole process. This thesis aims at automating the information extraction and source file download work, which will make the latter preparation of the analysis task much easier and more efficient.</p>

A process for the analysis and collection of information of software systems has been defined. It extracts relevant information of project source files from an online repository and stores that meta-information in a database for further processing. Then, according to the meta-information in the database, it downloads the source files and writes the feedback information back to the database as well. Now the data can be used as input for various analysis tools, in our case a tool called VizzAnalyzer, which reads the project source code and performs a series of software quality analyses. But actually, the process, which is mentioned above needs, a lot of manual work, makes the work inefficient and the analysis of large numbers of projects impossible. Thus, a series of thesis projects has been devised to automate the whole process. This thesis aims at automating the information extraction and source file download work, which will make the latter preparation of the analysis task much easier and more efficient.

Today a lot of software projects are using version control systems for maintaining their software source code. There are a lot of version control systems, and the choice of which one to choose is far from simple. Today the two biggest version control systems are Git and Subversion. In this paper we have found the main differences between the two, and investigated how the choice between them affects software developers. Although software developers in many aspects are unaffected by the choice, we did find some interesting findings. When using Git, our empirical study shows that software developers seem to check in their code to the main repository more frequently than they do when using Subversion. We also found indications that software developers tend to use Subversion with a graphical interface, whereas the preferred interface for working with Git seems to be command-line. We were also surprised of how insignificant the learning aspect of the systems seems to be for the developers. Our goal with this paper is to provide a foundation to stand upon when choosing what version control system to use for a software project.

The topic of this paper is creation of new ServiceNow development tool. ServiceNow is cloud based IT service support management tool. It is widely customizable, mainly by creating scripts. The problem is that scripts are created via web browser, which is not very user friendly. The main goal of this paper is to design better solution for creating scripts in ServiceNow and implement it for selected integrated development environment - Eclipse. Created development tool should support these operations - checking out scripts from ServiceNow to local workspace, editing them in special editor, updating them to newest version and committing them back to ServiceNow with check that work of some other developer is not overwritten. The main contribution of this paper is created ServiceNow development tool that provides better user experience than existing solutions. This paper is only start of development. It will continue in the future.

Git is a distributed version control system that tracks changes to a project overtime and is used to save these changes. Today it is being used by millions of people and is becoming a demand on the job market. For this reason it has become important to learn the version control system. Learning Git however may be difficult for beginners and learning it through tutorials may not always be effective. Learning it through a serious educational game (SEG) may be more effective as a SEG can provide motivation and feedback which are two factors for successful learning. This study seeks to assess how effective a SEG is in teaching Git by looking at the amount of knowledge gained from playing a SEG. This study also seeks to assess how much participants learned Git using a tutorial compared to participants who used a serious educational game. From the results, the study found that the SEG expanded the understanding of Git. The study also found that there was no significant difference in the amount of understanding gained from the SEG and the tutorial.

No description available.

Collaboration is one of the most important topics regarding the evolution of the World Wide Web and thus also for the Web of Data. In scenarios of distributed collaboration on datasets it is necessary to provide support for multiple different versions of datasets to exist simultaneously, while also providing support for merging diverged datasets. In this paper we present an approach that uses SPARQL 1.1 in combination with the version control system Git, that creates commits for all changes applied to an RDF dataset containing multiple named graphs. Further the operations provided by Git are used to distribute the commits among collaborators and merge diverged versions of the dataset. We show the advantages of (public) Git repositories for RDF datasets and how this represents a way to collaborate on RDF data and consume it. With SPARQL 1.1 and Git in combination, users are given several opportunities to participate in the evolution of RDF data.

This thesis concerns a dilemma of multi-lingual web applications. The document describes some general solutions while suggesting such applications, however first of all it is aimed for information system VUT and its enlargement for translation administration. The text contains structural description of this system and instruments used during its development, but especially it defines system requirements of programming engineers and translators, describes and evaluates new language versions solution and there are possibilities of contingent extensions considered at the conclusion of my thesis.

Les logiciels dépendent de bibliothèques tierces pour réduire les coûts liés à leur développement et à leur maintenance. Elles proposent un ensemble de fonctionnalités robustes dont les développeurs peuvent tirer parti depuis une interface de programmation. Cependant, cette forte dépendance entre un logiciel et ses bibliothèques oblige les développeurs à reconsidérer leur rôle lorsque le logiciel évolue. Dans cette thèse, nous identifions plusieurs problématiques impliquant les bibliothèques tierces dans un contexte de maintenance logicielle. Plus particulièrement, une bibliothèque peut ne plus répondre aux besoins d’un logiciel et doit être remplacée par une nouvelle.Nous nommons cette opération une migration de bibliothèque.Nous soulevons dans ce contexte trois points qui caractérisent les difficultés rencontrées par les développeurs. Vers quelle bibliothèque migrer ? Comment appliquer la migration ? Avec l’aide de quels développeurs ? Cette thèse discute de solutions et apporte des contributions autour de ces problèmes. Nous présentons plusieurs approches et les évaluons lors de différents cas d’étude. L’analyse de l’évolution logicielle sera notre support de travail, dont la méthodologie est basée sur l’observation des changements de logiciels. Nous décrivons les limites actuelles de nos contribu-tions et ouvrons des perspectives futures pour enrichir l’état de l’art dans ce domaine / Software depend on third-party libraries to reduce development and maintenance costs. Developers have access to robust functionalities through an application programming interface designed by these libraries. However, due to the strong relationship with these libraries, developers have to reconsider their position when the software evolves. In this thesis, we identify several re-search problems involving these third-party libraries in a context of software maintenance. More specifically, a library may not satisfy the software new requirements and has to be replaced by anew one. We call this operation a library migration.We leverage three points that characterize the impediments met by developers in this situation.To which library should they migrate ? How to migrate their software ? Who can help them in this case ? This thesis suggests answers and exposes several contributions to these problems. We define three approaches that are evaluated through several case studies. To achieve this work, weuse a methodology based on software evolution analysis to observe and understand how software change. We describe numerous perspectives to overcome the current limitations of our solutions.

When performing an analysis of the evolution of software quality and software metrics,there is a need to get access to as many versions of the source code as possible. There isa lack of research on how data or source code can be extracted from the source controlmanagement system Git. This thesis explores different possibilities to resolve thisproblem. Lately, there has been a boom in usage of the version control system Git. Githubalone hosts about 6,100,000 projects. Some well known projects and organizations thatuse Git are Linux, WordPress, and Facebook. Even with these figures and clients, thereare very few tools able to perform data extraction from Git repositories. A pre-studyshowed that there is a lack of standardization on how to share mining results, and themethods used to obtain them. There are several tools available for older version control systems, such as concurrentversions system (CVS), but few for Git. The examined repository mining applicationsfor Git are either poorly documented; or were built to be very purpose-specific to theproject for which they were designed. This thesis compiles a list of general issues encountered when using repositorymining as a tool for data gathering. A selection of existing repository mining tools wereevaluated towards a set of prerequisite criteria. The end result of this evaluation is thecreation of a new repository mining tool called Doris. This tool also includes a smallcode metrics analysis library to show how it can be extended.