2022

VISION
FOR

ELECTRICITY BILL
MANAGEMENT SYSTEM
Version 1.0

Prepared by
Usman Ahmad
&
Muhammad diyan irfan
13 th June, 2022
 Revision History
Version Description Author Date
The Electricity Billing Usman Ahmed
1.0 System has been Muhammad diyan 13th june,2022
developed to irfan
override the
problems prevailing
in the practicing
manual system

Table of Contents
1. Introduction4
 1.1 Purpose4
1.2 Scope4
1.3 Definitions, Acronyms and Abbreviations4
1.4 References4
1.5 Overview5
2. Positioning5
2.1 Business Opportunity5
2.2 Problem Statement5
2.3 System Position Statement6
3. Stakeholder and User Descriptions6
3.1 Stakeholder Summary7
3.2 User Summary7
3.3 Stakeholder Profiles7
3.3.1 Administrator7
3.3.2 Data Entry Operator8
3.4 Key Stakeholder / User Needs8
4. System Overview8
4.1 System Perspective9
4.2 Summary of Capabilities9
4.3 Assumptions and Dependencies9
4.4 Cost and Pricing9
4.5 Licensing and Installation9
5. System Main Features10
6. System Priorities10
7. Constraints10
8. Quality Ranges10
9. Other Item Requirements11
9.1 System Requirements11
9.1.1 Platform11
9.1.2 Printer11
9.1.3 Hardware requirements

1. Introduction
 This system is named as Electricity Bill Management System. This system is made to keep the
records about the bills of the customers. The admin can manage all the accounts and the
registered users like employees and customers can only manage their own accounts.
In the existing system the data is entered only manually which is difficult to main correctly.
The proposed system computerize the data using this application.

1.1 Purpose
The purpose of propose system is to develop a system of improve facilities. The propose
system can overcome all the limitations of the existing system. The system provides proper
security and reduces the manual work.

1.2 Scope
It will help a person to know the management of passed year perfectly and vividly. It also
helps in current all works relative to Electricity Billing system. It will also reduce the cost of
collecting the management & collection procedure will go on smoothly. Our project aims at
business process automation.

1.3 Definitions, Acronyms and Abbreviations

Term/ abbreviation Description

EBMS Electricity Bill Management System

RUP Rational Unified Process

1.4 Reference
Planning a project with RUP by David West (PDF)
Books
Planning a project with RUP by David West (PDF)
SE A Practitioner's Approach 7th Edition - Roger Pressman

1.5 Overview
Our project is only a humble venture to satisfy the needs to manage their project work. Several
user friendly coding have also adopted.

2. Positioning
1.1 Business Opportunity

The previous system in use is totally manual and it is hard to use and manage. The new system
are much closer to electricity customers. These includes services and products that help
customers manage and reduce their electricity consumption or help them generate their own
power.
2.2 Problem Statement

The old manual system was suffering from a series of drawbacks. Since
whole of the system was to be maintained with hands the process of
The problem keeping, maintaining and retrieving the information was very tedious
of and lengthy.

The records were never used to be in a systematic order. There used to be

lots of difficulties in associating any particular transaction with a particular
Effects context.

If any information was to be found it was required to go through the

The impact of different registers, documents there would never exist anything like
which is report generation. There would always be unnecessary consumption of
time while entering records and retrieving records. One more problem
was that it was very difficult to find errors while entering the records.
Once the records were entered it was very difficult to update these
records.

A system which provides simplicity and efficiency with compromising the

security of the business. An error free system and will providing best
A successful management of Electricity Bills, Customers, and Employee etc. This system will
solution be reliable, and efficient.
should be
2.3 System Position Statement

For Bank , Rawalpindi, Pakistan

Who The existing environment has no such system being used, which
provides automatic management of billing records, payment’s
records, customer’s record, Employee’s record etc.
The
Electricity Bill Management System (EBMS)
(Product name)

That Keeps a large number of records of items, customer, Employees

Unlike Manual EBMS, that is not suitable for holding large number of records
due to storage problems, lack of security, performance issues

Our Product Uses new technologies for development. This system is going to be
built by keeping in mind the latest business requirements. By
providing better performance, security, reliability so that the business
runs efficient and fast
2. Stakeholder and User Descriptions
2.1 Stakeholder Summary

Name Represents Role

Gives the user all the It manages the employee’s data, their salary,
Admin authority he needs to leaves the electricity bill.
control the system
Uses the electricity He pays the bill for the electricity.
Consumer weather for daily basis
and for commercial
purpose in the
industry.
Contributes in proper They help in managing the electricity records and
Employee calculation and also filters the feedback which is send to the
coordinating the work concerning departments by the consumers.
along with establishing
proper connection with
the consumers.

2.2 User Summary

Name Description

