Keywords

1 Introduction

Source Code Management (SCM) plays an important role in organizing, managing, and controlling the changes delivered by the developers to the source code, documents, and other entities. In LGSI, there is no system that can track the changes delivered by the various stakeholders. The Change Tracker system aims to allow the developers to create a list of interesting files and send notifications to the intended stakeholders if any changes are committed and also the committed changes need to be reviewed by the reviewer. The proposed system is intended for use within LGSI to keep track of changes delivered by the LGSI developers. In addition, it is helpful in keeping stakeholders in communication by sending notifications when any new change is committed. This scope of the work can also be extended to other domains, like the TV team managed by the service provider. Users need not have to worry about the services or management. The best example is the web-based email service. The change Tracker system has been developed with Agile methodology. Agile methodology is popular for its nature of incorporating change in the industry with Agile frameworks such as scrum, Kanban, and extreme programming. The main components of the Scrum framework are organizing small teams, daily scrum meetings to know the status, making sprint planning and review, collaboration with other teams, and meetings with stakeholders. At first, the initial requirement of the Change Tracker system is to track the changes made to code by each developer in later stages based on discussions happened with the product manager and the internal stakeholders; the other requirements are captured such as displaying analytics, exporting permalinks details to excel, and other functionalities. The feedback from various stakeholders play important role in developing a Change Tracker system. The proposed methodology Change Tracker is used in an IT security and compliance management platform. The Change Tracker benefits enterprises track and authenticate changes to the performance of devices, files, and configurations. The important features in Change Tracker are agentless integrity monitoring and intrusion detection.

2 Literature Survey

In SDLC, the same file is modified by many developers from different teams and geographical locations [1]. The latest version of the file may undergo several changes by the developers (Fig. 1). It is very difficult to identify who made the changes to a specific file and also difficult to find or recover accidentally lost files. This problem will directly affect project deliverables and may cause delays in identifying the problem and resolving issues [2]. In addition, the current system is not notifying the developers [3]. The advantages of the protractions are diminished when whiskers make contact with objects, according to the author [4], which causes whiskers to have a tendency to only barely touch the environment. There has been research on how this mechanism affects sensory input, but less is known about how sensory input alters the motor pattern [4].

Fig. 1
A hierarchy chart of the latest version update. The master branch leads to users 1, 2, and 3, respectively. Users 1 and 2 have question marks on the top while user 3 has 2 plus signs.

Existing system

Full size image

Currently, there is no system to notify other developers who previously modified the same file, and there is no system to track developer’s action when exaggerated past designations file modified by others. Introducing changes accidentally may cause project risk.

3 Proposed System

The proposed system is capable of tracking changes delivered by the LGSI developers and enables communication between respective stakeholders. The proposed system is capable of tracking changes delivered by the LGSI developers and enables the communication between respective stakeholders. The Change Tracker tracks the files delivered by all users. It keeps track of the users interested in a file. Once a particular file is modified, Change Tracker notifies all the developers interested in that file. PL can track LGSI applicability on developer interested file. He proposed system facilitate developers to create list of interested Files. The Change Tracker tracks the files delivered by all users. It keeps a track of the users interested in a file. Once a particular file is modified, Change Tracker notifies all the developers interested in that file. The study is conducted before developing the Change Tracker application and analyzed the facts that will affect the project completion. In this study, we identified the technology stack essential for developing this Change Tracker system, such as HTML, CSS, Bootstrap, and JavaScript for the front end and Java, JSP, MySQL, and Java Servlets for the back end and also identified the organization has a strong technical team with essential skills and has the necessary hardware requirements. The development of this application is possible within the threshold budget for the entire project; the costs will include hardware and software costs, development costs, and operational costs. The Change Tracker application can be developed without any extra cost to the organization as this project can be carried out with the existing infrastructure of the organization [5]. This application is beneficial for the organization as it can track changes made to the project and avoids any accidental changes and ensures the software quality which will be beneficial for the organization in terms of finance. The proposed system facilitates developers to create a list of interested files [6].

4 Methodology

In the recent years, study has been conducted to map the behavior of components of complex systems and to clarify material flow and mixing properties. Although research groups have established systems to track rodents through video, with the exception of [7], prior approaches all need a secured computer for computation. In software engineering, software engineering researchers have provided many software development methodologies that fit or are adapted by various industries’ Software solutions. During the initial stages of the project Change Tracker, there were various methodologies planned, and the Agile methodology was best suited for this project and worked accordingly. In recent years, the organization faced more difficulties as there is no system or software application for tracking permalinks and all their information. Therefore, the organization planned such an application that adapted one of the software development methods, agile development (Fig. 2). The agile development methodology is the simplest form. As a result of this concern, the advantages of agile software development [8] are that the organization is capable of reducing the overall risk which is associated with the Change Tracker tool.

Fig. 2
A 2-part flow diagram of the organization methodology of the software development method. Part 1 includes permalinks 1, 2, and 3 that lead to Gerrit files 1, 2, and 3, respectively. In part 2, the Gerrit files lead to files 1, 2, 3, and the database which further leads to 2 tables titled review committee and domain interested file notification.

Architecture of Change Tracker

Full size image

The user can view records consisting of permalinks (Fig. 3) details created by all the developers. The internal stakeholders of the Change Tracker system can export the record of permalink details, including information such as date, permalink, branch, project, owner, query type, reviewer, status, and history.

Fig. 3
A screenshot of the L G change tracker. The header lists permalinks, settings, and management. It loads the permalink page with a table that has 10 columns.

User Permalink

Full size image

In the settings, users can view records consisting of details created by the developers. They include information such as entities branch (Fig. 4), project, file, added type, status, copy query, and add query. Type is maintained to be application and state should be active [9].

Fig. 4
A screenshot of the L G change tracker. The header lists permalinks, settings, and management. It loads the settings page with a table that has 6 columns.

Record view

Full size image

The Change Tracker system must enable communication between the admin, reviewer, and user through email notifications (Fig. 5).

Fig. 5
A screenshot of the L G change tracker. It loads the email notification setting page from the settings page. The notification setting option is set to no from the email notification setting tab.

Email notification setting

Full size image

5 Results and Discussions

After deploying the site on the elastic instance, we obtain the URL and visit the website that we deployed [10]. We then enter our credentials (Fig. 6) to log in, as the users are authenticated functions.

Fig. 6
A screenshot of the L G change tracker. It loads login with your A D account tab that lists your A D account, password, domain, and group details to login in.

Login to the module

Full size image

Here, the admin (Fig. 7) can post the permalink for other users to access and read them. This is how we can see the permalinks.

Fig. 7
A screenshot of the L G change tracker. It loads the permalinks table with 10 columns and 5 entries.

Dashboard of permalink

Full size image

6 Conclusion

In this paper, we have proposed the Change Tracker system to address one of the major problems faced by the LGSI employees in identifying who modified the code, removed files during software development. The Change Tracker system allows every individual developer to keep track of changes delivered to his/her interested files and creates permalinks delivered by LGSI developers then the permalinks will be reviewed by the review task team. In addition, Change Tracker notifies the respective stakeholders when the changes are made. Thus, this application helps in taking care of any risk associated when a new change is introduced or modified. In the future, the organization plans to enhance the proposed system by incorporating features like all DevOps activities such as tracking android security patches, domain patches also the Change Tracker system into a single application as its future goal.