0% found this document useful (0 votes)
14 views43 pages

Smit final report

The internship report details Smit Goyani's experience as a Full Stack Developer intern at Kartum Infotech, where he developed a fully functional Interview Web Application using modern technologies. The report highlights the skills gained in both front-end and back-end development, including user authentication and data management. It also acknowledges the guidance received from mentors and the support from faculty during the internship period.

Uploaded by

fenildesai3675
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
14 views43 pages

Smit final report

The internship report details Smit Goyani's experience as a Full Stack Developer intern at Kartum Infotech, where he developed a fully functional Interview Web Application using modern technologies. The report highlights the skills gained in both front-end and back-end development, including user authentication and data management. It also acknowledges the guidance received from mentors and the support from faculty during the internship period.

Uploaded by

fenildesai3675
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 43

INTERNSHIP ON FULL STACK DEVELOPER

INTERNSHIP REPORT

Submitted by

Smit Tulshibhai Goyani

2107020701026

In partial fulfillment for the award of the degree of

BACHELOR OF TECHNOLOGY

in

Information Technology

Bhagwan Arihant Institute of Technology, Surat

Bhagwan Mahavir University, Surat

[April,2025-26]
Bhagwan Arihant Institute of Technology
BMEF Campus, VIP road Bharthana Vesu ,Surat,
Gujarat 395007 India

CERTIFICATE

This is to certify that the internship report submitted with the internship

entitled Internship on Full Stack Developer has been carried out by Mr.

Smit Goyani under my guidance in partial fulfilment for the degree of

Bachelor of Engineering in Information Technology , 8th Semester of

Bhagwan Mahavir University, Surat during the academic year 2025–26.

Mr. Nikul Vaghani Prof. RaukiYadav

External Guide Head of the Department

Prof. Ashka bhalodiya

Internal Guide External Examiner


Bhagwan Arihant Institute of Technology
BMEF Campus, VIP road Bharthana Vesu, Surat,
Gujarat 395007 India

DECLARATION

We have declare that the Internship report submitted along with the Internship

entitled Internship on Full Stack Developer submitted in partial fulfillment

for the degree of Bachelor of Engineering in Information Technology to

Bhagwan Mahavir University, Surat is a bonafide record of original internship

work carried out by me at Bhagwan Arihant Institute of Technology / Kartum

Infotech. under the supervision of Prof. / Mr. Nikul Vaghani and that no part

of this report has been directly copied from any students report or taken from

any other source, without providing due reference.

Name of the Student Signature of Student

Smit Goyani
ACKNOWLEDGMENT

I express my deep sense of gratitude to Mr. Bhavesh Hirapara and Mr. Nikul Vaghani for

their kind cooperation and valuable guidance throughout the process of my work. I would

also like to express my gratitude to the officials and another staff member of Nobletex Ind.

Ltd. who rendered their help during the period of my internship.

The thanks to Prof. Ashka Bhalodiya and Head of Department Prof. Rauki Yadav, with

other faculty members of the Computer Engineering department, Bhagwan Arihant

Institute of Technology, who always helped me by giving fruitful suggestions, support, and

encouragement which not only helped me in preparing this work but also in having a better

insight in this field.

Lastly, I also extend my thanks and appreciation to my family members, my friends, and

my classmates who have played a very important role in helping and strengthening me.

Smit Goyani

2107020701026

ii
ABSTRACT

The scope of this document is to identify and describe the development process, the project
completed, and the experience gained as a Full Stack Developer intern. An internship in Full Stack
Development offers the opportunity to work in a real-world software environment, learn from
experienced professionals, and build complete web applications from front-end to back-end. The
project developed during this internship was a fully functional Interview Web Application,
incorporating modern web technologies such as HTML, CSS, JavaScript, React, Node.js, Express,
and MongoDB. This application includes features like user authentication, role-based dashboards,
scheduling, and data management. The internship significantly enhanced my skills in designing,
developing, and deploying full stack solutions, and provided a solid foundation for future growth
in the software development industry.

ii
List of Figures

Fig1.1 Organization Chart.................................................................................................... 2


Fig2.1 Schematic layout of manufacturing .......................................................................... 4
Fig5.1 Class Diagram ......................................................................................................... 21
Fig6.1 Home Page .............................................................................................................. 23
Fig6.2 Admin Login........................................................................................................... 23
Fig6.3 Company Login ...................................................................................................... 24
Fig6.4 Interview Login ...................................................................................................... 24
Fig6.5 Candidate Login ..................................................................................................... 25
Fig8.1 Work Desk .............................................................................................................. 28
Fig8.2 Working .................................................................................................................. 29
Fig8.3 Project Discussion................................................................................................... 29

iii
List of Tables
Table3.1 1stWeek Work Plan ............................................................................................. 11
Table3.2 2nd Week WorkPlan ............................................................................................ 11
Table3.3 3rd Week Work Plan ............................................................................................ 12
Table3.4 4th WeekWork Plan ............................................................................................. 12
Table3.5 5th WeekWork Plan ............................................................................................. 13
Table3.6 6th WeekWork Plan ............................................................................................. 13
Table3.7 7th WeekWork Plan ............................................................................................. 14
Table3.8 8th WeekWork Plan ............................................................................................. 14
Table3.9 9th WeekWork Plan ............................................................................................. 15
Table3.10 10th Week WorkPlan ......................................................................................... 15
Table3.11 11th Week WorkPlan ......................................................................................... 16
Table3.12 12th Week WorkPlan ......................................................................................... 16
Table3.13 13th Week WorkPlan ......................................................................................... 17
Table3.14 14th Week WorkPlan ......................................................................................... 17