Admin This actor governs the system in a ritualize manner therefore it visualize the
interface of login and then after the dashboard shows the options which are
necessary to regulate the interface and flow of data into the system.

consumer This actor is responsible for the payment of the bill on time and gives feedback
as required about the services, he can also connect with me admin directly of
he faces any system issue this feature is provided on the home screen of the
consumer dashboard.

Employee The employee manages the data of the consumers and also the bill
management along with the queries of the consumer, the user interface allows
the employee to access the data of the employees which is required also he can
connect with the admin as per requirement.
3.3 Stakeholder Profiles
3.3.1 Administrator

Representative Mr. Ahmed Ali

Type Primary Actor

Description Keep the records of all the bills of the customers.

Responsibilities Manages the employee’s data, there salary, leaves and the electricity
bill.

The Administrator is the stakeholder who will define the success if he

Success Criteria will totally satisfy with the system

Involvement Managing business processes without direct human involvement.

Deliverables There will be no deliverables provided by this stakeholder. Thus he

saves human efforts and resources.

Comments Issues With respect to this stakeholder this project is reliable that it should
always deliver the correct and timely Information

3.3.2 Employee

Representative Mr. Muhammad Shahid

Type Primary Actor

Description A person who will use the system could enter different records
Responsibilities Managing account balances to discover outstanding debts or other
inconsistencies and checking the data input in the accounting system to
ensure accuracy of final bill.
Success Criteria Successful and satisfactory entry of data

Involvement The employee is the stakeholder who is involved in the project by

entering entries of different things like customer’s details, bill details
and feedback/complains of the customers etc.
Deliverables There will be no deliverables provided by this stakeholder

Comments Issues With respect to this stakeholder this project is reliable that it should
always deliver the correct information

1.1 Key Stakeholder / User Needs

Existing manages records manually and can’t be updated efficiently as required. EBMS
will provide, maintain, efficiently update handling different situations etc. and will be
easy to access each and every record available in EBMS when needed at once or at
different times.

3. System Overview
This system is being made to replace the old manual system. The main idea is to have easy
access to the records and managing them efficiently. This alternate to the manual system will
provide the main feature of digitally accessing the different records, which was not possible
before. The users will have their own accounts, separate according to user category, where
they will be able to enter records according to privileges
The main purpose of this system to convert the manual billing system into the computerized
system, it should do following things

 Employee records
 Adminship
 Add feeders
 Register consumer
 Deactivate meter
 Activate meter
 Check status
 Add rates for both commercial and home meters
 Add different government taxes
 Unit history
 Bill history
 Generate bill
 Paid bill
 Maintain paid and unpaid history of a consumer
 Total payments
 Reports
This should also perform some reports such as
 Employees of a department
 Specific amidships
 Check feeders
 Generate Reports for rates and taxes
 Find total connections
 Disconnection list
 Total active and DE active list
 Monthly reports for income
 Annual report for income
These are different user of this organization

 Admin
 Connection offices
 Billing officer
 Finance officer
  Computer operator
 Super admin
4.1 System Perspective
This EBMS is a completely new system for the users. It has the database of billing methods,
customer’s details, Employee’s details etc.
4.2 Summary of Capabilities

Benefit Supporting Features

Users will digitally access information Digital information is easy to access

Administrator would manage the system Computerized system plus digital information
easily as compared to existing manual system management using computers makes
management easier

System can generate different types of Computerized system settings will always
reports according to given criteria makes the business running efficiently

4.3 Assumptions and Dependencies

The Default language of the EBMS is English so the user of the system should be able to
read, write and understand the proper meaning.
On the developing side the implementers should be familiar with the programming languages
used.
4.4 Cost and Pricing
This is our Semester Project & have no Cost & Pricing
4.5 Licensing and Installation
All the installation rights will be mentioned in the license agreement. Installation of the
system will take place after complete development

5. System Main Features

 Login management
 Electricity Bill management
  Employee management
 Customer Management
6. System Priorities

1. Login Management
 Priority: High
 Process Login

2. Electricity Bill management

 Priority: High
 Billing Method
 Priority: High
 Electricity Bill
 Priority: High
Information
 Priority: High
 Bill’s Payment Date

3. Employee management
 Priority: High
 Add Employee
 Priority: High
 Update Employee
 Priority: High
 Search Employee
 Priority: High
 Generate Report

4. Customer Management
 Add Customer  Priority: High
 Update Customer  Priority: High
 Search Customer  Priority: High
 Generate Report  Priority: High
7.
Constraints
The system is only compatible for the Windows Platform. Since we are using powerful
tools i.e. Visual Studio 2012 with JavaScript and MS SQL Server therefore the system on
which this whole EBMS is installed must be at least single core 2 GHZ.

8. Quality Ranges
 Accuracy
