1.

Introduction
The project “Internship portal for Government of Sikkim” is a digital solution aimed
to migrate the current offline process of internship management process to a digital platform
providing a web-based internship management system which allows students from various
organizations to apply for internship, monitor the internship lifecycle under the Government
of Sikkim. The system is aimed to provide an internship management platform covering
both the aspects i.e., the student or the intern and the internship instructor.

The project consists of three modules based on the user role i.e., Student/Intern, Instructor
and Administrator. The project consists of four services, that is, application service,
internship management service and remarks, certificate service and mail service.
The Student/Intern and Admin module of the project handles the following features of the
project application i.e., application/registration form submission for internship, fetching the
selected internship, assigned project, uploading the project files and data in the designated
folder, request and claim for certification.

1.1. Aim and Objectives

1.1.1. Aim:
To develop two modules (student/intern and admin) of web-based system
“Internship portal for Government of Sikkim” that allows students doing
internship under Government of Sikkim to monitor and manage the cycle of an
internship, commencing from application registration till the completion of the
internship and gaining certification with the features which includes internship
registration, application form status tracking, central repository for storing
necessary files associated with the internship, request and claim for
certification. Additionally, to provide administrative tools for the administrator
of the system to manipulate and manage the data of the system.

1.1.2. Objectives:
• To develop an internship registration service.
• To develop a centralized repository for storing files.
• To develop a role specific dashboard.

1
 • To integrate email service to provide updates and important
notifications.
• To automate certificate generation.
1.2. General Overview of the Problem
The current internship management process in the Government of Sikkim relies
entirely on offline methods, leading to significant issues like inefficiency, a lack of a
centralized platform, and communication gaps. The entire process is manual, making it time-
consuming and prone to delays in application processing and approvals. Moreover, there is
no clear platform for uploading and sharing internship files, which complicates the ability of
students to access and work on their projects. This lack of a standardized system may cause
difficulties in monitoring and showcasing of progress at various stages of the internship
cycle. Additionally, the manual certification process requires approvals from multiple levels
of authority, resulting in further delays in receiving completion certificates. Finally, the
absence of timely information, such as email notifications for application submissions, status
updates, project deadlines, or allocation details, may trigger in absence of knowledge about
the internship deadlines.

1.3. Feasibility Study

1.3.1. Technical feasibility:
• Frontend: Angular provides a modern framework for building responsive
and interactive user interfaces.
• Backend: Spring Boot offers a scalable, reliable, and efficient backend server
with RESTful service support.
• Database: MySQL provides a relational database to manage internship data
effectively.
1.3.2. Operational feasibility:
• Students: Provides an easy-to-use platform for application submission, status
tracking, and certificate downloads
• Administrators: Provides simple yet powerful interface and system for data
and system management reducing the manual efforts.
1.3.3. Economic feasibility:
• The project is cost-effective, as it utilizes open-source technologies for both
development and deployment.
• The primary cost involves initial deployment, and hosting, which can be
scaled based on user demand.

2
 1.4. Literature Survey
Table No 1.4.1: Existing System Survey
SL Portal Name URL Organization Features Limitations Similarities with the proposed
No system

1 MEA Internship Portal [1] https://internship.mea.gov.in/internship Ministry of Official platform providing internship Limited to internships under Government-linked platform with
External Affairs, opportunities under MEA for students MEA; lacks private sector structured internship workflow like
Government of with interest in international opportunities. the proposed portal.
India. diplomacy and governance.

2 Internshala [2] https://internshala.com/student/dashboard Internshala Pvt. Comprehensive portal offering Requires user sign-up; some Includes core features like student
Ltd. internships, online trainings, and listings lack clear selection registration, resume uploads, and
certification programs. Widely used procedures; occasional quality internship search.
by students across India. inconsistency.

3 AICTE Internship Portal [3] https://internship.aicte-india.org All India Council Centralized internship platform for Limited to students enrolled in Education-focused portal with
for Technical engineering/tech students; curated by AICTE-approved institutions; document submission and
Education educational institutes and government interface can be outdated. verification like the proposed
(AICTE) bodies. system.

4 National Career Service https://www.ncs.gov.in Ministry of Labour Provides job/internship listings, career Too broad; lacks targeted Offers government internships, user
(NCS) [4] & Employment, counselling, skill development features specifically for registration, and career tools
Government of programs, and access to government students/interns. relevant to your use-case.
India schemes.

