CDAC-ACTS, PUNE

Requirement specification
For the project

EXPENSE Tracking
 Introduction

The goal of this document is to give description of Expense Tracker. This project is used to
provide facilities to the registered customers such as to view the goods supplied by vendor, to place
order , make online payment, keep track of its expenses and view expenses whenever required. It is
also helpful for vendor to accept orders from different customers , accept online payment and keep
tracking of expenses of different clients.

Most of the E-Commerce web sites are based on phenomenon such that shop and make
payment immediately. In India, there is a good understanding and co-ordination between client and
vendors that they shop day to day necessary things and pay after some period. This helps vendors to
make more and permanent customers and helps customers to make payment as per their comfort.

An important thing is to keep the track of customers. As the number of customers increases
it becomes difficult. Most of the times vendor keep the records in a book which is difficult to manage
and any one can change the content of it. Also the usage of paper is more which is not eco-friendly.
So this project helps to vendors to keep records of customers expenses in secured , easy manner.
Client can also enjoy shopping without worrying of keeping expense records. Hence the project gives
a reliable solution to both customer and vendor.

Apart from this, the project provides a platform to vendor to showcase its goods to
customers from different locations. Also let customers to shop from home which is time saving,
comfortable.

This project is a small step to reduce the communication difference between customers and
vendors and helps to maintain a good co-ordination between customers and vendor by allowing our
traditional Indian payment method .
 Functional Requirements
The Functional Requirement (also called Functional Specifications or Functional Requirement
Specifications), defines the capabilities and functions that a System must be able to perform
successfully.

The functional specification describes what the system must do; how the system does it is described in
the Design Specification.

It should include functions performed by specific screens, outlines of work-flows performed by the
system and other business or compliance requirements the system must meet.

General Application Requirements:

1. The application should provide facility for clients to place orders.
2. The application should allow the vendor to accept the orders .

User Roles:

1. Vendor(admin)
2. User (client)

Requirements Details:
1. Software should be used by authentic users.
2. Vendor(admin)
i. Vendor should be able to create clients.
ii. Vendor should be able to update or delete clients, in case of any changes in personal
information.
iii. Vendor should be able to see clients details.
iv. Vendor should be able to change the prices of the commodities/items.
v. Vendor should be able to see the expense details per client.
vi. Vendor should be able to accept the payments.
vii. Vendor should be able to block the clients when required.
3. Clients:
i. Client should be able to register and login.
ii. Client should be able to search a commodity/item in the store and if not found,
he can request for the item and get to know after how many days it will be
available.
iii. Client should be able to update his details.
iv. Client should be able to place and delete orders.
v. Client should be able to see the new discounts.
vi. Client should be able to see the expenses.
User Interface Requirements:

Each of the above mentioned requirements are discussed below:

1. Software should be used by authentic users.

Only the users who are allowed to use the software should use it. To meet this requirement we build
a login page which asks the username and password before using the software.

Figure 1: Login page design

Software checks the username and password in the database. If credentials are there in database,
user can login. Otherwise software will prompt the user to enter valid username and password.

2. Vendor
2.1. Vendor should be able to create client.

Password :

Figure 2: Client Registration Form design

A unique Customer ID and Login Password will be auto generated for each and every client.

2.2 Vendor should be able to update or delete client details, in case of any changes in personal
information.

Figure 3: Update or delete

Form design

If vendor selects delete then record

of client with that Customer ID will be
deleted from the database. If admin
selects update then a following
form will get appeared for updating
contact information of particular
client.

Figure 4: Update Form design

After clicking the update button vendor will get a alert box “updated successfully” if record is
updated successfully or “updating failed” in case of update failure.

2.3 Vendor should be able to see client details.

If vendor wants to see the details of clients, he must be able to see his\her details by entering his\
her unique id given at the time of registration.

Figure 5: Search Form design

 Figure 6: Update Price Form design
Only vendor will have the right to change the price structure for the clients. For this he has to
select the product whose price he wants to update. Then he has enter the new price then click
on update. If he clicks on cancel then form will be again reset.

3. Clients

Clients are the ones who will be able to access all the services provided by the vendor.

3.1 Client should be able to search a product, if one doesn’t find that product then one can
request for product and get to know after how many days that product will be available.

Figure 7: Search Product Form design

To search a product, client has to enter name of the product. When he clicks on search button if
that is found in store, then a message will be displayed “Product is available”. If product is not
currently available, then a message “Product currently not available” will be displayed.
When clients click on request then he will get to know after how many days he can get that
product.
For Example: If product will be available after 2 days then the client who has requested for that
product then he will be displayed a message ”Product will be available after two days.”

3.2 Client should be able to edit his details.

If a student wants to edit his/her details, there is a link for this. Client will have to fill a form and
give the required information.
 Figure 8: Accounts Form design

Figure 9: Price Details design

To pay online client must have a debit card. He has to fill required details about his account and
debit card such as card number, pin or expiry date etc as required by the payment gateway of the
particular bank.

Figure 10: Pay Form design

If debit card has sufficient balance then fee will be submitted and that will be deducted from his/her
account and message “payment received” will be displayed. If account has insufficient balance then
error message “Payment failed, try again” will be displayed.