KAJIAN VERSION CONTROL DALAM MENDUKUNG KINERJA DEVELOPER PADA PT. JAWASOFT
DOI:
https://doi.org/10.31000/jika.v2i1.1191Abstract
Abstract - Version Control is a system that keeps track of the historical changes and usage of a resource within an integrated storage media. Version Control (also widely known as a Source Code Management System) is a crucial component for any team working on software development. Version control will keep a record of every single source code change to a file or document, such as historical data, comparisons between different versions, and even access rights to that file or document. A wise choice on which Version Control system to use will have a massive effect on the performance of the Software Developers. Hence many factors must be acknowledged in the process of making the decision of which product to use. The objective of this research is to find which features/attributes of a Version Control System are most influential in the aforementioned decision making process. The research explores the features/attributes inherent in three well known Version Control systems – Subversion, Mercurial and Git. This is done using ISO 9126 as a criteria. Influential factors in the decision making process are gauged using a descriptive analysis technique, and the instrument used in this case is the Analytical Hierarchy Process (AHP). Extensive questionnaire data was 'fed' into the AHP technique, and based on the results obtained, it was calculated that Subversion is the more favorable Version Control system compared to Mercurial and Git. It can thus be concluded that Subversion is the best Version Control system to support the productivity of software developers.
Â
Keywords: Version Control, Subversion, Mercurial, Git, Analytical Hierarchy Process.
Downloads
Published
Issue
Section
License
License and Copyright Agreement
In submitting the manuscript to the journal, the authors certify that:
- They are authorized by their co-authors to enter into these arrangements.
- That it is not under consideration for publication elsewhere,
- That its publication has been approved by all the author(s) and by the responsible authorities – tacitly or explicitly – of the institutes where the work has been carried out.
- They secure the right to reproduce any material that has already been published or copyrighted elsewhere.
- They agree to the following license and copyright agreement.
Copyright
Authors who publish with International Journal of Advances in Intelligent Informatics agree to the following terms:
- Authors retain copyright and grant the journal right of first publication with the work simultaneously licensed under a Creative Commons Attribution License (CC BY-SA 4.0) that allows others to share the work with an acknowledgment of the work's authorship and initial publication in this journal.Â
- Authors are able to enter into separate, additional contractual arrangements for the non-exclusive distribution of the journal's published version of the work (e.g., post it to an institutional repository or publish it in a book), with an acknowledgment of its initial publication in this journal.
- Authors are permitted and encouraged to post their work online (e.g., in institutional repositories or on their website) prior to and during the submission process, as it can lead to productive exchanges, as well as earlier and greater citation of published work.
Licensing for Data Publication
International Journal of Advances in Intelligent Informatics use a variety of waivers and licenses, that are specifically designed for and appropriate for the treatment of data:
Open Data Commons Attribution License, http://www.opendatacommons.org/licenses/by/1.0/ (default)
Creative Commons CC-Zero Waiver, http://creativecommons.org/publicdomain/zero/1.0/
Open Data Commons Public Domain Dedication and Licence, http://www.opendatacommons.org/licenses/pddl/1-0/
Other data publishing licenses may be allowed as exceptions (subject to approval by the editor on a case-by-case basis) and should be justified with a written statement from the author, which will be published with the article.
Open Data and Software Publishing and Sharing
The journal strives to maximize the replicability of the research published in it. Authors are thus required to share all data, code or protocols underlying the research reported in their articles. Exceptions are permitted but have to be justified in a written public statement accompanying the article.
Datasets and software should be deposited and permanently archived inappropriate, trusted, general, or domain-specific repositories (please consult http://service.re3data.org and/or software repositories such as GitHub, GitLab, Bioinformatics.org, or equivalent). The associated persistent identifiers (e.g. DOI, or others) of the dataset(s) must be included in the data or software resources section of the article. Reference(s) to datasets and software should also be included in the reference list of the article with DOIs (where available). Where no domain-specific data repository exists, authors should deposit their datasets in a general repository such as ZENODO, Dryad, Dataverse, or others.
Small data may also be published as data files or packages supplementary to a research article, however, the authors should prefer in all cases a deposition in data repositories.