Version Control in Software Engineering

1st Dhruv Shah 2nd Hitesh Gehlot 3rd Akshay Lakshmanan

Dept. of Electronics and Communication Dept. of Electronics and Communication Dept. of Electronics and Communication
Nirma University Nirma University Nirma University
Ahmedabad, India Ahmedabad, India Ahmedabad, India
[email protected] [email protected] [email protected]

Abstract—Version Control Systems (VCS) are foundational collaboration, allowing developers to work on different fea-
tools in software engineering, providing mechanisms to track tures, bug fixes, or experimental changes concurrently without
and manage changes to software projects. This paper explores disrupting the main codebase. This is particularly valuable in
the critical role VCS plays in facilitating parallel development,
collaborative workflows, and maintaining the integrity of complex large teams, where maintaining a stable development environ-
codebases. By comparing Centralized Version Control Systems ment is critical.
(CVCS) and Distributed Version Control Systems (DVCS), we Moreover, VCS supports traceability, which is essential for
highlight the evolving nature of version control as modern soft- debugging, compliance, and quality assurance. The ability
ware projects become increasingly distributed and concurrent. to track the lifecycle of every code change ensures that
Key concepts such as branching, merging, and automated change
management are discussed in-depth, including strategies to miti- any issues can be traced back to their source, making the
gate integration challenges and conflicts. Additionally, the paper debugging process more efficient. This traceability also meets
examines the integration of virtual and physical artefacts through regulatory requirements in industries where code transparency
the Digital Twin paradigm, demonstrating the growing need for and accountability are critical.
version control in multidisciplinary projects that combine hard- This paper provides a comprehensive overview of VCS,
ware and software development. The discussion concludes with
an exploration of emerging trends in version control, including examining both centralized and distributed systems and com-
its application in Agile environments and large-scale systems. paring their strengths and weaknesses. Key functionalities such
This review provides a comprehensive understanding of current as branching, merging, and commit protocols are explored
practices and future directions in version control, emphasizing in-depth, illustrating how these tools enable developers to
its indispensable role in modern software engineering. maintain an organized and effective workflow. Additionally,
Index Terms—Version Control Systems, Centralized VCS,
Distributed VCS, Digital Twin, Branching, Merging, Hardware- the paper highlights innovative applications of VCS, including
Software Integration, Creative Version Control, Automated the integration of Digital Twins for synchronized virtual-
Change Management, Project-Based Learning physical system management and Creative Version Control
Systems (CVCS) for artistic and exploratory projects. These
I. I NTRODUCTION emerging applications of VCS demonstrate its versatility be-
Version Control Systems (VCS) are vital tools in software yond traditional software development, showing its potential
development, designed to track and manage changes to code, in fields like design, art, and product development.
configuration files, and documentation. They provide a robust
safety net by recording a detailed history of modifications, II. T YPES OF V ERSION C ONTROL S YSTEMS
which allows developers to revert to previous versions or A. Centralized Version Control Systems (CVCS)
identify the source of issues. This functionality is crucial Centralized Version Control Systems (CVCS), like Subver-
in maintaining consistency and minimizing errors throughout sion (SVN) and Concurrent Versions System (CVS), rely on a
the development process. VCS also facilitates seamless col- single central repository to store and manage project files. This
laboration by enabling multiple developers to work on the centralized approach simplifies version tracking by providing
same project simultaneously, ensuring that their work does not a single source of truth for the entire project. Developers can
conflict or overwrite each other’s changes. By automating ver- ”checkout” files, make modifications, and then ”commit” their
sion management, VCS streamlines development workflows, changes back to the central repository. While CVCS works
making it easier to recover older versions, merge changes, and well for smaller projects or teams, it faces challenges with
track the overall progress of the project. offline access and risks downtime if the central server fails.
In today’s complex and fast-paced software development Moreover, CVCS requires careful management to prevent file-
landscape, VCS has become indispensable for managing large locking issues that can hinder collaborative development.
codebases and supporting parallel development across dis-
tributed teams. The use of VCS mitigates significant risks B. Distributed Version Control Systems (DVCS)
such as errors, conflicts, and data loss, as it ensures that every Distributed Version Control Systems (DVCS), such as Git
change is recorded, recoverable, and can be traced back to its and Mercurial, offer a more decentralized approach to version
origin. Features like branching and merging further enhance control compared to CVCS. Each developer has a complete
local copy of the project’s history, enabling offline work and users to access earlier versions, undo changes, or compare
independent development. Changes are committed to the local revisions. The system is efficient in storage, as it only saves
repository and then synchronized with a shared, remote repos- the differences, not complete versions.
itory. This model supports extensive branching and merging, However, local VCS has its limitations. Because it’s stored
allowing developers to experiment freely and integrate changes on a single machine, it doesn’t support collaborative work
without constant server access. DVCS has revolutionized the or version tracking across multiple locations, making it less
management of large projects, facilitating the handling of mul- suitable for distributed teams or projects requiring extensive
tiple branches simultaneously and providing advanced conflict teamwork.
resolution capabilities. The local operation and decentralized
nature of DVCS make it the preferred choice for open-source III. C ORE C OMPONENTS OF VCS
and large-scale projects with globally distributed teams. A. Branching
Branching is a cornerstone of VCS, enabling developers to
isolate code changes in parallel environments. With branching,
developers can work on new features or bug fixes indepen-
dently without affecting the main codebase. DVCS, especially
Git, facilitates lightweight branching, making it easy to create
branches frequently and at low cost. Common branching
strategies include ”feature branching,” where each new feature
is developed on a separate branch, and ”release branching” for
finalizing versions. This isolation fosters flexible development
workflows, ensuring that work on new features does not
interfere with ongoing development or introduce bugs into
production code.
Fig. 1. CVCS

Fig. 3. Various Branching Strategies

Talking about the various branching strategies as showcased