iv
Abbreviations

HTML Hyper Text Markup Language


CSS Cascading Style Sheets
JS JavaScript
JSX JavaScript XML
DOM Document Object Model
API Application Programming Interface
CRUD Create, Read, Update, Delete
DB Database
JWT JSON Web Token
UI User Interface
UX User Experience
NPM Node Package Manager
JSON JavaScript Object Notation
HTTPS Hyper Text Transfer Protocol Secure
HTTP Hyper Text Transfer Protocol

v
Table of Contents

ACKNOWLEDGEMENT..................................................................................................... I
ABSTRACT ........................................................................................................................ II
LIST OF FIGURES............................................................................................................ III
LIST OF TABLES .............................................................................................................. V
ABBREVIATION .............................................................................................................. VI
LIST OF CONTENTS ..................................................................................................... VII
CHAPTER1 OVERVIEWOF THE COMPANY............................................................ 1
1.1 HISTORY ................................................................................................................... 1
1.2 DIFFERENT PRODUCTS ......................................................................................... 1
1.3 ORGANIZATION CHART ....................................................................................... 2
CHAPTER2 OVERVIEWOF DIFFERENT PLANT .................................................... 3
2.1 WORKBEING CARRIED OUT INEACH DEPARTMENT ................................... 3
2.2 SPECIFICATION OF EQUIPMENTUSED INDIFFERENT DEPARTMENT ....... 4
2.3 SCHEMATIC LAYOUT TO SHOW SEQUENCE OF OPERATION FOR
MANUFACTURINGEND PRODUCT ........................................................................... 4
2.4 DESCRIPTION OF EACH STAGE OF PRODUCTION ......................................... 5
CHAPTER 3 INTRODUCTION TO INTERNSHIP AND INTERNSHIP
MANAGEMENT................................................................................................................ 7
3.1 INTERNSHIP SUMMARY ....................................................................................... 7
3.2 PURPOSE................................................................................................................... 7
3.3 OBJECTIVE ............................................................................................................... 7
3.4 SCOPE........................................................................................................................ 8
3.5 TECHNOLOGY AND LITERATURE REVIEW ..................................................... 8
3.6 INTERNSHIPPLANNING ........................................................................................ 10
3.6.1 InternshipEffortsandTime .................................................................................... 10
3.6.2 RoleandResponsibilities ....................................................................................... 10
3.6.3 GropeDependencies ............................................................................................. 10
3.6.4 Plan ofWork ....................................................................................................... 11
CHAPTER4 SYSTEMANALYSIS................................................................................. 18
4.1 STUDY OF CURRENT SYSTEM .......................................................................... 18
4.2 PROBLEM AND WEAKNESS OF CURRENT SYSTEM .................................... 18
4.3 REQUIREMENTS OF NEW SYSTEM .................................................................. 18

vi
4.4 SYSTEM FEASIBILITY ......................................................................................... 18
4.4.1 Does the system contribute to the overall objectives of the organization? ........ 18
4.4.2 Can the system be implemented using the current technology and within the
given cost and schedule constraints? .......................................................................... 19
4.4.3 Can the system be integrated with other systems which are already in place?..18
4.5 ACTIVITYINNEW SYSTEM ................................................................................. 19
4.6 MAINMODULE OFNEW SYSTEM ...................................................................... 19
4.7 SELECTIONOFHARDWARE/SOFTWAREAND JUSTIFICATION ................... 20
CHAPTER5 SYSTEMDESIGN ..................................................................................... 21
5.1 UML DIAGRAMS ................................................................................................... 21
5.1.1 Class Diagrams .................................................................................................. 21
CHAPTER6 IMPLEMENTATION ............................................................................... 22
6.1 IMPLEMENTATIONPLATFORM/ ENVIRONMENT .......................................... 22
6.2 TECHNOLOGY ....................................................................................................... 22
6.3 OUTCOMES ............................................................................................................ 23
6.4 RESULTANALYSIS ............................................................................................... 25
CHAPTER7INSIGHTSANDANALYSIS ...................................................................... 26
7.1 INSHIGHTSAND ANALYSIS ................................................................................ 26
CHAPTER8CONCLUSIONAND DISCUSSION ......................................................... 28
8.1 OVERALLANALYSIS OF INTERNSHIP ............................................................. 28
8.2 PHOTOGRAPH AND DATE OF SURPRISEVISIT BY INSTITUTE MENTOR
........................................................................................................................................ 28
8.3 DATES OF CONTINUOUS EVALUATION ......................................................... 30
8.4 PROBLEM ENCOUNTERED AND POSSIBLESOLUTION ................................ 30
8.5 SUMMARY OF INTERNSHIP ............................................................................... 30
8.6 LIMITATION AND FUTURE ENHANCEMENT ................................................. 31
REFERENCES ................................................................................................................. 32

