TASK : ONLINE MOBILE RECHARGE SYSTEM.

AIM : To Create a System to Perform the Online Mobile

Recharge system .

Procedure :
(i.) Problem Statement :
Design and develop an online mobile recharge system that allows
customers to recharge their mobile phones safely and efficiently. The system should support
various recharge plans, payment gateways, and provide a user-friendly interface for customers
to easily recharge their mobile phones. By addressing all the problems and requirements, the
online mobile recharge system will provide a convenient, secure, and efficient way for
customers to recharge their mobile phones, while also streamlining the recharge process for
administrators.

(ii) Software Requirement Specification :

Introduction :
In today's digital age, mobile phones have become an essential part of our daily lives,
and maintaining a stable mobile connection is crucial for communication, work, and
entertainment. However, the traditional mobile recharge process can be time-consuming,
inconvenient, and often limited by payment options. To address these challenges, we propose
the design and development of an online mobile recharge system that provides a secure,
efficient, and user-friendly platform for customers to recharge their mobile phones. Through
this project in Case Tools Lab, we aim to create a comprehensive online recharge solution that
streamlines the recharge process, offers multiple payment gateways, and enhances the overall
customer experience.

Purpose :
The purpose of this project is to design and develop a user-friendly, secure, and efficient
online mobile recharge system that enables customers to recharge their mobile phones
conveniently, anytime and anywhere, using various payment gateways, and to provide a
comprehensive platform for administrators to manage recharge plans, customer accounts,
and system settings, thereby enhancing the overall customer experience and streamlining the
recharge process.
Scope :
➢ For designing and developing an online mobile recharge system.
➢ Implementing user registration and login functionality.
➢ Creating a recharge plan selection and purchase process.
➢ Integrating multiple payment gateways (credit/debit cards, net banking, wallets).
➢ Developing a recharge confirmation and notification system.
➢ Implementing a recharge history and balance check feature.
➢ Creating an administrator dashboard for managing recharge plans, customer
accounts, and system settings.
➢ Ensuring security, data privacy, and scalability of the system.
➢ Conducting testing and validation of the system.

Definition, acronyms and abbreviations :

➢ Definitions:
• Online Mobile Recharge: A digital platform that enables users to recharge their mobile
phones using various payment gateways.
• Recharge Plan: A package of mobile services (e.g., data, voice, SMS) offered by a
mobile operator.
• Payment Gateway: A system that facilitates online payments.

➢ Acronyms:
• OMRS: Online Mobile Recharge System
• MOP: Mobile Operator Portal
• PG: Payment Gateway
• API: Application Programming Interface

➢ Abbreviations:
• OTP: One-Time Password
• USSD: Unstructured Supplementary Service Data
• SMS: Short Message Service
• IVR: Interactive Voice Response

Technologies to be used :
• HTML5
• JSP
• JavaScript
 • ReactJS (front-end framework)
• Material-UI

Tools to be used :
• Eclipse
• Rational Rose Tools

Overview :
Overview provides a high-level summary of the project, including its objectives,
functional and non-functional requirements, tools and technologies, methodology, timeline,
and team structure.

Overall Description :
The system provides a user-friendly interface for customers to select their recharge
plans, make payments, and view their recharge history. The system also provides an
administrator dashboard for managing recharge plans, customer accounts, and system
settings.

Software Interface:
• Front-end: HTML5, CSS3, JavaScript
• Database: MySQL
• Payment Gateway: PhonePay , Paytm, Google pay
• SMS Gateway: Messenger
• Operating System: Windows/Linux/MacOS

Hardware Interface:
The server is directly connected to the Client system . The client system has access to the
data base of server .

System Functions :
 • Recharge Plan Selection: This function allows users to select from various recharge
plans offered by different mobile operators. The system displays the available plans,
and the user can choose the desired plan based on their needs.
• Payment Processing: This function processes the payment for the selected recharge
plan. The system integrates with various payment gateways, such as credit/debit cards,
net banking, and wallets, to facilitate secure and efficient payments.
• Recharge Confirmation: This function sends a confirmation notification to the user via
SMS and email after the payment is successful. The system also displays a recharge
confirmation message on the screen, ensuring that the user knows that the recharge
is successful.
• Recharge History: This function allows users to view their recharge history, including
the date, time, and amount of each recharge. The system provides a detailed record
of all recharges made by the user.
• Balance Check: This function enables users to check their current account balance. The
system displays the available balance, and the user can recharge their account if
needed.

User Characteristics :
• Active Mobile User : The user has a valid mobile number and uses their mobile phone
regularly.
• Internet Savvy : The user has access to the internet and is comfortable using online
services and making digital payments.
• Regular Recharger : The user recharges their mobile phone regularly, either weekly,
monthly, or as needed.

Constraints :
• Users may not be tech-savvy or familiar with online recharge processes, requiring an
intuitive and user-friendly interface.
• Users may be hesitant to share personal and financial information online, requiring
robust security measures to ensure data protection.
• Users may experience internet connectivity issues or slow data speeds, requiring a
system that can adapt to varying network conditions.

(iii.)Use Case Diagram :