in the Figure 3 are part of GitFlow.
1) Feature Branching: Feature branching is a popular ap-
Fig. 2. DVCS proach where each new feature is developed in its own branch.
This isolated branch contains all changes specific to the feature
and is only merged into the main codebase (often the main
C. Local Version Control Systems or develop branch) once the feature is complete and has
Local version control systems (VCS) are foundational tools passed all necessary tests. This strategy minimizes disruptions
for managing file changes on a single computer. They track in the main codebase, as unfinished or experimental features
each modification in a simple database, creating a record remain isolated until they are stable. Feature branches are ideal
of every file’s history. This setup is especially useful for for projects requiring frequent additions or modifications to
individual users or smaller projects where collaboration is functionality, supporting continuous integration and thorough
limited to a single location. testing before code merges into production.
A commonly used local VCS is the Revision Control 2) Release Branching: Release branching is commonly
System (RCS). RCS works by saving ”patch sets,” which used to prepare a product for a final release. A release branch
are the specific changes made between file versions. Each is created from the main or develop branch, allowing the
patch is stored in a particular format on the disk. When a team to focus on bug fixes, polishing, and testing specific to
specific version is needed, RCS applies these patches in order, the release without introducing new features. This branch is
reassembling the file as it was at that point in time. This allows merged back into the main branch and often tagged to mark
the release version. Release branching supports versioned ancestors. This makes it particularly useful for long-running
releases, enabling developers to maintain previous versions for feature branches or when incorporating substantial changes
debugging or hotfixes, which is particularly useful in produc- from multiple contributors over an extended period.
tion environments requiring backward compatibility and stable
deployment cycles.
3) Hotfix Branching: Hotfix branches are crucial for ad-
dressing critical bugs in production. When an urgent issue
arises, a hotfix branch is created from the main branch, allow-
ing developers to work on fixes without interrupting ongoing
development. Once the fix is complete, the hotfix branch is
merged back into both the main and develop branches (or any
equivalent development branch) to ensure the fix is integrated
into the ongoing work. This strategy is particularly valuable for
production systems that require rapid resolution to minimize
downtime or errors.
4) Develop Branching: Develop Branching is a common
strategy employed in projects adhering to structured workflows
like Gitflow. In this approach, the develop branch serves as the
primary branch for active development, positioned between the
main branch (representing stable, production-ready code) and
feature branches.
Fig. 4. Fast Forward Merge
B. Merging and Conflict Resolution
Merging involves combining changes from one branch into
another, often to bring new features back into the main
codebase. Distributed Version Control Systems (DVCS) are
particularly effective at handling merges, allowing for complex
branch integrations while minimizing conflict risks. In larger
teams, conflicts are managed through systematic methods,
such as regular integration merges, which incorporate changes
gradually. Platforms like GitHub and Bitbucket offer visual
interfaces to simplify conflict resolution, while DVCS employs
advanced algorithms to address conflicts at both the syntactic
and semantic levels. Effective merging and conflict resolution
practices are essential to maintaining project stability and re-
ducing merge-related disruptions. Common merging strategies
in Git include:
1) Fast-Forward Merge: A fast-forward merge occurs when Fig. 5. Recursive Merge
the target branch has no changes that diverge from the source
branch. In this scenario, the commit history is updated by 3) Octopus Merge: The octopus merge strategy is a spe-
simply advancing the target branch’s pointer to the latest cialized technique in Version Control Systems (VCS) that
commit on the source branch. As there are no conflicting enables the integration of changes from multiple branches in
changes, no additional merge commit is created, maintaining a single operation. This method is particularly beneficial for
a linear project history. This strategy is straightforward and complex projects that require merging several feature branches
preserves a clean project history. It’s commonly used when back into a main branch simultaneously. Unlike standard
merging feature branches back into a main branch (like main merges, which involve just two branches, octopus merges
or develop) after the feature work is completed and no new can incorporate changes from multiple source branches into
commits have been added to the main branch in the interim. a single merge commit, making it ideal for scenarios such
2) Recursive Merge: Recursive merges are an extension as feature integration at the end of a development cycle or
of three-way merges, designed for scenarios with multiple for release management when multiple updates or fixes need
common ancestors, like repeated merges. This approach re- to be merged at once. However, if conflicts occur during an
solves conflicts by recursively analyzing several parent com- octopus merge, they must be resolved individually for each
mits. Recursive merges effectively handle complex branch branch involved, which can complicate the process. While the
structures, especially when a feature branch has diverged octopus strategy offers efficient multi-branch integration, it
and merged multiple times. The algorithm aims to resolve requires careful conflict management and team coordination
conflicts automatically by examining changes across all shared to ensure codebase stability.
crafted commit message explains the specific change and its
purpose, which is valuable for both current developers and
future maintainers. An effective commit message typically
includes a brief summary, with a more detailed description if
needed. Such documentation provides insights into a project’s
development and the intent behind each change, which is
particularly helpful in larger teams. ”Atomic commits,” where
each commit represents a single functional change, further
simplify the process of locating, understanding, and possibly
reverting specific updates. By following structured commit
practices, developers create a project history that is clear, easy
to navigate, and beneficial for collaboration, code reviews, and
audits.
IV. I NTEGRATION OF V IRTUAL AND P HYSICAL A RTIFACTS
A. Concept of Digital Twins
The Digital Twin concept enables teams to maintain syn-
chronized updates between virtual models and their physical
equivalents, creating a seamless connection between digital de-
signs and real-world artifacts. In industries like manufacturing,
product design, and IoT, Digital Twins are invaluable as they
allow for real-time adjustments to digital models based on data
from physical prototypes. This synchronized version control
ensures that both digital and physical versions progress in har-
mony, enhancing the efficiency of iterative design processes.
Fig. 6. Octopus Merge Through a centralized digital model, VCS can incorporate
real-time updates and facilitate predictive analysis, thereby
accelerating prototype development and refinement.
4) Three-way Merge: A three-way merge is a merging
B. Version Control for Hardware-Software Integration
technique that uses three commits: the common ancestor, the
latest commit on the source branch, and the latest commit on In intricate systems combining hardware and software el-
the target branch. This strategy is applied when both branches ements, integrated Version Control Systems (VCS) handle
have diverged and need to be combined. It creates a new version tracking for both digital models and hardware com-
commit that integrates changes from both branches, ensuring ponents. This functionality ensures synchronization between
that both sets of modifications are retained. If conflicts exist software updates and hardware prototype modifications, a
between the branches, manual conflict resolution is necessary critical factor in fields like embedded systems, automotive,
to complete the merge. and aerospace. VCS enables developers to simultaneously
monitor changes in code, hardware specifications, and design
C. Commit Practices and Version Granularity schematics, creating a unified versioning framework that cap-
tures updates across both domains. This method minimizes
Commits serve as snapshots of a project’s changes, record-
inconsistencies between design and implementation, facilitat-
ing each modification to enable easy tracking and rollback
ing smoother development and testing processes.
of updates. In Distributed Version Control Systems (DVCS),
commits tend to be more granular and frequent, as devel-
opers work within local repositories where they can save
incremental progress. This contrasts with Centralized Version
Control Systems (CVCS), where commits are often larger and
more comprehensive. The fine-grained approach in DVCS pro-
motes traceability, allowing developers to commit each small
change—such as reaching a feature milestone or fixing a minor
bug—making it easier to isolate errors, review change history,
and revert to stable versions without affecting unrelated work.
Frequent commits also enhance continuous integration work-
flows, as committed changes can be automatically tested and
integrated, reducing the risk of conflicting updates.
Commit messages are a critical component of effective Fig. 7. Digital Twin System
commit practices, though they are often overlooked. A well-
V. T OOLS AND T ECHNOLOGIES IN V ERSION C ONTROL

