Version Control System

14,000,000 Leading Edge Experts on the ideXlab platform

Scan Science and Technology

Contact Leading Edge Experts & Companies

Scan Science and Technology

Contact Leading Edge Experts & Companies

The Experts below are selected from a list of 62172 Experts worldwide ranked by ideXlab platform

Motoshi Saeki - One of the best experts on this subject based on the ideXlab platform.

  • IWPSE - Hierarchical categorization of edit operations for separately committing large refactoring results
    Proceedings of the 14th International Workshop on Principles of Software Evolution - IWPSE 2015, 2015
    Co-Authors: Jumpei Matsuda, Shinpei Hayashi, Motoshi Saeki
    Abstract:

    In software configuration management using a Version Control System, developers have to follow the commit policy of the project. However, preparing changes according to the policy are sometimes cumbersome and time-consuming, in particular when applying large refactoring consisting of multiple primitive refactoring instances. In this paper, we propose a technique for re-organizing changes by recording editing operations of source code. Editing operations including refactoring operations are hierarchically managed based on their types provided by an integrated development environment. Using the obtained hierarchy, developers can easily configure the granularity of changes and obtain the resulting changes based on the configured granularity. We confirmed the feasibility of the technique by applying it to the recorded changes in a large refactoring process.

  • Meta-Modeling Based Version Control System for Software Diagrams
    IEICE Transactions on Information and Systems, 2006
    Co-Authors: Takafumi Oda, Motoshi Saeki
    Abstract:

    In iterative software development methodology, a Version Control System is used in order to record and manage modification histories of products such as source codes and models described in diagrams. However, conventional Version Control Systems cannot manage the models as a logical unit because the Systems mainly handle source codes. In this paper, we propose a Version Control technique for handling diagrammatical models as logical units. Then we illustrate the feasibility of our approach with the implementation of Version Control functions of a meta-CASE tool that is able to generate a modeling tool in order to deal with various diagrams.

  • ICSM - Generative technique of Version Control Systems for software diagrams
    21st IEEE International Conference on Software Maintenance (ICSM'05), 2005
    Co-Authors: Takafumi Oda, Motoshi Saeki
    Abstract:

    In iterative software development methodology, a Version Control System is used in order to record and manage modification histories of products such as source codes and models described in diagrams. However, conventional Version Control Systems cannot manage the models in a logical unit because the Systems mainly handle with source codes. In this paper, we propose a technique of Version Control based in a logical unit for models described in diagrams. Then we illustrate the feasibility of our approach with the implementation of Version Control functions on a meta-CASE tool that is able to generate a modeling tool in order to deal with various diagrams.

Rik Van De Walle - One of the best experts on this subject based on the ideXlab platform.

  • git2prov exposing Version Control System content as w3c prov
    International Semantic Web Conference, 2013
    Co-Authors: Tom De Nies, Sara Magliacane, Ruben Verborgh, Sam Coppens, Paul Groth, Erik Mannens, Rik Van De Walle
    Abstract:

    Data provenance is defined as information about entities, activities and people producing or modifying a piece of data. On the Web, the interchange of standardized provenance of (linked) data is an essential step towards establishing trust [2]. One mechanism to track (part of) the provenance of data, is through the use of Version Control Systems (VCS), such as Git. These Systems are widely used to facilitate collaboration primarily for both code and data. Here, we describe a System to expose the provenance stored in VCS in a new standard Web-native format: W3C PROV [4]. This enables the easy publication of VCS provenance on the Web and subsequent integration with other Systems that make use of PROV. The System is exposed as a RESTful Web service, which allows integration into user-friendly tools, such as browser plugins.

  • International Semantic Web Conference (Posters & Demos) - Git2PROV: exposing Version Control System content as W3C PROV
    2013
    Co-Authors: Tom De Nies, Sara Magliacane, Ruben Verborgh, Sam Coppens, Paul Groth, Erik Mannens, Rik Van De Walle
    Abstract:

    Data provenance is defined as information about entities, activities and people producing or modifying a piece of data. On the Web, the interchange of standardized provenance of (linked) data is an essential step towards establishing trust [2]. One mechanism to track (part of) the provenance of data, is through the use of Version Control Systems (VCS), such as Git. These Systems are widely used to facilitate collaboration primarily for both code and data. Here, we describe a System to expose the provenance stored in VCS in a new standard Web-native format: W3C PROV [4]. This enables the easy publication of VCS provenance on the Web and subsequent integration with other Systems that make use of PROV. The System is exposed as a RESTful Web service, which allows integration into user-friendly tools, such as browser plugins.

Cláudia Werner - One of the best experts on this subject based on the ideXlab platform.

  • Towards odyssey-VCS 2: improvements over a UML-based Version Control System
    Proceedings of the 2008 international workshop on Comparison and versioning of software models - CVSM '08, 2008
    Co-Authors: Leonardo Murta, Chessman K. F. Corrêa, João Gustavo Prudêncio, Cláudia Werner
    Abstract:

    Models are becoming first class artifacts in Software Engineering. Due to that, an infrastructure is needed to support model evolution in the same way we have for source-code. One of the key elements of such infrastructure is a Version Control System properly designed for models. In previous work, we presented Odyssey-VCS, a Version Control System tailored to fine-grained UML model elements. In this paper, we discuss the main improvements that we are incorporating on the second release of this System, which are: support for UML 2, reflective processing, explicit branching and auto-branching, generic merge algorithm, support for pessimistic concurrency policy, and support for hooks.

  • odyssey scm an integrated software configuration management infrastructure for uml models
    Science of Computer Programming, 2007
    Co-Authors: Leonardo Murta, Hamilton Oliveira, Cristine Dantas, Luiz Gustavo Lopes, Cláudia Werner
    Abstract:

    Model-driven development is becoming a reality. Different CASE tool vendors support this paradigm, allowing developers to define high-level models and helping to transform them into refined models or source code. However, current software configuration management tools use a file-based data model that is barely sufficient to manipulate source code. This file-based data model is not adequate to provide Versioning capabilities for software modeling environments, which are strongly focused on analysis and architectural design artifacts. The existence of a Versioned repository of high-level artifacts integrated with a customized change Control process could help in the development and maintenance of such model-based Systems. In this work, we introduce Odyssey-SCM, an integrated software configuration management infrastructure for UML models. This infrastructure is composed of a flexible Version Control System for fine-grained UML model elements, named Odyssey-VCS, and two complementary components: a customizable change Control System tightly integrated with the Version Control System, and a traceability link detection tool that uses data mining to discover change traces among Versioned UML model elements and provides the rationale of change traces, automatically collected from the integrated software configuration management infrastructure.

  • odyssey vcs a flexible Version Control System for uml model elements
    Software Configuration Management Workshop, 2005
    Co-Authors: Hamilton Oliveira, Leonardo Murta, Cláudia Werner
    Abstract:

    Many current Version Control Systems use a simple data model that is barely sufficient to manipulate source-code. This simple data model is not sufficient to provide Versioning capabilities for software modeling environments, which are strongly focused on analysis and architectural design artifacts. In this work, we introduce a flexible Version Control System for UML model elements. This Version Control System, named Odyssey-VCS, deals with the complex data model used by UML-based CASE tools. Moreover, it allows the configuration of both the unit of Versioning and unit of comparison for each specific project, respecting the different needs of the diverse development scenarios.

  • SCM - Odyssey-VCS: a flexible Version Control System for UML model elements
    Proceedings of the 12th international workshop on Software configuration management - SCM '05, 2005
    Co-Authors: Hamilton Oliveira, Leonardo Murta, Cláudia Werner
    Abstract:

    Many current Version Control Systems use a simple data model that is barely sufficient to manipulate source-code. This simple data model is not sufficient to provide Versioning capabilities for software modeling environments, which are strongly focused on analysis and architectural design artifacts. In this work, we introduce a flexible Version Control System for UML model elements. This Version Control System, named Odyssey-VCS, deals with the complex data model used by UML-based CASE tools. Moreover, it allows the configuration of both the unit of Versioning and unit of comparison for each specific project, respecting the different needs of the diverse development scenarios.

Robert Morris - One of the best experts on this subject based on the ideXlab platform.

  • pastwatch a distributed Version Control System
    Networked Systems Design and Implementation, 2006
    Co-Authors: Alexander Yip, Benjie Chen, Robert Morris
    Abstract:

    Pastwatch is a Version Control System that acts like a traditional client-server System when users are connected to the network; users can see each other's changes immediately after the changes are committed. When a user is not connected, Pastwatch also allows users to read revisions from the repository, commit new revisions and share modifications directly between users, all without access to the central repository. In contrast, most existing Version Control Systems require connectivity to a centralized server in order to read or update the repository. Each Pastwatch user's host keeps its own writable replica of the repository, including historical revisions. Users can synchronize their local replicas with each other or with one or more servers. Synchronization must handle inconsistency between replicas because users may commit concurrent and conflicting changes to their local replicas. Pastwatch represents its repository as a "revtree" data structure which tracks the relationships among these conflicting changes, including any reconciliation. The revtree also ensures that the replicas eventually converge to identical images after sufficient synchronization. We have implemented Pastwatch and evaluate it in a setting distributed over North America. We have been using it actively for more than a year. We show that the System is scalable beyond 190 users per project and that commit and update operations only take 2-4 seconds. Currently, five users and six different projects regularly use the System; they find that the System is easy to use and that the System's replication has masked several network and storage failures.

  • NSDI - Pastwatch: a distributed Version Control System
    2006
    Co-Authors: Alexander Yip, Benjie Chen, Robert Morris
    Abstract:

    Pastwatch is a Version Control System that acts like a traditional client-server System when users are connected to the network; users can see each other's changes immediately after the changes are committed. When a user is not connected, Pastwatch also allows users to read revisions from the repository, commit new revisions and share modifications directly between users, all without access to the central repository. In contrast, most existing Version Control Systems require connectivity to a centralized server in order to read or update the repository. Each Pastwatch user's host keeps its own writable replica of the repository, including historical revisions. Users can synchronize their local replicas with each other or with one or more servers. Synchronization must handle inconsistency between replicas because users may commit concurrent and conflicting changes to their local replicas. Pastwatch represents its repository as a "revtree" data structure which tracks the relationships among these conflicting changes, including any reconciliation. The revtree also ensures that the replicas eventually converge to identical images after sufficient synchronization. We have implemented Pastwatch and evaluate it in a setting distributed over North America. We have been using it actively for more than a year. We show that the System is scalable beyond 190 users per project and that commit and update operations only take 2-4 seconds. Currently, five users and six different projects regularly use the System; they find that the System is easy to use and that the System's replication has masked several network and storage failures.

  • A serverless, wide-area Version Control System
    2004
    Co-Authors: Benjie Chen, Robert Morris
    Abstract:

    This thesis describes Pastwatch, a distributed Version Control System. Pastwatch maintains Versions of users' shared files. Each Version is immutable: to make changes, a user checks out a Version onto the user's computer, edits the files locally, then commits the changes to create a new Version. The motivation behind Pastwatch is to support wide-area read/write file sharing. An example of this type of sharing is when loosely affiliated programmers from different parts of the world collaborate to work on open-source software projects. To support such users, Pastwatch offers three properties. First, it allows users who travel frequently or whose network connections fail from time to time to access historical Versions of the shared files or make new Versions while disconnected. Second, Pastwatch makes the current and historical Versions of the shared files highly available. For example, even when their office building experiences a power failure, users can still create new Versions and retrieve other users' changes from other locations. Supporting disconnected operation is not adequate by itself in these cases; users also want to see others' changes. Third, Pastwatch avoids using dedicated servers. Running a dedicated server requires high administrative costs, expertise, and expensive equipment. Pastwatch achieves its goals using two interacting approaches. First, it maintains a local branch tree of Versions on each user's computer. A user can check out Versions from the local tree and commit changes into the local tree. Second, Pastwatch uses a shared branch tree in a DHT to publish users' new Versions. It contacts the tree to keep a user's local branch tree up-to-date. (Copies available exclusively from MIT Libraries, Rm. 14-0551, Cambridge, MA 02139-4307. Ph. 617-253-5668; Fax 617-253-1690.)

Takafumi Oda - One of the best experts on this subject based on the ideXlab platform.

  • Meta-Modeling Based Version Control System for Software Diagrams
    IEICE Transactions on Information and Systems, 2006
    Co-Authors: Takafumi Oda, Motoshi Saeki
    Abstract:

    In iterative software development methodology, a Version Control System is used in order to record and manage modification histories of products such as source codes and models described in diagrams. However, conventional Version Control Systems cannot manage the models as a logical unit because the Systems mainly handle source codes. In this paper, we propose a Version Control technique for handling diagrammatical models as logical units. Then we illustrate the feasibility of our approach with the implementation of Version Control functions of a meta-CASE tool that is able to generate a modeling tool in order to deal with various diagrams.

  • ICSM - Generative technique of Version Control Systems for software diagrams
    21st IEEE International Conference on Software Maintenance (ICSM'05), 2005
    Co-Authors: Takafumi Oda, Motoshi Saeki
    Abstract:

    In iterative software development methodology, a Version Control System is used in order to record and manage modification histories of products such as source codes and models described in diagrams. However, conventional Version Control Systems cannot manage the models in a logical unit because the Systems mainly handle with source codes. In this paper, we propose a technique of Version Control based in a logical unit for models described in diagrams. Then we illustrate the feasibility of our approach with the implementation of Version Control functions on a meta-CASE tool that is able to generate a modeling tool in order to deal with various diagrams.