We created this system while keeping in view the specified requirements. The
result would be shown according to the requirements collected by the stakeholder.

 Performance
2022

EBMS has a GUI which is quite simple to understand for the user. The user
will be satisfied while using this system.

 Security
Our EBMS is computerized so we are providing the security feature as well.
Without proper authentication no one can access the system

 Usability
The system will be easy to use. The EBMS has a simple GUI, which is menu based
and has all of the components arranged logically so that the users of the system will not
have any problem in handling the system. The overall experience of the usage will be
satisfactory.
 Availability
As the system is a desktop application it will run for as long as the user wants it
to run
9. Other Item Requirements
9.1 System Requirements
9.1.1 Platform
The system must use windows platform
9.1.2Printer
It will use printer for printing purposes.
9.1.3 Hardware requirements
 Intel Pentium Process
 32 MB RAM or higher
 1.2 GB Hard Disk or greater

Video Display Unit

Specifications
FOR

ELECTRICITY BILL MANAGEMENT SYSTEM

 Version 1.0

Prepared by

Usman Ahmed

&

Muhammad Diyan Irfan

Revision History

Version Description Author Date

1.0 The electricity billing Usman Ahmed 15th June, 2022

system has been Muhammad diyan
developed to irfan
override the
 problems prevailing
in the practicing
manual system.

1. Introduction
Electricity bill management system is made to keep the records of the bills of the customers.
The admin can manage all the accounts and the registered user like employees and customers
can manage their accounts. This system helps in maintaining the bills and the payments.
My engineering project gives you this project where the different module is there for
employees to check the customer’s if their job requires. Admin, employees, and customers all
have a different interface and different privileges according to their needs.
The overall project report is divided into some parts. These parts are further divided into their
subparts. In the parts we have described the purpose, scope of the project.

1.1 purpose
The purpose of propose system is to develop a system of improve facilities. The propose
system can overcome all the limitations of the existing system. The system provides proper
security and reduces the manual work.

1.2 scope
Scope of the project electricity bill management system it may help collecting perfect
management in details. In very short time, the collection will be obvious, simple and sensible. It
help a person to know the management of passed year perfectly and vividly. It also help in
current all works relative to Electricity Billing System.
Scope of any software depends upon the following things:
1. It satisfy the user requirement
2. be easy to understand by the user and operator
3. be easy to operate
4. Have a good user interface
5. Delivered on schedule within the budget.

The system has various modules as:

 Login management system
 User management system
 Admin management system
 Queries management system
 Department management system
 Meters management system
 Login management module
After registration, one can log in to the system as the end-user of the system on the
behalf on the behalf of the user. The user will get only those privileges that are given
to the user for which one has registered.
 user management module
The user can be anyone either a customer or an employee. If the user is an employee
then he can make changes to the data like adding units in the bill, used by a customer.
 Admin management module
This module can only have one account and this account has all the privileges which a
user account might not have. First of all, the admin account is created and then if the
admin verifies a registering user his account will be created otherwise not.
 Queries management module
In this module, the customers can ask any query he has he has and his question with
his details will sent to the person who is managing queries and then he or she can
reply to the query of a customer.
 Department management module
In this section, all the employee’s details can be seen by the privileged user. All the
employees are divided into different sections according to their job profile. Employees
working in multiple section might get repeated into the different departments.
 Meters
In this, new customers can be added, monthly bills can be sent to the customer’s
accounts, any particular customer can be found using a unique meter id and the
remaining balance of a customer can be checked.

Term/Abbreviation Definition

EBMS Electricity bills management system

Hypertext markup language

HTML
 CSS (Cascading style sheets)create attractive layout

MYSQL My SQL is a database, it is used for

Hypertext processor (PHP) is a technology that allow

PHP software developers to create dynamically generated web
pages. PHP is open source software.
Bootstrap Responsive design mobile friendly site

JavaScript It is a programming language, commonly use with web

browser.

1.3 References
Websites:
 https://www.javatpoint.com/paymentbilling-product-project
 Database Programming with JDBC and Java by O'Reilly
 Head First Java 2nd Edition

Books:
Planning a project with RUP by David West (PDF)
SE A Practitioner's Approach 7th Edition - Roger Pressman
1.4 overview
Our project is only a humble venture to satisfy the needs to manage their project work.
Several user friendly coding have also adopted.

1.5 System’s main features

 Login management
 User management
  Admin management
 Queries management
 Department management
 Meters management

2. Functional Requirements
2.1 Login Management

2.1.1 Process Login

SRS-1 User can enter the system by entering the username and password

SRS-2 The user name should be unique

SRS-3 Authentication should be provided and the suitable access of the system should
be given according to privileges

2.2 Electricity bill management

2.2.1 Electricity bill information

SRS-4 Admin and employee can search for customer’s bill details.

SRS-5 System should allow admin and employee to get the electricity bill details of
the customer i.e., Electricity bill amount and bill number.
SRS-6 System should show the details based on bill number.

SRS-7 System should show bill details.

2.2.2 Billing method

SRS-8 Admin and employee can allow customer to use any billing /payment method.
 SRS-9 Billing method should have following attributes payment method (cash or
payment by credit card), and payment date.

SRS-10 Billing method’s documents should be proper and legal.

SRS-11 System should save this information.

SRS-16 System should generate reports of customer’s bill such that how much was the
bill, which payment method is used by the customer to pay his bill and also
save the date of bill’s payment.

2.2.3 Generate bill reports

2.3 Employee management

2.3.1 Add dealer

SRS-17 New dealer can be added into the system by admin.

SRS-18 Details of the employee i.e. Name, CNIC Number, contact number, and Bank’s
name should be entered.
SRS-19 System should save this information.

2.3.2 Search Employee

SRS-20 The employee to be updated will be searched first.

SRS-21 System should give facility of searching employee information on the basis of
employee’s CNIC.
SRS-22 Admin can search for an employee.

SRS-23 The system should display search information.

2.3.3 Update employee

SRS-24 The updating of the employee should be according to this parameters
 SRS-25 Admin should be able to update the employee information

SRS-26 System should update this information

2.3.4 Generate Employee Report

SRS-27 System should generate reports of the employee by Name, CNIC Number,
Phone Number, and Company name. They can be viewed by the admin of the
EBMS on runtime.

2.4 Customer management

2.4.1 Add Customer
SRS-28 New customer can be added into the system by employee.

SRS-29 Details of the customers i.e. Name, CNIC Number, Phone number and city.

SRS-30 System should save this information.

2.4.2 Search Customer

SRS-31 System should give facility of searching customer information the basis of
customer CNIC
SRS-32 Administrator and employee can search for a customer

SRS-33 System should display search information

2.4.3 Update Customer

SRS-34 System should give facility of searching customer information on the basis of
customer CNIC
 SRS-35 The updating of the customer should be according to his/her CNIC

SRS-36 Administrator should be able to update the customer information

SRS-37 System should update this information

2.4.4 Generate Customer Report

SRS-38 System should generate report of the customer by Name, Phone Number, City
and CNIC, they can viewed by the administrator of the EBMS.

2.5 Complain management

2.5.1 Complain details
SRS-39 User can submit complain about his bill to the employee who is working in
particular department.
SRS-40 Customer complain can be searched using customer’s CNIC

SRS-41 System should save this information

2.5.2 Response to complain

SRS-42 Only can response can response the customer complains.

SRS-44 System should display complain information

2.5.3 Generate Report

SRS-49 System should generate report of the complains by customer they can be
viewed by the admin of the EBMS.
3. Non-Functional Requirement
1. Security
The system have advanced security control mechanisms. This is by provided a password login
system for authorized users.
2. Usability
With proper guidance and use of manual.

3. Reliability
Availability The system facility will be available to its users for 24 hours
Bugs or defect rate Very little
Robustness Our system will generate appropriate exceptions

Accuracy The system will generate accurate results and will behalf
according to the user requirement
Correctness Our system will be according to all the requirements collected

4. Performance
 The EBMS has a simple GUI, which is self-explanatory and user friendly
 The lists, reports and results generated by the system will not take more than 2-3 sec
 The EBMS shall display confirmation messages to user within 1-2 sec after the user
submits information to the system. In other words robustness is maintained
 Resources required
Hardware Minimum Recommended
Processor 2 core 2GHz Dual core 2+GHz
RAM 1 GB 2GB
Hard-drive 20 GB As required
5. Design constraints
Specify design constraints imposed by other standards, company policies, hardware
limitation, etc. that will impact this software project.
6. User help manual
Detail system manuals are given to the system users and training session will be held to
ensure that the user of the system understands the system fully and can get the maximum
benefit from the system

7. External Interface Requirement

7.1 User interfaces
1. There will be a login screen where the user will enter login details. It will have the fields
a. User ID
b. Password
c. Category
2. There will be an input screen for entering student details where authorized user will
enter student details. The form has the following fields
a. Surname
b. Second name
c. F
d. G
3. This section must be very specific and all interactions screen must be included

7.2 Hardware interfaces

 Intel Pentium IV 3.0Ghz processor and above
 1Gb RAM above
 120 GB Hard Disk and above
 Computer network and internet connection
 UPS backup facility
 32 bit monitor with (at least)1024 by 768 resolution
 Internet connection
7.3 Software Interface
 Microsoft windows 2007 professional operating system
 Microsoft Office
 Microsoft visual basic version 6.0
8. Licensing requirements
The system will developed according to the business oriented nature of EBMS, and it is
licensed by Electricity bill management system.