A use case diagram is a visual representation of the functional requirements of
a system, showing how users (actors) interact with the system to achieve specific goals. It is
a type of UML (Unified Modeling Language) diagram that illustrates the relationships between
The Actors to be used in Use Case Diagram:
 • Customer (primary actor): The person who wants to recharge their mobile phone.
• Administrator (secondary actor): The person responsible for managing the system,
recharge plans, and customer accounts.
• Payment Gateway (secondary actor): The system that processes customer payments.

The Use Cases to be used in Use case Diagram :

• Recharge Mobile: The customer recharges their mobile phone.

• View Recharge History: The customer views their previous recharge transactions.
• Manage Recharge Plans: The administrator manages and updates recharge plans.
• Process Payment: The payment gateway processes customer payments.
• Send Recharge Confirmation: The system sends recharge confirmation to the
customer.
• Manage Customer Accounts: The administrator manages customer accounts and
profiles.

Use Case Diagram :

Activity Diagram :
An activity diagram is a type of UML (Unified Modeling Language) diagram that shows the
dynamic aspects of a system, including the flow of control and data between activities. In the
context of case tools lab, an activity diagram can be used to model the behavior of a system,
such as a online mobile recharge system.
An activity diagram is a visual representation of the sequential and concurrent activities
involved in the online mobile recharge process. It shows the flow of control and data between
various activities, such as:

• Customer selects recharge plan

• Customer enters payment details
• Payment gateway processes payment
• Recharge confirmation sent to customer
• Customer receives recharge confirmation
• System updates recharge history
• Administrator manages recharge plans
• Administrator views recharge history

Activity Diagram :
Class Diagram :
A class diagram is a type of static structure diagram that represents the structure of a
system by showing the classes, attributes, operations, and relationships between them. It is a
graphical representation of the classes and their relationships in an object-oriented system.

• Classes: Represented by rectangles, classes are the basic building blocks of the system.
• Attributes: Represented by compartments within the class rectangle, attributes are the
data members of the class.
• Operations: Represented by compartments within the class rectangle, operations are
the functions or methods of the class.
• Relationships: Represented by lines and arrows, relationships show how classes
interact with each other.

The Classes are involved in the class diagram:

➢ Customer : It has Containing Four attributes and Two operations.

o Attributes: Customer ID, name, phone Number, email
o Operations: recharge Mobile, view Recharge History

➢ Recharge Plan: It has Containing Four attributes and Two operations.

o Attributes: plan ID, plan Name, description, amount
o Operations: get Plan Details, get Recharge Amount

➢ Payment Gateway: It has Containing Three attributes and Two operations.

o Attributes: payment Gateway ID, name, API Key
o Operations: process Payment, verify Payment

➢ Transaction: It has Containing Five attributes and Two operations.

o Attributes: transaction ID, customer ID, plan ID, payment Gateway ID,
status
o Operations: recharge Mobile, update Status

➢ Recharge History: It has Containing Four attributes and Two operations.

o Attributes: recharge History ID, customer ID, plan ID, transaction ID,
recharge Date
o Operations: view Recharge History, get Recharge Details

Relationships:

➢ A Customer can have multiple Recharge Plans (association)

➢ A Recharge Plan is part of a Payment Gateway (composition)
➢ A Transaction is associated with a Customer and a Recharge Plan (association)
 ➢ A Recharge History is associated with a Customer and a Transaction
(association)

Class Diagram :
State Chart Diagram :
A state chart diagram, also known as a state machine diagram or state transition diagram,
is a behavioral diagram that shows the different states of a system or an object and the
transitions between them. It is used to model the dynamic behavior of a system, highlighting
how it changes state in response to events or conditions.

Deployment Digram :
A deployment diagram for an online mobile recharge system shows how the system's
components are deployed across various nodes (e.g., servers, devices, etc.) and how they
interact with each other. Here's a possible deployment diagram for the online mobile recharge
system.
Component Diagram :
A component diagram for an online mobile recharge system shows how the system's
components interact with each other to provide the recharge functionality. Here's a possible
component diagram for the online mobile recharge system:
This component diagram shows how the online mobile recharge system's components
interact with each other to provide the recharge functionality. The diagram highlights the key
components, interfaces, and connections involved in the system.
This is just one possible component diagram for the online mobile recharge system.
Depending on the specific requirements and architecture, the component diagram may vary.
Components:

• Customer Interface
• Recharge Controller
• Payment Gateway Integration
• Recharge Engine
• Database Access
Collaboration Diagram :
A collaboration diagram for an online mobile recharge system shows the interactions
and relationships between the system's components and external entities (e.g., customer,
payment gateway) to perform a specific task, in this case, an online mobile recharge.
This collaboration diagram shows the interactions and relationships between the online
mobile recharge system's components and external entities to perform an online mobile
recharge. The diagram highlights the key participants, interactions, and relationships involved
in the process.
This is just one possible collaboration diagram for the online mobile recharge system.
Depending on the specific requirements and architecture, this about the collaboration
diagram .
Sequence Diagram :
This sequence diagram shows the sequence of events and interactions between the online
mobile recharge system's components and external entities to perform an online mobile
recharge. The diagram highlights the key events, interactions, and participants involved in the
process. A sequence diagram for an online mobile recharge system shows the sequence of
events and interactions between the system's components and external entities (e.g.,
customer, payment gateway) to perform a specific task, in this case, an online mobile recharge.