sample srs document

Electricity Billing System Software Requirements Specification Version 1.2

ELECTRICITY BILLING SYSTEM

Software Requirement Specification

Version 1.2

Prepared By

Keerthana.I.P

RegNo: 82455

Dept. of Computer Science & Engineering

MA College of Engineering (MACE)Kothamangalam, Kerala-686 666

DECEMBER 2, 2013

Dept. of CSE MA College of Engg, Kothamangalam


Document Control Data Sheet

Project Code EBS

Project Name Electricity Billing System

Document Name Software Requirement Specification

Version 1.2

File NameElectricity Billing System _SRS.doc

Classification Confidential

Client MA College of engineering, Kothamangalam

Name Signature & Date

Prepared ByKeerthana.I.P

Reviewed By Eldo P EliasAshna Mary George

Approved By Eldo P EliasAshna Mary George

Distribution List1. Dept. Library2. CS Faculty



Document change procedures and history


Version Date Author Reviewer

1.0 15-11-2013 Keerthana.I.PEldo P EliasAshna Mary George

1.1 22-11-2013 Keerthana.I.PEldo P EliasAshna Mary George


Table of Contents

1 Introduction......................................................................................................11.1 Purpose...............................................................................................................................11.2 Intended Audience..............................................................................................................11.3 Scope of Project.................................................................................................................21.4 Glossary..............................................................................................................................41.5 References..........................................................................................................................4

1.6 Overview of Document.......................................................................................................42 Overall Description..........................................................................................5

2.1 System Environment..........................................................................................................52.2 Product Perspective............................................................................................................62.3 Product Functions...............................................................................................................6

2.3.1 Login...........................................................................................................................6 2.3.2 Consumer Management..............................................................................................6 2.3.2.1 New Consumer Acquisition................................................................................6 2.3.2.2 Modification of Consumer..................................................................................6 2.3.2.3 Deletion of Consumer.........................................................................................6 2.3.2.4 Query Consumer.................................................................................................7 2.3.2.5 Meter Change......................................................................................................7 2.3.2.6 Meter Part Change..............................................................................................7 2.3.3 Billing.........................................................................................................................7 2.3.3.1 Online Receipt....................................................................................................7 2.3.3.2 Receipt Cancel....................................................................................................7

2.4 User Characteristics............................................................................................................7 2.4.1 Consumers...................................................................................................................7 2.4.2 Administrator..............................................................................................................82.5 Development Environment................................................................................................82.6 Constraints..........................................................................................................................8

2.7 Assumptions and Dependencies.........................................................................................83 Requirements Specification.............................................................................9

3.1 External Interface Requirements........................................................................................9 3.1.1 User interfaces............................................................................................................9 3.1.2 Hardware interfaces....................................................................................................9 3.1.3 Software interfaces......................................................................................................9 3.1.4 Communications interfaces.........................................................................................9

3.2 Functional Requirements....................................................................................................9 3.2.1 Login Management.....................................................................................................9 3.2.1.1 Login Information...............................................................................................9 3.2.1.2 Administrator Login Operation.........................................................................10 3.2.1.3 Consumer Login Operation...............................................................................10 3.2.2 Consumer Management...........................................................................................10 3.2.2.1 Personal Information.........................................................................................10 3.2.2.2 Consumer Information......................................................................................11 3.2.2.3 Meter Information.............................................................................................11 3.2.2.4 New Consumer Acguisition Operation.............................................................12 3.2.2.5 Modify Consumer Operation.............................................................................12 3.2.2.6 Delete Consumer Operation..............................................................................12



3.2.2.7 Query Consumer Operation..............................................................................12 3.2.2.8 Meter Change Operation...................................................................................12 3.3.2.9 Meter Part Change Operation............................................................................12 3.2.3 Receipt and Billing...................................................................................................12 3.2.3.1 Online Receipt Generation.................................................................................12 3.2.3.2 Receipt Cancel Operation...................................................................................12 3.2.3.3 Bill and Receipt Information..............................................................................134 System Features..............................................................................................14 4.1 Software Requirements Collected From Stakeholders....................................................14 4.2 List Of Actors..................................................................................................................15 4.3 List Of Use Cases............................................................................................................15 4.4 Mapping Functional Requirements To Use Cases...........................................................16