vii
1010206801

CHAPTER 1 OVERVIEW OF THE COMPANY

1.1 HISTORY

• CompanyName: Kartum Infotech.

• Expertise:Web development, App Development, Software Testing, Gaming, SEO,


Digital Marketing Designing

• Website: https://kartuminfotech.com/

• Address: 230, Apple square, yogi chowk, nana varachha, surat

• We are a leading IT firm that offers professional Web Design and Mobile
Application Development as well as Offshore Business Application Solutions to
clients both, global and domestic. Over the years, Kartum Infotech has evolved into
a one-stop solution for customized, comprehensive, feasible, and affordable web
based solutions for business requirements.

1.2 DIFFERENT PRODUCTS

ProductsofCompany:
• Web Development
• Web Design
• Mobile App Development
• Digital Marketing
• E-Commerce Solutions
• Software Development

Bhagwan Mahavir University 1 BAIT, Surat


1010206801

1.3 ORGANIZATION CHART

• CEO: Bhavesh Hirapra

• Project Manager: Nikul Vaghani

• Development Team: Anuj Kikani,Nigam , Smit goyani

• Marketing Team: Vasu Chovatiya

• Support Team: Staff for customer services

Bhagwan Mahavir University 2 BAIT, Surat


1010206801

CHAPTER 2 OVERVIEW OF DIFFERENT PLANT

2.1 WORK BEING CARRIED OUT IN EACH DEPARTMENT

• Development Department: Responsible for the design, development, and maintenance of


the overall website and application products.
• UI/UX: Focuses on the user interface and user experience design for both the web
and application platforms.
• Coder: Involved in writing and implementing the software code for both web and
application components.
• Project Manager: Oversees the planning, execution, and completion of
development projects for both web and application initiatives.
• Web Department: Specifically responsible for the development and maintenance
of the website.
• App Department: Specifically responsible for the development and maintenance
of the mobile application.
• Overall Focus: Coding, testing, and deploying the software for both platforms.
• Goal: Ensure both the website and application meet user needs and industry
standards.
• Communication: Regular stand-up meetings to discuss progress and address
challenges across all development areas.
• Marketing Department: Engages in promoting the funded accounts, managing customer
relations, and developing marketing strategies to attract potential users.
• Conducts market research to understand user preferences.
• Tailors marketing campaigns accordingly.
• Utilizes social media, email marketing, and online advertising to reach their target
audience.
• Support Department: Provides assistance to users, addressing their queries and concerns
regarding the platform.
• Plays a crucial role in ensuring customer satisfaction and retention.
• Maintains a knowledge base.
• Provides training materials to help users navigate the platform effectively (both
web and app).

Bhagwan Mahavir University 3 BAIT, Surat


1010206801

2.2 SPECIFICATION OF EQUIPMENT USED IN DIFFERENT

DEPARTMENT

• IT Department:
o Personalcomputer, Laptop
o Servers, Internet

2.3 SCHEMATIC LAYOUT TO SHOW SEQUENCE OF OPERATION

FOR MANUFACTURING END PRODUCT

Fig2.1 Schematic layout of manufacturing product

Bhagwan Mahavir University 4 BAIT, Surat


1010206801

2.4 DESCRIPTION OF EACH STAGE OF PRODUCTION

2.4.1 DESCRIPTION OF EACH STAGE OF MANUFACTURING PRODUCT

1. Requirement:The process starts with gathering and analyzing requirements from


stakeholders, clients, or end-users. This step helps in understanding the project scope,
objectives, and functionalities needed in the software.

2. Design:Based on collected requirement, system architecture, UI/UX wireframes, and


database structures are planned. This phase ensures a clear roadmap for development,
reducing errors in later stages.

3. Development:Developers begin coding the software based on the design


specifications. This includes front-end, back-end, and database development,
ensuring all functionalities are implemented correctly

4. Testing:After development, the software undergoes rigorous testing to identify and


fix bugs, performance issues, or security vulnerabilities. This phase ensures the
software is stable and meets quality standards.

5. Deployment:Once the software is tested and proved, it is deployed for end-users.


This may include on servers, distributing to app stored, or launching on client
systems.

6. Review: After deployment, feedback is collected from users and stakeholders to evaluate
performance. Any necessary improvements or updates are planned for future releases,
ensuring continuous software enhancement.

Bhagwan Mahavir University 5 BAIT, Surat


1010206801

2.4.2 DESCRIPTION OF EACH STAGE OF CREATINGVISUALS

1. Identify BusinessProblem:Definewhat problem youwant to solve.

2. Data Collection:Collectthedatarequiredfor analysis.

3. Data Exploration:Exploredatawithvisualexplorationtounderstandwhatisina

dataset.

4. Data Preparation:Datacleaning,calculatedfieldsanddata validation.

5. Data Analysis: Use data analysis techniques to understand, interpret, and

deriveconclusions based on the requirements.

6. Visualization & Reporting: Share Present findings through charts, graph and

dashboardsto effectively communicate insights to stakeholders

Bhagwan Mahavir University 6 BAIT, Surat


