Tribhuvan University

Faculty of BICTE

(Bachelor in Information & Communication Technology Education)

INSTITUTE MANAGEMENT SYSTEM

Submitted by

PAWAN SUBEDI
(REG. No: 9-2-214-51-2019)

TANKA ACHARYA
(REG. No: 9-2-214-59-2019)

MOHAMMAD TAUSIF REJA

(REG. No: 9-2-214-46-2019)

NISCHAL PAUDEL
(REG. No: 9-2-214-49-2019)

A PROJECT REPORT

Submitted to

Department of BICTE

SUKUNA MULTIPLE CAMPUS

In partial fulfillment of the requirements for the Bachelor in Information &

Communication Technology Education

December 2025

Under the
Supervision of
Santosh Dahal

2
 Sukuna Multiple Campus
(Bachelor in Information & Communication Technology Education)

SUPERVISOR’S RECOMMENDATION

We hereby recommend that this project prepared under my supervision by Pawan

Subedi, Tanka Acharya, Mohammad Tausif Reja and Nischal Paudel
entitled“INSTITUTE MANAGEMENT SYSTEM ” in partial fulfillment of the
requirements for the degree of Bachelor of Computer Application is recommended for the
final evaluation.

………………

SIGNATURE

Santosh Dahal

SUPERVISOR

Department of BICTE

Sukuna Multiple Campus

ii
 LETTER OF APPROVAL

This is to certify that this project prepared by Pawan Subedi, Tanka Acharya,
Mohammad Tausif Reja and Nischal Paudel entitled “INSTITUTE
MANAGEMENT SYSTEM” in partial fulfillment of the requirements for the degree of
Bachelor in Information & Communication Technology Education has been
evaluated. In our opinion, it is satisfactory in the scope and quality as a project for the
required degree.

……………………….. ……………………………
SIGNATURE of Supervisor SIGNATURE of Focal Person
Mr. Santosh Dahal Mr. Santosh Dahal
Department of BICTE Department of BICTE
Sukuna Multiple Campus Sukuna Multiple Campus

Sundarharaincha-12, Morang Sundarharaincha-12, Morang

….……….……….……….…………… ….……….……….……….……………
SIGNATURE SIGNATURE
Internal Examiner External Examiner

iii
 ABSTRACT
The Institute Management System (IMS) is a specialized solution developed to meet the
needs of educational institute owners by centralizing and streamlining administrative
operations. This system provides comprehensive tools to manage day-to-day activities
effectively, such as tracking attendance, customizing fee collection programs, and
monitoring financial transactions. The IMS allows administrators to review absences,
communicate with parents, and access detailed demographic information to enhance
decision-making and operational efficiency.
Designed to address the challenges of manual administrative processes, the IMS reduces
errors and inefficiencies in data management. It automates tasks like student enrollment,
fee management, class scheduling, and teacher assignments, thereby minimizing manual
effort and allowing staff to focus more on educational quality and student engagement.
The system also facilitates the analysis, graphing, and reporting of data, giving
administrators full control over institutional operations.

iv
 ACKNOWLEDGEMENT
In the successful culmination of the " Institute Management System" project, heartfelt
gratitude goes out to those who played pivotal roles and offered unwavering support
throughout this journey.

Foremost, we extend our sincere appreciation to our project supervisor and focal person,
Er. Santosh Dahal, whose guidance and encouragement paved the way for the
development of this innovative application.

We would also like to express our gratitude to Mr. Atul Bhattarai, for his past
contributions and support. His insights and guidance have been valuable in the early
stages of the project.

We also express our gratitude to the entire teaching faculty for their encouragement and
valuable feedback. Their academic insights and recommendations enriched our
understanding of the project's scope and potential.

To our parents and friends, whose unwavering support and understanding were
indispensable, we offer our deepest thanks. Their encouragement motivated us through
challenges and contributed to the timely completion of the project.

This collaborative effort reflects the synergy of a supportive network, and we are truly
grateful for the contributions of each individual who played a part in making "Institute
Management System" a reality.

Yours sincerely,

Pawan Subedi

Tanka Acharya

Mohammad Tausif Reja

Nischal Paudel

v
 LIST OF ABBREVIATIONS

DFD: Data Flow Diagram

ERD: Entity-Relationship Diagram
Gantt Chart: Graphical representation of a project schedule
iOS: Operating System used in Apple devices
NPR: Nepalese Rupee
UI: User Interface

vi
 LIST OF FIGURES
Figure 1 Alige Model.........................................................................................................14

Figure 2 Scrum Model.......................................................................................................15

Figure 3 ER Diagram.........................................................................................................24

Figure 4 Data Flow Diagram (DFD) of the Application....................................................25

Figure 5 Architectural design.............................................................................................27

Figure 6 Database Schema.................................................................................................29

Figure 7 System Flowchart................................................................................................30

Figure 8 Add Transaction..................................................................................................33

Figure 9 Dashboard............................................................................................................33

Figure 10 User Registration...............................................................................................33

Figure 12 Data Visualization.............................................................................................33

Figure 11 User Settings......................................................................................................33

Figure 13 Physical DFD of the Hisab: Income Expenses App..........................................34

LIST OF TABLES

vii
Table 1 User Entity............................................................................................................23

Table 2 Transaction Entity.................................................................................................23

Table 3 Budget Entity........................................................................................................24

Table 4 Financial Literacy Entity.......................................................................................24

Table 5 Relationships.........................................................................................................24

Table 6 User Table.............................................................................................................27

Table 7 Transaction Table..................................................................................................28

Table 8 Security Table.......................................................................................................28

Table 9 Settings Table........................................................................................................28

Table 10 Education Table..................................................................................................28

Table 11 Graph Table........................................................................................................28

Table 12 Feature Request Table.........................................................................................28

Table 13 User Table...........................................................................................................31

Table 14 Transaction Table................................................................................................31

Table 15 ExpenseCategory Table......................................................................................31

Table 16 Test Cases for Unit Testing.................................................................................38

Table 17 Test Cases for System Testing............................................................................38

viii
 Table of Contents
SUPERVISOR’S RECOMMENDATION..........................................................................ii

LETTER OF APPROVAL.................................................................................................iii

ABSTRACT........................................................................................................................iv

ACKNOWLEDGEMENT...................................................................................................v

LIST OF ABBREVIATIONS.............................................................................................vi

LIST OF FIGURES...........................................................................................................vii

LIST OF TABLES.............................................................................................................vii

1 Introduction................................................................................................................11

1.1 Problem Statement..............................................................................................11

1.2 Objectives............................................................................................................12

1.3 Scope and Limitations.........................................................................................12

1.3.1 Scope............................................................................................................13

1.3.2 Limitations...................................................................................................13

2 Development Methodology........................................................................................14

2.1 Report Organization............................................................................................16

3 Background Study and Literature Review.................................................................18

3.1 Background Study...............................................................................................18

3.2 Literature Review................................................................................................19

4 System Analysis and Design......................................................................................19

4.1 System Analysis..................................................................................................19

4.1.1 Requirement Analysis..................................................................................19

4.1.2 Feasibility Analysis......................................................................................21

4.1.3 Data Modelling (ER Diagram).....................................................................23

4.1.4 Process Modelling (DFD)............................................................................25

9
 4.2 System Design.....................................................................................................27

4.2.1 Architectural Design...................................................................................27

4.2.2 Database Schema........................................................................................27

4.2.3 System Flowchart.........................................................................................30

4.2.4 Database Table.............................................................................................30

4.2.5 Interface Design...........................................................................................31

4.2.6 Physical DFD...............................................................................................34

4.2.7 Algorithm detail...........................................................................................34

5 Implementation and Testing.......................................................................................36

5.1 Implementation....................................................................................................36

5.1.1 Tools Used...................................................................................................36

5.1.2 Implementation details of modules..............................................................36

5.2 Testing.................................................................................................................37

5.2.1 Test Cases for Unit Testing..........................................................................37

5.2.2 Test Cases for System Testing.....................................................................37

6 Conclusion and Future Recommendations................................................................39

6.1 Conclusion...........................................................................................................39

6.2 Lesson Learnt......................................................................................................39

6.3 Future Recommendations....................................................................................39

7 References..................................................................................................................41

8 Appendices.................................................................................................................43

10
 1 Introduction

Institute management system is a complete solution for managing an

administration. In other words, an enhanced tool that assists in organizing the day-to-day
activities of the Institutes. Institute management system centralizes institute by providing
features to its Administration, Students and Staffs. The attendance review shows all
students, staffs absent today and students absent for the current marking period, select
students and parents for SMS communications, click on student's name to see
demographic information to call parents, detail level absenteeism, comments entered by
teachers/office staff. Administrator can keep eye on the regular money transactions and
institute fees collection program can be customized according to institute rules. Data in
the systems can be analysed, graphed and reported in the format of user's choice.
Administrators are provided with a full control over this software. Administration can
send announcements of the events to all users in the institute. Students are provided with
user ids and password. Students can access their full details regarding marks, fees,
examination results. Parents can access the details of their wards report card,
performance, comments from teachers and everything related to their ward. This system
provides a simple interface for the maintenance of student and staff information. It can be
used by educational institutes to maintain the records of students easily.

11
1.1 Problem Statement

In the education sector, Institutes face challenges in efficiently managing their

operations, including student enrolment, course scheduling, teacher assignments, and
performance tracking. Existing manual systems often lead to administrative
inefficiencies, errors in data management, and difficulty in meeting student and parent
expectations for timely information and updates. There is a critical need for a
comprehensive Institute Management System (IMS) that automates and integrates these
processes, providing administrators, teachers, students, and parents with a user-friendly
platform to streamline operations, enhance communication, and improve overall
educational outcomes.
Motivation
The motivation behind developing an Institute Management System (IMS) stems
from several key factors that aim to address challenges and enhance the efficiency of
Institutes:
Operational Efficiency: IMS automates repetitive administrative tasks such as
student enrolment, fee collection, scheduling classes, and managing teacher assignments.
This automation reduces manual effort, minimizes errors, and allows staff to focus more
on teaching and student engagement.
Improved Communication: By providing a centralized platform, IMS facilitates
seamless communication among administrators, teachers, students, and parents. This
includes announcements, notifications, progress updates, and feedback, fostering a
collaborative environment and enhancing transparency.
Enhanced Student Experience: IMS offers students and parent’s convenient
access to course information, schedules, attendance records, grades, and performance
analytics. This transparency helps students track their progress, identify areas for
improvement, and stay motivated.
Compliance and Security: IMS ensures compliance with regulatory requirements
and data protection laws by securely managing sensitive information such as student
records, financial transactions, and personal data.
In essence, the motivation behind an Institute Management System is to transform
traditional institute operations into streamlined, efficient, and technology-driven
processes that enhance educational quality, student satisfaction, and organizational
effectiveness.

12
1.2 Objectives

i. To simplify administration of classes, courses, and staff.

ii. To streamline student enrollment and fee management.

1.3 Scope and Limitations

1.3.1 Scope

Administrative Management:
Enrolment and Registration: Manage student admissions, registrations, and enrolment
processes efficiently.
Fee Management: Handle fee collection, payment processing, and financial tracking.
Teacher and Staff Management: Assign teachers to courses, manage their schedules, track
performance, and facilitate communication.

Academic Management:
Course and Curriculum Management: Create, update, and manage course offerings,
curriculum content, and syllabi.
Class Scheduling: Generate and manage class schedules, including room assignments and
timetable adjustments.
Attendance Management: Track student attendance, monitor trends, and generate
attendance reports.

Student and Parent Portal:

Student Information System: Maintain student records, academic history, performance
evaluations, and personal details.
Parent Communication: Provide parents with access to their child’s academic progress,
attendance records, and institute announcements.

Communication and Collaboration:

Internal Communication: Facilitate communication among administrators, teachers, and
staff through messaging systems, notifications, and announcements.
External Communication: Engage with students and parents through newsletters, event
notifications, and performance updates.

Security and Compliance:

Data Security: Implement robust security measures to protect sensitive student data,
financial information, and institute records.

13
Compliance: Ensure adherence to educational regulations, data protection laws, and
industry standards.

1.3.2 Limitations

i. Cost Considerations: High upfront costs for implementation, customization, and

ongoing maintenance.

ii. Integration Challenges: Difficulty integrating with existing systems and

potential compatibility issues.

iii. Dependence on Technology: Reliance on stable internet connectivity and

technology infrastructure.

iv. User Adoption and Training: Need for comprehensive training and support to
ensure effective adoption.

v. Customization Constraints: Limitations in adapting off-the-shelf solutions to

specific institute workflows and requirements.

2 Development Methodology

The development methodology employed for "Institute Management system" follows a

dynamic and iterative approach, drawing inspiration from waterfall methodology. This
choice is grounded in the principles of adaptability, collaboration, and a commitment to
continuous enhancement throughout the app's development lifecycle.

14
 Figure 1 waterfall Model

2.1 Report Organization

This report on the development of "Institute Management System" is organized to provide

a systematic and comprehensive overview of the project. Each section contributes distinct
insights into the various stages of app development, ensuring clarity and coherence in
understanding the process.

15
The report begins with an introduction that sets the stage for the project. It outlines the
problem statement, objectives, scope, and limitations, providing a foundational
understanding of the context and goals.

This section delves into the background study, offering insights into existing financial
management tools and apps. Additionally, it includes a literature review that draws on
relevant studies and articles, establishing the theoretical framework for the project.

A detailed analysis of the system precedes the design phase. This section covers
requirement analysis, feasibility analysis, data modeling with an ER diagram, and process
modeling using a DFD. The subsequent system design includes architectural design,
database schema, system flowchart, database table, interface design, and physical DFD.

The report then transitions to the practical aspects of implementation and testing. It
discusses the tools used for implementation, such as Flutter, providing insight into the
modules and their detailed implementation. Testing is addressed through unit testing and
system testing, with corresponding test cases.

The final section offers a conclusion that summarizes key findings, lessons learned, and
insights gained from the development process. Additionally, future recommendations
outline potential enhancements or features for subsequent iterations of the software.

The report is structured to facilitate a comprehensive understanding of the project's

journey, from conceptualization to implementation, providing valuable insights for
readers, stakeholders, and future developers.

16
 3 Background Study and Literature Review

3.1 Background Study

An Institute Management System (IMS) is a comprehensive software solution designed to

streamline the administrative and academic operations of educational institutions such as
training centers, coaching institutes, and learning academies. The system serves as a
centralized platform to manage key activities, including student admissions, course
management, fee collection, staff and teacher management, and examination results,
among others. By automating routine tasks, the IMS reduces human error, enhances
efficiency, and improves the overall learning experience for students and faculty alike.

Need for an Institute Management System

Educational institutions, especially small and medium-sized institutes, face numerous
challenges in managing their day-to-day operations. Traditional paper-based methods are
often time-consuming, error-prone, and inefficient. Manual handling of student data, fee
records, class schedules, and examination results can lead to delays, miscommunication,
and operational inefficiencies. An Institute Management System addresses these
challenges by providing a digital solution to automate and streamline these processes.

3.2 Literature Review

A review of existing literature underscores the need for personalized and

culturally relevant solutions for financial management, especially in diverse economic
environments like Nepal (Shrestha et al., 2019). The positive correlation between
financial literacy and financial well-being is well-documented (Bartik, 2020).
Technology, particularly mobile applications, has emerged as a promising avenue for
enhancing financial literacy and providing practical tools for expense tracking (Adhikari
et al., 2022; Shrestha et al., 2019).

The identified challenges and opportunities from the background study and
literature review lay the groundwork for the development of "Hisab: Income Expense
Tracker." The app aims to fill the existing gaps by offering a user-friendly, culturally
relevant solution designed explicitly for the Nepalese population. Through this endeavor,

17
"Hisab" seeks to empower individuals, improve financial literacy, and contribute to the
overall financial well-being of users in Nepal.

4 System Analysis and Design

4.1 System Analysis

System analysis is a crucial phase in the development of an Institute Management System

(IMS). It involves examining the current system, understanding user requirements, and
identifying potential improvements to design a system that addresses the needs of all
stakeholders. This section outlines the key components, user requirements, and system
specifications that form the foundation of an effective IMS.

4.1.1 Requirement Analysis

Several expense-tracking applications, prevalent in both local and international contexts,

were examined to understand the landscape of available solutions. Notable systems such
as Mint, PocketGuard, and Expensify were assessed for their functionalities, user
interfaces, and overall user experiences. Each system was dissected to extract valuable
features and functionalities that could contribute to enhancing the "Hisab" app.

4.1.1.1 Findings and Insights:

School Diary : Includes features like one-to-one messaging, auto-scheduling, and

automated attendance. It also has a built-in inventory and library management system.

Sparkrock 365 : An integrated ERP platform that can handle student management,
payroll, and budgeting.

PowerSchool : A platform for educational institutions that includes features like student
information systems, grade management, and behavior tracking. It also has tools for
learning management, such as creating and managing courses and online assessments.
4.1.1.2 User Feedback and Preferences:

In addition to examining the features of similar systems, direct user feedback was
collected through surveys and interviews. Users expressed a common desire for a more
user-friendly and culturally relevant solution tailored to the specific financial practices
and preferences in Nepal.

"Designing Hisab: Insights from a Graphics Design Perspective on an Income

Expense Tracker App"8

18
 The user survey conducted from a graphics design perspective for the "Hisab:
Income Expense Tracker" app revealed several key insights. Participants, including a
freelance graphics designer, predominantly use Expensify and highly value its clean and
intuitive interface with customizable categories. The survey emphasizes the paramount
importance of a user-friendly design, garnering a top rating of 5 on a scale of 1-5,
indicating a strong preference for an intuitive user experience.

In terms of feature preferences, participants consider visual representation of

spending, customizable expense categories, and quick transaction entry as essential
elements for effective expense tracking. There's a notable preference for a balanced
approach to expense categorization, combining user customization with automated
suggestions. Security emerges as a significant concern, with users expressing a preference
for features such as end-to-end encryption, secure login methods, and biometric
authentication to safeguard their financial data.

Cultural relevance is a key aspect highlighted by users, suggesting the

incorporation of traditional symbols or themes in visual elements to resonate with
Nepalese users. Additionally, users emphasize considering unique financial practices
related to festivals and seasonal spending habits in Nepal. Feature preferences include a
positive inclination towards integrating educational resources on financial literacy within
the app, with users valuing short tutorials or tips on budgeting and financial planning.

In the realm of graphics design, users prefer an app with interactive graphs, color-
coded categories, and the ability to add custom icons to transactions for balance tracking
and expense visualization. The visual style preference leans towards a modern and
minimalistic design with vibrant yet culturally relevant color schemes. Participants stress
that a visually appealing app enhances user engagement and emphasize the importance of
consistency in design and attention to detail for an overall positive user experience.

In conclusion, the survey findings underscore the significance of combining

functional effectiveness with a visually appealing and culturally relevant design in the

19
development of the "Hisab: Income Expense Tracker" app. User preferences guide key
decisions related to customization, security, cultural resonance, and visual aesthetics,
ensuring the app meets the expectations of its target audience.

4.1.2 Feasibility Analysis

The "Institute management system" app has undergone a rigorous feasibility

analysis to ascertain its technical, operational, and economic viability. This scrutiny is
pivotal to ensuring the success of the project and its ability to deliver a robust institute
management solution tailored for users in Nepal.

4.1.2.1 Technical Feasibility

The technical feasibility study evaluates the technological requirements and

capabilities needed for the development and implementation of the app. It examines
factors such as the availability of suitable development tools, programming languages,
and frameworks like Flutter that allow for cross-platform compatibility. Additionally, it
considers the scalability of the app to handle a growing user base and the integration of
necessary APIs for features such as currency conversion or data visualization. As
individuals with a background in Bachelor of Information and Communication
Technology Education (BICTE), we possess the necessary technical knowledge and skills
to undertake the development of the app.

4.1.2.2 Operational Feasibility

The operational feasibility study focuses on assessing whether the app can be
seamlessly integrated into existing processes and systems. It considers factors such as
user acceptance and adoption, ease of use, and compatibility with existing Institute
management practices in Nepal. This includes analyzing the app's user interface design to
ensure it aligns with user expectations and cultural preferences. Moreover, it examines the
availability and accessibility of required resources, such as internet connectivity and
smartphone penetration, to ensure widespread usage of the app among the target user
base. By conducting surveys, interviews, and user testing sessions, we will gather
feedback and insights from potential users to ensure that the app meets their needs and
aligns with their preferred methods of managing educational.

20
4.1.2.3 Economic Feasibility

The economical feasibility study examines the financial aspects of the project. It
evaluates the costs associated with developing and maintaining the app, as well as the
potential benefits and returns on investment. This includes considering the expenses
related to development resources, infrastructure, marketing, and ongoing maintenance.
Additionally, it assesses the potential revenue streams, such as in-app purchases,
subscription models, or partnerships with financial institutions or organizations. The
study also takes into account the projected user base and market demand in Nepal. By
conducting a cost-benefit analysis, we will determine the financial viability of the project
and assess its long-term sustainability.

By conducting a comprehensive feasibility study, we will assess the technical

feasibility, operational feasibility, and economical feasibility of the Institute Management
System project. This will help us make informed decisions, mitigate risks, and ensure that
the app is technically feasible, aligns with user needs.

4.1.3 Data Modelling (ER Diagram)

The ER diagram for the Institute Management project depicts a streamlined

system for managing small Institute centres effectively. It revolves around key entities
such as Institute Centre, Class, Course, Teacher, Student, Staff, Fee, Result, and Notice.
Each Institute Centre can manage multiple Classes, each offering various Courses.
Teachers are assigned to Courses, while Students are enrolled in specific Classes. Staff
members handle administrative roles, and both Fees and Results are tracked per Student.
Notices are published by Institute Centres to communicate with their community. This
ER diagram ensures a structured approach to organizing and maintaining Institute
operations, emphasizing simplicity and functionality for small Institute centres.

Entities and Attributes:

Attribute Data Type Key
UserID INT Primary
Username VARCHAR(255)
Password VARCHAR(255)
Table 1 User Entity

21
 These relationships illustrate how entities are connected in the data model of the
"Hisab: Income Expense Tracker" app.Figure 2 ER Diagram

Figure 2 ER Diagram

Key considerations in the development of the "Hisab: Income Expense Tracker"

app encompass a user-centric approach, robust security measures, and seamless
integration with the Hive database. The app prioritizes providing real-time balance
tracking, insightful expense graphs, and a user-friendly interface. Custom fonts, assets,
and dependencies enhance the visual experience, while styled icons and conditional logic
streamline database operations. Cross-platform compatibility, achieved through Flutter,
ensures accessibility on both iOS and Android devices. Chart visualization and
integration with Hive database contribute to the app's production-ready status, addressing
the specific needs of users for efficient income and expense tracking.

22
 This ER diagram reflects the current requirements of the "Hisab" app. It ensures
that the app can effectively store, manage, and retrieve user and financial data in a
structured and organized manner.

4.1.4 Process Modelling (DFD)

In the system analysis phase of the "Hisab: Income Expense Tracker" app, a
detailed process model was developed to visually represent the flow of data within the
system. The Data Flow Diagram (DFD) provides insights into how information moves
through various processes and data stores, facilitating a comprehensive understanding of
the app's functionalities.

Figure 3 Data Flow Diagram (DFD) of the Application

The DFD comprises several key elements:

i. Processes:
a. User Input: Represents the initial interaction where users input their financial data,
including income and expenses.
b. Transaction Recording: This process involves the recording of transactions,
including details such as date, description, and amount.

23
 c. Expense Categorization: A crucial step where the system categorizes expenses
either automatically or with user input.
d. Data Visualization: Involves the generation of expense graphs and visual
representations for users to gain insights.
e. Balance Tracking: The process responsible for real-time tracking of users' financial
balances.
ii. Data Stores:
a. Hive Database: Represents the secure storage of user data, ensuring the
confidentiality and integrity of financial information.
b. Expense Categories: Stores predefined categories and allows users to customize
their own categories.

iii. External Entities:

a. Users: The primary external entity interacting with the system, providing input and
receiving output.
b. Educational Resources: Represents external sources providing financial literacy
resources and tips.

iv. Data Flows:

a. User Input to Transaction Recording: The flow of data from user input to the
recording of financial transactions.
b. Transaction Data to Expense Categorization: Data flow ensuring accurate
categorization of expenses based on recorded transactions.
c. Expense Data to Data Visualization: Facilitates the generation of visualizations
based on categorized expense data.
d. Transaction Data to Balance Tracking: Enables real-time balance tracking by
incorporating transaction data.

The DFD illustrates the logical flow of information within the "Hisab" app,
serving as a valuable tool for system analysis. It provides a foundation for further design
and implementation phases, ensuring that the app aligns with the specified requirements
and objectives.

4.2 System Design

24
 In the System Design phase of the "Hisab: Income Expense Tracker" app, various
aspects are considered to ensure a robust and user-centric architecture that aligns with the
app's objectives. This phase involves defining the overall structure, components, and
interfaces of the system.

4.2.1 Architectural Design

The architectural design of the app revolves around a

client-server model, where the client is the mobile application,
and the server hosts the Hive database. This ensures that user
data is securely stored and can be accessed across devices.

4.2.2 Database Schema

The database schema defines the structure of the Hive Figure 4 Architectural design
database, specifying how data is organized and related.
Field Type Key
UserID INT PRIMARY KEY
Username VARCHAR
Password VARCHAR
Age INT
Occupation VARCHAR
MonthlyIncome DECIMAL
MobileOS VARCHAR
Table 2 User Table

Field Type Key

TransactionID INT PRIMARY KEY
UserID INT FOREIGN KEY
Amount DECIMAL
TransactionType VARCHAR
Category VARCHAR
Date DATE
Description VARCHAR
PaymentMethod VARCHAR
Table 3 Transaction Table

Field Type Key

UserID INT PRIMARY KEY
EncryptionKey VARCHAR
25
BiometricData VARCHAR
Table 4 Security Table

Field Type Key

UserID INT PRIMARY KEY
Theme VARCHAR
Language VARCHAR
Currency VARCHAR
Table 5 Settings Table

Field Type Key

ArticleID INT PRIMARY KEY
Title VARCHAR
Content TEXT
Table 6 Education Table

Field Type Key

UserID INT PRIMARY KEY
GraphData TEXT
Table 7 Graph Table

Field Type Key

RequestID INT PRIMARY KEY
UserID INT FOREIGN KEY
RequestDate DATE
RequestDescription TEXT
Table 8 Feature Request Table

The database schema can be clearly visualized by the following illustration.

26
Figure 5 Database Schema

27
4.2.3 System Flowchart

Figure 6 System Flowchart

The system flowchart for the "Hisab: Income Expense Tracker" app illustrates a
user-centric process beginning with user interaction, where existing users undergo a login
check and proceed to the Dashboard upon successful login, allowing them to record
income and expenses, generate expense graphs, and view visual insights. For new users,
the registration process is initiated, and upon successful registration, they are directed to
the Dashboard. The flowchart incorporates error handling, displaying login or registration
errors when necessary. Overall, this representation encapsulates the core functionalities of
the app, providing users with a seamless experience in managing their financial activities.

4.2.4 Database Table

The "Hisab: Income Expense Tracker" app utilizes Hive as its database
management system, providing a lightweight and efficient solution for data storage. The

28
database schema is structured to accommodate key entities essential for seamless income
and expense tracking. The main entities include:
Field Data Type Description
UserID Integer (PK) Unique identifier for each user.
Username String User's chosen username for login.
Password String Encrypted password for user authentication.
FullName String User's full name for personalization.
CreatedAt Timestamp Timestamp indicating user registration date.
Table 9 User Table

Field Data Type Description

TransactionID Integer (PK) Unique identifier for each transaction.
UserID Integer (FK) Links to the User Table, indicating the owner.
Amount Numeric Numeric value representing the transaction amount.
Category String Categorical field specifying the transaction type.
Date Date Date of the transaction.
Description String Additional details or notes for the transaction.
Table 10 Transaction Table

Field Data Type Description

CategoryID Integer (PK) Unique identifier for each expense category.
CategoryName String Name of the expense category (e.g., groceries).
Icon String Icon associated with the category for visualization.
Table 11 ExpenseCategory Table

The relationships between tables are established using foreign keys, ensuring data
integrity and coherence within the database. The User Table is linked to the Transaction
Table, allowing each user to have multiple transactions associated with their unique
identifier. Additionally, the ExpenseCategory Table is referenced in the Transaction
Table, enabling categorization of transactions based on predefined expense categories.
This database structure optimally supports the app's functionality, allowing for secure and
efficient storage and retrieval of user and transaction data. The use of Hive as a database
management system aligns with the project's goal of providing a scalable and user-
friendly solution for managing personal finances.

4.2.5 Interface Design

The interface design of the "Hisab: Income Expense Tracker" app focuses on
creating a user-friendly and visually appealing environment to enhance the overall user

29
 experience. The following key aspects highlight the design principles and elements
incorporated into the app:
i. Navigation and Layout:
a. A clean and intuitive navigation menu positioned for easy access to essential
features such as balance tracking, expense graphs, and transaction entry.
b. Consistent layout design across different sections to provide users with a
seamless and familiar experience.

ii. Visual Elements:

a. Integration of custom fonts and assets to add a unique and visually appealing
touch to the app.
b. Use of styled icons for categories, transactions, and other UI elements,
enhancing the app's aesthetic appeal.

iii. Transaction Entry:

a. Date selection functionality enabling users to input transaction details with
ease.
b. Conditional logic for database operations to ensure accurate and efficient
processing of transactions.

iv. Expense Graphs:

a. Implementation of chart visualization for expense graphs, offering users clear
insights into their spending patterns.
b. Color-coded categories for easy identification and analysis of different
expense types.

v. Platform Compatibility:
a. Utilization of the Flutter framework for cross-platform compatibility, ensuring
a consistent and seamless experience on both iOS and Android devices.

vi. Simplified Design:

a. Modern and minimalistic design approach to enhance user engagement and
streamline the overall interface.
b. Vibrant yet culturally relevant color schemes to resonate with Nepalese users.
30
 The interface design aims to create an engaging and efficient environment for
users to manage their income and expenses effortlessly. By combining intuitive
navigation, visual elements, and customization options, the "Hisab" app seeks to provide
a delightful user experience while ensuring accessibility and cultural relevance.

The screenshots of the app’s interface design is provided below:

Figure 7 Add Transaction

Figure 8 User Registration Figure 9 Dashboard
Figure 10 User Settings
Figure 11 Data Visualization

31
4.2.6 Physical DFD

The Physical Data Flow Diagram (DFD) illustrates the physical implementation of
data flow within the app, detailing how data moves between components.

Figure 12 Physical DFD of the Hisab: Income Expenses App

The Physical DFD illustrates the flow of data and interactions between different
components of the system. It showcases the practical implementation of the app,
emphasizing the role of the Hive database, user interface, and external integrations in
ensuring a comprehensive and functional expense-tracking solution.

4.2.7 Algorithm detail

The algorithmic details embedded within the "Hisab: Income Expense Tracker"
app are designed to ensure a seamless and secure user experience for income and expense
tracking. The first step involves robust user authentication processes, guaranteeing that

32
only authorized users can access the app. As users input new transactions, the algorithm
employs conditional logic to validate and process the transaction data before securely
storing it in the Hive database. This integration with Hive establishes a structured data
organization, including entities like users, transactions, and settings. The app's
functionality extends to generating insightful expense graphs, utilizing data visualization
techniques to present users with clear and interactive graphical representations of their
spending patterns.

Customization settings play a crucial role in tailoring the user experience, and the
algorithm ensures that user preferences are securely stored in the Hive database.
Leveraging the Flutter framework for cross-platform compatibility, the app delivers a
consistent experience on both iOS and Android devices. External resource integration
involves fetching and presenting financial literacy content within the app, contributing to
users' overall financial awareness. The algorithm also outlines robust security measures,
including encryption and user authentication, to safeguard sensitive financial information.

Continuous improvement is a key aspect of the algorithm, with features

implemented to gather user feedback, conduct testing, and iteratively enhance the app
based on user preferences. Altogether, these algorithmic details collectively contribute to
the efficiency, security, and user-centric design of the "Hisab" app.

33
 5 Implementation and Testing

5.1 Implementation

5.1.1 Tools Used

The implementation of the "Hisab: Income Expense Tracker" app involves the
utilization of cutting-edge tools and technologies. The app is developed using the Flutter
framework, a popular open-source UI software development toolkit. Flutter enables the
creation of natively compiled applications for mobile, web, and desktop from a single
codebase, ensuring efficiency and consistency across platforms. The integration of Hive,
a lightweight and fast NoSQL database, provides a robust and secure foundation for
storing user data, transactions, and settings.

5.1.2 Implementation details of modules

The "Hisab: Income Expense Tracker" app encompasses several key modules that
collectively contribute to its seamless functionality. The User Authentication Module
ensures the security of user data, employing secure login methods to grant access
exclusively to authorized users. Within the Transaction Processing Module, conditional
logic is implemented to validate and process user transactions, guaranteeing accurate and
secure storage in the Hive database.

The Data Visualization Module employs advanced techniques to generate

insightful expense graphs, offering users a clear and interactive representation of their
spending patterns. Additionally, the Customization Module empowers users to
personalize their experience by storing customization preferences securely in the Hive
database.

Cross-platform compatibility is achieved through the Cross-Platform

Compatibility Module, leveraging the Flutter framework. This ensures a consistent and
seamless user experience across both iOS and Android devices. The External Resource
Integration Module enriches the user experience by fetching and presenting financial
literacy content within the app, contributing to users' overall financial awareness.

34
 A robust Security Module is in place, implementing encryption and user
authentication measures to safeguard sensitive financial information. Lastly, the
Continuous Improvement Module facilitates iterative updates based on user feedback,
ensuring the app remains user-centric, intuitive, and aligned with evolving user
preferences. This modular approach to implementation enhances the app's feature
richness, security, and user satisfaction.

5.2 Testing

5.2.1 Test Cases for Unit Testing

Unit testing involves scrutinizing individual modules to ensure they function

correctly in isolation. For the User Authentication Module, tests will verify that user login
and access are secure and accurate. The Transaction Processing Module will undergo
tests to confirm the correct validation and processing of transactions. The Data
Visualization Module will be assessed for its accuracy in generating insightful expense
graphs. Additionally, the Cross-Platform Compatibility Module will be tested to
guarantee a seamless experience across both iOS and Android devices.

5.2.2 Test Cases for System Testing

System testing evaluates the app as a whole, examining how different modules
interact and ensuring the integrated system functions as intended. Comprehensive tests
will be conducted to simulate user interactions, including transaction entries,
customization preferences, and external resource access. The Security Module will be
rigorously examined to verify encryption and authentication measures. Continuous
Improvement Module testing will focus on the app's responsiveness to user feedback,
ensuring updates are seamless and improve the overall user experience.

35
Test Case ID Module Tested Description Expected Result Actual Result Status
Verify user login with correct Successful login Successful login Passed
UT001 User Authentication Module
credentials
Attempt login with incorrect Error message: "Incorrect Error message: "Incorrect Passed
UT002 User Authentication Module
password password" password"
Transaction Processing Add a new income Transaction added Transaction added Passed
UT003
Module transaction successfully successfully
Transaction Processing Add a new expense Transaction added Transaction added Passed
UT004
Module transaction successfully successfully
View expense graph for the Graph displays accurate data Graph displays accurate data Passed
UT005 Data Visualization Module
last month for the selected period for the selected period
Test app functionality on iOS App functions seamlessly on App functions seamlessly on Passed
UT006 Cross-Platform Compatibility
device iOS device iOS device
Test app functionality on App functions seamlessly on App functions seamlessly on Passed
UT007 Cross-Platform Compatibility
Android device Android device Android device
Attempt unauthorized access Access denied, user prompted Access denied, user prompted Passed
UT008 Security Module
to log in to log in
Table 12 Test Cases for Unit Testing

Test Case ID Scenario Tested Description Expected Result Actual Result Status
User records an income and an Balances updated correctly Balances updated correctly Passed
ST001 End-to-End User Workflow
expense
User categorizes an expense Transaction appears under the Transaction appears under the Passed
ST002 Expense Categorization
transaction selected category selected category
Attempt unauthorized access Access denied, security Access denied, security Passed
ST003 Data Security and Privacy
to user's data measures in place measures in place
Test app functionality on App functions seamlessly on App functions seamlessly on Passed
ST004 Cross-Platform Compatibility
various devices different devices different devices
Table 13 Test Cases for System Testing

36
 6 Conclusion and Future Recommendations

6.1 Conclusion

In conclusion, the development of the "Hisab: Income Expense Tracker" app

represents a significant step towards providing users in Nepal with a robust and user-
friendly platform for effective financial management. The app incorporates innovative
features such as real-time balance tracking, insightful expense graphs, and seamless
integration with the Hive database. The user-centric design, with custom fonts, assets, and
UI elements, enhances the overall user experience. The implementation of chart
visualization and automation of expense tracking processes contributes to the app's
efficiency, allowing users to make informed financial decisions effortlessly. The cross-
platform compatibility, utilizing the Flutter framework, ensures accessibility for both iOS
and Android users, maximizing the app's reach.

6.2 Lesson Learnt

Throughout the development process, several key lessons were learned. User
feedback from surveys played a pivotal role in shaping the app's features and design. The
importance of security and privacy, highlighted by users' concerns, led to the
implementation of robust security measures, including encryption and biometric
authentication. The iterative development approach, as reflected in the agile
methodology, facilitated continuous improvements. Regular user testing and feedback
loops allowed for timely adjustments, ensuring the app remains responsive to user needs.

6.3 Future Recommendations

As we look to the future, several recommendations emerge for further enhancing the
"Hisab" app:

Enhanced Educational Resources: Consider expanding the app's educational resources

by collaborating with financial experts or institutions to provide in-depth tutorials and tips
on various financial topics.

Customization Options: Introduce more customization options for users, allowing them
to personalize the app according to their cultural preferences and financial practices.

37
Notification Features: Explore the addition of notification features to remind users of
important financial events, such as bill due dates or budget milestones. Collaboration with
Financial Institutions: Forge partnerships with local financial institutions to integrate
additional services like account linking or investment tracking. By addressing these
recommendations, "Hisab" can evolve into a comprehensive financial management tool,
continually meeting the dynamic needs of users in Nepal.

38
 7 References

Adhikari, K., Dhakal, S., & Ojha, D. R. (2022). A Survey on Financial Literacy: The
Case of Nepal. International Journal of Business and Management Invention,
11(6), 18-25.

Bartik, A. W. (2020). Financial Literacy, Financial Education, and Economic Outcomes.

Annual Review of Economics, 12, 581-610.

Central Bureau of Statistics. (2020). Nepal Living Standards Survey 2019/20.

Flutter. (2021). Flutter - Beautiful native apps in record time.
Ministry of Finance. (2021). Economic Survey 2021.
Mishra, N., Dhungana, S., & Chaulagain, N. (2021). Financial Literacy and Financial
Well-being: An Empirical Analysis of Nepalese Working Population. Financial
Innovation, 7(3), 1-23.

Poudel, S. R., Gautam, P., Thapa, A., & Pandey, S. (2020). A Comparative Study on
Usage of Android, iOS and Windows Smartphones in Nepal. International Journal
of Scientific & Engineering Research, 11(9), 798-805.

Sharma, S., & Gurung, R. (2021). Financial Inclusion and Financial Literacy: An
Empirical Study of Nepal. Journal of Financial Economic Policy, ahead-of-print
(ahead-of-print).

Shrestha, A. K. (2018). Determinants of Financial Literacy: A Case Study of Nepal.

International Journal of Research in Business Studies and Management, 5(8), 10-
22.

Shrestha, A. K., Sapkota, M., & Sharma, K. (2019). Access to Finance, Financial
Literacy and Financial Inclusion in Nepal. Journal of Management and
Development Studies, 36(4), 424-444.

39
World Bank. (2021). World Bank Country and Lending Groups.
[https://datahelpdesk.worldbank.org/knowledgebase/articles/906519-world-bank-
country-and-lending-groups](https://datahelpdesk.worldbank.org/
knowledgebase/articles/906519-world-bank-country-and-lending-groups)

Poudel, P., Ghimire, A., & Timilsina, R. (2020). Mobile App Development: An
Evaluation of Flutter for Cross-Platform Mobile Development. Journal of
Information Engineering and Applications, 10(10), 43-54.

Dhakal, B., & Bohara, B. (2020). Financial Literacy and Behavior: Evidence from Nepal.
Journal of Asian Finance, Economics and Business, 7(8), 599-606.

Maharjan, S., & Koirala, S. (2021). Financial Inclusion and Digital Banking Adoption in
Nepal. International Journal of Applied Business and International Management,
6(1), 15-30.

Mishra, B. K., Mohapatra, S., Pani, S. K., & Jena, S. K. (2019). Financial Literacy and
Financial Planning: An Empirical Study of Indian Investors. Journal of Financial
Reporting and Accounting, 17(3), 365-380.

World Bank. (2021). Nepal - Overview.

[https://www.worldbank.org/en/country/nepal/overview](https://www.worldbank.
org/en/country/nepal/overview)

40
 8 Appendices

User Survey Questionnaire: Hisab App Development - Graphics Design

Perspective18

Thank you for participating in our survey! Your insights are crucial in shaping the
visual aspects of our expense-tracking app. Please take a few minutes to share your
thoughts.

1. Personal Information:
a. Age: 28
b. Occupation: Freelance Graphics Designer
c. Monthly Income Range: NPR. 40,000- 50,000
d. Mobile Operating System: iOS

2. Current Expense-Tracking Habits:

a. Do you currently use any expense-tracking apps? If yes, please specify.
 Yes, I use Expensify.
b. What features do you find most useful in your current expense-tracking app?
 I find the clean and intuitive interface along with customizable categories to be
highly useful.

3. Preferences and Priorities:

a. How important is user-friendly design in an expense-tracking app for you? (Scale: 1-
5)
 5 - Extremely important.
b. What features do you consider essential for effective expense tracking?
 Visual representation of spending, customizable expense categories, and quick
transaction entry.
c. Would you prefer automated expense categorization or manual categorization for
transactions?

41
  I prefer a balance of both, allowing users to customize but with automated
suggestions.

4. Security and Privacy:

a. How concerned are you about the security of your financial data in expense-tracking
apps? (Scale: 1-5)
 4 - Very concerned.
b. What security features would you like to see in an expense-tracking app to ensure data
protection?
 End-to-end encryption, secure login methods, and an option for biometric
authentication.

5. Cultural Relevance:
a. In what ways do you think an expense-tracking app can be culturally relevant for
users in Nepal?
 Incorporating traditional symbols or themes in visual elements to resonate with
Nepalese users.
b. Are there specific financial practices or preferences unique to Nepal that you believe
should be considered in the app?
 Consideration for festivals and seasonal spending habits.

6. Feature Preferences:
a. Would you value integration with educational resources on financial literacy within
the app?
 Yes, short tutorials or tips on budgeting and financial planning would be
beneficial.
b. What specific features would you like to see in a balance tracking and expense
visualization tool?

42
  Interactive graphs, color-coded categories, and the ability to add custom icons to
transactions.
c. Do you have preferences for a specific visual style or theme in the app?
 A modern and minimalistic design with vibrant yet culturally relevant color
schemes.

7. Additional Comments:
a. Is there anything else you would like to share regarding your expectations from an
expense-tracking app?
 I believe a visually appealing app enhances user engagement. Consistency in
design and attention to detail are crucial.

Thank you for your valuable input! Your feedback will play a significant role in
creating a visually stunning and user-centric expense-tracking app.

43