4.5 UseCase Diagram............................................................................................................17 4.5.1 Use Case-1: Register.................................................................................................18 4.5.2 Use Case-2: Login.....................................................................................................19 4.5.3 Use Case-3: Update Personal Details.......................................................................20 4.5.4 Use Case-4: View Bill..............................................................................................21 4.5.5 Use Case-5: Delete Consumer..................................................................................22 4.5.6 Use Case-6: Update Consumer Details.....................................................................23 4.5.7 Use Case-7: Query Consumer...................................................................................24 4.5.8 Use Case-8: Bill Generation.....................................................................................25 4.5.9 Use Case-9: Receipt Creation...................................................................................26

4.5.10 Use Case-10: ReceiptCancel.....................................................................................27

5 Other Nonfunctional Requirements.............................................................28 5.1 Performance Requirements..............................................................................................28 5.2 Security Requirements.....................................................................................................28

Index…………………………………………………………………………..….29



List of Figures

Figure 2.1 EBS System Environment.............................................................................................5Figure 4.1 EBS UseCase...............................................................................................................17

List of Tables

Table 1.1 Glossary.........................................................................................................................4Table 3.1 User Login Information.................................................................................................9Table 3.2 Personal Information.....................................................................................................9Table 3.3 Consumer Information.................................................................................................11Table 3.4 Meter Information........................................................................................................11Table 3.5 Bill and Receipt Information.......................................................................................13Table 4.1 Software Requirements................................................................................................14Table 4.2 Actors...........................................................................................................................15Table 4.3 Use Cases.....................................................................................................................15Table 4.4 Functional Requirements To Use Cases Mapping.......................................................16Table 4.5 UC1..............................................................................................................................18Table 4.6 UC2..............................................................................................................................19Table 4.7 UC3..............................................................................................................................20Table 4.8 UC4..............................................................................................................................21Table 4.9 UC5..............................................................................................................................22Table 4.10 UC6..............................................................................................................................23Table 4.11 UC7..............................................................................................................................24Table 4.12 UC8..............................................................................................................................25Table 4.13 UC9..............................................................................................................................26Table 4.14 UC10............................................................................................................................27



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



distributed as only a single system is used. As it is confined only to a particular system,

scope is limited and there is a hindrance to the reliability if the system fails.

The demerits of this alternate system are…

Only single system used.

If the system crashes then the data is lost

too overburdened

not reliable

slow processing

less flexible

not so user friendly

The proposed system is developed based on the client server architecture,

a request-response paradigm and is implemented with the help of a JAVA using the

NETBEANS IDE. The employees can maintain and do the transactions online.

The application starts by asking for user name and password which provides

authentication. This system provides high security where the unauthorized users cannot

access the data.

Later we have different options for the employee like

Consumer Management

Billing

Receipt generation

Reports

Meter Details

The objectives of the proposed system are as follows:

Easy to use, effective and efficient

Accurate results

Easy maintenance

Fast access

More feasibility and reliability

More secure

Provides high consistency



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.

MeterIt 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.

StakeholderAny 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.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.2.3 Deletion of consumer

If any consumer disconnects the connection then administrator has to delete the

consumer related information from system. This module is used to delete the consumer.



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.



3 Requirements Specification

3.1 External Interface Requirements

3.1.1 User interfaces

The system will allow access using web browsers. Most common browsers will

be supported. The system will provide the ability for consumer and administrator to

access the EBS via the Internet. There will be two different user interfaces that will

accompany this website: one for the consumer and another for the administrator.

At first consumer has to register with the EBS. The consumer can login into the

EBS by using the username and password provided during the registration process. After

login consumers can view the personal details, and bill details.

The administrator will be provided with special functionalities like

Consumer management

Billing.

3.1.2 Hardware interfaces

There are no external hardware interface requirements for EBS.

3.1.3 Software interfaces

There are no external software interface requirements for EBS.

3.1.4 Communications interfaces

There are no external communications interface requirements for EBS.

3.2 Functional Requirements

3.2.1 Login Management

3.2.1.1 Login Information

The system shall maintain at a minimum the information in Table 3.1.

