Open source software (OSS) is typically created in a decentralized self-organizing process by a community of developers having the same or similar interests. A key factor for the success of OSS over the last two decades is the internet: Developers who rarely meet face-to-face can employ new means of communication, both for rapidly writing and deploying software. Therefore, many tools emerged that assist a collaborative software development process, including in particular tools for source code management (SCM) and version control. In the R world, SCM is not a new idea, in fact, the R Development Core Team has always been using SCM tools for the R sources; first by means of Concurrent Versions System (CVS), and then via Subversion (SVN). A central repository is hosted by ETH Zürich mainly for managing the development of the base R system. Mailing lists like R-help, R-devel and many others are currently the main communication channels in the R community. Also beyond the base system, many R contributors employ SCM tools for managing their R packages, e.g., via web-based SVN repositories like SourceForge (http://SourceForge.net/) or Google Code (http://Code.Google.com/). However, there has been no central SCM repository providing services suited to the specific needs of R package developers. Since early 2007, the R-project offers such a central platform to the R community. R-Forge (http://R-Forge.R-project.org/) provides a set of tools for source code management and various web-based features. It aims to provide a platform for collaborative development of R packages, R-related software or further projects. / Series: Research Report Series / Department of Statistics and Mathematics

O controle de versões é uma das principais funcionalidades do Gerenciamento de Configuração de Software (GCS) e visa, entre outras coisas, a recuperação e auditoria (quem, quando e o quê) de versões anteriores e a redução do espaço de armazenamento dos produtos em desenvolvimento. Existem ferramentas que auxiliam esse controle - o CVS (Concurrent Versions System) é uma delas e tem sido amplamente adotado. Como apoio à edição colaborativa na Web, o CVS pode proporcionar benefícios no sentido de recuperar e verificar versões anteriores. Atualmente, ferramentas conhecidas como “wiki", que possibilitam edição colaborativa por meio da Web, têm obtido muitos adeptos. Um exemplo desse tipo de ferramenta é a CoTeia, que tem sido utilizada no ambiente acadêmico do Instituto de Ciências Matemáticas e de Computação (ICMC) da Universidade de São Paulo (USP) desde 2001, e vem sendo utilizada também, integrada à ferramenta DocRationale, usada para registro do Design Rationale (DR). Além da edição colaborativa, é possível também o armazenamento de arquivos (uploads) associados às páginas Web da wiki. A ferramenta DocRationale viabiliza o armazenamento de artefatos relacionados ao processo de desenvolvimento de software, através do upload de arquivos. No entanto, o controle de versões desses artefatos na CoTeia não era provido. De fato, não existe um consenso da literatura a respeito do suporte de controle de versões em áreas de upload nas wikis. Neste trabalho foi realizado um estudo para análise do uso de controle de versões nas páginas e nos uploads em um conjunto de wikis pesquisadas. Já na DocRationale, como os artefatos são alterados durante o processo de desenvolvimento de software, o controle de versões na CoTeia se torna um mecanismo importante. Com isso, foi implementado o controle de versões dos artefatos armazenados na ferramenta DocRationale, através da integração do CVS à CoTeia utilizada na DocRationale. / Versions Control is one of the main activities of Software Configuration Management (SCM) and aims, among other goals, the previous versions retrieval and auditing (who, when and what), and the reduction of storage space required by under development products. There are tools that help this control – CVS is one of these and has been widely adopted. As a support to web collaborative editing, CVS can provide benefits by retrieving and checking previous versions. Nowadays, the tools known as wiki, which allow web collaborative editions, have been gathered many adopters. An example of this kind of tool is CoTeia, that has been used in academic environment at Institute of Mathematics Science and Computing (ICMC) of University of São Paulo (USP) since 2001. CoTeia has also been used integrated to DocRationale tool, which is used to register design rationale. Besides the collaborative editing, CoTeia also permits the file uploads related to wiki webpages. DocRationale makes possible artifacts storage related to software development process, through file uploads. However, versions control of the artifacts in CoTeia was not provided. Indeed, in literature there is not a consensus about the versions control support in uploads wiki area. The present dissertation shows an analysis of versions control usage on pages and uploads areas of a set of selected wikis. On the other hand, in DocRationale, because the artifacts can be changed during all the software development process, the versions control in CoTeia becomes an important mechanism. For this reason, versions control of artifacts stored in DocRationale was implemented, through integration of CVS to CoTeia used in DocRationale.

<p>Version control is an important tool for safekeeping of data and collaboration between colleagues. These days, new distributed version control systems are growing increasingly popular as successors to centralized systems like CVS and Subversion. Graphical user interfaces (GUIs) make it easier to interact with version control systems, but GUIs for distributed systems are still few and less mature than those available for centralized systems. The purpose of this thesis was to propose specific GUI ideas to make distributed systems more accessible. To accomplish this, existing version control systems and GUIs were examined. A usage survey was conducted with 20 participants consisting of software engineers. Participants were asked to score various aspects of version control systems according to usage frequency and usage difficulty. These scores were combined into an index of each aspect's "unusability" and thus its need of improvement. The primary problems identified were committing, inspecting the working set, inspecting history and synchronizing. In response, a commit helper, a repository visualizer and a favorite repositories list were proposed, along with several smaller suggestions. These proposals should constitute a good starting point for developing GUIs for distributed version control systems.</p>

<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.

Version control is an important tool for safekeeping of data and collaboration between colleagues. These days, new distributed version control systems are growing increasingly popular as successors to centralized systems like CVS and Subversion. Graphical user interfaces (GUIs) make it easier to interact with version control systems, but GUIs for distributed systems are still few and less mature than those available for centralized systems. The purpose of this thesis was to propose specific GUI ideas to make distributed systems more accessible. To accomplish this, existing version control systems and GUIs were examined. A usage survey was conducted with 20 participants consisting of software engineers. Participants were asked to score various aspects of version control systems according to usage frequency and usage difficulty. These scores were combined into an index of each aspect's "unusability" and thus its need of improvement. The primary problems identified were committing, inspecting the working set, inspecting history and synchronizing. In response, a commit helper, a repository visualizer and a favorite repositories list were proposed, along with several smaller suggestions. These proposals should constitute a good starting point for developing GUIs for distributed version control systems.

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.

O controle de versões é uma das principais funcionalidades do Gerenciamento de Configuração de Software (GCS) e visa, entre outras coisas, a recuperação e auditoria (quem, quando e o quê) de versões anteriores e a redução do espaço de armazenamento dos produtos em desenvolvimento. Existem ferramentas que auxiliam esse controle - o CVS (Concurrent Versions System) é uma delas e tem sido amplamente adotado. Como apoio à edição colaborativa na Web, o CVS pode proporcionar benefícios no sentido de recuperar e verificar versões anteriores. Atualmente, ferramentas conhecidas como “wiki”, que possibilitam edição colaborativa por meio da Web, têm obtido muitos adeptos. Um exemplo desse tipo de ferramenta é a CoTeia, que tem sido utilizada no ambiente acadêmico do Instituto de Ciências Matemáticas e de Computação (ICMC) da Universidade de São Paulo (USP) desde 2001, e vem sendo utilizada também, integrada à ferramenta DocRationale, usada para registro do Design Rationale (DR). Além da edição colaborativa, é possível também o armazenamento de arquivos (uploads) associados às páginas Web da wiki. A ferramenta DocRationale viabiliza o armazenamento de artefatos relacionados ao processo de desenvolvimento de software, através do upload de arquivos. No entanto, o controle de versões desses artefatos na CoTeia não era provido. De fato, não existe um consenso da literatura a respeito do suporte de controle de versões em áreas de upload nas wikis. Neste trabalho foi realizado um estudo para análise do uso de controle de versões nas páginas e nos uploads em um conjunto de wikis pesquisadas. Já na DocRationale, como os artefatos são alterados durante o processo de desenvolvimento de software, o controle de versões na CoTeia se torna um mecanismo importante. Com isso, foi implementado o controle de versões dos artefatos armazenados na ferramenta DocRationale, através da integração do CVS à CoTeia utilizada na DocRationale. / Versions Control is one of the main activities of Software Configuration Management (SCM) and aims, among other goals, the previous versions retrieval and auditing (who, when and what), and the reduction of storage space required by under development products. There are tools that help this control – CVS is one of these and has been widely adopted. As a support to web collaborative editing, CVS can provide benefits by retrieving and checking previous versions. Nowadays, the tools known as wiki, which allow web collaborative editions, have been gathered many adopters. An example of this kind of tool is CoTeia, that has been used in academic environment at Institute of Mathematics Science and Computing (ICMC) of University of São Paulo (USP) since 2001. CoTeia has also been used integrated to DocRationale tool, which is used to register design rationale. Besides the collaborative editing, CoTeia also permits the file uploads related to wiki webpages. DocRationale makes possible artifacts storage related to software development process, through file uploads. However, versions control of the artifacts in CoTeia was not provided. Indeed, in literature there is not a consensus about the versions control support in uploads wiki area. The present dissertation shows an analysis of versions control usage on pages and uploads areas of a set of selected wikis. On the other hand, in DocRationale, because the artifacts can be changed during all the software development process, the versions control in CoTeia becomes an important mechanism. For this reason, versions control of artifacts stored in DocRationale was implemented, through integration of CVS to CoTeia used in DocRationale.

This Diploma thesis deals with the information system. It contains the analysis of the present state and particular parts of this matter including suggestion of information system for CTMOS company, economic cost evaluation and applicability in practice.