Software Requirements

Specification
–Electricity Billing System
Vandana Venu
Date: August 1, 2022

Confidential 1

Copyright notice: Copyright © 1996-2004 Aspire Systems. All rights reserved. The contents on this document are
not to be reproduced or duplicated in any form or kind, either in part or full, without written consent from Aspire
Systems.
 • Abstract

Electricity Billing System is a software-based application developed in Java

programming language.The project aims at serving the department of electricity by
computerizing the billing system.It mainly focuses on the calculation of Units consumed
during the specified time and the money to be paid to electricity offices. This
computerized system will make the overall billing system easy, accessible,comfortable
and effective for consumers.

The application has high speed of performance with accuracy and efficiency.The
software provides facility of data sharing.It doesn’t require any staffs as in the
conventional system. Once it is installed on the system, only the meter readings are to
be given by the customer.The electricity billing software calculates the units consumed
by the customer and makes bills.It has the provision of security restriction and requires
only small storage for installation and functioning.

2.Module Description

The system has a different segment to process a specific task which is the modules. This will
help the system to developed easily and makes it more user-friendly.

The modules of the project are: –

2.1 System Environment

The project electricity bill management involves two users and they are Administrator and
consumers. The administrator has all the controls to the system. Only after the login
process, the rest of the application is made available to the user. In order to login, user has
to first register by providing desired user-ID and password. Provided user-IDs and
passwords by the users are maintained in a database. SQL database is used to maintain a
database. Then the user logins in to the application by giving user-ID and password
provided during registration process. JDBC is used to connect the application with the
database. User Login Sequence will be as follows:

 User registration by providing user-ID and password(credentials)

 User will be prompted to enter user credentials.

 If the user enters correct credentials then he gets access to the application and can view
the personal details and the bill details

2.2 Product Perspective

The project Electricity Billing System involves three users and they are administrator, KSEB
unit and consumers. There is only one administrator having the overall control of the
system. The administrator has all the controls to the system. Each user i.e. administrator,
consumer, can login to the system by using the username and password .The administrator
has the authorization to view the meter reading for each consumer. And also the
administrator can view the details of payment for each user in a monthly basis. The last role
for administrator is that he can add rate for one unit energy.

2.3 Product Functions

EBS will have three major functions as described in the subsections below.

2.3.1 Login

There is only one administrator having the overall control of the system. The user logins in
to the application by giving user-ID and password. Based on the user, if it is a consumer he
can view his bill and if it is an administrator he can perform consumer management and
billing functions.

2.3.2 Consumer Management

To design front-end forms according to consumer specifications it was like addition of new
consumer, deletion, modification of consumer, query consumer, etc. This module deals with
consumer information details.

2.3.2.1 New Consumer Acquisition

The proposed software allows the end user to add the new consumer with his personal
details

2.3.2.2 Update Consumer details

If any particulars has modified with consumer details, this sub module is used to modify the
consumer details by the administrator.

2.3.3 Billing

Billing is done by spot billing machines and updated to billing database. This module deals
with collection of payments through collection centers by online or offline each consumer
wise.

2.3.3.1 Online Receipt

This sub module is used to online bill payment receipts. It will provide the entry fields to
accept payments. It will show the consumer bill details and based on that we will know the
bill details which were belongs to consumer whether consumer is having arrears or not. It is
done on the spot when the consumer comes to pay bill.

2.4 User Characteristics

Users who can access the system are two

2.4.1 Consumers

Only after the login process, the rest of the application is made available to the user. In
order to login, user has to first register by providing desired user- ID and password.
Consumer can update personal information,view the bill.

2.4.2 Administrator

Administrator has overall control of the system. Administrator can perform the operations
such as addition of new consumer, deletion of consumer, update consumer details, query
consumer, bill generation, and receipt creation.

2.5 Development Environment

Development environment is as follows. Final decision on the development environment
shall be taken during the design phase.

• JAVA

• Database: SQL

3.Functional And Non Functional Requirements

3.1 Functional Requirements

• Login Information-The system shall maintain a minimum the information of user

name and password

• Administrator login Operation-By giving the user name and password the admin can
login into the EBS and thereby managing consumer and bill details

• Consumer login Operation-By giving the user name and password the consumer can
login into the EBS and can view his personal details, bill details and update the
personal details.

• New Consumer Acquisition Operation-Here new consumer can register into the EBS
with his personal details and by providing a username and password.

• Modify Consumer Operation-Here the administrator can modify the details of a

consumer with a particular consumer number.

• Meter Change Operation-Meter will change then the meter details will be change in
database. This sub module is used to update meter details by administrator.

• Online Receipt generation-Here the administrator will generate the online receipt for
a consumer with a particular consumer number.

3.2 Non Functional Requirements

In software engineering non-functional requirements are requirements which specify criteria

that can be used to judge the operation of a system, rather than specific behaviors. This
should be contrasted with functional requirements that specify specific behavior or
functions. Non-functional requirements are often called qualities of a system. Other terms
for non-functional requirements are "constraints", "quality attributes","quality goals" and
"quality of service requirements". Qualities, of Non-functional requirements can be divided
into two main categories. Execution qualities, such as security and usability, are observable
at run time. Evolution qualities, such as extensibility and scalability,
embody in the static structure of the software system.

4.Use Case Diagram

5.SEQUENCE DIAGRAM