A. Tools
1) Git: Git is the most popular Distributed Version Con-
trol System (DVCS), known for its decentralized structure,
flexible branching, and powerful merging abilities. It supports
advanced development workflows, such as feature-based or
developer-specific branches, without impacting the main code-
base. Its extensive capabilities and compatibility with plat-
forms like GitHub, GitLab, and Bitbucket make Git adaptable
for projects of any complexity level.
Git organizes files into three core states: the working
Fig. 9. SVN Basic Architecture
directory, staging area, and repository. When changes are
made, they initially reside in the working directory, allowing
developers to modify code freely. Ready-to-track changes B. Automated Change Management
move to the staging area, where related modifications can Automation tools simplify VCS processes by using com-
be grouped into a single commit. After staging, changes are mands such as commit, pull, and push to manage workflows,
committed to the repository, creating a snapshot that Git reducing the risk of human error. In Git, for instance, automa-
can retrieve later. This commit history documents all project tion supports Continuous Integration (CI) and Continuous De-
updates, enabling developers to revert changes, merge updates, livery (CD), enabling frequent testing and deployment without
and trace contributions by author. manual input. Integrating with CI/CD platforms like Jenkins
or GitHub Actions further streamlines development cycles,
minimizing delays and speeding up release pipelines. This
automation enhances collaboration by enforcing consistent
code quality checks, which is especially valuable in large-scale
collaborative projects that require minimal manual supervision.

Fig. 8. How actually Git works

2) SVN (Subversion): SVN, a widely used Centralized Fig. 10. CI/CD Pipeline
Version Control System (CVCS), provides a straightforward,
centralized approach to project management. It’s well-suited A CI/CD (Continuous Integration/Continuous Deployment)
for smaller or simpler projects, ensuring developers can re- pipeline is an automated workflow that simplifies code de-
liably access a single version of the repository. Although it velopment, testing, and deployment processes. During the
doesn’t offer the offline functionality found in Distributed Continuous Integration (CI) phase, developers regularly merge
Version Control Systems (DVCS), SVN’s clear workflow and code changes into a central repository, triggering automated
secure repository controls make it ideal for projects that benefit builds and tests with each update. This early detection of bugs
from centralized oversight. or integration issues ensures the code remains in a deployable
With SVN, developers start by ”checking out” a working state. Automated tests, such as unit and integration tests,
copy of the project, creating a local version that mirrors validate code quality, while builds produce executable files
the current repository state. As they make edits, they can or packages. CI establishes a fast feedback loop, allowing
periodically use the svn update command to sync their local developers to quickly identify and address issues, encourag-
copy with any recent changes made by others. When ready to ing frequent, small commits that enhance code stability and
save updates to the repository, they use svn commit, logging collaboration.
each modification as a new version in the repository’s history. The Continuous Deployment (CD) phase builds on CI by
SVN supports file locking, which restricts simultaneous edits automating the release process and preparing code for pro-
on crucial files, helping to avoid conflicts in certain projects. duction. Once code passes the CI pipeline, it is automatically
Additionally, SVN branches allow for feature development or staged for deployment in a testing or staging environment, or,
bug fixes separate from the main branch, with merging tools in full continuous deployment, directly into production. This
available to integrate these changes back into the core project. minimizes manual intervention, enabling faster, more frequent
releases with reduced risk of deployment errors. CD pipelines B. Creative Version Control Systems
may include additional stages to validate readiness across From [6], in creative domains, VCS has adapted to provide
various environments, like staging or testing. By automating version tracking for non-linear workflows, where artists and
integration and deployment, a CI/CD pipeline enables teams designers use versions to experiment and explore alterna-
to deliver high-quality software efficiently, supporting faster, tives. Creative VCS offers features that support low-fidelity
more reliable development cycles. versioning, where only critical changes are saved, enabling
exploration without overloading project history. This flexibility
VI. I MPACT OF T EAM S IZE AND P ROJECT S CALE ON VCS allows artists to reimagine and experiment freely, turning
U SAGE version control into a dynamic “palette” rather than a strict
linear progression.
A. Scalability Challenges in Large Projects
VIII. F UTURE D IRECTIONS AND I NNOVATIONS IN VCS
As projects grow in team size or complexity, Version Con- A. Integration with Advanced Project Management and AI
trol Systems (VCS) encounter specific scalability challenges. AI and Machine Learning are transforming the way devel-
Large teams, especially within open-source or enterprise opers interact with Version Control Systems (VCS), bringing
projects, often adopt complex branching structures to manage a new level of automation, intelligence, and efficiency to the
simultaneous feature development, bug fixes, and releases. In process. AI and ML models can analyze code changes across
these environments, advanced branching strategies (such as multiple branches, anticipate potential merge conflicts, and
Gitflow or trunk-based development) are crucial for organizing recommend conflict resolution strategies before issues arise.
development, ensuring that each branch corresponds to specific This predictive capability helps reduce disruptions in collab-
features, releases, or urgent fixes. While branches help reduce orative environments, which is especially valuable in large-
conflict frequency, they require efficient workflows to merge scale or high-frequency commit scenarios where conflicts can
changes smoothly. Moreover, large projects frequently rely on be more common. Additionally, AI-driven recommendations
issue-tracking tools like Jira, GitHub Issues, or Bugzilla to for branching—based on insights drawn from development
coordinate tasks and link commits to specific bugs, features, patterns—can help teams optimize branch creation, enhancing
or user stories. Integrating these tools with VCS maintains workflow efficiency and preventing the creation of redundant
visibility over roles, tracks progress, and strengthens team branches. Advanced VCS tools are also beginning to incor-
collaboration. The above insights came from paper [3]. porate AI-powered search capabilities, enabling developers
to quickly locate specific code changes or past versions,
B. Structured vs. Ad Hoc Policies which accelerates the development process and ensures greater
accuracy in tracking changes and managing the codebase.
Policies for branching, committing, and merging can vary
greatly depending on team size and project complexity. For B. Expanding Low-Fidelity Versioning for Exploratory
larger teams, structured policies are advantageous as they Projects
guide version control practices, reducing the risk of conflicts Low-Fidelity Versioning is emerging as an ideal solution for
and helping to maintain code stability across the project. creative and experimental projects where maintaining detailed
Smaller teams, on the other hand, may prefer more flexible, version histories may not be necessary. In fields such as digital
ad hoc approaches that support faster iteration without the art, design, or experimental coding, creating high-resolution
need for strict guidelines. VCS systems are versatile, providing snapshots for every change can lead to bloated repositories
both structured repository management and flexible branching and excessive storage demands. Low-fidelity versioning ad-
topologies to support a range of development environments dresses this by capturing only the key changes, omitting minor
and team dynamics. edits or experimental versions, thus streamlining the version
control process while preserving essential milestones. This
VII. V ERSION C ONTROL IN N ON -S OFTWARE D OMAINS method enables flexible iteration and exploration, making it
particularly valuable in fields where the final outcome is
A. Project-Based Learning with VCS uncertain or frequent adjustments are needed. By prioritizing
storage efficiency while still preserving critical checkpoints,
In education, VCS enables students to manage real-world low-fidelity version control offers a lightweight alternative
projects, simulating collaborative workflows in software engi- to traditional high-fidelity systems, making it well-suited for
neering. Project-based learning models that use VCS facilitate workflows that focus on creativity and rapid prototyping.
supervised, role-based collaboration, where students can take
responsibility for individual tasks while still working towards C. Enhanced Security and Access Management in Multi-Level
a shared goal. VCS also allows instructors to evaluate con- Projects
tributions at an individual level, enabling accurate assessment As Version Control Systems (VCS) are increasingly adopted
of teamwork and personal development in coding and project in regulated industries, the need for advanced security and
management skills as mentioned in paper [1]. access control mechanisms is growing. Future VCS tools
are likely to incorporate multi-level access protocols and
secure connections to support projects involving sensitive
or confidential data. These enhanced security features will
ensure that only authorized team members can access specific
branches or data sets, balancing the need for collaboration
with stringent data protection requirements. By implementing
robust access controls, VCS can offer greater flexibility in
collaborative environments while maintaining the integrity and
confidentiality of sensitive project information.
C ONCLUSION
Version Control Systems have significantly transformed
software engineering and beyond, fostering efficient, traceable,
and collaborative workflows. This paper explores the profound
impact of VCS across various fields, including software devel-
opment, creative industries, and educational projects. As VCS
evolves, future advancements such as AI-driven management
and adaptable versioning methods will further enhance its abil-
ity to meet the changing demands of both software engineering
and interdisciplinary projects, ensuring continued innovation
and versatility in diverse domains.
R EFERENCES
[1] I. Milentijevic, V. Ciric, and O. Vojinovic, ”Version control in project-
based learning,” Computers and Education, vol. 50, pp. 1331–1338,
April 2008.
[2] S. Philips, J. Sillito, and R. Walker, ”Branching and Merging: An In-
vestigation into Current Version Control Practices,” Procedia Computer
Science, vol. 131, pp. 627–634, 2018.
[3] C. Brindescu, M. Codoban, S. Shmarkatiuk, and D. Dig, ”How do
centralized and distributed version control systems impact software
changes?,” in Proc. Int. Conf. Softw. Eng. (ICSE), Hyderabad, India,
2014, pp. 322–333.
[4] N. Zolkifli, A. Ngah, and A. Deraman, ”Version Control System: A
Review” Procedia Computer Science, vol. 135, pp. 408-415, 2018.
[5] D. Jones, A. Nassehi and C. Snider, ”Towards integrated version control
of virtual and physical artefacts in new product development: inspirations
from software engineering and the digital twin paradigm” Procedia
CIRP, vol. 100, pp. 283–288, 2021.
[6] S. Sterman, M. J. Nicholas, and E. Paulos, ”Towards creative version
control,” Proc. ACM Hum.-Comput. Interact., vol. 6, no. CSCW2, pp.
336:1–336:25, Nov. 2022.
Page 1 of 11 - Cover Page Submission ID trn:oid:::1:3072804366

