A Project Report

Submitted in partial fulfillment of the

requirements for the award of the Degree of
BACHELOR OF SCIENCE (INFORMATION TECHNOLOGY)
By

KIRAN PATIL
Seat Number: _______________
Seat Number: _______________
Under the esteemed guidance of

Prof Ganesh Bhagwat

Assistant Professor, Department of Information Technology

DEPARTMENT OF INFORMATION TECHNOLOGY

VALIA COLLEGE OF INFORMATION TECHNOLOGY

(Affiliated to University of Mumbai)
MUMBAI, 400 037
MAHARASHTRA
2019 - 2020

1
 VALIA COLLEGE OF INFORMATION TECHNOLOGY
(Affiliated to University of Mumbai)
MUMBAI-MAHARASHTRA-400037
DEPARTMENT OF INFORMATION TECHNOLOGY

CERTIFICATE
This is to certify that the project entitled, "Daily Expense Tracker System ", is bonafied work
of Kiran Patil bearing Seat No: __________________ submitted in partial fulfilment of the
requirements for the award
of degree of BACHELOR OF SCIENCE in INFORMATION TECHNOLOGY from
University of Mumbai.

Internal Guide Coordinator

Internal Examiner External Examiner

Date: College Seal Principal

 ABSTRACT

We are developing an android application named as “Expense Tracker” and

this application is used to manage the application user‘s daily expenses in a more
efficient and manageable way. By using this application we can reduce the
manual calculations for their daily expenses and keep the track of the expenditure.
In this application, user can provide his income to calculate his total expenses per
day and these results will stored for unique user.
 ACKNOWLEDGEMENT
It is a great pleasure and a moment of immense satisfaction for us to express our profound
gratitude to my project guide Prof. GANESH BHAGHWAT Co-ordinator Department
of Information Technology whose constant encouragement enabled us to work enthusiastically.
Her perpetual motivation, patience and expertise in discussion during progress of work have
benefited me to an extent, which is beyond expression. Working under her guidance has been
a fruitful and unforgettable experience. Despite of her busy schedule, she was always available
to give us advise, support and guidance during entire period of my project. The completion of
this project would not have been possible without her constant support and patience guidance.

We are thankful to Prof. GANESH BHAGHWAT Co-ordinator Department of Information

Technology of Valia C.L. College, Mumbai University for her encouragement, guidance and
support for our project.

We are thankful to Prof. SHOBHA MENON Principal, Institute of Information Technology

of Valia C.L. College for his encouragement and providing outstanding academic environment.
 DECLARATION
We hereby declare that the project entitled, “DAILY EXPENSE TRACKER SYSTEM” done
at Valia college of Information Technology, has not been in any case duplicated to submit to
any other universities for the award of any degree. To the best of my knowledge other than me,
no one has submitted to any other university.

The project is done in partial fulfillment of the requirements for the award of degree of
BACHELOR OF SCIENCE (INFORMATION TECHNOLOGY) to be submitted as final
semester project as part of our curriculum.

Name and Signature of the Students

 TABLE OF CONTENTS

SR.NO TOPICS PAGE.NO

Chapter1:
INTRODUCTION
1.1 Background 1

1.2 Literature Review 2

1.3 Problem Definition 3

1.4 Objectives 4

1.5 Scope 5

1.6 Limitations 5

Chapter 2:
SURVEY OF
TECHNOLOGIES
 User Interface User Interface
46
4.3.7 Design Design User Interface
4.3.8 Security Issues Security Issues Security Issues 47
References/ Bibliography/ Websites Used 48
 LIST OF TABLES
Table 1: Data of institution ......................................................................................................20
Table 2:Criterion1_Curricular Aspects ....................................................................................21
Table 3: Criterion 2_Teaching-Learning and Evaluation ........................................................23
Table 4Criterion 3_Research, Innovation and Extension ........................................................25
Table 5: Criterion 5_Student Support and Progression ...........................................................27
CCCHHIVCCJB
CHAPTER 1

INTRODUCTION
1.1 BACKGROUND

With the launch and increase in sales of smartphones and comes new
technology over the last few years, people are using mobile applications and
technology to get their work done, which makes their lives easier. applications
comprise various different categories such as Entertainment, Sports, Lifestyle,
Education, Games, Food and Drink, Health and Fitness, Finance, etc. This Daily
Expense Tracker System application falls in the Finance Category and serves
the With the important purpose of managing finances which is a very important
part of one’s life.
The application is not much user intensive but just comprises having them
enter the expense amount, date, category, entering notes about the expense, the
user is able to see the expense details daily, weekly, monthly, and yearly in
figures. Daily Expense tracker system is refined system which allows user to
efficiently manage user expense. Tracking daily expense can really help
To us save lot of money. All these topics have been explained in detail in their
respective chapters .aim of this these is to provide a solution for users on how to
manage finances in any circumstance by keeping track of their expenses
everyday.
1.2 LITERATURE REVIEW

Tracking daily expense is not so innovative . Many traditional and

technological approach is found to track our expenses and budget with their
own functionality. from decades ago and today we have been writing our
expenditure in a register to calculate the profit or saving. Not only this many
desktop and mobile application has been developed for this purpose
Quicken and Microsoft money were the first desktop application was developed
decades ago but was not so familiar with the users. Personal capital and dollar
bird application were used to visualize the expenses in chart or graph with the
calendar system. QuickBooks were the application for the small business holder
to wrap up their whole business. YNAB is an expense tracker that gives the
automatic tracking of our expense through our bank account and credit cards.

Comparison of existing similar application is shown below:

Software YNAB Quicken Microsoft QuickBooks

Name Money
Emerging 2013 2008 2000 2008
Date
Automatic yes no no no
Expense no no no no
information
Pre-define yes no No no
expenses
Mobile yes yes yes no
Friendly

1.3 PROBLEM DEFINITION

Every earning people are mostly obsessed at the end of the month as the they
cannot remember where all of their money have gone when they have spent
and ultimately have to sustain in little money minimizing their essential needs.
Users has to keep a log in a diary or in a computer also all the calculation needs
to be done by the user which may sometimes results in errors leading to losses.
Due to lack of a complete tracking system. There is a constant overload to
rely on the daily entry of the expenditure and total estimation till the end of the
month
1.4 OBJECTIVES

The objectives of this system are:

 To keep track of daily expenses and budgeting;

 To save money for predefined expenses which will help planning on

your future investments.

1.5 SCOPE

This application can take a good market as it is usable by anyone who are
Willing to manage their expenses and aiming to save for the future investments
And many more there is not any range criteria or any kind of profession or
gender are focused , it wil used hugely.

1.6 LIMITATIONS

 User have to entry every record manually.

 The category divided may be blunder.

 CHAPTER 2
SURVEY OF TECHNOLOGIES
The technology chosen for the project are:

ASP.Net (ACTIVE SERVER PAGES) Technology

SQL Server (STRUCTURED QUERY LANGUAGE) Database

ASP.NET is an open-source server-side web application framework designed for

web development to produce dynamic web pages. It was developed by Microsoft
to allow programmers to build dynamic web sites, web applications and web
services.

ASP_NET is a technology which is used for both Front-end & Back-end

development in the software industry.

Front-end: ASP_NET provide large set of controls with .NET framework for
Front-end of any Web App or Website. (like, Grid View, Repeater, Data List,
Dropdown control…etc.)

Back-end: It also has lot of on back-end side with VB and C# languages. SQL-
Server is also one of the most secure databases with support of Microsoft. if you
want just back-end for mobile application or other Web app. It has web-services
too. WCF (Windows Communication Foundation) is latest technology used for
web services.

Microsoft SQL Server is a relational database management system developed

by Microsoft. As a database server, it is a software product with the primary
function of storing and

retrieving data as requested by other software applications—which may run either

on the same computer or on another computer across a network (including the
Internet).
Microsoft markets at least a dozen different editions of Microsoft SQL Server,
aimed at different audiences and for workloads ranging from small single-
machine applications to large Internet-facing applications with many concurrent
users.
❖
ASP.NET in comparison of JAVA
❖
Dot Net As A Proprietary Platform
❖
Dot Net the Most Secure Platform
❖
Dot Net Has Mature Runtime as CLR
❖
Dot Net Has Mature Programming Languages
❖
Dot Net Has Mature Single Framework as ASP.NET

ASP.NET in comparison of other programming languages: -


Keep you Asp.net applications secured with the built-in Windows
authentication and per-application configuration.
 
Asp.Net has reduced the long lines of code required to develop large
applications.

Asp.Net framework is language independent, means you can choose any

programming language which best suited to you application .

CHAPTER 3
REQUIREMENT ANALYSIS AND FEASIBILITY

3.1. Data Collection Methods

3.1.1 Source of Data

- User

Interview: Interview were carried out with some of the students in our
own college asking about the expenses that they do in day to day life.
While taking those samples we got that they always broke off at the
end of the month which means they do not end up calculating those
expenses that they spend day to day.

1.2 Requirement Specification

 Calender -:To enter date to keep record.

 Add expense -:add the expenses.
 Add Income -:add the income.
 Categaory -: the system shall allow users to add categories of
their expenses.
3.2. USECASE DIGRAM:

SIGN UP ADD EXPENSE ADD INCOME ADD DATE ADD CATEGARY LOGIN

<<include>>

AUTHENTICATION
SIGN UP ADD EXPENSE ADD INCOME ADD DATE ADD CATEGARY LOGIN

USER

<<include>>

AUTHENTICATION
ADMIN

USER

ADMIN

Name Description
Initiating actor User

Login To provide identification details and

enter the system
Authentication To validate the details entered by the
user
Add Expense TO Add new Expenses

2. Add Category TO Add Category Of expense

Add Date To add the date of expenditure.

3.3 Non – Functional Requirement

 Usability

There is a consistency in all the modules and webpages. To ease

the navigation there is a back tab to provide access to previous
page. There is proper instruction on each page.
  Reliability

Each data record is stored on a well-built efficient database there is

no risk data loss. The internal evaluation of data is well coded.

 Performance

In order to ease the accessibility the types of expense are

categorized along with an date.

 Avilability

The system is available all the time , no time constraint.

3.4 Hardware Specification

 Processor - Dual core

 Hard Disk - 50 GB

 Memory – 1GB RAM

3.5 Software Specification

 Window 2007

 Visual Studio 2010

 Sql 2008

3.6 Operational Feasibility

 This assessment has a simple UI. Anyone with the basic
knowledge of mobile phones.

3.7 Economic Feasibility

The only cost for building this project is for printing and binding
the report files .the user does not need to pay single money to use this
app.

3.8 Functionalities Of Daily Expense Tracker

 Core Functionalities of the system

Core features of any project is the heart of that project or you can say
the features without which system is incomplete.
Core features are complete user friendly , effective , multimedia site.

 Member’s Registration

In this functionality new members will be registered in the mobile so

that they can access all the functionalities of the system.

 Save Daily Expenses

This is the one of the main functionality of this system which will
save all the daily expenses which the user will like to save.
3.9 Categaory And Types Of Expenses

 Housing

Rent / mortgage , heating fuel , gas , electricity , water , phones

,furnishes , equipment , taxes , insurance.

 Transportation

Car and Insurance payment , public transportation etc.

 Fun and Entertainment

Cable TV, internet , computers , books ,newspaper , etc

 Apparel and services

Cloths , shoes , accessories etc.

Miscellaneous Expenses

 Educations
 CHAPTER 4

DESIGN

4.1 Use Case

To model a system, the most important aspect is to capture the dynamic

behavior. Dynamic behavior means the behavior of the system when it is
running/operating.
Only static behavior is not sufficient to model a system rather dynamic behavior
is more important than static behavior. In UML, there are five diagrams available
to model the dynamic nature and use case diagram is one of them. Now as we
have to discuss that the use case diagram is dynamic in nature, there should be
some internal or external factors for making the interaction.
These internal and external agents are known as actors. Use case diagrams
consists of actors, use cases and their relationships. The diagram is used to model
the system/subsystem of an application. A single use case diagram captures a
particular functionality of a system.
Hence to model the entire system, a number of use case diagrams are used.

Purpose of Use Case Diagrams

The purpose of use case diagram is to capture the dynamic aspect of a system.
However, this definition is too generic to describe the purpose, as other four
diagrams (activity, sequence, collaboration, and Statechart) also have the same
purpose. We will look into some specific purpose, which will distinguish it from
other four diagrams.
Use case diagrams are used to gather the requirements of a system including
internal and external influences. These requirements are mostly design
requirements. Hence, when a system is analyzed to gather its functionalities, use
cases are prepared and actors are identified.
When the initial task is complete, use case diagrams are modelled to present the
outside view.
In brief, the purposes of use case diagrams can be said to be as follows −
 Used to gather the requirements of a system.
 Used to get an outside view of a system.
 Identify the external and internal factors influencing the system.
 Show the interaction among the requirements are actors.
How to Draw a Use Case Diagram?
Use case diagrams are considered for high level requirement analysis of a
system. When the requirements of a system are analyzed, the functionalities are
captured in use cases.
We can say that use cases are nothing but the system functionalities written in
an organized manner. The second thing which is relevant to use cases are the
actors. Actors can be defined as something that interacts with the system.
Actors can be a human user, some internal applications, or may be some external
applications. When we are planning to draw a use case diagram, we should have
the following items identified.
 Functionalities to be represented as use case
 Actors
 Relationships among the use cases and actors.
Use case diagrams are drawn to capture the functional requirements of a system.
After identifying the above items, we have to use the following guidelines to
draw an efficient use case diagram
 The name of a use case is very important. The name should be chosen in
such a way so that it can identify the functionalities performed.
 Give a suitable name for actors.
 Show relationships and dependencies clearly in the diagram.
 Do not try to include all types of relationships, as the main purpose of the
diagram is to identify the requirements.
 Use notes whenever required to clarify some important points.
Following is a sample use case diagram representing the order management
system. Hence, if we look into the diagram then we will find three use
cases (Order, SpecialOrder, and NormalOrder) and one actor which is the
customer.
The SpecialOrder and NormalOrder use cases are extended from Order use case.
Hence, they have extended relationship. Another important point is to identify
the system boundary, which is shown in the picture. The actor Customer lies
outside the system as it is an external user of the system.
Where to Use a Use Case Diagram?
As we have already discussed there are five diagrams in UML to model the
dynamic view of a system. Now each and every model has some specific purpose
to use. Actually these specific purposes are different angles of a running system.
To understand the dynamics of a system, we need to use different types of
diagrams. Use case diagram is one of them and its specific purpose is to gather
system requirements and actors.
Use case diagrams specify the events of a system and their flows. But use case
diagram never describes how they are implemented. Use case diagram can be
imagined as a black box where only the input, output, and the function of the
black box is known.
These diagrams are used at a very high level of design. This high level design is
refined again and again to get a complete and practical picture of the system. A
well-structured use case also describes the pre-condition, post condition, and
exceptions. These extra elements are used to make test cases when performing
the testing.
Although use case is not a good candidate for forward and reverse engineering,
still they are used in a slightly different way to make forward and reverse
engineering. The same is true for reverse engineering. Use case diagram is used
differently to make it suitable for reverse engineering.
In forward engineering, use case diagrams are used to make test cases and in
reverse engineering use cases are used to prepare the requirement details from
the existing application.
Use case diagrams can be used for −
 Requirement analysis and high level design.
 Model the context of a system.
 Reverse engineering.
 Forward engineering.
 SIGN UP ADD EXPENSE ADD INCOME ADD DATE ADD CATEGARY LOGIN

<<include>>

AUTHENTICATION

USER

ADMIN

4.2 Sequence Diagram

A sequence diagram is a type of interaction diagram because it describes

how—and in what order—a group of objects works together. These
diagrams are used by software developers and business professionals to
understand requirements for a new system or to document an existing
process. Sequence diagrams are sometimes known as event diagrams or
event scenarios.

Benefits of sequence diagrams

Sequence diagrams can be useful references for businesses and other
organizations. Try drawing a sequence diagram to:

 Represent the details of a UML use case.

 Model the logic of a sophisticated procedure, function, or
operation.
 See how objects and components interact with each other to
complete a process.
 Plan and understand the detailed functionality of an existing or
future scenario.
Sequence Diagram Notations –

1. Actors –

An actor in a UML diagram represents a type of role where it interacts with the
system and its objects. It is important to note here that an actor is always outside
the scope of the system we aim to model using the UML diagram.

2. Lifelines –

A lifeline is a named element which depicts an individual participant in a

sequence diagram. So basically each instance in a sequence diagram is
represented by a lifeline. Lifeline elements are located at the top in a sequence
diagram. The standard in UML for naming a lifeline follows the following
format – Instance Name : Class Name

3 .Messages –

Communication between objects is depicted using messages. The messages

appear in a sequential order on the lifeline. We represent messages using
arrows. Lifelines and messages form the core of a sequence diagram.
Messages can be broadly classified into the following categories :

3. Synchronous messages –

A synchronous message waits for a reply before the interaction can move
forward. The sender waits until the receiver has completed the processing of
the message. The caller continues only when it knows that the receiver has
processed the previous message i.e. it receives a reply message. A large
 number of calls in object oriented programming are synchronous. We use a
solid arrow head to represent a synchronous message.

5.Asynchronous Messages –

An asynchronous message does not wait for a reply from the receiver. The
interaction moves forward irrespective of the receiver processing the previous
message or not. We use a lined arrow head to represent an asynchronous
message.

6. Guards –
To model conditions we use guards in UML. They are used when we need to
restrict the flow of messages on the pretext of a condition being met. Guards
play an important role in letting software developers know the constraints
attached to a system or a particular process.
retrieving
same data as
computer orrequested
on anotherbycomputer
other software
across applications—which
a network (includingmay run either on the
the Internet).

1
2
3
7
retrieving data as requested by other software applications—which may run either on the same
computer or on another computer across a network (including the Internet).

Microsoft markets at least a dozen different editions of Microsoft SQL Server, aimed at
different audiences and for workloads ranging from small single-machine applications to large
Internet-facing applications with many concurrent users.
❖
ASP.NET in comparison of JAVA
❖
Dot Net As A Proprietary Platform

❖
Dot Net the Most Secure Platform

❖
Dot Net Has Mature Runtime as CLR

❖
Dot Net Has Mature Programming Languages

❖
Dot Net Has Mature Single Framework as ASP.NET

ASP.NET in comparison of other programming languages: -

❖
Keep you Asp.net applications secured with the built-in Windows authentication
and per-application configuration.
❖
Asp.Net has reduced the long lines of code required to develop large applications.
❖
Asp.Net and Html, together generate dynamic web pages smoothly.

❖
Being an ideal server-side scripting technology, Asp.Net code first runs on
Windows server before displaying on the web browser.
❖
Asp.Net framework is language independent, means you can choose any
programming language which best suited to you application.
❖
With the built-in configuration information, Asp.Net is easy to deploy.
8
❖
The windows web server thoroughly monitors the web pages, multiple components,
and applications running over it.

❖
The Dot Net Framework quickly gives an alert for memory leaks, unbounded loops,
and other wrong behaviours, immediately killing them and restart them over again.
❖
Asp.Net features like early binding, JIT compilation, caching services and native
optimization supports gives your application the high level of performance.
❖
All the Asp.Net applications are highly monitored and managed to help application
available to handle requests.