Download Electricity Billing System and more Schemes and Mind Maps English Language in PDF only on Docsity!
ELECTRICITY BILLING
SYSTEM
Software Requirement Specification
Version 1.
Prepared By
Keerthana.I.P
RegNo: 82455
Dept. of Computer Science & Engineering MA College of Engineering (MACE) Kothamangalam, Kerala-686 666 DECEMBER 2, 2013
Document Control Data Sheet Project Code
EBS
Project Name Electricity Billing System Document Name
Software Requirement Specification
Version
File Name
Electricity Billing System _SRS.doc
Classification Confidential Client MA College of engineering, Kothamangalam Name Signature & Date Prepared By
Keerthana.I.P
Reviewed By Eldo P Elias Ashna Mary George Approved By Eldo P Elias Ashna Mary George Distribution List
1. Dept. Library
2. CS Faculty
Table of Contents
1 Introduction 1.1 Purpose
In today’s world of emerging technology, computers are playing a vital role in
every walk of life. The problems due to the traditional system are overcome with the help
of tasks being online. This new system named “Electricity Billing System (EBS)” is an
Executive Information System that could be used for entering, calculating and monitoring
the Billing details of the Electricity Consumers. It provides environment to maintain the
consumer details starting from getting new connection, receiving bill, payments etc., and
performance information to the administrator. The groups of people that are going to use
the system are administrator and consumers. Consumer can update personal information,
view the bill. The administrator can perform the operations such as addition of new
consumer, deletion of consumer, modification of consumer, query consumer, adding
meter details, bill generation, and receipt creation. Billing is done by collection of
payments and there by generating receipts for each consumer wise, receipt cancel in the
case of errors. Proposed system shall provide authentication to avoid unauthorized
access.
The purpose of this Software Requirements Specification document is to maintain
all the functions and the specifications of ‘Electricity Billing System’. Besides it contains
detailed descriptions of all the requirements specified. It will explain the purpose and
features of the system, the interfaces of the system, what the system will do, and the
constraints under which it must operate. This document is intended for both the
stakeholders and the developers of the system.
1.2 Intended Audience
This intended audience of this document includes all stakeholders of EBS project
who are supposed to review and sign-off this document. The primary stakeholders of the
system include consumers and administrator.
1.3 Scope of Project
This application is basically written as a solution to the drawbacks of existing stem.
This application can be used as a real world application and by any organization. It’s
could be used as a general application with few minor modifications. The purpose of this
application is to develop “EBS” (Electricity Billing System), which is a web application
which provides a service to all the consumers and employees of K.S.E.B to deal with the
transactions online.
Here the cost to develop the project will be less but the reliability will be degraded.
Thus this application provides a solution to problems of single tier. Consumers can lodge
a complaint or deal with new connections just by logging into the system and do the
transactions online.
In the traditional system files were used to maintain the database which was done
manually. This existing system consumes a lot of time. This time consuming evaluation
coupled by the huge maintenance problem and may also lead to erroneous results. The
various operations performed on these files like sorting, adding, modifying and deletion
of the records are very tedious. Moreover these manually maintained files have the
possibility of getting worn out. Thus, less durability is achieved.
Thus the demerits of the existing system can be summarized as follows…
There is no consistency as the data may not be updated on time.
Feasibility is reduced
Less reliability
Security is not provided and any one can access
Prioritization of records is difficult.
More erroneous
Difficult to maintain
As everything is done manually its slow process
No timely acknowledgement service
Taking the demerits into consideration, an alternative system which uses JAVA
as front end and SQL as back end was used. In front end, retrieval of the data from the
database is done through SQL queries. This is not a web application and the data is not
1.4 Glossary
Term Definition
EBS-Electricity Billing System Electricity Billing System is an Executive Information System that could be used for entering, calculating and monitoring the Billing details of the Electricity Consumers. Administrator Administrator having the overall control of the system Consumer It is the user who consumes electricity. Meter It is an electronic device which records the usage status of electricity. Database Collection of all the information monitored by this system. Software Requirements Specification A document that completely describes all of the functions of a proposed system and the constraints under which it must operate. For example, this document. Stakeholder Any person with an interest in the project who is not a developer. User A user of the EBS can be Consumer or Administrator Table 1.1: Glossary 1.5 References
[1] IEEE. IEEE Std 830-1998 IEEE Recommended Practice for Software
Requirements Specifications. IEEE Computer Society, 1998.
1.6 Overview of Document
Overall Description section, of this document gives an overview of the
functionality of the EBS System. It describes the informal requirements and is used to
establish a context for the technical requirements specification in the next chapter.
The third chapter, Requirements Specification section, of this document is written
primarily for the developers and describes in technical terms the details of the
functionality of the EBS System. Both sections of the document describe the same
software product in its entirety, but are intended for different audiences and thus use
different language.
2 Overall Description 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.
Figure 2.1: EBS System Environment
2.3.2.4 Query Consumer
Whenever administrator needs to see the details of any particular consumer then
this sub module will invoke the details and will display on the screen.
2.3.2.5 Meter Change
Every consumer is having meter for reading details. If meter will change then the
meter details will be change in database. This sub module is used to update meter details.
2.3.2.6 Meter part Change
If any changes occurred in meter particulars then this sub module is used to
update. The difference between Meter Change and Meter part Change is when ever Meter
will change Meter Change sub module will use and Meter will not Change but Meter
Characteristics will change then Meter part change sub module will use.
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.3.3.2 Receipt Cancel
This sub module is allows the user to correct the mistakes done in the receipt. It
will provide the entry fields to cancel the payment receipts only.
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
2.6 Constraints
a. Regulatory Policies: NA
b. Hardware Limitations: NA
c. Interfaces to other application: An external interface for online bill payment is
provided.
d. Parallel operations: NA
e. Audit Functions: NA
f. Control Functions: NA
g. Safety and Security Considerations: The password and a valid username are the
security issues. The backup process at the server side shall satisfy data protection.
h. Reliability Requirements: Total number of bugs in the system shall not exceed
1% of the total line number of code, except connection reliability, which is out of
range.
i. Criticality of the Application: The server applications shall be available 365
days.
2.7 Assumptions and Dependencies
Since the EBS is only accessible through the Internet, it is assumed that the end
user has a connection to the Internet. It is also assumed that the user has a web browser
able to display the website.
Table 3.1: User Login Information
3.2.1.2 Administrator login Operation
By giving the user name and password the admin can login into the EBS and
thereby managing consumer and bill details.
3.2.1.3 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.
3.2.2 Consumer Management
3.2.2.1 Personal Information
The system shall maintain at a minimum the information in Error: Reference
source not found 3.2.
Property Mandatory Explanation
Name Yes Name of the consumer Address Yes Address of the consumer Location No Local area of the consumer Town Yes Name of town of the consumer Pin code No Pin code of that area Phone No Contact number of the consumer Contracted Load Yes Amount of load in Watts in the contract Connected Load Yes Amount load in Watts which is connected Supply Connection Date Yes Starting date of the connection supply Consumer Type Yes Type of supply like single phase, three phase LT or HT Table 3.2: Personal Information
3.2.2.2 Consumer Information
The system shall maintain at a minimum the information in table 3.3.
Property Mandatory Explanation
Service Number Yes Service Number of an electricity consumer Post Number Yes Electricity post number Transformer Name Yes Local Name of the Transformer Section Yes Section name of the Transformer Category Yes Categories like Domestic, Commercial supply etc. Service Type Yes Service type like Government or non-Government Phase Yes like single phase, three phase Area Code Yes Code number for that particular area Table 3.3: Consumer Information
3.2.2.3 Meter Information
The system shall maintain at a minimum the information in table 3.4.
Property Mandatory Explanation
Meter Number Yes Number of the meter Multiplying Factor Yes Multiplying Factor of the Meter. Meter Capacity No Capacity of the meter to run electrical energy Structure Code Yes Code that is used to uniquely identify the meter. Meter TC Seal(Y/N) No State whether meter has Seal or not Meter Phase Yes Meter phase like single phase, three phase Opening Reading Rate Yes Initial meter reading of the billing period with date. Closing Reading Rate Yes Final meter reading of the billing period with date. Meter Status No Status of meter like ok/defective/missing etc. Average Unit Yes Average units consumed till the billing period Billed Unit Yes Number of units consumed during the billing period. Table 3.4: Meter Information
3.2.3.3 Bill and Receipt Information
The system shall maintain at a minimum the information in Error: Reference
source not found 3.5.
Property Mandatory Explanation
Service Number Yes Service number of the consumer Name Yes Name of the consumer Mobile No No Mobile number of the consumer Bill No Yes Number of the bill Bill Date Yes Date of the bill Bill Area Yes Area code for the bill Energy Charge Yes electricity supply charge, This per-kWh rate is for the actual power you use Fixed Charge Yes This cover utilities fixed costs such as labor, equipment, return on investment, etc. Meter Charge Yes This charge covers the costs of meter reading and other services such as installing, maintaining, and testing meter equipment. Duty Charge Yes Electricity duty charge Customer Charges Yes basic service charge Additional Charge Yes Addl. Charges for belated payment Arrears Yes Electricity bill debt Advance Yes Advance payed towards bill Total Bill Amount Yes Total amount to be payed Payment Mode Yes Specify payment mode like Cash, DD, Cheque Receipt No Yes Number of the receipt Receipt Date Yes Date of the receipt Amount Towards Bill Yes The amount payed towards bill Total Yes Total bill amount payed Table 3.5: Bill and Receipt Information
4 System Features
This section gives the details of system features and functions identified as
different use cases relevant for various users (or actors) of the system. The following
sections group and specify the use cases.
4.1 Software Requirements Collected From Stakeholders
R.No Requirements
Requirement
Type
Priority
R
The system must generate the electricity bill of consumers on monthly basis STRQ1 High R2 The receipt should be generated after the payment STRQ2 High R Contents in the electricity bill are: consumer details, meter details, amount STRQ3 High R4 The consumer has to register with his personal details STRQ4 High R5 System access is limited to consumers and administrator FEAT1 High R6 The consumer can update his personal details STRQ5 High R7 Consumers may view electricity bill STRQ6 High R The administrator can perform operations such as addition of new consumer, deletion of consumer, update consumer details, query consumer, bill generation, receipt creation and receipt cancel STRQ7 High R System shall provide authentication to avoid unauthorized access STRQ8 High R10 System has to be a web application FEAT2 High R System should be developed using SQL as backend and JAVA as front end FEAT3 High R12 System should run in the LAN FEAT4 High R13 Use CAPTCHA to reduce automated logins FEAT5 Medium Table 4.1: Software Requirements
