2022

VISION

FOR

ELECTRICITY BILL
MANAGEMENT SYSTEM
Version 1.0

Prepared by
Usman Ahmad
&
Muhammad diyan irfan
13th 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. Introduction --------------------------------------------------------------------------------------------------------------------------- 4
1.1 Purpose ---------------------------------------------------------------------------------------------------------------------------- 4
1.2 Scope ------------------------------------------------------------------------------------------------------------------------------- 4
1.3 Definitions, Acronyms and Abbreviations -------------------------------------------------------------------------------- 4
1.4 References ------------------------------------------------------------------------------------------------------------------------ 4
1.5 Overview --------------------------------------------------------------------------------------------------------------------------- 5
2. Positioning ----------------------------------------------------------------------------------------------------------------------------- 5
2.1 Business Opportunity ---------------------------------------------------------------------------------------------------------- 5
2.2 Problem Statement ------------------------------------------------------------------------------------------------------------- 5
2.3 System Position Statement --------------------------------------------------------------------------------------------------- 6
3. Stakeholder and User Descriptions -------------------------------------------------------------------------------------------- 6
3.1 Stakeholder Summary ---------------------------------------------------------------------------------------------------------- 7
3.2 User Summary -------------------------------------------------------------------------------------------------------------------- 7
3.3 Stakeholder Profiles ------------------------------------------------------------------------------------------------------------ 7
3.3.1 Administrator -------------------------------------------------------------------------------------------------------------- 7
3.3.2 Data Entry Operator------------------------------------------------------------------------------------------------------ 8
3.4 Key Stakeholder / User Needs ----------------------------------------------------------------------------------------------- 8
4. System Overview -------------------------------------------------------------------------------------------------------------------- 8
4.1 System Perspective ------------------------------------------------------------------------------------------------------------- 9
4.2 Summary of Capabilities ------------------------------------------------------------------------------------------------------- 9
4.3 Assumptions and Dependencies -------------------------------------------------------------------------------------------- 9
4.4 Cost and Pricing ------------------------------------------------------------------------------------------------------------------ 9
4.5 Licensing and Installation ----------------------------------------------------------------------------------------------------- 9
5. System Main Features------------------------------------------------------------------------------------------------------------ 10
6. System Priorities ------------------------------------------------------------------------------------------------------------------- 10
7. Constraints -------------------------------------------------------------------------------------------------------------------------- 10
8. Quality Ranges --------------------------------------------------------------------------------------------------------------------- 10
9. Other Item Requirements ------------------------------------------------------------------------------------------------------- 11
9.1 System Requirements -------------------------------------------------------------------------------------------------------- 11
9.1.1 Platform ------------------------------------------------------------------------------------------------------------------- 11
9.1.2 Printer ---------------------------------------------------------------------------------------------------------------------- 11
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. This package shall prove to be a powerful package in
satisfying all the requirements of the school. The objective of software
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 and
of 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 management of
A successful Electricity Bills, Customers, and Employee etc. This system will be reliable, and
solution 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
These system helps in maintaining the bills and the payments.

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 Data Entry Operator

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 Data Entry Operator is the stakeholder who is involved in the
project by entering entries of different things like customer’s detail, 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
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