DHRUV SHAH
21BEC030_47_59_Version_Control_in_Software_Engineering.…
ENTREPRENEURSHIP DEVELOPEMENT

ENTREPRENEURSHIP DEVELOPEMENT

Institute of Technology, Nirma University

Document Details

Submission ID

trn:oid:::1:3072804366 7 Pages

Submission Date 4,189 Words

Nov 9, 2024, 4:10 PM GMT+5:30

25,457 Characters

Download Date

Nov 9, 2024, 4:15 PM GMT+5:30

File Name

21BEC030_47_59_Version_Control_in_Software_Engineering.pdf

File Size

2.2 MB

Page 1 of 11 - Cover Page Submission ID trn:oid:::1:3072804366

Page 2 of 11 - Integrity Overview Submission ID trn:oid:::1:3072804366

8% Overall Similarity
The combined total of all matches, including overlapping sources, for each database.

Filtered from the Report

Bibliography

Quoted Text

Match Groups Top Sources

28 Not Cited or Quoted 8% 6% Internet sources

Matches with neither in-text citation nor quotation marks
4% Publications
0 Missing Quotations 0% 4% Submitted works (Student Papers)
Matches that are still very similar to source material

0 Missing Citation 0%
Matches that have quotation marks, but no in-text citation

0 Cited and Quoted 0%

Matches with in-text citation present, but no quotation marks

Page 2 of 11 - Integrity Overview Submission ID trn:oid:::1:3072804366

Page 3 of 11 - Integrity Overview Submission ID trn:oid:::1:3072804366

Match Groups Top Sources

28 Not Cited or Quoted 8% 6% Internet sources

Matches with neither in-text citation nor quotation marks
4% Publications
0 Missing Quotations 0% 4% Submitted works (Student Papers)
Matches that are still very similar to source material

0 Missing Citation 0%
Matches that have quotation marks, but no in-text citation

0 Cited and Quoted 0%

Matches with in-text citation present, but no quotation marks

Top Sources
The sources with the highest number of matches within the submission. Overlapping sources will not be displayed.

1 Internet

fastercapital.com 1%

2 Publication

Balu Nivrutti Ilag, AjayKumar P. Baljoshi, Ganesh J. Sangale, Yogesh Athave. "Mas… 1%

3 Internet

appmaster.io 1%

4 Student papers

University of Sydney 1%

5 Publication

D. Venkata Manikanta, Mohinder Bassi, Harpreet Bedi. "Enhanced topology base… 1%