1010206801

CHAPTER 3 INTRODUCTION TO INTERNSHIP AND

INTERNSHIP MANAGEMENT

3.1 INTERNSHIP SUMMARY

During my internship with Kartum Infotech, I gained hands-on experience in full


stack web development by working on a real-world Interview Web Application project.
The internship allowed me to practically apply the knowledge acquired in my academic
studies while working with modern technologies like HTML, CSS, JavaScript, React,
Node.js, Express.js, and MongoDB.
I worked across both front-end and back-end development environments, building
responsive user interfaces, implementing authentication systems, creating RESTful APIs,
and managing data storage with MongoDB. The project followed the MVC architecture
and involved features such as user registration, login, role-based dashboards, file uploads,
and scheduling modules.
Throughout the internship, I encountered challenges such as debugging API issues,
handling asynchronous operations, managing state with Redux, and optimizing
performance. Working in a professional environment also exposed me to real-world
collaboration, code versioning through Git, and deployment strategies using cloud
services.

3.2 PURPOSE

The purpose of this internship was to gain industry-relevant experience as a Full


Stack Developer by working on a production-level web application. It provided an
opportunity to build complete applications from front to back, learn professional coding
standards, and understand how software development teams operate in a real-world
environment.

3.3 OBJECTIVE

The objective of this internship was to gain practical experience in full stack web
development by working on a real-world application. It aimed to strengthen my skills in
both front-end and back-end technologies such as React, Node.js, and MongoDB. I also
learned to manage source code using Git and collaborate in a professional development
environment. This internship helped bridge the gap between classroom learning and
industry practices.
Bhagwan Mahavir University 7 BAIT, Surat
1010206801

3.4 SCOPE

Full Stack Development plays a vital role in modern software engineering, offering
a comprehensive skill set that spans user interface design, server-side logic, and
database management. Full stack developers are in high demand across industries due
to their ability to independently manage and develop end-to-end web solutions.

This internship provided exposure to various aspects of web development, including


authentication, session management, API integration, security implementation, and
cloud deployment. As businesses continue to digitize, the need for full stack
professionals is growing rapidly, offering excellent career prospects and growth
potential.

3.5 TECHNOLOGY AND LITERATUREREVIEW

• Technology

HTML/CSS/JavaScript: Core technologies for front-end development, enabling the creation of


structured, styled, and interactive web pages.

React.js: A JavaScript library for building dynamic user interfaces. It allows component-based
architecture and is widely used for creating single-page applications (SPAs).

Node.js: A server-side JavaScript runtime environment used to build scalable network


applications and REST APIs.

Express.js: A minimalist web framework for Node.js used to build backend services and APIs
with routing, middleware, and request handling.

MongoDB: A NoSQL database designed to store and manage data in a flexible JSON-like format.
It enables high scalability and real-time performance.

Git & GitHub: Version control tools used to manage source code, track changes, and collaborate
with team members efficiently.

Vercel & Render: Cloud platforms used to deploy front-end and back-end applications
respectively, enabling public access and real-time testing.

Bhagwan Mahavir University 8 BAIT, Surat


1010206801

• Literature Review

Modern web development emphasizes the integration of both front-end


and back-end technologies to build fully functional web applications. Full stack
development offers the flexibility to handle UI, server logic, and database
management, making developers more versatile and valuable in team settings.

The Interview Web Application project focused on building a user-centric


platform to manage candidate profiles, schedule interviews, and maintain secure
access for admins and users. By incorporating technologies like React and
Express, the application offered responsive user interfaces and robust backend
services. The use of MongoDB provided scalable data handling for resumes, user
sessions, and scheduling logs.

This project highlighted the importance of modular design, secure


authentication, and performance optimization in web applications. It also
underscored the relevance of testing, version control, and deployment strategies
in a real-world development lifecycle.

Bhagwan Mahavir University 9 BAIT, Surat


1010206801

3.6 INTERNSHIP PLANNING

3.6.1 Internship Effort and Time

The total duration of the internship was three months, from 23th December 2024
to 31th Match 2025. The internship followed a five-day work week, with
approximately nine hours of work per day. Each day typically began with receiving a
task or update from the Team Leader. After clarifying the requirements, I would
conduct the necessary research and begin implementing features or debugging issues as
assigned..

3.6.2 Role and Responsibilities

As a Full Stack Developer Intern at Kartum Infotech, my responsibilities


included developing and maintaining features on both the client and server sides of a
web application. On the front end, I worked with HTML, CSS, JavaScript, and React
to create responsive and user-friendly interfaces. On the back end, I used Node.js and
Express.js to build RESTful APIs and manage routing, business logic, and server
operations. I also integrated MongoDB for data storage and implemented
authentication, session management, and role-based access control. Additionally, I was
responsible for writing clean, modular code, debugging errors, collaborating with team
members via Git, and regularly submitting daily and weekly progress reports.

3.6.3 Group Dependencies

Task dependencies played a critical role in organizing the workflow for our web
application development. For instance, backend API development had to be completed
before frontend components could fetch or display data. Similarly, database schemas
had to be finalized before implementing CRUD operations. UI design components
needed to be in place before full integration and routing. Feature modules were built in
a sequence to avoid breaking existing functionality, ensuring smooth collaboration
among developers working on interconnected parts of the system.