3
1.5. Problem Definition:
• The offline application and approval are time-consuming and prone to delays,
and there are no notifications regarding the updates and deadlines of the
internship project neither application status.
• There is lack of centralized repository to store the projects that have been
developed during the internship by the interns.
• The manual process of certification is time consuming, requires meeting
various authorities for approval.

1.6. Proposed Solution Strategy

• To digitize the offline internship application process by transitioning to online
process of internship application through web-based platform along with email-
based notifications for important updates and events.
• Develop a centralized repository feature for interns to store the projects, mutually
shared between intern and the instructor.
• Develop an automated certificate generation service which accepts instructor’s
remarks as parameter.

1.7. Software Requirement Specifications (SRS)

SRS document or Software Requirement document provides a technical
specification for the requirements of the software. The aim of software requirements
definition becomes that of completely and consistently specifying the technical
requirements for the software, accurately and without being vague.

1.7.1. Functional Requirements

R1: Registration process:
Description: This requires the user to provide his/her details such as, email,
username, password, phone number to register with the system.
Input: username, password, email and phone number.
Output: OTP generated and redirects user to the OTP verification page.

1
Processing: The passed attributes are stored in temporary database table
until the OTP is verified.

R2: OTP verification process:

Description: This requires the user to provide the OTP received in the
registered email address.
Input: 6-digit OTP received in the email address.
Output: Redirected to login page after successful validation and the user
details gets persisted into the database.
Processing: The entered OTP is validated against the OTP stored in the
database for the corresponding email address.

R3: Internship application submission process:

Description: This requires the user to apply for the available internships in
the system.
Input: User details with the attributes such as, full name, college name,
address, college location, branch of study.
Output: Popup that notifies the user about the application submission.
Processing: User details persisted in the internship-application database.

R4: Internship application tracking process:

Description: This requires the user to select one application from the
applications set for which the internship application must been submitted.
Input: User email.
Output: Application status of the internship in which the student has
applied.
Processing: User email is checked against the application database and the
matched data is displayed.

R5: Internship status tracking process:

Description: This requires the user to select the active internship he/she has
been working on.
Input: User email, internship id.
Output: Details of the internship
2
Processing: User email and internship id is checked against the database
and according to the internship state the internship details, the data for the
corresponding user is displayed.

R6: Project submission process:

Description: This requires the user to input the project files in .zip, .gzip
and .rar format.
Input: User email, project id, internship id and project file.
Output: Successful operation notifies the user.
Processing: Project attributes are saved in the database and project file is
saved in the file system with predefined folder patterns.

R7: Certification generation process:

Description: This requires the user to request for the certificate against the
internship, and project he/she has performed.
Input: User email, internship id, project ids.
Output: Certificate available to download in PDF format with unique
UUID which can be used later for verification.
Processing: Project and Internship attributes are checked against the
database and if all the projects associated with an internship are marked as
complete then the certificate will be available to download.

R8: Instructor creation process:

Description: This requires the user having role as ‘ROLE_ADMIN’ to
create a new user with the role as ‘ROLE_INSTRCTOR’.
Input: User email, username, department and contact details.
Output: Notifies the user.
Processing: The user details is checked against the database and if the user
doesn’t exist then a new user is created with the given input parameters.

R9: Department creation process:

Description: This requires the user having role as ‘ROLE_ADMIN’ to
create a new department.
Input: Department Name.
3
 Output: Notifies the user.
Processing: The department name is checked against the database and if the
department doesn’t exist then a new department is created with the provided
department name.

R10: Update user details process:

Description: This requires the user to update the details of the currently
authenticated user.
Input: User details such as username, contact information, educational
details, resume, profile picture etc.
Output: Notifies the user by updating the page with the updated
information.
Processing: The user details is checked against the database and if the user
exists then the user details are updated according to the input values.
R11: Certificate validation process:
Description: This requires the user to provide the certificate UUID included
in the certificate.
Input: Certificate ID.
Output: Displays the legitimacy of the certificate.
Processing: The certificate id is checked against the database and if the
certificate id matches, the certificate is shown as valid else invalid.

1.7.2. Non-Functional Requirements

• Performance requirements: The system must be able to handle at least 150
concurrent requests.
• Security Requirements:
o Use https for secure communication.
o Use JWT based authentication for secure subsequent.
o Ensure role-based-access-control to prevent unauthorized access of
resources.