6 Internet

dev.to 0%

7 Internet

www.scaler.com 0%

8 Student papers

Universiti Tenaga Nasional 0%

9 Student papers

Southampton Solent University 0%

10 Student papers

IUBH - Internationale Hochschule Bad Honnef-Bonn 0%

Page 3 of 11 - Integrity Overview Submission ID trn:oid:::1:3072804366

Page 4 of 11 - Integrity Overview Submission ID trn:oid:::1:3072804366

11 Internet

ntnuopen.ntnu.no 0%

12 Student papers

Liverpool John Moores University 0%

13 Internet

www.ncbi.nlm.nih.gov 0%

14 Publication

David Jones, Aydin Nassehi, Chris Snider, James Gopsill, Peter Rosso, Ric Real, Mar… 0%

15 Internet

blog.devart.com 0%

16 Internet

dzone.com 0%

17 Internet

imarcgroup.bigcartel.com 0%

18 Internet

www.redshiftrecruiting.com 0%

19 Internet

doktori.bibl.u-szeged.hu 0%

Page 4 of 11 - Integrity Overview Submission ID trn:oid:::1:3072804366

Page 5 of 11 - Integrity Submission Submission ID trn:oid:::1:3072804366

Version Control in Software Engineering

1st Dhruv Shah 2nd Hitesh Gehlot 3rd Akshay Lakshmanan
5 Dept. of Electronics and Communication Dept. of Electronics and Communication Dept. of Electronics and Communication
Nirma University Nirma University Nirma University
Ahmedabad, India Ahmedabad, India Ahmedabad, India
[email protected] [email protected] [email protected]

1 Abstract—Version Control Systems (VCS) are foundational collaboration, allowing developers to work on different fea-
tools in software engineering, providing mechanisms to track tures, bug fixes, or experimental changes concurrently without
and manage changes to software projects. This paper explores disrupting the main codebase. This is particularly valuable in
the critical role VCS plays in facilitating parallel development,
collaborative workflows, and maintaining the integrity of complex large teams, where maintaining a stable development environ-
8 codebases. By comparing Centralized Version Control Systems ment is critical.
(CVCS) and Distributed Version Control Systems (DVCS), we Moreover, VCS supports traceability, which is essential for
highlight the evolving nature of version control as modern soft- debugging, compliance, and quality assurance. The ability
ware projects become increasingly distributed and concurrent. to track the lifecycle of every code change ensures that
Key concepts such as branching, merging, and automated change
management are discussed in-depth, including strategies to miti- any issues can be traced back to their source, making the
gate integration challenges and conflicts. Additionally, the paper debugging process more efficient. This traceability also meets
14 examines the integration of virtual and physical artefacts through regulatory requirements in industries where code transparency
the Digital Twin paradigm, demonstrating the growing need for and accountability are critical.
version control in multidisciplinary projects that combine hard- This paper provides a comprehensive overview of VCS,
ware and software development. The discussion concludes with
an exploration of emerging trends in version control, including examining both centralized and distributed systems and com-
its application in Agile environments and large-scale systems. paring their strengths and weaknesses. Key functionalities such
13 This review provides a comprehensive understanding of current as branching, merging, and commit protocols are explored
practices and future directions in version control, emphasizing in-depth, illustrating how these tools enable developers to
its indispensable role in modern software engineering. maintain an organized and effective workflow. Additionally,
Index Terms—Version Control Systems, Centralized VCS,
Distributed VCS, Digital Twin, Branching, Merging, Hardware- the paper highlights innovative applications of VCS, including
Software Integration, Creative Version Control, Automated the integration of Digital Twins for synchronized virtual-
Change Management, Project-Based Learning physical system management and Creative Version Control
Systems (CVCS) for artistic and exploratory projects. These
I. I NTRODUCTION emerging applications of VCS demonstrate its versatility be-
1 Version Control Systems (VCS) are vital tools in software yond traditional software development, showing its potential
development, designed to track and manage changes to code, in fields like design, art, and product development.
configuration files, and documentation. They provide a robust
3 II. T YPES OF V ERSION C ONTROL S YSTEMS
3 safety net by recording a detailed history of modifications,
which allows developers to revert to previous versions or A. Centralized Version Control Systems (CVCS)
identify the source of issues. This functionality is crucial Centralized Version Control Systems (CVCS), like Subver-
19 in maintaining consistency and minimizing errors throughout sion (SVN) and Concurrent Versions System (CVS), rely on a
the development process. VCS also facilitates seamless col- single central repository to store and manage project files. This
17 laboration by enabling multiple developers to work on the centralized approach simplifies version tracking by providing
same project simultaneously, ensuring that their work does not a single source of truth for the entire project. Developers can
16 conflict or overwrite each other’s changes. By automating ver- ”checkout” files, make modifications, and then ”commit” their
sion management, VCS streamlines development workflows, changes back to the central repository. While CVCS works
making it easier to recover older versions, merge changes, and well for smaller projects or teams, it faces challenges with
track the overall progress of the project. offline access and risks downtime if the central server fails.
1 In today’s complex and fast-paced software development Moreover, CVCS requires careful management to prevent file-
landscape, VCS has become indispensable for managing large locking issues that can hinder collaborative development.
codebases and supporting parallel development across dis-
10 tributed teams. The use of VCS mitigates significant risks B. Distributed Version Control Systems (DVCS)
such as errors, conflicts, and data loss, as it ensures that every Distributed Version Control Systems (DVCS), such as Git
change is recorded, recoverable, and can be traced back to its and Mercurial, offer a more decentralized approach to version
origin. Features like branching and merging further enhance control compared to CVCS. Each developer has a complete

Page 5 of 11 - Integrity Submission Submission ID trn:oid:::1:3072804366

Page 6 of 11 - Integrity Submission Submission ID trn:oid:::1:3072804366

18 local copy of the project’s history, enabling offline work and users to access earlier versions, undo changes, or compare
independent development. Changes are committed to the local revisions. The system is efficient in storage, as it only saves
repository and then synchronized with a shared, remote repos- the differences, not complete versions.
itory. This model supports extensive branching and merging, However, local VCS has its limitations. Because it’s stored
allowing developers to experiment freely and integrate changes on a single machine, it doesn’t support collaborative work
without constant server access. DVCS has revolutionized the or version tracking across multiple locations, making it less
management of large projects, facilitating the handling of mul- suitable for distributed teams or projects requiring extensive
tiple branches simultaneously and providing advanced conflict teamwork.
resolution capabilities. The local operation and decentralized
nature of DVCS make it the preferred choice for open-source III. C ORE C OMPONENTS OF VCS
and large-scale projects with globally distributed teams. A. Branching
Branching is a cornerstone of VCS, enabling developers to
isolate code changes in parallel environments. With branching,
1 developers can work on new features or bug fixes indepen-
dently without affecting the main codebase. DVCS, especially
Git, facilitates lightweight branching, making it easy to create
branches frequently and at low cost. Common branching
9 strategies include ”feature branching,” where each new feature
is developed on a separate branch, and ”release branching” for
finalizing versions. This isolation fosters flexible development
workflows, ensuring that work on new features does not
interfere with ongoing development or introduce bugs into
production code.
Fig. 1. CVCS