PropertyMandator

yExplanation

User Name Yes Username for the login process

Password Yes Password for the login process



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 found3.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

DateYes 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.


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.


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.2.4 New Consumer Acquisition Operation

Here new consumer can register into the EBS with his personal details and by

providing a username and password.

3.2.2.5 Modify Consumer Operation

Here the administrator can modify the details of a consumer with a particular

consumer number.

3.2.2.6 Delete Consumer Operation

Here the administrator can delete a consumer with a particular consumer number.

3.2.2.7 Query Consumer Operation

Here the administrator can view the details of a consumer with a particular

consumer number.

3.2.2.8 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.

3.2.2.9 Meter Part Change Operation

If Meter will not Change but Meter Characteristics will change then Meter part

change operation is used to update meter details by administrator.

3.2.3 Receipt and Billing

3.2.3.1 Online Receipt generation

Here the administrator will generate the online receipt for a consumer with a

particular consumer number.

3.2.3.2 Receipt cancel operation

This operation allows the administrator to correct the mistakes done in using

online receipt. It will provide the entry fields to cancel the payment receipts only.



3.2.3.3 Bill and Receipt Information

The system shall maintain at a minimum the information in Error: Reference source not found3.5.

Property Mandatory ExplanationService 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 Yeselectricity supply charge, This per-kWh rate is for the

actual power you use

Fixed Charge YesThis 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 RequirementsRequirement

TypePriority

R1The system must generate the electricity bill of

consumers on monthly basisSTRQ1 High

R2 The receipt should be generated after the payment STRQ2 High

R3Contents in the electricity bill are: consumer details,

meter details, amountSTRQ3 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

R8

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

R9System shall provide authentication to avoid

unauthorized accessSTRQ8 High

R10 System has to be a web application FEAT2 High

R11System should be developed using SQL as backend and

JAVA as front endFEAT3 High

R12 System should run in the LAN FEAT4 High

R13 Use CAPTCHA to reduce automated logins FEAT5 Medium

Table 4.1: Software Requirements



4.2 List Of Actors

Actor No Actor Description

A1 Consumer Consumer can update personal details and view the bill.

A2 Administrator

Administrator can perform the operations such as deletion of

consumer, update consumer details, query consumer, bill

generation, receipt creation and receipt cancel.

Table 4.2: Actors

4.3 List Of Use Cases

Use Case No Use Cases Description

UC1 Register Actors: consumer

UC2 Login Actors: Administrator , consumer

UC3 Update Personal details Actors: consumer

UC4 View bill Actors: consumer

UC5 Delete consumer Actors: Administrator

UC6 Update consumer details Actors: Administrator

UC7 Query consumer Actors: Administrator

UC8 Bill generation Actors: Administrator

UC9 Receipt creation Actors: Administrator

UC10 Receipt cancel Actors: Administrator

Table 4.3: Use Cases



4.4 Mapping Functional Requirements To Use Cases

Functional Requirement (STRQ) No

Description Use Case No

STRQ1The system must generate the electricity bill of

consumers on monthly basisUC8

STRQ2 The receipt should be generated after the payment UC9, UC10

STRQ3Contents in the electricity bill are: consumer details,

meter details, amountUC6,UC8

STRQ4 The consumer has to register with his personal details UC1

STRQ5 The consumer can update his personal details UC3

STRQ 6 Consumers may view electricity bill UC4

STRQ 7

The data entry 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

UC5,UC6,UC7,U

C8,UC9,UC10

STRQ8System shall provide authentication to avoid

unauthorized accessUC2

Table 4.4: Functional Requirements To Use Cases Mapping



4.5 Use Case Diagram

Figure 4.1: EBS Use Case



4.5.1 Use Case-1: Register

Use Case UC1. Register

Description Allows the consumer to register by entering the personal details

Assumptions Consumer has a service number to use the system

Actors Consumer

Entry Condition Access the home page of EBS

Steps

1. Press ‘New User Registration’ button in the home page

2. System displays the registration page

3. Enter Service number(Mandatory field)

4. Enter Consumer name(Mandatory field)

5. Enter Consumer’s date of birth(Mandatory field)

6. Enter Consumer’s Mobile number(Mandatory field)