4
2. Project Planning
2.1. Hardware and Software Requirements
2.1.1. Hardware Requirements
Table No 2.1.1.1: Hardware Requirements
Components Development Production
Processor Intel i5 or AMD Ryzen 5 Intel Xeon / AMD
EPYC
RAM 8 GB (min), 16 GB 16 GB (min), 32 GB
(recommended) (recommended)
Storage 256–512 GB SSD 500 GB SSD (NVMe
preferred),

2.1.2. Software Requirements

Table No 2.1.2.1: Software Requirements
Components Development Production
Operating System Fedora 41, Windows 11 Ubuntu Server 20.04
LTS / RHEL
IDE / Code Editor Visual Studio Code, IntelliJ Not Applicable
IDEA
Java Development Kit OpenJDK 17 OpenJDK 17
Package Managers NPM, Maven NPM, Maven
Version Control Git with GitHub Git
Database Tools MySQL Server, JetBrains MySQL Server,
DataGrip MySQL CLI
Web Server Tomcat: Spring Boot NGINX or Apache
embedded, Angular dev
server)

5
2.2. Team Structure

Figure No: 2.2.1. Team Structure

2.3. SDLC
2.3.1. Agile Methodology: As already pointed out, though the iterative waterfall
model has been very popular during the 1970s and 1980s, developers face
several problems while using it on present day software projects. The main
difficulties included handling change requests from customers during product
development, and the unreasonably high cost and time that is incurred while
developing customised applications. Capers Jones carried out research
involving 800 real-life software development projects and concluded that on the
average 40 percent of the requirements arrived after the development has
already begun. In this context, over the last two decade or so, several life cycle
models have been proposed to overcome the important shortcomings of the
waterfall-based models that become conspicuo.us when used in modern
software development projects [5]

6
 Agile Methods: Extreme Programming, Scrum, Crystal Methods, Feature
Driven Development, Lean Development, and Dynamic Systems Development
Methodology. [6]

Fig 2.3.1.1. Illustration of Agile SDLC Model. [8]

2.3.2. Scrum Framework: Scrum was developed by Jeff Sutherland in 1993, and
its goal is to become a development and management methodology that follows
the principles of Agile methodology. Scrum is an additional responsive
framework of software development for software projects and manage products
or application development. The focus is on "strategy, a flexible holistic
product development where the development team worked as a unit to achieve
common goals" as opposed to "traditional approaches, a sequence". Scrum has a
complex process in which many factors that affect the result. [7]

Fig 2.3.2.1. Illustration of Scrum process workflow. [7]

7
 2.4. Gantt chart
Table No: 2.4.1. Gantt chart
Activity 14/01/2025- 26/01/2025- 16/02/2025- 15/03/2025- 13/04/2025- 27/04/2025-
25/01/2025 15/02/2025 15/03/2025 12/04/2025 26/04/2025 12/05/2025

Initial Setup and

Gathering

Design

Implementation

Testing and
Integration

Deployment

Documentation

Target
Achieved

8
3. Design strategy for the solution.
3.1. Architecture Diagram

Client Machine Angular Spring Boot

Front-end Server Back-end Server

MySQL

Database Server

Fig 3.1.1. Architecture Diagram

9
3.2. Use Case Diagram:

Fig 3.2. 1 Use Case Diagram

10
3.3. Class Diagram:

Fig 3.3. 1 Class Diagram

11
3.4. Sequence Diagram:

Fig 3.4. 1 Sequence Diagram

12
3.5. Entity Relationship Diagram

Fig 3.5. 1 Entity Relationship Diagram

13
4. Implementation Details
4.1. Pseudo Codes:
Following are the pseudo codes of some of the important algorithms used in developing the
application:
4.1.1. Pseudo Code for User Registration
Begin
FUNCTION registerUser(RegistrationRequest user)
STORE user in temporaryDatabase
generatedOTP ← generateRandomOTP()
SEND generatedOTP to user.email
RETURN HTTP 201 (ResponseEntity(“User data stored), HTTPStatus.OK)
END FUNCTION
End
4.1.2. Pseudo Code for Validating OTP and User creation
Begin
FUNCTION validateOTP(String email, String userOTP)
storedOTP ← FETCH OTP FROM temporaryDatabase WHERE email =
user
IF storedOTP == userOTP THEN
userData ← FETCH user FROM temporaryDatabase WHERE email =
user
STORE userData in permanentDatabase
DELETE userData FROM temporaryDatabase
RETURN HTTP 200 (ResponseEntity(“User successfully registered”,
HTTPStatus.OK))
ELSE
RETURN HTTP 400 (ResponseEntity(“Invalid OTP”,
HTTPStatus.BAD_REQUEST))
END IF
END FUNCTION
End