Fig. 3. Various Branching Strategies

Talking about the various branching strategies as showcased

in the Figure 3 are part of GitFlow.
1) Feature Branching: Feature branching is a popular ap-
Fig. 2. DVCS proach where each new feature is developed in its own branch.
This isolated branch contains all changes specific to the feature
and is only merged into the main codebase (often the main
12 C. Local Version Control Systems or develop branch) once the feature is complete and has
Local version control systems (VCS) are foundational tools passed all necessary tests. This strategy minimizes disruptions
for managing file changes on a single computer. They track in the main codebase, as unfinished or experimental features
each modification in a simple database, creating a record remain isolated until they are stable. Feature branches are ideal
of every file’s history. This setup is especially useful for for projects requiring frequent additions or modifications to
individual users or smaller projects where collaboration is functionality, supporting continuous integration and thorough
limited to a single location. testing before code merges into production.
A commonly used local VCS is the Revision Control 2) Release Branching: Release branching is commonly
2 System (RCS). RCS works by saving ”patch sets,” which used to prepare a product for a final release. A release branch
are the specific changes made between file versions. Each is created from the main or develop branch, allowing the
patch is stored in a particular format on the disk. When a team to focus on bug fixes, polishing, and testing specific to
2 specific version is needed, RCS applies these patches in order, the release without introducing new features. This branch is
reassembling the file as it was at that point in time. This allows merged back into the main branch and often tagged to mark

Page 6 of 11 - Integrity Submission Submission ID trn:oid:::1:3072804366

Page 7 of 11 - Integrity Submission Submission ID trn:oid:::1:3072804366

the release version. Release branching supports versioned ancestors. This makes it particularly useful for long-running
releases, enabling developers to maintain previous versions for feature branches or when incorporating substantial changes
debugging or hotfixes, which is particularly useful in produc- from multiple contributors over an extended period.
tion environments requiring backward compatibility and stable
deployment cycles.
3) Hotfix Branching: Hotfix branches are crucial for ad-
dressing critical bugs in production. When an urgent issue
2 arises, a hotfix branch is created from the main branch, allow-
2 ing developers to work on fixes without interrupting ongoing
11 development. Once the fix is complete, the hotfix branch is
merged back into both the main and develop branches (or any
equivalent development branch) to ensure the fix is integrated
into the ongoing work. This strategy is particularly valuable for
production systems that require rapid resolution to minimize
downtime or errors.
4) Develop Branching: Develop Branching is a common
strategy employed in projects adhering to structured workflows
like Gitflow. In this approach, the develop branch serves as the
primary branch for active development, positioned between the
main branch (representing stable, production-ready code) and
feature branches.
Fig. 4. Fast Forward Merge
B. Merging and Conflict Resolution
2 Merging involves combining changes from one branch into
another, often to bring new features back into the main
codebase. Distributed Version Control Systems (DVCS) are
particularly effective at handling merges, allowing for complex
branch integrations while minimizing conflict risks. In larger
teams, conflicts are managed through systematic methods,
such as regular integration merges, which incorporate changes
gradually. Platforms like GitHub and Bitbucket offer visual
interfaces to simplify conflict resolution, while DVCS employs
advanced algorithms to address conflicts at both the syntactic
and semantic levels. Effective merging and conflict resolution
practices are essential to maintaining project stability and re-
ducing merge-related disruptions. Common merging strategies
in Git include:
4 1) Fast-Forward Merge: A fast-forward merge occurs when Fig. 5. Recursive Merge
the target branch has no changes that diverge from the source
branch. In this scenario, the commit history is updated by 3) Octopus Merge: The octopus merge strategy is a spe-
4 simply advancing the target branch’s pointer to the latest cialized technique in Version Control Systems (VCS) that
commit on the source branch. As there are no conflicting enables the integration of changes from multiple branches in
changes, no additional merge commit is created, maintaining a single operation. This method is particularly beneficial for
a linear project history. This strategy is straightforward and complex projects that require merging several feature branches
preserves a clean project history. It’s commonly used when back into a main branch simultaneously. Unlike standard
merging feature branches back into a main branch (like main merges, which involve just two branches, octopus merges
or develop) after the feature work is completed and no new can incorporate changes from multiple source branches into
commits have been added to the main branch in the interim. a single merge commit, making it ideal for scenarios such
2) Recursive Merge: Recursive merges are an extension as feature integration at the end of a development cycle or
of three-way merges, designed for scenarios with multiple for release management when multiple updates or fixes need
common ancestors, like repeated merges. This approach re- to be merged at once. However, if conflicts occur during an
solves conflicts by recursively analyzing several parent com- octopus merge, they must be resolved individually for each
mits. Recursive merges effectively handle complex branch branch involved, which can complicate the process. While the
structures, especially when a feature branch has diverged octopus strategy offers efficient multi-branch integration, it
and merged multiple times. The algorithm aims to resolve requires careful conflict management and team coordination
conflicts automatically by examining changes across all shared to ensure codebase stability.

Page 7 of 11 - Integrity Submission Submission ID trn:oid:::1:3072804366

Page 8 of 11 - Integrity Submission Submission ID trn:oid:::1:3072804366

crafted commit message explains the specific change and its