7. Enter Consumer place of residence

8. Enter Consumer’s address(Mandatory field)

9. Enter Consumer’s e-mail ID(Mandatory field)

10. Enter Username, which the Consumer wants to use in future(Mandatory

field)

11. Enter Password, which the Consumer wants to use in future(Mandatory

field)

12. Press ‘Register’ button

Variations None

Exit condition

If Service Number is valid and all mandatory values entered correctly ,Then

Display message “Registered successfully”

Else

Display message “mandatory values missing”

Non Functional The error message should be colored in red

Issues Usage should be only within the LAN and browser should be compatible

Table 4.5: UC1



4.5.2 Use Case-2: Login

Use Case UC2. Login

Description Allows the user to login to the system using his user ID and password

Assumptions User has to be a registered member of the system

Actors Consumer, Administrator

Entry Condition Access Home Page of EBS

Steps

1. User types in username field

2. User types in password field

3. User clicks on the 'Login' button

4. IF credentials are valid THEN show home page of User

ELSE display error message

Variations CAPTCHA can be Included to reduce automated login

Exit condition

If credentials are valid, Then

Show Home page of Consumer or administrator

Else

Display error message “Invalid User ID or password.

Please try again”

Non-functional The error message should be colored in red

IssuesUsage should be only within the LAN and browser should be

compatible

Table 4.6: UC2



4.5.3 Use Case-3: Update personal details

Use Case UC3. Update personal details

Description Allows the Consumer to edit the personal details

Assumptions Consumer has successfully logged into the system

Actors Consumer

Entry Condition Access the Consumer home page of EBS

Steps

1. Click the ‘Update Details’ button in the home page

2. System displays the existing details of the Consumer

3. Edit required fields

4. Click ‘submit’ button

Variations None

Exit condition

If Consumer is a valid consumer and details updated, Then

Display message “Personal Details updated successfully”Else

Display “Consumer does not exist” error message



Table 4.7: UC3



4.5.4 Use Case-4: View bill

Use Case UC4. View bill

Description Allows the Consumer to view the bill

Assumptions Consumer has successfully logged into the system

Actors Consumer

Entry Condition Access the Consumer home page of EBS

Steps

1. Click ‘View Bill’ button in the home page

2. System displays Electricity bill with Consumer details, meter details

and payment details and having following buttons:”save” and “print”

3. Click on ‘Save’ button to save the bill

4. Click on ‘Print’ button to print the bill

Variations None

Exit condition

If Consumer is a valid consumer, Then

Display the billElse

Display “Consumer does not exist” error message



Table 4.8: UC4



4.5.5 Use Case-5: Delete consumer

Use Case UC5. Delete consumer

Description Allows the administrator to delete a particular consumer

Assumptions Administrator has successfully logged into the system

Actors Administrator

Entry Condition Access the Admin home page of EBS

Steps

1. Click the ‘Delete Consumer’ button in the home page

2. System displays the Delete Consumer page

3. Enter Service Number and consumer name to be deleted

4. Press ‘Delete’ button

5. System displays message “Are you sure to delete the consumer?”

having two buttons ‘Yes’ and ‘No’

6. Click ‘Yes’ button to delete the Consumer

Variations None

Exit condition

If Service Number is valid ,Then

Display “successfully deleted the consumer” messageElse

Display “Consumer does not exist or error in deletion ” error

message



Table 4.9: UC5



4.5.6 Use Case-6: Update consumer details

Use Case UC6. Update consumer details

Description Allows the administrator to update the details of a particular consumer




Steps

1. Click the ‘Update Consumer’ button in the home page

2. System displays the Update Consumer page

3. Enter Service Number and consumer name whose details to be updated

4.Press ‘Show’ button

5. IF Service Number valid THEN

1.System displays the existing details of the Consumer

2. Edit the required fields such as Consumer details, meter details,

bill details and click ‘Update’ button

ELSE Display error message

Variations None

Exit condition

If Service Number is valid and details updated, Then

Display “successfully Updated the consumer details” messageElse

Display “Consumer does not exist or error in updation ” error

Message



Table 4.10: UC6



4.5.7 Use Case-7: Query Consumer