14
4.1.3. Pseudo Code for fetching available Internships
Begin
FUNCTION getAvailableInternships(InternshipFilters filters)
internships ← FETCH FROM internshipTable WHERE filters MATCH
RETURN HTTP 200 (ResponseEntity(internships, HTTPStatus.OK))
END FUNCTION
End
4.1.4. Pseudo Code for applying for Internship
Begin
FUNCTION applyForInternship(String email, Long internshipId)
applicationStatus ← STORE (email, internshipId) IN applicationsTable
IF applicationStatus SUCCESS THEN
RETURN HTTP 200 (ResponseEntity(“Application submitted”,
HTTPStatus.OK))
ELSE
RETURN HTTP 500 (ResponseEntity(“Failed to apply”,
HTTPStatus.INTERNAL_SERVER_ERROR))
END IF
END FUNCTION
End
4.1.5. Pseudo code for fetching the assigned Project
Begin
FUNCTION getAssignedProject(String email, Long internshipId)
projectDetails ← FETCH FROM projectTable WHERE email = user AND
internshipId = internshipId
IF projectDetails EXISTS THEN
RETURN HTTP 200 (ResponseEntity(projectDetails, HTTPStatus.OK))
ELSE
RETURN HTTP 404 (ResponseEntity(“No assigned project found”,
HTTPStatus.NOT_FOUND))
END IF
END FUNCTION
End

15
4.1.6. Pseudo code for uploading Project files
Begin
FUNCTION uploadProjectFile(String email, Long internshipId, File file)
filePath ← STORE file IN localFileSystem WITH predefinedFolderPattern

IF filePath SUCCESS THEN

fileMetadata ← CREATE new ProjectFileMetadata(
email = user,
internshipId = internshipId,
fileName = file.originalName,
filePath = filePath,
uploadTimestamp = CURRENT_TIMESTAMP
)
STORE fileMetadata IN repository (database)

RETURN HTTP 201 (ResponseEntity(“File uploaded successfully”,

HTTPStatus.CREATED))
ELSE
RETURN HTTP 500 (ResponseEntity(“File upload failed”,
HTTPStatus.INTERNAL_SERVER_ERROR))
END IF
END FUNCTION
End
4.1.7. Pseudo code for request for certificate
Begin
FUNCTION requestCertificate(String email, Long internshipId)
completionStatus ← CHECK IF user COMPLETED internship
instructorApproval ← CHECK IF instructor APPROVED
IF completionStatus SUCCESS AND instructorApproval SUCCESS
THEN
certificate ← GENERATE certificate FOR user
RETURN HTTP 201 (ResponseEntity(“Certificate generated”,
HTTPStatus.OK))
ELSE
16
 RETURN HTTP 403 (ResponseEntity(“Completion pending or approval
missing”, HTTPStatus.FORBIDDEN))
END IF
END FUNCTION
End
4.2. Algorithms Implemented
• HMAC-SHA256 for JWT token generation
o Utilized HMAC-SHA256(Hash based encoding) for securely
encrypting the user’s data.
• JWT structure
o Header: Contains metadata about the token, including the
signing algorithm (HMAC-SHA256).
o Payload: Holds the claims, including user information and
roles.
o Signature: Generated by combining the encoded header,
payload, and a secret key using HMAC-SHA256 to verify the
token's validity.
• Blowfish encryption algorithm
o Utilized Bcrypt algorithm for hashing the user password with
12 iteration encryptions.

17
5. Results
5.1. Snapshots

Fig 5.1.1 Landing Page for Desktop

Description: This is the landing page of the Internship Portal for Desktop. At the top, there's a
navigation bar that helps users easily move between different sections of the platform.

Fig 5.1.2 Registration Page

Description: This is the registration page of the Internship Portal. It allows the user to register to the
system using the fields asked in the form.

18
 Fig 5.1.3 OTP Verification Page

Description: This is the OTP validation page of the Internship Portal. It allows the user to validate
the email used for registration.

Fig 5.1.4 Login Page