Bhagwan Mahavir University 10 BAIT, Surat


1010206801

3.6.4 Planof Work

Table3.11stWeekWork Plan

Date Topic
Introduction to the team and project overview; Setup of
23/12/2024 development environment; Installation of required tools
and software

24/12/2024 Studied project architecture and database structure; Basic


1st Git workflow and repository access; Attended team
WEEK meeting on project roadmap
Started working on frontend UI components using
26/12/2024 React.js; Learned about API integration; Fixed minor UI
bugs

27/12/2024 Implemented authentication module; Worked with


REST APIs and JWT authentication; Debugging and
troubleshooting errors

Table3.22nd Week WorkPlan

Date Topic
Resumed work on frontend UI components; Debugged
30/12/2024 and optimized form validation; Attended sprint planning
meeting

31/12/2024 Integrated additional API endpoints; Improved


2nd responsiveness of UI elements; Conducted code
WEEK refactoring based on feedback
Worked on improving UI responsiveness; Fixed minor
01/01/2025 layout issues in React components; Integrated error
handling for form inputs

Explored Redux for state management; Implemented basic


02/01/2025 Redux store for application state; Debugged API request
issues

Bhagwan Mahavir University 11 BAIT, Surat


1010206801

Table3.33rd Week Work Plan

Date Topic
Started implementing a new feature for the dashboard;
06/01/2025 Worked on database schema improvements; Debugged
deployment issues

07/01/2025 Continued development on dashboard feature;


3rd Collaborated with teammates for UI improvements;
WEEK Resolved performance bottlenecks in API responses
Completed and tested the new dashboard feature; Worked
08/01/2025 on security enhancements for user data; Prepared a report
on the work completed so far

Started working on backend API optimizations; Improved data caching


09/01/2025 authentication bugs

10/01/2025 Worked on implementing role-based access control;


Optimized API response times; Conducted unit testing on
major endpoints

Table3.44th Week Work Plan

Date Topic
Researched and implemented JWT refresh token
13/01/2025 mechanism; Improved session expiration handling;
Debugged and fixed UI state inconsistencies

16/01/2025 Worked on database indexing for improved performance;


4th Refactored API endpoints for scalability; Participated in
WEEK a sprint review meeting
Integrated third-party authentication services; Resolved
17/01/2025 minor UI/UX inconsistencies; Tested API error handling
mechanisms

Bhagwan Mahavir University 12 BAIT, Surat


1010206801
Table3.55th Week Work Plan

Date Topic
Started working on reporting module; Designed
20/01/2025 database schema for reports; Implemented API
endpoints for fetching reports

21/01/2025 Completed backend logic for reporting module;


5th Developed frontend UI for report visualization;
WEEK Debugged and optimized report generation speed
Conducted integration testing for reporting module;
22/01/2025 Fixed identified bugs in report calculations; Prepared
API documentation for the module

23/01/2025 Started working on notifications system; Integrated real-


time push notifications; Optimized database queries for
notifications

24/01/2025 Completed backend logic for notifications; Worked on


frontend UI for displaying alerts; Fixed minor
notification-related bugs

Table3.66th Week Work Plan

Date Topic
Conducted end-to-end testing for notifications;
27/01/2025 Improved UI responsiveness for alerts; Prepared
documentation for notifications system

28/01/2025 Reviewed and finalized the work completed in January; Participated in a m


6th meeting; Planned tasks for the upcoming month
WEEK Started working on file upload functionality;
29/01/2025 Implemented backend API for file storage; Researched
cloud storage integration

30/01/2025 Developed frontend UI for file uploads; Implemented


progress indicators for uploads; Fixed minor bugs in file
validation logic

31/01/2025 Integrated cloud storage API; Conducted testing for file


upload performance; Debugged issues with large file
handling

Bhagwan Mahavir University 13 BAIT, Surat


1010206801

Table3.77th Week Work Plan

Date Topic
Optimized backend for efficient file retrieval; Worked
03/02/2025 on implementing access control for files; Conducted
security testing for uploads

04/02/2025 Finalized file upload module; Performed end-to-end


7th testing; Prepared documentation for the module
WEEK Started working on real-time chat feature; Implemented
05/02/2025 backend socket connections; Designed chat UI
components

06/02/2025 Integrated frontend with WebSocket connections;


Worked on message storage and retrieval; Debugged
latency issues in real-time updates

07/02/2025 Improved chat UI responsiveness; Implemented read


receipts and typing indicators; Conducted user testing
for feedback

Table3.88th Week Work Plan

Date Topic
Worked on chat notifications system; Integrated push
10/02/2025 notifications for new messages; Fixed minor UI
inconsistencies

11/02/2025 Finalized real-time chat feature; Conducted security


8th testing for chat data; Prepared deployment
WEEK documentation
Started implementing role-based permissions; Developed
12/02/2025 admin panel for user management; Integrated permission
checks in backend APIs

13/02/2025 Completed user roles and permissions; Debugged and


fixed access-related issues; Conducted testing for
different user roles

14/02/2025 Started working on performance optimization; Improved


