Mid term project presentation

on
PaisaBox
Prepared by:
K S Satyanarayan
Reg no: 170970062
Manipal Institute of Technology, Manipal.

Under the guidance of

1
Internal guide External guide
Mr. Ganapathi Nayak K. Mr.Nandish
Assistant Professor Senior Scale Senior Software Engineer
Dept. of Computer Applications PaisaBox E-commerce Pvt Ltd
Manipal Institute of Technology Bengaluru – 560085.
Manipal – 576104.
 Index
2
Sl. No Contents Slide

1. Introduction 3

2. Existing system and proposed system 4

3. Objectives 5

4. System requirements 6-7

5. Use case diagram 8

6. Data flow diagram 9

7. Schema diagram 10

8. Functional modules 11 - 13

9. User Interface 14 - 17

10. Project timeline 18

11. Work remaining 19

3 Introduction

Raycharge is an e-commerce web based application. It is

a B2B provider who provides online facility to recharge any
prepaid mobile phone, post-paid mobile, DTH & Data
cards, water bill, electricity bill and much more in India. It is
focuses at providing an easy and reliable services to their
users.
4 Existing and Proposed System

 The existing system was built by using ASP.NET language where the
system uses only windows server. Since the server maintenance is
costlier than proposed system.

 The proposed system is built in PHP language. Since it’s a open

source language and highly popular language, also it is free and
performance of the system is more than ASP.NET System.
5 Objectives

 The objectives of proposed system is:

1. Providing all kind of recharge services through online.

2. Providing reliable and easy way to recharge every payment
through online.
3. Providing security for there payments and services.
6 System requirements

Hardware requirements

Requirement Minimum Recommended

Memory 512 MB 2GB or above

Disk space 1GB 10GB

Processor 800 MHz 1.7 GHz and above.

7 System requirements

Software requirements

Front end HTML, JavaScript and CSS3.

Framework Bootstrap 4.

Database MySQL.

Language PHP.
8 Use case diagram

Fig 1: Use case diagram

9 Data flow diagram

Fig 2: Data flow diagram

10 Schema diagram

Fig 3: Schema diagram

11 Functional modules
 Login: Using this module the user can login with the given username,
phone number and password.
 Add User: This module is used to add users under current distributer for the
role type FOS, Retailer and User.
 User Details: Displaying the users under distributer by searching users by
date, name and also download the result.
 Prepaid Balance: Prepaid Balance has the following modules which will do
the specific tasks.
 Transfer Balance
 Transferred Details
 Balance Received
 Balance Request
12 Functional modules
 Wallet Balance: Wallet balance has the same task as prepaid balance but
it will work for post-paid recharges.
 Transfer Balance
 Transferred Details
 Balance Received

 Commission Details: Displaying each operator commission details as a

table.
13 Functional modules
 Account setting: Account setting has the following modules.
 Change password: password can be changed using this module.
 Move User: User can be moved under different users using this module.
 DTH Booking: Distributer can add new customer with their provider and package
details. Distributer can search the existing customer.
 Aadhar upload: Distributer can upload Aadhar card, PAN card and GST number
images for verification process which can be done by Super admin.
 Profile: Distributer can update his/her personal details and also update their
profile images.
14 User Interface

Fig 4: Login Page Fig 5: KYC upload Page

15 User Interface

Fig 6: Add user Page

16 User Interface

Fig 7: Transfer balance

Page
17
User Interface

Fig 8: profile setting Page Fig 9: DTH Booking Page

18 Project timeline

Date Work Assigned

January 15th – January 31th Knowing the details about project and it’s
components.
February 1st – February 10th Started working on database design.

February 12th – March 3rd Working on designing webpages.

March 5th - till date Working on PHP back end coding.

19 Work remaining

Date Work remaining

 Following testing to be done
1. Unit testing.
Before 30-04-2018 2. System testing.
3. Integration testing.
4. Performance testing.