Description: This is the login page of the Internship Portal. It allows the user to login to the system
using their credentials.

19
 Fig 5.1.5 Student Home Page for Desktop

Description: This is the home page of the Internship Portal for Students. It allows the students to
view the active internships and apply filters according to the available departments.

Fig 5.1.6 View Submitted Applications for Desktop

Description: This is the view submitted applications page of the Internship Portal for Students. It
allows the students to view the submitted applications and apply filters according to the available
status.

20
 Fig 5.1.7 View Selected Internships for Desktop

This is the view selected internships page of the Internship Portal for Students. It allows the students
to view the submitted applications and apply filters according to the available status.

Fig 5.1.8 View Selected Internships for Desktop after Project Allocation for Desktop

Description: This is the view selected internships page of the Internship Portal for Students after the
allocation of Project. It allows the students to view the allocated projects details by clicking on the
project name.

21
 Fig 5.1.9 View Project Details for Desktop

Description: This is the view project details page of the Internship Portal. It allows the students to
view the allocated projects, download project description and upload project data.

Fig 5.1.10 Upload Project for Desktop

Description: This is the view project details page of the Internship Portal. It allows the students to
view the allocated projects, download project description and upload project data. To upload the
project student must select a file with .zip, or .rar extension and after selecting the file user must
click the upload project button to upload the project into the central repository.

22
 Fig 5.1.11 Download Certificate after Project Completion for Desktop

Description: This is the view project details page of the Internship Portal for. It allows the students
to download the certificate for an internship which has been marked as complete by the instructor.
Only after the internship is marked as complete, the download button will appear.

Fig 5.1.12 Downloaded Certificate Sample

Description: This is downloaded certificate. It contains the necessary information regarding the
student, instructor, internship name and internship duration.

23
 Fig 5.1.13 Landing Page for Mobile

Description: This is the landing page of the Internship Portal for Mobile. At the top, there's a
navigation menu that helps users easily move between different sections of the platform.

24
 Fig 5.1.14 Student Home Page for Mobile

Description: This is the home page of the Internship Portal for Students for Mobile. It allows the
students to view the active internships and apply filters according to the available departments.

25
 Fig 5.1.15 View Submitted Applications for Mobile

Description: This is the view submitted applications page of the Internship Portal for Students for
Mobile. It allows the students to view the submitted applications and apply filters according to the
available status.

26
 Fig 5.1.16 View Selected Internships for Mobile

Description: This is the view selected internships page of the Internship Portal for Students for
Mobile. It allows the students to view the submitted applications and apply filters according to the
available status.

27
 Fig 5.1.17 View Selected Internships for Desktop after Project Allocation for Mobile

Description: This is the view selected internships page of the Internship Portal for Students after the
allocation of Project for Mobile. It allows the students to view the allocated projects details by
clicking on the project name.

28
 Fig 5.1.18 View Project Details for Mobile

Description: This is the view project details page of the Internship Portal for Mobile. It allows the
students to view the allocated projects, download project description and upload project data.

29
 Fig 5.1.19 Upload Project for Mobile

Description: This is the view project details page of the Internship Portal for Mobile. It allows the
students to view the allocated projects, download project description and upload project data. To
upload the project student must select a file with .zip, or .rar extension and after selecting the file
user must click the upload project button to upload the project into the central repository.

30
 Fig 5.1.20 Update Student Profile

Description: This is the update profile page of Internship Portal for Students. It allows the students
to update their personal information in the system which includes name, education, skills, profile
picture, resume etc.

31
 Fig 5.1.21 Add New Department for Admin

Description: This is the home page for the admin which displays the total uses, total instructors and
departments present within the system. It allows the admin to add a new department using the above
form which accepts a single parameter which is department name.

Fig 5.1.22 Add New Instructor for Admin

Description: This is the home page for the admin which displays the total uses, total instructors and
departments present within the system. It allows the admin to add a new instructor using the above
form which accepts an instructor name, email, contact information, and department name from the
list of the existing departments.

32
 Fig 5.1.23 Update Profile for Admin

Description: This is the update profile page of Internship Portal for Admin. It allows the admin to
update their personal information in the system which includes name, email address and phone
number.

Fig 5.1.24 Forget Password for All Users

Description: This is the forget password page of Internship Portal for all categories of Users. It
allows the users to find the account associated with a particular email address. If the account exists
then only the Claim Account button appears, upon clicking the button an OTP is sent to the given
email address.