API response times using caching; Reduced database
query load

Bhagwan Mahavir University 14 BAIT, Surat


1010206801

Table3.99th Week Work Plan

Date Topic
Conducted stress testing for backend APIs; Optimized
17/02/2025 frontend rendering performance; Identified and fixed
memory leaks

18/02/2025 Reviewed overall system security; Fixed vulnerabilities


9th found in testing; Prepared security audit report
WEEK Started working on analytics dashboard; Designed UI for
19/02/2025 data visualization; Integrated charting libraries

20/02/2025 Developed backend endpoints for analytics data;


Worked on dynamic filtering of reports; Debugged
inconsistencies in data retrieval

21/02/2025 Improved visual elements in the dashboard; Conducted


usability testing with teammates; Fixed UI issues based
on feedback

Table3.1010th Week Work Plan

Date Topic
Finalized analytics dashboard; Conducted testing and
24/02/2025 performance reviews; Prepared documentation for end-
users

25/02/2025 Reviewed all work done in February; Participated in


10th monthly progress meeting; Planned roadmap for
WEEK upcoming tasks

27/02/2025 Started working on user activity tracking; Implemented backend logic for
Developed UI components for activity logs

28/02/2025 Integrated activity tracking with database; Debugged


and optimized log retrieval queries

Bhagwan Mahavir University 15 BAIT, Surat


1010206801

Table3.1111th Week Work Plan

Date Topic
Conducted security testing on user tracking data;
03/03/2025 Designed analytics reports based on user activity;
Implemented charting features for activity trends

04/03/2025 Fixed UI inconsistencies in the dashboard; Conducted


11th performance testing on activity logs
WEEK Optimized frontend rendering of large datasets; Prepared
05/03/2025 documentation for user activity tracking

Table3.1212th Week Work Plan

Date Topic
Finalized user activity tracking feature; Conducted end-
10/03/2025 to-end testing; Deployed updates to staging environment

11/03/2025 No Work to day

12th
WEEK 12/03/2025 Started working on system notifications improvements; Integrated email n
important alerts

13/03/2025 Fixed minor bugs in the push notification system;


Improved email notification templates

Bhagwan Mahavir University 16 BAIT, Surat


1010206801

Table3.1313th Week Work Plan

Date Topic
Worked on UI improvements for notification center;
18/03/2025 Debugged minor inconsistencies in alert triggers

19/03/2025 Conducted testing for notification delays; Optimized


backend logic for scheduled alerts
Fixed minor authentication bugs in notifications; Worked
13th 20/03/2025 on final improvements for notifications
WEEK

21/03/2025 Conducted security audits for sensitive alerts; Prepared


documentation for the system changes

Table3.1414th Week Work Plan

Date Topic
Worked on final improvements for notifications;
24/01/2025 Conducted security audits for sensitive alerts

25/01/2025 Prepared documentation for the system


changes;Reviewed and finalized the work done
14th in March
WEEK Participated in a progress meeting; Planned remaining
26/01/2025 tasks for project completion

28/01/2025 Conducted a mid-project review

Bhagwan Mahavir University 17 BAIT, Surat


1010206801

CHAPTER 4 SYSTEM ANALYSIS

4.1 STUDY OF CURRENT SYSTEM


The current system for managing funded accounts at Indifunded relies on manual processes.
This approach entails a significant reliance on human intervention for tasks such as account
creation, maintenance, transaction tracking, and reporting. Our analysis reveals that this
manual workflow is inherently susceptible to inefficiencies and potential errors. Furthermore,
the existing infrastructure presents limitations in providing users with timely access to critical
information, particularly regarding their trading activities and real-time market data. This lack
of automation hinders scalability and can negatively impact the overall user experience.

4.2 PROBLEM AND WEAKNESS OF CURRENT SYSTEM

There is no proper tool to analyze the real time data, no tool to determine the
performance of customers across regions, no tool to determine the best customers
considering historical data, no proper tool to determine the best regions, no sufficient
tool to compare Actual vs Target data.

4.3 REQUIREMENTS OF NEW SYSTEM

To address the identified problems and weaknesses, a new, automated system for managing
funded accounts is imperative. This system must seamlessly integrate both web and
application functionalities to provide a unified and efficient user experience. The core
requirements of this new system include.

4.4 SYSTEM FEASIBILITY

4.4.1 Does the system contribute to the overall objective of the organization?

Yes, the system contributes to the overall objective of the organization by providing
valuable insights into sales performance, customer behavior, and market trends. By
leveraging data-driven analysis, it helps in strategic decision-making, improving
efficiency, and optimizing sales processes to drive business growth."

Bhagwan Mahavir University 18 BAIT, Surat


1010206801

4.4.2 Can the system be implemented using the current technology and within the

given cost and schedule constraints?

Yes, ,the new system can be integrated with current marketing and customer
relationship management tools to provide a seamless user experience. This integration
will allow for better tracking of user interactions and more effective marketing strategies.

4.4.3 Can the system be integrated with other system which are already in place?

The system is designed to be compatible with existing systems, allowing seamless


integration for enhanced functionality and data sharing.

4.5 ACTIVITYINNEW SYSTEM