Use Case UC7. Query Consumer

Description Allows the administrator to View the details of a particular consumer




Steps

1. Click the ‘Query Consumer’ button on the top of the home page

2. System displays the Query Consumer page

3. Enter Service Number and consumer name whose details to be viewed

4. Press ‘Show’ button

5. IF Service Number valid THEN displays the details of the consumer


Variations None

Exit condition

If Service Number valid , Then

Display the consumer details including Meter details, consumer

details, and bill details

Else

Display “Consumer does not exist ” error message



Table 4.11: UC7



4.5.8 Use Case-8: Bill Generation

Use Case UC8. Bill Generation

DescriptionAllows the administrator to calculate the electricity bill of a particular

consumer




Steps

1. Click the ‘Bill Generation’ button in the home page

2. System displays the Bill Generation page

3. Enter Service Number and consumer name whose electricity bill to be

calculated

4. Press ‘Create’ button


1. Show the Consumer details having following buttons :

‘Generate’ , and ‘Exit’

2. Click on ‘Generate’ button to generate the bill


Variations None

Exit condition

If Service Number valid, Then

Display “Bill generated successfully” messageElse

Display “Invalid Service Number “error message



Table 4.12: UC8



4.5.9 Use Case-9: Receipt Creation

Use Case UC9. Receipt Creation

DescriptionAllows the administrator to generate the receipt of a particular consumer

after the payment




Steps

1. Click the ‘Receipt Generation’ button in the home page

2. System displays Receipt Generation page

3. Enter Service Number and consumer name whose receipt to be

generated

4.Press ‘Create’ button


1. Show the Consumer details having following buttons :

‘Generate’ , and ‘Exit’

2. Click on ‘Generate’ button to generate the receipt


Variations None

Exit condition


Display “Receipt generated successfully” message

Else




Table 4.13: UC9

4.5.10 Use Case-10: Receipt Cancel



Use Case UC10. Receipt Cancel

DescriptionAllows the administrator to cancel the receipt of a particular consumer in

the case of errors




Steps

1. Click the ‘Receipt Cancel’ button in the home page

2. System displays Receipt Cancel Page

3. Enter Service Number and consumer name whose receipt to be generated

4. Press ‘Cancel’ button


1. Show a message “Are you sure to cancel the receipt” having

following buttons :’Yes’ and ‘No’

2. Click on ‘Yes’ button to cancel the receipt


Variations None

Exit condition


Display “Receipt cancelled successfully” message

Else




Table 4.14: UC10

5 Other Nonfunctional 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.

5.1 Performance Requirements

The server on which this system will be running is expected to be available at all

hours of the day to provide full time accessibility. The system is developed based on the

client server architecture, a request-response paradigm and is implemented with the help

of a JAVA using the NETBEANS IDE and it uses SQL server as back end.

Major performance requirements are:

All web pages should be loaded within 10 seconds

The system should provide proper authentication

5.2 Security Requirements

The access to the software application will be restricted to the authorized users

identified by a valid username and password. New consumers can register or signup to

the system with personal details. The users will be categorized into two roles

administrator and consumer. The modules and functions accessible or available to the

users will vary based on their roles. The users will be able to login to the application

using the username and password and access the modules or functions based on their

role. CAPTCHA will be included to reduce automated login. Error messages will be displayed in

the case of errors during the system access.


http://en.wikipedia.org/wiki/Constraints

http://en.wikipedia.org/wiki/Functional_requirements

http://en.wikipedia.org/wiki/Requirements

http://en.wikipedia.org/wiki/Systems_engineering


6 Index

Actor 14, 15, 18-27

Administrator 1, 4-10, 12, 14-17, 19, 22-28

Bill 1, 3-17, 21, 24, 25

Consumer 1-28

Database 4, 5, 7, 8

EBS 1, 4-6, 8-10, 12, 17-27

Meter 1, 3, 4, 6, 7, 11-14, 16, 21, 23, 24

Receipt 1, 3, 7, 8, 12-17, 26, 27

Use Case 14-27


sample srs document

Documents

query consumer operation12

consumer information11table

consumer login operation10

consumer management10

consumer management6

list of use cases15

meter change operation12

new consumer acquisition6