33
 Fig 5.1.25 Account Claim using OTP for All Users

Description: This is the OTP validation for forget password page of Internship Portal for all
categories of Users. The OTP input accepts a 6-digit numeric OTP and validates it against the OTP
stored in the database associated with the user email.

Fig 5.1.26 Password Reset after Claiming account using OTP for All Users

Description: This is the password reset for forget password page of Internship Portal for all
categories of Users. The OTP entered by the user is validated against the OTP stored for the user
email. If the OTP matches, then only the user is prompted to enter the new password for the account.
Upon clicking the Reset button, the password is changed for the account associated with the email
address.

34
6. Summary and Conclusion
6.1. Progress summary:
• User registration and Login: Successfully implemented the user registration and
login process, which includes email verification using OTP.
• Fetching internships: Completed the successful fetching of internships having
status as active.
• Applying for internship: Successfully implemented the internship application
feature, enabling students to apply for internships they have not previously
applied for.
• Fetching selected internships: Successfully implemented fetching the internships
where the student has been selected with the internships details and assigned
project.
• Project upload: Successfully implemented one time upload of project associated
with a particular internship on central repository.
• Certificate claim: Successfully implemented the functionality to claim for the
certificate of an internship where all the projects are uploaded, and the project is
marked as complete by Instructor.
• Update profile: Successfully implemented the functionality to update user details.
• Admin panel: Successfully developed admin panel to fetch all users, students and
instructors. Completed the functionality to add new departments and users.

6.2. Conclusion
In conclusion, the student/admin modules of Internship portal for Government of
Sikkim tends to migrate the current offline process of internship application, managing
internship reports and datum, storing the projects on a dedicated centralized repository and
issuing of certificates of completion that allows the students doing internship under
Department of Information Technology, Government of Sikkim and the administrator of the
system of Department of Information Technology, Government of Sikkim to efficiently
monitor and manage the internship cycle. It also mitigates the physical involvement of
students in the process of the internship by providing a web-based solution to perform the
operations within the application.

35
References

[1] M. o. E. A. Affairs, “Internship Portal,” Ministry of External Affairs, Government of India, 2024.
[Online]. Available: https://internship.mea.gov.in/internship. [Accessed 14 April 2025].

[2] I. P. Ltd., “Internshala Student Dashboard,” Internshala Pvt. Ltd., 2024. [Online]. Available:
https://internshala.com/student/dashboard. [Accessed 14 April 2025].

[3] A. I. C. f. T. E. (AICTE), “AICTE Internship Portal,” AICTE, 2023. [Online]. Available:

https://internship.aicte-india.org. [Accessed 14 April 2025].

[4] M. o. L. &. Employment, “ National Career Service (NCS),” Government of India, 2024. [Online].
Available: https://www.ncs.gov.in. [Accessed 14 April 2025].

[5] R. Mall, in Fundamentals of Software Engineering, PHI Learning Private Limited, 2014, pp. 105-
114.

[6] M. L. P. C. David Cohen, in Agile Software Development:A DACS State-of-the-Art Report, Data
and Analysis Center for Software, 2003, pp. 11-15.

[7] P. A. G. Permana, “Scrum Method Implementation in a Software,” International Journal of

Advanced Computer Science and Applications (IJACSA), vol. 6, no. 9, pp. 198-199, 2015.

[8] E. Altynpara, “What Is Agile Model in SDLC: The Guide on Software Development
Methodology,” Cleveroad, 18 January 2024. [Online]. Available:
https://www.cleveroad.com/blog/agile-sdlc/. [Accessed 22 January 2025].

[9] P. Software, “Spring Boot Reference Documentation,” Spring.io, 2024. [Online]. Available:
https://docs.spring.io/spring-boot/. [Accessed 14 April 2025].

[10] A. Team, “Angular Docs,” angular.io, 2024. [Online]. Available: https://v14.angular.io/docs.

[Accessed 25 April 2025].

[11] F. S. Foundation, “Bash Reference Manual,” GNU.org, 2022. [Online]. Available:

https://www.gnu.org/software/bash/manual/bash.html. [Accessed 14 April 2025].

[12] O. Corporation, “MySQL 8.0 Reference Manual,” dev.mysql.com, 2023. [Online]. Available:
https://dev.mysql.com/doc/refman/8.0/en/. [Accessed 14 April 2025].

36