The new system will automate account management and provide real-time updates to users,
allowing them to track their trading activities effectively. Users will be able to access their
account information, view transaction history, and receive notifications about important
updates.

4.6 FEATUREOFNEW SYSTEM

ThemainfeaturesofaProductSalesAnalysisDashboardencompassacomprehensive suite
of tools designed to provide stakeholders with actionable insights into sales
performance.

4.7 MAIN MODULE OF NEW SYSTEM

ThemainmoduleoftheProductSalesAnalysisDashboardusingExcel,PowerBI,and SQL
provides a user-friendly interface for analyzing and interpreting sales data,
empoweringstakeholderstomakedata-drivendecisionsandoptimizesalesstrategies.
Excel is utilized for data preparation and manipulation, allowing users to clean,
transform, and format raw sales data before importing it into Power BI for analysis.
SQL serves as the relational database to store sales data, including product details, sales
transactions, customer information, and other relevant metrics. Power BI functions as
the frontend visualization tool, providing interactive dashboards and reports that enable
users to explore sales performance metrics.

Bhagwan Mahavir University 19 BAIT,Surat


1010206801

4.8 HARDWARE/SOFTWARE SELECTION

Hardware Requirements

• Minimum: Core i5 processor, 8GB RAM


• Hosting Server: Cloud-based (optional for deployment)

Software Stack

• Frontend: HTML, CSS, JavaScript, EJS


• Backend: Node.js, Express.js
• Database: MongoDB
• Security: JWT
• Version Control: GitHub

Development Methodology

• Agile-inspired approach with iterative development


• Weekly reviews and updates
• Testing after each major module implementation

Bhagwan Mahavir University 20 BAIT,Surat


1010206801

CHAPTER 5 SYSTEMDESIGN

5.1 UML DIAGRAMS

5.1.1 Class-Diagram

Fig5.1 Class Diagram

Bhagwan Mahavir University 21 BAIT,Surat


1010206801

CHAPTER 6 IMPLEMENTATION

6.1 IMPLEMENTATION PLATFORM/ENVIRONMENT


Withthefollowingimprovements,theMERN-basedenvironmentwasusedtoconstructthe automobile
selling system:

• Backend:Express.js (Node.js)
• Frontend:HTML/CSSandJavaScriptincorporatedinEJS templates
• Database: MongoDB
• JWT(JSONWebToken) andOTP(email)areusedfor authentication.

6.2 TECHNOLOGY

Frontend:

The frontend of a MERN stack application is developed using React.js, a powerful


JavaScript library used to build interactive and dynamic user interfaces. React allows
developers to create reusable components and efficiently manage the application's state. It
is often combined with Tailwind CSS for styling and responsive design, Axios for making
API requests, and React Router for client-side routing and navigation between different
pages. This combination helps create a smooth and user-friendly experience for users
interacting with the web application.

Backend:

The backend is built using Node.js and Express.js. Node.js is a JavaScript runtime
environment that allows developers to run server-side code using JavaScript, while
Express.js is a lightweight and flexible framework that simplifies the process of building
server-side applications and APIs. Together, they handle business logic, routes,
authentication, and server responses. Additional tools such as JWT (JSON Web Token)
are used for secure user authentication, and Bcrypt.js is used for encrypting passwords,
ensuring that user data is handled securely.

Database:

The database used in the MERN stack is MongoDB, a NoSQL database that stores data in
a flexible, JSON-like format. It allows for easy storage of complex data structures and
scales efficiently with application growth. MongoDB is typically used with Mongoose, an
Object Data Modeling (ODM) library that provides a structured schema and simplifies
interactions between the backend application and the database. This combination ensures
efficient data handling and makes it easier to define models and validate data within the
application.

Bhagwan Mahavir University 22 BAIT,Surat


1010206801

6.3 OUTCOMES

AllfiltersoftheAnalysisdashboardareworking,therearemultiplepagesforSales Analysis
Dashboard.

VISUALS OF WEBSITE https://www.flairx.ai/

Fig6.1HomePage

ADMINT LOGIN https://admin.flairx.ai/

Bhagwan Mahavir University 23 BAIT,Surat


1010206801

COMPANY LOGIN https://company.flairx.ai/

Fig6.3 Company login

INTERVIEW LOGIN https://interview.flairx.ai/

Fig6.4 Interview login

Bhagwan Mahavir University 24 BAIT,Surat


1010206801

CANDIDATE LOGIN https://admin.flairx.ai/

Fig6.4 Candidate login

6.4 RESULTANALYSIS

All the dashboards and visuals were checked at the during the implementation
and at the end oftheimplementation, theresults were positiveand all the filters ofthe
dashboardwereworkingperfectly,butinsomecase,wealsofindsomemissbehavioral of the
charts and that will be fixed in the future increments.

Bhagwan Mahavir University 25 BAIT,Surat


1010206801

CHAPTER 7 INSIGHTS AND ANALYSIS

7.1 INSIGHTSAND ANALYSIS

A Full Stack Developer is a professional who is capable of working on both the

client-side (frontend) and server-side (backend) of web applications. This role encompasses

a wide range of tasks, including UI/UX implementation, server logic, API development,