purpose, which is valuable for both current developers and
future maintainers. An effective commit message typically
includes a brief summary, with a more detailed description if
needed. Such documentation provides insights into a project’s
development and the intent behind each change, which is
particularly helpful in larger teams. ”Atomic commits,” where
each commit represents a single functional change, further
simplify the process of locating, understanding, and possibly
reverting specific updates. By following structured commit
practices, developers create a project history that is clear, easy
to navigate, and beneficial for collaboration, code reviews, and
audits.
IV. I NTEGRATION OF V IRTUAL AND P HYSICAL A RTIFACTS
A. Concept of Digital Twins
The Digital Twin concept enables teams to maintain syn-
chronized updates between virtual models and their physical
equivalents, creating a seamless connection between digital de-
signs and real-world artifacts. In industries like manufacturing,
product design, and IoT, Digital Twins are invaluable as they
allow for real-time adjustments to digital models based on data
from physical prototypes. This synchronized version control
ensures that both digital and physical versions progress in har-
mony, enhancing the efficiency of iterative design processes.
Fig. 6. Octopus Merge Through a centralized digital model, VCS can incorporate
real-time updates and facilitate predictive analysis, thereby
accelerating prototype development and refinement.
4) Three-way Merge: A three-way merge is a merging
B. Version Control for Hardware-Software Integration
technique that uses three commits: the common ancestor, the
latest commit on the source branch, and the latest commit on In intricate systems combining hardware and software el-
the target branch. This strategy is applied when both branches ements, integrated Version Control Systems (VCS) handle
have diverged and need to be combined. It creates a new version tracking for both digital models and hardware com-
commit that integrates changes from both branches, ensuring ponents. This functionality ensures synchronization between
that both sets of modifications are retained. If conflicts exist software updates and hardware prototype modifications, a
between the branches, manual conflict resolution is necessary critical factor in fields like embedded systems, automotive,
to complete the merge. and aerospace. VCS enables developers to simultaneously
monitor changes in code, hardware specifications, and design
C. Commit Practices and Version Granularity schematics, creating a unified versioning framework that cap-
tures updates across both domains. This method minimizes
Commits serve as snapshots of a project’s changes, record-
inconsistencies between design and implementation, facilitat-
ing each modification to enable easy tracking and rollback
ing smoother development and testing processes.
of updates. In Distributed Version Control Systems (DVCS),
commits tend to be more granular and frequent, as devel-
opers work within local repositories where they can save
incremental progress. This contrasts with Centralized Version
Control Systems (CVCS), where commits are often larger and
more comprehensive. The fine-grained approach in DVCS pro-
motes traceability, allowing developers to commit each small
change—such as reaching a feature milestone or fixing a minor
bug—making it easier to isolate errors, review change history,
and revert to stable versions without affecting unrelated work.
Frequent commits also enhance continuous integration work-
flows, as committed changes can be automatically tested and
integrated, reducing the risk of conflicting updates.
Commit messages are a critical component of effective Fig. 7. Digital Twin System
commit practices, though they are often overlooked. A well-

Page 8 of 11 - Integrity Submission Submission ID trn:oid:::1:3072804366

Page 9 of 11 - Integrity Submission Submission ID trn:oid:::1:3072804366

V. T OOLS AND T ECHNOLOGIES IN V ERSION C ONTROL

A. Tools
1) Git: Git is the most popular Distributed Version Con-
trol System (DVCS), known for its decentralized structure,
flexible branching, and powerful merging abilities. It supports
advanced development workflows, such as feature-based or
developer-specific branches, without impacting the main code-
base. Its extensive capabilities and compatibility with plat-
forms like GitHub, GitLab, and Bitbucket make Git adaptable
for projects of any complexity level.
Git organizes files into three core states: the working
Fig. 9. SVN Basic Architecture
directory, staging area, and repository. When changes are
made, they initially reside in the working directory, allowing
developers to modify code freely. Ready-to-track changes B. Automated Change Management
move to the staging area, where related modifications can Automation tools simplify VCS processes by using com-
be grouped into a single commit. After staging, changes are mands such as commit, pull, and push to manage workflows,
committed to the repository, creating a snapshot that Git reducing the risk of human error. In Git, for instance, automa-
can retrieve later. This commit history documents all project tion supports Continuous Integration (CI) and Continuous De-
updates, enabling developers to revert changes, merge updates, livery (CD), enabling frequent testing and deployment without
and trace contributions by author. manual input. Integrating with CI/CD platforms like Jenkins
or GitHub Actions further streamlines development cycles,
minimizing delays and speeding up release pipelines. This
automation enhances collaboration by enforcing consistent
code quality checks, which is especially valuable in large-scale
collaborative projects that require minimal manual supervision.

Fig. 8. How actually Git works

15 2) SVN (Subversion): SVN, a widely used Centralized

7 Fig. 10. CI/CD Pipeline
Version Control System (CVCS), provides a straightforward,
centralized approach to project management. It’s well-suited A CI/CD (Continuous Integration/Continuous Deployment)
for smaller or simpler projects, ensuring developers can re- pipeline is an automated workflow that simplifies code de-
liably access a single version of the repository. Although it velopment, testing, and deployment processes. During the
6 doesn’t offer the offline functionality found in Distributed Continuous Integration (CI) phase, developers regularly merge
Version Control Systems (DVCS), SVN’s clear workflow and code changes into a central repository, triggering automated
secure repository controls make it ideal for projects that benefit builds and tests with each update. This early detection of bugs
from centralized oversight. or integration issues ensures the code remains in a deployable
With SVN, developers start by ”checking out” a working state. Automated tests, such as unit and integration tests,
copy of the project, creating a local version that mirrors validate code quality, while builds produce executable files
the current repository state. As they make edits, they can or packages. CI establishes a fast feedback loop, allowing
periodically use the svn update command to sync their local developers to quickly identify and address issues, encourag-
copy with any recent changes made by others. When ready to ing frequent, small commits that enhance code stability and
save updates to the repository, they use svn commit, logging collaboration.
each modification as a new version in the repository’s history. The Continuous Deployment (CD) phase builds on CI by
SVN supports file locking, which restricts simultaneous edits automating the release process and preparing code for pro-
on crucial files, helping to avoid conflicts in certain projects. duction. Once code passes the CI pipeline, it is automatically
Additionally, SVN branches allow for feature development or staged for deployment in a testing or staging environment, or,
bug fixes separate from the main branch, with merging tools in full continuous deployment, directly into production. This
available to integrate these changes back into the core project. minimizes manual intervention, enabling faster, more frequent

Page 9 of 11 - Integrity Submission Submission ID trn:oid:::1:3072804366

Page 10 of 11 - Integrity Submission Submission ID trn:oid:::1:3072804366

