Source code management using version control system

Majumdar, Rana; Jain, Rachna; Barthwal, Shivam; Choudhary, Chetna

doi:10.1109/icrito.2017.8342438

Cited by 11 publications

(5 citation statements)

References 1 publication

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…Documentation Debt (insufficient, incomplete or outdated documentation) has reportedly been considered the most impactful and interesting for scientific software reviewers [19] given its influence on software reuse and replicability [71]. Finally, Versioning Debt (related to problems in producing and tracing previous versions of the system) is fundamental for collaborative work, given the relevance of versioning for open-science and handling TD [4,15,56]).…”

Section: Technical Debtmentioning

confidence: 99%

“…Version control is a class of systems responsible for managing changes to computer programs or collections of information. Its popularity has grown exponentially over the last decade [56], and it is also being taught in statistical or mathematical courses [15,30,46,77]. Table 12 summarises the findings in this area.…”

Section: Versioning Debtmentioning

confidence: 99%

“…This study aims to address this gap by providing a first exploratory study of TD in MP. We focused on three specific TD types: Code (the most commonly admitted by developers [7,22,75,89], and one of the most researched [33,54]), Documentation (the most impactful and interesting for scientific software reviewers [19]), and Versioning (given the relevance of versioning for open-science and handling TD [15,56]). To do this, we conducted an online, anonymous survey with well-established OR academics and practitioners, and gathered 168 full responses regarding self-reported practices that may favour (or control) TD.…”

Section: Introductionmentioning

confidence: 99%

See 2 more Smart Citations

On technical debt in mathematical programming: An exploratory study

Vidoni

Cúnico

2022

Math. Prog. Comp.

View full text Add to dashboard Cite

The Technical Debt (TD) metaphor describes development shortcuts taken for expediency that cause the degradation of internal software quality. It has served the discourse between engineers and management regarding how to invest resources in maintenance and extend into scientific software (both the tools, the algorithms and the analysis conducted with it). Mathematical programming has been considered ‘special purpose programming’, meant to program and simulate particular problem types (e.g., symbolic mathematics through Matlab). Likewise, more traditional mathematical programming has been considered ‘modelling programming’ to program models by providing programming structures required for mathematical formulations (e.g., GAMS, AMPL, AIMMS). Because of this, other authors have argued the need to consider mathematical programming as closely related to software development. As a result, this paper presents a novel exploration of TD in mathematical programming by assessing self-reported practices through a survey, which gathered 168 complete responses. This study discovered potential debts manifested through smells and attitudinal causes towards them. Results uncovered a trend to refactor and polish the final mathematical model and use version control and detailed comments. Nonetheless, we uncovered traces of negative practices regarding Code Debt and Documentation Debt, alongside hints indicating that most TD is deliberately introduced (i.e., modellers are aware that their practices are not the best). We aim to discuss the idea that TD is also present in mathematical programming and that it may hamper the reproducibility and maintainability of the models created. The overall goal is to outline future areas of work that can lead to changing current modellers’ habits and assist in extending existing mathematical programming (both practice and research) to eventually manage TD in mathematical programming.

show abstract

Section: Technical Debtmentioning

confidence: 99%

Section: Versioning Debtmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

See 1 more Smart Citation

On technical debt in mathematical programming: An exploratory study

Vidoni

Cúnico

2022

Math. Prog. Comp.

View full text Add to dashboard Cite

show abstract

“…Distributed Version Control Systems such as Git is the best choice for project development, but the researches done in the past haven't given light to the enhancement of the architecture and methodology of Git [22]. Git developed in April 2005 as an open-source code and distributed version control system, to handle source code with speed and efficiency [16].…”

Section: Gitmentioning

confidence: 99%

Comparison of version control system tools

Khleel

Nehéz

2020

MDT

View full text Add to dashboard Cite

Version control systems (VCS) are widely applied at software companies as a collaborative tool and to maintain multiple versions of source code and documentation. VCS is a software tool that manages development of software projects and provide methods to manage several developers working together and track them. Collaboration considers the master purpose of version control systems. Modern VCS supports the parallel development of artifacts using branches and merges. Currently, the version control system adopts on two approaches to software development, the Centralized Version Control System (CVCS) and the Distributed Version Control System (DVCS). This article introduces the concepts and comparison of Version Control Systems and some criteria to consider when selecting.

show abstract

“…Para alcançar os objetivos propostos acima, é necessário controlar a evolução do software, através do controle de versões, solicitações de mudanças e construção do software [4]. Nesse contexto, o controle de versões combina procedimentos e ferramentas para gerir diferentes versões de itens de configuração que são criados durante o processo de software.…”

Section: Introductionunclassified

Implementando o Gitflow para Gerencia de Configuração em um Projeto de Desenvolvimento de Software Ágil: Um Relato de Experiência

Rivero¹,

Silva²,

Cutrim³

et al. 2021

Anais Do XII Computer on the Beach - COTB '21

View full text Add to dashboard Cite

In software engineering, Software Configuration Management is a set of support activities that allows for the orderly absorption of changes inherent to software development. For that, organization models for code versioning like Gitflow have been proposed. In Gitflow, two fixed branches (master and develop) are used to store the project history and be the starting point for changes. Despite the popularity of Gitflow for being considered a simple workflow, there are few: (a) reports of its use in practice and / or (b) documentation on how to deploy it in a real environment. This paper presents the process of adapting Gitflow and creating rules for its application in a real software development project. This adaptation took into account the opinions of managers and developers of a team of approximately 30 people within an agile Scrum life cycle. As a result, definitions and documents were generated to keep track of development, in addition to defining the necessary steps for its application considering the development process adopted by the team.

show abstract

Source code management using version control system

Cited by 11 publications

References 1 publication

On technical debt in mathematical programming: An exploratory study

On technical debt in mathematical programming: An exploratory study

Comparison of version control system tools

Implementando o Gitflow para Gerencia de Configuração em um Projeto de Desenvolvimento de Software Ágil: Um Relato de Experiência

Contact Info

Product

Resources

About