database management, and deployment processes. The versatility of Full Stack Developers

makes them invaluable to organizations that prioritize agile development and cross-

functional team collaboration.

7.2 Testing

Unit Testing

• Focused on individual components and functions (e.g., backend routes, frontend


components).
• Ensured isolated modules performed as expected.
• Tools used: Jest (for JavaScript/React), Mocha (Node.js environments).

Integration Testing

• Verified the correct interaction between different modules (e.g., API communication
between frontend and backend).
• Helped in identifying database connectivity and API logic issues.

Functional Testing

• Ensured that application features functioned in accordance with specified requirements.


• Validated login/signup functionality, data submission forms, and UI behavior.

End-to-End (E2E) Testing

• Simulated real user scenarios to verify the complete workflow.


• Tools like Cypress and Selenium can be used in real-world projects for this type of testing.

Manual Testing

• Conducted by manually navigating the application to find unexpected behavior or UI


issues.
• Ensured visual consistency, responsiveness, and form validations.

Bhagwan Mahavir University 26 BAIT,Surat


1010206801

API Testing

• Performed using Postman to test RESTful APIs.


• Included methods such as GET, POST, PUT, and DELETE for CRUD operations.

7.3 Challenges Faced in Testing

• Test Coverage: Ensuring comprehensive test coverage for both frontend and backend
logic was time-consuming.
• Dynamic Content Testing: Handling asynchronous data loading in frontend testing
required additional configuration.
• Environment Setup: Setting up mock data and test environments for backend testing
involved initial complexity.

Bhagwan Mahavir University 27 BAIT,Surat


1010206801

CHAPTER 8 CONCLUSION AND DISCUSSION

8.1 OVERALL ANALYSIS OF INTERNSHIP


The car selling system project acted as a thorough educational opportunity that
aided in bridging the knowledge gap between academia and practical software
development. I was able to get useful knowledge about database architecture, dynamic
frontend rendering, and backend development by working with technologies like
Node.js, EJS, and MongoDB. I now have a deeper grasp of web application security
and user experience thanks to the deployment of features like role-based access, OTP
verification, JWT authentication, and order management systems.

Additionally, the project improved my ability to solve problems, particularly


when managing asynchronous activities, handling data relationships, and creating
reusable components. My technical skill set was much enhanced by the practical
experience with a lifelike system simulation, which also better equipped me for future
software development positions. All things considered, this internship assignment was
a fruitful step toward the practical and scalable application of theoretical knowledge..

8.2 PHOTOGRAPH AND DATE OF SURPRISEVISIT BY

INSTITUTE MENTOR

Fig8.1 Work Desk

Bhagwan Mahavir University 28 BAIT,Surat


1010206801

Fig8.2 Working

Fig8.3 Project Discussion

Bhagwan Mahavir University 29 BAIT,Surat


1010206801

8.3 DATES OF CONTINUOUS EVALUATION


Continues Evaluation 1 17th March 2025

8.4 PROBLEMENCOUNTERED AND POSSIBLESOLUTIONS

• PROBLEM ENCOUNTERED:

This individual project, created during the internship's last semester,


effectively illustrates the fundamental characteristics of an automobile selling
platform, including user roles, safe authentication, and fundamental e-commerce
capabilities. Utilizing a full-stack methodology with Node.js, EJS, and MongoDB,
the project showcases realworld expertise in creating scalable online applications.
Important goals including putting in place role-based access, secure registration, and
an interactive order system were successfully accomplished.

• POSSIBLE SOLUTIONS:

• Email OTP setup: Initial issues in sending emails were resolved by configuring secure
SMTP and using environment variables.

• Token-based login: Debugging token expiration and authentication flow required careful
middleware handling.

• MongoDB Data Structuring: Early schema design had redundant data; refactored for
efficient document referencing and performance

8.5 SUMMARY OF INTERNSHIP

• Developed a full-stack car selling platform from scratch.

• Implemented secure JWT login with OTP verification.

• Created modules for catalog, search, cart, checkout, and order management.

• Successfully handled both Buyer and Seller roles with different functionalities.

• Designed and tested all major system components.

Bhagwan Mahavir University 30 BAIT,Surat


1010206801

8.6 LIMITATION AND FUTUREENHANCEMENT

Limitation

• No real-time stock update.


• Basic admin panel, limited to contact form responses.

Future Enhancement

• Integration of AI base work.


• Admin dashboard with analytics and approval and the interview.
• Easy to find Employe.

Bhagwan Mahavir University 31 BAIT,Surat


REFERENCES

1. Node.js Official Documentation – https://nodejs.org/

2. Express.js Guide – https://expressjs.com/

3. MongoDB Manual – https://www.mongodb.com/docs/manual/

4. EJS Templating – https://ejs.co/

5. Nodemailer - https://www.nodemailer.com/

6. JWT (JSON Web Tokens) – https://jwt.io/introduction

7. W3Schools – HTML, CSS, JavaScript – https://www.w3schools.com/

8. GeeksforGeeks – Full Stack Development Articles – https://www.geeksforgeeks.org/

9. GitHub Repositories – For reference on structure and coding patterns

BhagwanMahavirUniversity 32 BAIT,Surat

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy