project srs
project srs
IT DEPARTMENT
Anisha Srivastava(1900270110005)
Urvi Singh(1900270110060)
Anushree Gupta(1900270110010)
1
TABLE OF CONTENT
2.0 Scope
2 2
2
1.0 Introduction
This project is an attempt to manage our daily expenses in a more efficient and manageable
way. Sometime we can’t remember where our money goes. And we can’t handle our cash flow.
For this problem, we need a solution that everyone can manage their expenses. So we decided
to find an easier way to get rid of this problem. So, our application attempts to free the user
with as much as possible the burden of manual calculation and to keep the track of the
expenditure.
Instead of keeping a diary or a log of the expenses, this application enables the user to not just
keep the control on the expenses but also to generate and save reports. With the help of this
application, the user can manage their expenses on a daily, weekly and monthly basis. Users can
insert and delete transactions as well as can generate and save their reports.
2.0 Scope
3
2.5 Multiple Accounts
Users can create multiple accounts. In the account tab. User has the option available for creating
a new account. Users will click the “+” sign button then a dialog will appear on the screen and
the user can enter the name of the account then that name will be saved in the account tab. If a
user wants to delete the particular account then the user has to l click the account name user
want to delete. Then that account will be deleted.
2.6 Transactions overview as Pie/Bar/Graph
The user has three options available for graphical representation. When the user rotates the
device then the pie chart will appear on the screen and also switch is available on the screen
when the user will click on the bar chart will appear on the screen and when the user clicks on
graph then Graph will appear on the screen.
2.7 Themes
At the top bar, the user has a setting option when the user clicks that then background option
will appear user can select different background colors. After selecting the particular color
background color will be changed.
2.8 Passcode
The passcode is available in setting option at the top bar. When the user clicks on the passcode
switch when the user switches on then the passcode screen will appear and the user can choose
the password and that password will be saved in the database. After that when the user will
open the application user have to enter the passcode and that passcode will be matched with
passcode saved in the database. If the user entered the wrong passcode then the error message
will appear.
2.9 Currency Symbol
The currency symbol option is available at the top bar setting button. Users can select different
currency symbols. If the user selects the dollar symbol then that symbol will appear on the
spending tab.
4
3.0 Product Perspective
3.1 System Type
3.2 Client-Side
Android Mobile
3.3 Software
Android Studio
3.4 Database Server
SQLite Database
3.5 Flaws in the current system
5
4.0 Use case diagram
Fig 4.1
The user has the access to adding and modifying his income as per the required field. The
account book holder is the database that controls all the record and give the notification
according to the situations.
The user can also ask for record in visual formal in the form of a graph showing the income and
expense respectively.
6
5.0 Activity diagram
Fig 5.1
The process of the expense trackers begins with the activity of creating an account. The user
then has an option to chose from either expense or deposit.
Below the expense, the user makes a choice of the kind of expenditure done and then display
the transactions.
The income is added to the balance.
With this the complete transaction can be shown in a graph.
7
6.0 Class Diagram
Fig 6.1
The class diagram represents the static view of an application. It describes the attributes and
operations of a class and also the constraints imposed on the system.
Expense class is an abstract class and it has two concrete classes (inheritance
relationship) DailyExpense and MonthlyExpense.
Expense and ExpenseList are identified as the two elements of the system. They have a
one-to-many relationship.
The two inherited classes have all the properties as the Expense class
8
7.0 Sequence Diagram
Fig 7.1
Sequence diagrams are a popular dynamic modelling solution in UML because they specifically focus
on lifelines, or the processes and objects that live simultaneously, and the messages exchanged between
them to perform a function before the lifeline ends. It analyze the information, provide analytics on which
category did the user spent most of their money. Here different sessions are depicted, for an instance the
user adds the information about spending 100/- and in the next go he mentions spending 50/-, so now
these two sessions individually will not be stored within but will be stored as an amount spent together.
9
8.0 Deployment Diagram
Fig 8.1
UML diagram type that shows the execution architecture of a system, including nodes such as
hardware or software execution environments, and the middleware connecting them. It
visualizes the topology of the physical components of a system, where the software components
are deployed. The application is assumed to be a web-based application, which is deployed in a
clustered environment using a server. The user connects to the application using the Internet.
The control flows from the caching server to the clustered environment.
10
9.0 Collaboration Diagram
Fig 9.1
The collaboration diagram is used to show the relationship between the objects in a system.
Both the sequence and the collaboration diagrams represent the same information but
differently. Instead of showing the flow of messages, it depicts the architecture of the object
residing in the system as it is based on object-oriented programming. An object consists of
several features. Multiple objects present in the system are connected to each other. The
collaboration diagram, which is also known as a communication diagram, is used to portray the
object's architecture in the system.
11