NEW SUMMIT COLLEGE

(Affiliated to Tribhuvan University)

Project of
System Analysis and Design (CSC 315)
on

“Expense Tracker System”

Bachelor of Science in Computer Science and Information Technology

Institute of Science and Technology

Submitted by: Submitted to:

Name: Rajesh Adhikari, Pranisha Raya Parichaya Adhikari
Semester: V
Program: BSc CSIT

ABSTRACT
This document is presented as a requisite for the partial fulfillment of the requirements for
a Bachelor’s in Science in Computer Science and Information Technology (BSc. CSIT) at
New Summit College. The project titled 'Expense Tracker' constitutes a comprehensive

1
examination of an application designed to facilitate efficient financial management and
tracking for individuals. This software endeavors to provide a robust platform for users to
monitor, analyze, and manage their expenses seamlessly. The primary objective of the
'Expense Tracker' system is to offer users a streamlined and user-friendly interface for
recording and categorizing their expenditures. This application aims to empower
individuals in effectively managing their financial resources, fostering a greater
understanding of their spending patterns, and promoting responsible financial habits.
Through innovative features and a thoughtful design, the 'Expense Tracker' strives to
enhance users' financial literacy and contribute to their overall financial well-being.

Keywords: CSS, HTML, JavaScript, MySQL, MongoDB, NodeJS

2
 ACKNOWLEDGEMENT
It is a great pleasure to have the opportunity to extend our heartfelt gratitude to everyone
who helped us throughout the course of this project. We are profoundly grateful to our
supervisor Mr. Parichaya Adhikari for his expert guidance, continuous encouragement
and ever willingness to spare time from his otherwise busy schedule for the project’s
progress reviews. His continuous inspiration has made us complete this project and
achieve its target. We would also like to express our deepest appreciation to Mr. Chok
Raj Dawadi, Principal of New Summit College, for his constant motivation, support and
for providing us with a suitable working environment. We sincerely acknowledge direct
and indirect help, suggestions and feedback offered by our colleagues before, during and
after the development and implementation of the project. At last, our special thanks go to
all staff members of BSc CSIT department at New Summit College who kindly extended
their hands in making this project work a success.

With respect,

Pranisha Raya

Rajesh Adhikari

3
 Table of Contents
ABSTRACT.........................................................................................................................1

ACKNOWLEDGEMENT....................................................................................................3

CHAPTER 1: INTRODUCTION.........................................................................................6

1.1 BACKGROUND...................................................................................................6

1.2 PROBLEM DEFINITION.....................................................................................6

1.3 OBJECTIVES........................................................................................................7

1.4 SCOPE...................................................................................................................7

1.5 LIMITATIONS......................................................................................................7

CHAPTER 2: SYSTEM ANALYSIS................................................................................10

2.1 INTRODUCTION...............................................................................................10

2.2 FUNCTIONAL REQUIREMENTS....................................................................11

2.3 NON-FUNCTIONAL REQUIRMENTS.............................................................12

2.4 FEASIBILITY STUDY.......................................................................................13

2.5 GANTT CHART.................................................................................................14

2.6 DECISION TABLE.............................................................................................15

CHAPTER 3: SYSTEM SPECIFICATIONS....................................................................17

3.1 SERVER REQUIREMENTS (Minimum Requirements)...................................17

CHAPTER 4- MODULES AND THEIR DESCRIPTION................................................18

4.1 MAJOR MODULES............................................................................................18

4.1.1 Customer Module.............................................................................................18
4.1.2 Driver Module..................................................................................................18
4.1.3 Administration Module....................................................................................18

4.2 SYSTEM FLOW DIAGRAM.............................................................................19

4.2.1 Data Flow Diagram..........................................................................................19
4.2.2 ER Diagram......................................................................................................20
4.2.3 Sequence Diagram...........................................................................................21

CHAPTER 5: SYSTEM TESTING...................................................................................22

4
 5.1 INTRODUCTION...............................................................................................22
5.1.1 Steps Software is tested from two different perspectives................................22

5.2 TESTING METHODOLOGIES..........................................................................22

5.2.1 Unit testing:......................................................................................................22
5.2.2 Integration testing:...........................................................................................22
5.2.3 System testing:.................................................................................................23
5.2.4 Performance testing:.........................................................................................23
5.2.5 User acceptance testing:...................................................................................23
5.2.6 Security testing:................................................................................................23

CHAPTER 6: SYSTEM IMPLEMENTATION................................................................24

6.1 PURPOSE............................................................................................................24

6.2 SYSTEM MAINTENANCE...............................................................................24

CHAPTER 7- CONCLUSION AND FUTURE ENHANCEMENT.................................26

7.1 CONCLUSION....................................................................................................26

7.2 SCOPE FOR FUTURE DEVELOPMENT.........................................................26

REFERENCES...................................................................................................................28

APPENDIX........................................................................................................................28

List of Figures
Figure 1. Use Case Diagram.............................................................................................................11
Figure 2. Gantt Chart.......................................................................................................................14
Figure 3. Context-level Data Flow Diagram.....................................................................................19
Figure 4. Level-0 Data Flow Diagram...............................................................................................20
Figure 5. ER diagram........................................................................................................................20
Figure 6. Sequence diagram............................................................................................................21

5
1.1 BACKGROUND CHAPTER 1: INTRODUCTION

The Expense Tracking System has emerged as a practical solution in managing and
monitoring personal or business finances. With a growing awareness of the importance of
financial responsibility and the need to streamline expense management, individuals and
organizations are turning to these systems for effective tracking and control.

While the concept of expense tracking is not new, the advent of advanced Online Expense
Tracking Systems has revolutionized the way people manage their expenditures. The
Online Expense Tracking Systems have witnessed a surge in popularity due to their user-
friendly interfaces and the ability to effortlessly record and categorize expenses. These
systems provide a convenient and efficient means for individuals and businesses to
monitor their financial health without the complexities associated with traditional
accounting methods.

1.2 PROBLEM DEFINITION

While Online Expense Tracking Systems have gained popularity for their efficiency in
financial management, there are various concerns related to security and privacy that must
be addressed to safeguard the interests of users.

One primary concern revolves around data security and privacy. Online Expense
Tracking Systems involve the input and storage of sensitive financial information. If these
platforms do not implement robust security measures, users could be at risk of
unauthorized access, data breaches or identity theft.

Moreover, the potential misuse of financial data is another area of concern. If the
platforms do not have stringent access controls and authentication processes, there is a
risk that individuals with malicious intent may exploit vulnerabilities in the system,
leading to unauthorized transactions or manipulation of financial records.

Another challenge is related to the integration of third-party financial accounts with the
expense tracking system. If not adequately secured, these integrations may expose users
to potential risks, including unauthorized access to bank accounts or credit card
information.

To address these concerns, it is crucial for Online Expense Tracking Systems to prioritize
data security and privacy. This may involve the implementation of advanced encryption

6
technologies, regular security audits, and compliance with industry standards for
protecting financial information.

Additionally, user should be informed about best practices for securing their accounts,
recognizing potential phishing attempts, and understanding the importance of using strong
passwords.

In conclusion, while Online Expense Tracking Systems offer significant advantages in

financial management, safeguarding user data and privacy is paramount. By incorporating
robust security measures and promoting user awareness, these systems can continue to
provide efficient financial tracking solutions while mitigating potential risks.

1.3 OBJECTIVES
 To optimize User Interface and Experience through continuous improvement with
the help of User Feedback
 To track and keep history of both income and expense

1.4 SCOPE
The scope of this project involves the implementation and evaluation of enhanced
features and usability in Expense Tracking Systems, with a specific focus on addressing
user experience and compliance with financial standards. The project aims to improve the
overall functionality and user satisfaction of Expense Tracking Systems by streamlining
expense entry, ensuring accuracy, and facilitating compliance with financial regulations.

The project will include the following key activities:

 Review of Existing Expense Tracking Systems

 Development of effective expense tracking system
 Implementation of effective expense tracking system
 Development of user experience improvements
 Focus on introducing features that improve the ease of use and efficiency

1.5 LIMITATIONS
 Just, individuals who are familiar with standard utilization of mobiles or PCs can
work this software.
 The expense tracking application may encounter performance issues during
periods of high traffic.

7
 Pre-built expense tracking systems might lack the flexibility required to meet the
specific customization needs of some businesses.
 Implementing an expense tracking system can be a financial challenge,
particularly for small businesses with limited budgets.
 Expense tracking systems must be scalable to accommodate sudden increases in
demand or unexpected fluctuations in expense transactions.

Here are some limitations of an Expense Tracking System:

 Regulatory Constraints:
Expense Tracking Systems are subject to various legal and regulatory
constraints, which may limit the implementation of certain features or
standards related to financial reporting and compliance. Adherence to financial
regulations may impact the system's flexibility and functionality.
 Technology Limitations:
The implementation of new technologies in Expense Tracking Systems may
be constrained by factors such as the availability, affordability, or
compatibility of these technologies. Some advanced features may require
substantial investments or training to be effectively integrated into existing
systems.
 Geographic Limitations:
The implementation of certain expense tracking features may be influenced by
geographic factors, such as variations in tax regulations, currency, or regional
accounting practices. These factors can pose challenges to creating a
universally applicable system.
 Cost Limitations:
The incorporation of advanced features and ongoing system improvements
may require substantial financial investment. This can be a challenge for
smaller businesses or organizations operating in highly competitive markets
where cost considerations are paramount.
 Privacy Concerns:
Certain features aimed at improving expense tracking, such as real-time
monitoring or advanced analytics, may raise privacy concerns among users.
Striking a balance between enhanced tracking capabilities and respecting the

8
 privacy expectations of employees is crucial for successful system
implementation.
 User Behavior:
The effectiveness of Expense Tracking Systems relies on the responsible
behavior of users, including employees submitting expenses. Despite the
implementation of policies and protocols, some users may engage in non-
compliant practices, leading to discrepancies or violations that impact the
accuracy and reliability of expense data.

Addressing these limitations is essential for the successful deployment and sustained
effectiveness of an Expense Tracking System in various business contexts.

9
 CHAPTER 2: SYSTEM ANALYSIS
2.1 INTRODUCTION
System analysis is performed to systematically examine a system or its components with
the aim of identifying and understanding its objectives. This analytical process serves as a
problem-solving technique, contributing to the enhancement of the system's functionality.
The overarching goal is to optimize the performance of individual components, ensuring
seamless collaboration and efficiency to achieve desired outcomes.

The various tasks in the system analysis include the following:

 Requirement gathering:
Gathering requirements from stakeholders, including finance teams,
employees, and administrators, to comprehend their needs and expectations
from the expense tracking system.
 Functional analysis:
Identifying the functions and features necessary for the system to meet the
requirements gathered during the requirement gathering phase. This involves
understanding the core functionalities required for effective expense tracking
and financial management.
 Data analysis:
Analyzing the data required for the system, such as transaction details,
receipts, and financial records. Understanding the types of data needed and
how they interconnect is crucial for designing a comprehensive expense
tracking system.
 Process modeling:
Creating process models to understand how the system works, including how
expenses are submitted, approved, and reimbursed. This involves mapping out
the workflow of expense management within the organization.
 Use case analysis:
Identifying and analyzing the use cases of the system, including scenarios such
as employee submitting an expense, manager approving expenses, and finance
processing reimbursements.

10
  Performance analysis:
Evaluating the performance of the system, including its processing speed,
reliability, and scalability. This ensures that the expense tracking system can
handle varying levels of data input and provide timely and accurate results.
 Security analysis:
Analyzing the security of the system, including its vulnerability to
unauthorized access, data breaches, and other security threats. Implementing
measures to safeguard sensitive financial information is paramount for the
integrity of the expense tracking system.
 User interface analysis:
Evaluating the usability of the system's user interfaces, including web and
mobile applications used by employees and administrators.
 Testing:
Conducting testing to identify and resolve any bugs or issues with the system's
functionality.

2.2 FUNCTIONAL REQUIREMENTS

Functional requirements are a key aspect of system analysis, defining the features and
capabilities required for the system to meet the needs of its users.

Figure 1. Use Case Diagram

11
  Expense Submission and Acceptance:
The system must allow employees to submit expense reports, detailing
incurred expenses. It should facilitate an acceptance feature in order to record
the expense for tracking system.
 History of Expense:
The system must allow users to review the whole history of expense for the
purpose of tracking. It should provide the summary of every entered expense
so that users can track their financial health.
 Income Submission:
The system must offer user with feature to submit income so that the user can
compare the income and expense in order to understand their financial
situation in more detailed way.
 Customer Support:
The system must offer customer support features, allowing users to report any
issues related to expense submissions, reimbursements, or system
functionality. Providing a reliable support channel enhances user experience
and resolves concerns promptly.
 Real-time tracking and monitoring:
The system must monitor the entered data in order to categorize if the data
input is income or expense so that the tracking of expense can be done in real-
time providing a useful platform for user to track their expense.

2.3 NON-FUNCTIONAL REQUIRMENTS

For an Expense Tracking System, the following quality requirements stipulate how
effectively the web application fulfills its intended purpose:

 Performance:
The system must efficiently handle a large volume of expense submissions,
approvals, and payment transactions. It should process these tasks swiftly,
ensuring a responsive experience for users.
 Availability:
The system must guarantee 24/7 availability, minimizing downtime or
disruptions. Continuous accessibility is crucial to enable users, including

12
 employees and administrators, to access the system at any time without delays
or interruptions.
 Reliability:
The system must exhibit high reliability, minimizing errors and bugs. In the
event of errors or failures, the system should quickly and automatically
recover without causing significant disruptions or downtime. Reliability is
essential for maintaining accurate and consistent financial records.
 Security:
The system must prioritize security, safeguarding sensitive information such
as financial data and employee details. Implementation of robust security
measures is essential to prevent unauthorized access, data breaches, and other
security threats.
 Usability:
The system must feature a user-friendly interface that is easy to navigate and
understand. Usability is critical to ensure that users, including employees
submitting expenses and administrators managing financial records, can
interact with the system effectively, minimizing confusion and frustration.
 Compatibility:
The system must be compatible with various devices and operating systems.
Users should be able to access the expense tracking system seamlessly from
their preferred devices ensuring flexibility and convenience.
 Scalability:
The system must be scalable, capable of accommodating an increasing number
of users and expense transactions as the system grows. Scalability is vital to
meet the evolving needs and demands of users, ensuring the system's
effectiveness as the user base expands.

2.4 FEASIBILITY STUDY

It is necessary and prudent to evaluate the feasibility of a project at the earliest possible
time. There may be different ways of checking whether a system is feasible or not. The
following feasibility studies were performed to gauge the feasibility of the system.

13
  Operational Feasibility:
The operational feasibility assessment for the Expense Tracking System
involves evaluating the system's operational scope. The analysis indicates that
the proposed system is exceptionally user-friendly. With ample built-in help
features, even individuals with limited knowledge of financial software can
navigate the system effortlessly.
 Technical Feasibility:
The technical feasibility assessment encompasses a thorough study of the
system's functions, performance capabilities, and any constraints that might
impact the achievement of an acceptable system. The evaluation commences
with an analysis of the technical viability of the proposed Expense Tracking
System. Key factors considered include the need for various resources for
successful implementation.
 Economic Feasibility:
In the economic feasibility analysis, the development costs are evaluated in
relation to the ultimate income or benefits derived from the proposed Expense
Tracking System. The income generated can be monetary or in terms of
goodwill. The economic feasibility assessment confirms that the benefits
accrued, whether in terms of financial gains or enhanced organizational
reputation, outweigh the costs associated with developing and implementing
the system.

2.5 GANTT CHART:

Task Description

Project Planning
Requirements Gathering
System Design
Front-End Development
Back-End Development
Testing and Bug fixing
Deployment and launch
9/2/2023 9/9/2023 9/16/2023 9/23/2023 9/30/2023 10/7/2023 10/14/2023 10/21/2023 10/28/2023 11/4/2023 11/11/2023 11/18/2023 11/25/2023 12/2/2023

Figure 2. Gantt Chart

14
Explanation:

 Project Planning:
During this phase, the project team will establish project goals, define project
scope, identify stakeholders, and develop a project plan.
 Requirements Gathering:
During this phase, the project team will gather and document the functional
and non-functional requirements for the Online Ride Sharing System.
 System Design:
During this phase, the project team will develop the system architecture,
design database schemas, and create wireframes and mockups of the user
interface.
 Front-End Development:
During this phase, the project team will develop the front-end components of
the system, including the user interface and user experience design.
 Back-End Development:
During this phase, the project team will develop the back-end components of
the system, including the database schemas, API endpoints, and business logic.
 Testing and Bug Fixing:
During this phase, the project team will conduct system testing to identify and
resolve any bugs or issues.
 Deployment and Launch:
During this phase, the project team will deploy the system to a production
environment and launch it to the public.
 Post-Launch Maintenance:
During this phase, the project team will provide ongoing maintenance and
support for the system, including bug fixes, security updates, and feature
enhancements.

2.6 DECISION TABLE

Condition Action 1 Action 2
Expense is entered Recorded in history Added to expense
Income is entered Recorded in history Added to income
Expense is deleted Removed from history Decreased from expense
Income is deleted Removed from history Decreased from income

15
In this decision table, the conditions are listed in the left-hand column, and the possible
actions are listed in the header row. Each cell in the table represents a specific
combination of conditions and actions, and the corresponding action(s) to take based on
those conditions.

For example, if a user enters expense the expense is recorded in history and the amount is
added to expense.

Using a decision table like this can help ensure that all possible combinations of
conditions and actions are considered and accounted for in the design and development of
the Online Ride Sharing System.

16
 CHAPTER 3: SYSTEM SPECIFICATIONS
3.1 SERVER REQUIREMENTS (Minimum Requirements)
 NodeJS >= 18.12.0
 Mongoose ORM

3.2 DEVELOPMENT TOOLS USED

 Operating system: Windows 11 & MacOS
 IDE: VS Code
 Frameworks: ReactJS, ExpressJS
 Back-End: NodeJS
 Database: MongoDB, MySQL

17
 CHAPTER 4- MODULES AND THEIR DESCRIPTION
4.1 MAJOR MODULES
4.1.1 Customer Module
This module provides functionalities for customers. Customers can get information about
their expense and income status, history of all the amount entered and also delete the
unwanted history.

The customer module is a crucial component of an Expense Tracking System, as it allows

users to interact with the system and access the services it provides. The customer module
typically includes the following features:

 Enter expense (as negative amount)

 Enter income (as positive amount)
 User feedback and reviews
 Customer support
 Delete unwanted amount

By implementing a robust employee module, the Expense Tracking System can offer
users a seamless and user-friendly experience, resulting in heightened user satisfaction
and increased adherence to expense tracking practices. This module serves as a crucial
component for enhancing user engagement and promoting a positive experience
throughout the expense and income submission.

4.1.2 Driver Module

The manager module is a fundamental component of any Expense Tracking System,
providing administrators and finance personnel the ability to oversee and manage all
aspects of the expense tracking process. Here are some potential features of a driver
module:

 Expense management
 Income management
 History management
 Review management

4.1.3 Administration Module

The administrative module is a crucial component of an Expense Tracking System,
providing administrators with the tools and functionalities necessary to oversee and

18
control

19
the system's operations. Its role is essential in maintaining the integrity, security, and
effective functioning of the expense tracking system. The administrative module typically
includes the following features:

 Dashboard
 User management
 Expense management
 Income management
 History management
 System configuration

By incorporating a robust administrative module, the Expense Tracking System can be

effectively managed and maintained, resulting in heightened operational efficiency and
potential cost savings. This module encompasses various functionalities that empower
administrators to oversee and maintain the entire expense tracking application.

In the Expense Tracking System, the administrative module plays a pivotal role in
controlling the entire expense management process. Administrators can allocate
resources, set budgetary constraints, and oversee the overall financial health of the
organization.

4.2 SYSTEM FLOW DIAGRAM

4.2.1 Data Flow Diagram

Figure 3. Context-level Data Flow Diagram

20
 Figure 4. Level-0 Data Flow Diagram
4.2.2 ER Diagram

Figure 5. ER diagram

21
4.2.3 Sequence Diagram

Figure 6. Sequence diagram

22
 CHAPTER 5: SYSTEM TESTING
5.1 INTRODUCTION
Once the source code for the Expense Tracking System has been generated, the software
must undergo thorough testing to identify and rectify potential errors before delivery to
the customer. The objective is to devise a set of test cases with a high probability of
discovering errors. These techniques provide systematic guidance for designing test that

 Exercise the internal logic of software components

 Exercise the input and output domains of the program to uncover errors in
program function, behavior and performance.

5.1.1 Steps Software is tested from two different perspectives:

 Internal program logic is exercised using ―White box ǁ test case design
Techniques.
 Software requirements are exercised using ―block box ǁ test case Design
techniques. In both cases, the intent is to find the maximum number of errors with
the minimum amount of effort and time.

5.2 TESTING METHODOLOGIES

A robust strategy for testing the system should encompass a comprehensive approach that
addresses both low-level tests, focusing on the correctness of individual code segments,
and high-level tests, validating major system functions against customer requirements.
This strategy is designed to provide guidance for practitioners while offering a set of
measurable milestones for managers. Given the critical nature of testing, it is imperative
that progress is quantifiable, and any issues are identified early in the process, especially
during times of rising deadline pressures.

5.2.1 Unit testing:

This involves testing individual units or components of the system to ensure that they
work as intended. Unit testing is typically done by developers during the development
process.

5.2.2 Integration testing:

Integration testing is a crucial phase in the testing process that focuses on evaluating how
various components of a system collaborate and function collectively. This type of
testing, known as integration testing, is essential to guarantee the seamless interaction of
different modules and subsystems within the system.
23
5.2.3 System testing:
System testing is a critical phase in the software testing process that entails evaluating the
entire system to verify that it meets the specified requirements. This type of testing,
known as system testing, is conducted to ensure that the system is comprehensive, fully
developed, and functions according to the expected specifications.

5.2.4 Performance testing:

Performance testing is a crucial phase in the software testing process that involves
evaluating the system's behavior and responsiveness under varying conditions, such as
high user loads or peak usage times. This type of testing, known as performance testing,
is conducted to ensure that the system can effectively handle the expected workload and
deliver optimal performance.

5.2.5 User acceptance testing:

User acceptance testing (UAT) is a pivotal phase in the software testing process that
involves evaluating the system with actual users to confirm that it meets their needs and
expectations. This type of testing, known as user acceptance testing, is conducted to
ensure that the system is user-friendly and provides a positive overall user experience.

5.2.6 Security testing:

Security testing is a critical phase in the software testing process that involves evaluating
the security of the system to identify potential vulnerabilities or weaknesses. This type of
testing, known as security testing, is conducted to ensure that the system is robust and can
protect user data and sensitive information from unauthorized access or breaches.

24
 CHAPTER 6: SYSTEM IMPLEMENTATION
6.1 PURPOSE
System implementation is a crucial stage in a project where the theoretical design is
translated into a practical system. The primary stages in the implementation process
involve careful planning, training, system testing, and changeover planning. Each of these
stages contributes to the successful deployment and integration of the system into the
operational environment.

The main stages in the implementation are as follows:

 Planning
 Training
 System testing and
 Changeover Planning

Planning stands as the initial and foundational task in the system implementation process.
During the implementation of any system, collaboration is essential among individuals
from diverse departments, including system analysts. This collaborative effort is driven
by the practical need to address challenges associated with controlling various activities
involving people outside their respective data processing departments.

The line managers controlled through an implementation coordinating committee. The

committee considers ideas, problems and complaints of user department, it must also
consider:

 The implication of system environment

 Standby facilities and channels of communication
 Self-selection and allocation for implementation tasks
 Consultation with unions and resources available

6.2 SYSTEM MAINTENANCE

System maintenance is a crucial and ongoing aspect of any project, and this holds true for
an Expense Tracking System. To ensure the long-term success and sustainability of the
system, a comprehensive system maintenance strategy is essential. It is important to
establish a comprehensive maintenance plan that includes the following:

25
  Proactive Monitoring:
Continuous monitoring of the Expense Tracking System is essential to detect any
potential issues or performance anomalies. Proactive monitoring tools and
techniques are employed to identify and address issues before they escalate.
 Routine Updates and Upgrades:
Regular updates and upgrades are implemented to keep the system current with
the latest technologies, security patches, and industry standards. This ensures that
the Expense Tracking System remains robust, secure, and aligned with evolving
user expectations.
 Bug Fixes and Issue Resolution:
System maintenance involves addressing and resolving bugs or issues that may
arise during the system's operation. A systematic approach is taken to identify,
prioritize, and rectify any software glitches or unexpected behaviors.
 Backup and Disaster Recovery:
Robust backup and disaster recovery mechanisms are established to safeguard
data and ensure business continuity in the event of unexpected failures, data loss,
or other disruptive incidents.
 Performance Optimization:
Regular assessments of system performance are conducted to identify
opportunities for optimization. Performance tuning, such as improving response
times and optimizing database queries, is implemented to enhance the overall
efficiency of the system.
 Compliance with regulations:
The system should comply with all relevant regulations and standards, such as
data protection laws and industry standards.

In summary, system maintenance is a continuous and multifaceted process aimed at

ensuring the longevity, efficiency, and adaptability of the Expense Tracking System. It
involves proactive monitoring, routine updates, bug fixes, security enhancements, and
strategic planning to address evolving needs and challenges while providing a seamless
and reliable experience for users.

26
 CHAPTER 7- CONCLUSION AND FUTURE ENHANCEMENT
7.1 CONCLUSION
In conclusion, the development of an Expense Tracking System can offer a practical and
innovative solution to address the evolving needs of individuals and businesses in
managing their financial activities. This project entailed a thorough analysis of the
requirements, feasibility, and limitations associated with developing an Expense Tracking
System.

The comprehensive analysis involved considerations such as user requirements gathering,

the feasibility of implementing the system, potential limitations, and the identification of
key functionalities to meet the diverse needs of users. The aim was to create an efficient
and user-friendly system that addresses the challenges associated with expense tracking
and budget management.

The Expense Tracking System has the potential to streamline financial processes, enhance
accuracy in expense recording, and provide valuable insights into spending patterns. By
leveraging technology, this system can contribute to improved financial management,
aiding users in making informed decisions about their expenditures and financial goals.

It's important to acknowledge that, like any system, the Expense Tracking System may
have certain limitations and challenges. These could include issues related to user
adoption, integration with existing systems, and the need for ongoing updates to address
evolving financial practices and regulations.

In essence, the development of an Expense Tracking System presents an opportunity to

enhance financial management practices, improve transparency, and empower individuals
and businesses to achieve their financial objectives. The project has involved a
meticulous examination of requirements, feasibility considerations, and potential
challenges, paving the way for the creation of a valuable and efficient tool in the realm of
expense tracking and financial management.

7.2 SCOPE FOR FUTURE DEVELOPMENT

Based on the analysis and planning conducted in this project, there is substantial potential
for the future development of an Expense Tracking System. The project team has
diligently identified key requirements and limitations for developing such a system, along
with recognizing potential benefits and challenges associated with its implementation.

27
To propel the continued development of the system, it is recommended that the project
team focuses on the following critical areas:

 User Experience
 Customization and Flexibility

Automation and Smart Technologies

 Security and Privacy

Overall, the future development of an Expense Tracking System has the potential to
revolutionize personal and business financial management. By addressing the key areas
identified in this project, the system can be further optimized to meet the evolving needs
and expectations of users, providing a comprehensive and adaptable solution for effective
expense tracking and financial planning.

28
REFERENCES

[1] "MDN Web Docs," [Online]. Available: https://developer.mozilla.org/.

[2] "Study Tonight," [Online]. Available: https://www.studytonight.com.

[3] S. Stefanov, "React Up and Running".

[4] "CSS-Tricks," [Online]. Available: https://css-tricks.com/.

APPENDIX
Screenshots:

29