releases with reduced risk of deployment errors. CD pipelines B. Creative Version Control Systems
may include additional stages to validate readiness across From [6], in creative domains, VCS has adapted to provide
various environments, like staging or testing. By automating version tracking for non-linear workflows, where artists and
integration and deployment, a CI/CD pipeline enables teams designers use versions to experiment and explore alterna-
to deliver high-quality software efficiently, supporting faster, tives. Creative VCS offers features that support low-fidelity
more reliable development cycles. versioning, where only critical changes are saved, enabling
exploration without overloading project history. This flexibility
VI. I MPACT OF T EAM S IZE AND P ROJECT S CALE ON VCS allows artists to reimagine and experiment freely, turning
U SAGE version control into a dynamic “palette” rather than a strict
linear progression.
A. Scalability Challenges in Large Projects
VIII. F UTURE D IRECTIONS AND I NNOVATIONS IN VCS
As projects grow in team size or complexity, Version Con- A. Integration with Advanced Project Management and AI
trol Systems (VCS) encounter specific scalability challenges. AI and Machine Learning are transforming the way devel-
Large teams, especially within open-source or enterprise opers interact with Version Control Systems (VCS), bringing
projects, often adopt complex branching structures to manage a new level of automation, intelligence, and efficiency to the
simultaneous feature development, bug fixes, and releases. In process. AI and ML models can analyze code changes across
these environments, advanced branching strategies (such as multiple branches, anticipate potential merge conflicts, and
Gitflow or trunk-based development) are crucial for organizing recommend conflict resolution strategies before issues arise.
development, ensuring that each branch corresponds to specific This predictive capability helps reduce disruptions in collab-
features, releases, or urgent fixes. While branches help reduce orative environments, which is especially valuable in large-
conflict frequency, they require efficient workflows to merge scale or high-frequency commit scenarios where conflicts can
changes smoothly. Moreover, large projects frequently rely on be more common. Additionally, AI-driven recommendations
issue-tracking tools like Jira, GitHub Issues, or Bugzilla to for branching—based on insights drawn from development
coordinate tasks and link commits to specific bugs, features, patterns—can help teams optimize branch creation, enhancing
or user stories. Integrating these tools with VCS maintains workflow efficiency and preventing the creation of redundant
visibility over roles, tracks progress, and strengthens team branches. Advanced VCS tools are also beginning to incor-
collaboration. The above insights came from paper [3]. porate AI-powered search capabilities, enabling developers
to quickly locate specific code changes or past versions,
B. Structured vs. Ad Hoc Policies which accelerates the development process and ensures greater
accuracy in tracking changes and managing the codebase.
Policies for branching, committing, and merging can vary
greatly depending on team size and project complexity. For B. Expanding Low-Fidelity Versioning for Exploratory
larger teams, structured policies are advantageous as they Projects
guide version control practices, reducing the risk of conflicts Low-Fidelity Versioning is emerging as an ideal solution for
and helping to maintain code stability across the project. creative and experimental projects where maintaining detailed
Smaller teams, on the other hand, may prefer more flexible, version histories may not be necessary. In fields such as digital
ad hoc approaches that support faster iteration without the art, design, or experimental coding, creating high-resolution
need for strict guidelines. VCS systems are versatile, providing snapshots for every change can lead to bloated repositories
both structured repository management and flexible branching and excessive storage demands. Low-fidelity versioning ad-
topologies to support a range of development environments dresses this by capturing only the key changes, omitting minor
and team dynamics. edits or experimental versions, thus streamlining the version
control process while preserving essential milestones. This
VII. V ERSION C ONTROL IN N ON -S OFTWARE D OMAINS method enables flexible iteration and exploration, making it
particularly valuable in fields where the final outcome is
A. Project-Based Learning with VCS uncertain or frequent adjustments are needed. By prioritizing
storage efficiency while still preserving critical checkpoints,
In education, VCS enables students to manage real-world low-fidelity version control offers a lightweight alternative
projects, simulating collaborative workflows in software engi- to traditional high-fidelity systems, making it well-suited for
neering. Project-based learning models that use VCS facilitate workflows that focus on creativity and rapid prototyping.
supervised, role-based collaboration, where students can take
responsibility for individual tasks while still working towards C. Enhanced Security and Access Management in Multi-Level
a shared goal. VCS also allows instructors to evaluate con- Projects
tributions at an individual level, enabling accurate assessment As Version Control Systems (VCS) are increasingly adopted
of teamwork and personal development in coding and project in regulated industries, the need for advanced security and
management skills as mentioned in paper [1]. access control mechanisms is growing. Future VCS tools

Page 10 of 11 - Integrity Submission Submission ID trn:oid:::1:3072804366

Page 11 of 11 - Integrity Submission Submission ID trn:oid:::1:3072804366

are likely to incorporate multi-level access protocols and

secure connections to support projects involving sensitive
or confidential data. These enhanced security features will
ensure that only authorized team members can access specific
branches or data sets, balancing the need for collaboration
with stringent data protection requirements. By implementing
robust access controls, VCS can offer greater flexibility in
collaborative environments while maintaining the integrity and
confidentiality of sensitive project information.
C ONCLUSION
Version Control Systems have significantly transformed
software engineering and beyond, fostering efficient, traceable,
and collaborative workflows. This paper explores the profound
impact of VCS across various fields, including software devel-
opment, creative industries, and educational projects. As VCS
evolves, future advancements such as AI-driven management
and adaptable versioning methods will further enhance its abil-
ity to meet the changing demands of both software engineering
and interdisciplinary projects, ensuring continued innovation
and versatility in diverse domains.
R EFERENCES
[1] I. Milentijevic, V. Ciric, and O. Vojinovic, ”Version control in project-
based learning,” Computers and Education, vol. 50, pp. 1331–1338,
April 2008.
[2] S. Philips, J. Sillito, and R. Walker, ”Branching and Merging: An In-
vestigation into Current Version Control Practices,” Procedia Computer
Science, vol. 131, pp. 627–634, 2018.
[3] C. Brindescu, M. Codoban, S. Shmarkatiuk, and D. Dig, ”How do
centralized and distributed version control systems impact software
changes?,” in Proc. Int. Conf. Softw. Eng. (ICSE), Hyderabad, India,
2014, pp. 322–333.
[4] N. Zolkifli, A. Ngah, and A. Deraman, ”Version Control System: A
Review” Procedia Computer Science, vol. 135, pp. 408-415, 2018.
[5] D. Jones, A. Nassehi and C. Snider, ”Towards integrated version control
of virtual and physical artefacts in new product development: inspirations
from software engineering and the digital twin paradigm” Procedia
CIRP, vol. 100, pp. 283–288, 2021.
[6] S. Sterman, M. J. Nicholas, and E. Paulos, ”Towards creative version
control,” Proc. ACM Hum.-Comput. Interact., vol. 6, no. CSCW2, pp.
336:1–336:25, Nov. 2022.

Page 11 of 11 - Integrity Submission Submission ID trn:oid:::1:3072804366