Eleectricity Billing System

Electricity Consumption and Billing System
Wollo University,
Kombolcha Institute of Technology –
College of Informatics
Software Requirements Specification for Industrial project on

[Electricity consumption and billing system]
Group members
Name ID Number
1. Misganaw Getahun 0586/10
2. Adem Abate 0516/10
3. Moti Tulu 0590/10
4. Mudesir Maru 1781/10
Submitted to Instructor ፡YOHANNES
Submission Date: - 23/05/2012

2012 E.C // 2019 – 20 G.C
Wollo University, Kombolcha Institute of Technology
@GROUP ONE I
Declaration
The Project is our own and has not been copied from others or presented for a course project/a
degree/ in any other university and all the sources of material used for the project have been duly
acknowledged.
Misganaw Getahun ---------------------------------------------
Name Signature
Adem Abate -----------------------------------------------
Name Signature
Moti Tulu ---------------------------------------------
Name Signature
Mudesir Maru ---------------------------------------
Name Signature
College: Informatics
Program: Bachler Degree of Software Engineering
Project Title: Electricity consumption and Billing System
This is to certify that I have read this project and that in my supervision and the students’
performance, it is fully adequate, in scope and quality, as a project for the course Requirement
Engineering for particular year of study (i.e. third year software engineering).
Yohannes Sefane ---------------------------------------------
Name of Advisor/Instructor Signature
Examining committee members signature Date
1. Examiner1 ___________________
2. Examiner2 __________________
3. Examiner2 __________________
@GROUP ONE II
Table 1: Roles and Responsibilities of the Group Members
List of Tasks List members
Misganaw Moti Tullu Adem Abate Mudesir Maru

Getahun
Requirement Analysis
 
And Gathering
Design
   
Writing the SRS Document
 
@GROUP ONE III

Acknowledgment
First of all, we would like to praise to mine real GOD who initiates and gratified our project
successfully. Secondly we would like to salute our course teacher YOHANNIES who plays great
role by giving appropriate guidance system, for his useful comment on the subject matter and for
the knowledge that we gained by sharing ideas with him. Thirdly we would like to express our
gratitude to senior students of our college whose department is specially software engineering.
And the final we would like toothaches four team member
@GROUP ONE IV
List of acronyms
 DBMS
 SRS
 EBS
 GUI
 UML
 BR
 APB
List of Figures
 Figure 1: use case diagram of Electricity Billing System

 Figure 2: Electricity sale bill
 Figure 3: Customer login form
 Figure 4: Customer Register form
 Figure 5: data view of meter details form
 Figure 6: Calculate electricity bill form
 figure 7: Hardware Interfaces of billing system
 Figure 8: Sequence Diagram for generate bill
 Figure 9: Sequence Diagram for add employee
 Figure 10: Sequence Diagram for remove employee
 Figure 11: Sequence Diagram for calculate bill
 Figure 12: Sequence Diagram for bill history
 Figure 13: Activity Diagram for generate bill
 Figure 14: Activity Diagram for remove Employee
 Figure 15: Activity Diagram for list of Employee
 Figure 16: Activity Diagram for add Employee
 Figure 17: Activity Diagram for calculate bill
 Figure 18: Class Diagram Electricity consumption and billing system
@GROUP ONE V
List of Tables
 Table 1: Roles and Responsibilities of the Group Members

 Table 2: FR1: - Login
 Table 3: FR2: add employee
 Table 4: FR3: Remove employee

 Table 5:FR4: view employee
 Table 6: FR5: View list of login account
 Table 7: FR6: Change taxes
 Table 8: FR7: Change rates
 Table 9: FR8: Change bill
 Table 10: FR9: Waiting List
 Table 11: FR10: Calculate bill
 Table 12: NFR1 Performance
 Table 13: NFR2 Reliability
 Table 14: NFR3 Security
 Table 15: NFR4 Maintainability
 Table 16: NFR5 Portability
 Table 17: NFR6 Availability
 Table 18: UD: LOGIN
 Table 19: UD: Add employee
 Table 20: UD: remove employee
 Table 21: UD: view employee
 Table 22: UD: Calculate bill
 Table 23: UD: pay bill
 Table 24: UD: Gives new connection
 Table 25: Traceability Table
@GROUP ONE VI
Contents
1.INTRODUCTION ....................................................................................................................................................1
1.1 purpose ...............................................................................................................................................................1
1.2 Intended Audience and Reading Suggestions ..................................................................................................1
1.3 project Scope ......................................................................................................................................................2
1.4 Definitions, Acronyms, and Abbreviations. .....................................................................................................2
1.5 Overview of the Document ................................................................................................................................2
2. The Overall Description ..........................................................................................................................................2
2.1 Product Perspective ...........................................................................................................................................2
2.2 Operations ..........................................................................................................................................................3
2.3 Product Functions..............................................................................................................................................3
2.4 User Characteristics ..........................................................................................................................................3
2.5 General Constraints...........................................................................................................................................4
2.6 Assumptions and Dependencies ........................................................................................................................4
3.Specific requirements ...............................................................................................................................................4
3.1 User Requirements ............................................................................................................................................4
3.1.1. Functional User Requirements .................................................................................................................4
3.1.2. Non -Functional Requirements .................................................................................................................7
3.2 System Requirements ........................................................................................................................................9
3.2.1 Add user accounts .......................................................................................................................................9
3.2.2 Remove user ..............................................................................................................................................10
3.2.3 Add Employee ...........................................................................................................................................10
3.2.4 Remove Employee .....................................................................................................................................11
3.2.5 View list of employee ................................................................................................................................11
3.2.6 View list of login accounts ........................................................................................................................12
3.2.7 Total units consumed ................................................................................................................................12
3.2.8 Gives new connection ...............................................................................................................................13
3.02.9 Disconnection ..........................................................................................................................................13
3.2.10 Modify records ........................................................................................................................................14
3.2.11 Total connection ......................................................................................................................................14
3.2.12 List of consumer in a particular feeder .................................................................................................15
3.2.13 Calculate bill ...........................................................................................................................................15
3.2.14 change bill ................................................................................................................................................15
@GROUP ONE VII

3.2.15 Change rates ............................................................................................................................................16
3.2.16 Bill history ...............................................................................................................................................16
3.2.17 Generates bill ..........................................................................................................................................17
3.2.18 Pay bill .....................................................................................................................................................17
3.2.19 Waiting list ..............................................................................................................................................18
3.02 .1 Use case Diagram .......................................................................................................................................18
3.02.2 Use Case documentation ............................................................................................................................19
3.2.3 Business Rule Documentation......................................................................................................................32
3.2.4 Traceability Matrix ......................................................................................................................................32
4.External Interface Requirements ..........................................................................................................................33
4.1 User Interfaces .................................................................................................................................................33
4.2 hardware interface ...........................................................................................................................................39
4.3 Software Interfaces ..........................................................................................................................................39
4.4 Communications Interfaces ............................................................................................................................39
5. Analysis Models .....................................................................................................................................................40
5.1 Sequence Diagrams ..........................................................................................................................................40
5.2 Activity Diagrams ............................................................................................................................................45
5.3 Class Diagram ..................................................................................................................................................49
Appendix ....................................................................................................................................................................50
Reference ....................................................................................................................................................................50
@GROUP ONE VIII

1.INTRODUCTION
Electricity distribution systems are a vital infrastructure in modern society. The management of
such systems consists of balancing cost, performance and risk – taking into account different
aspects such as economic performance, quality of supply, safety and environmental impacts. The
"Electricity Consumption Billing System" is going to be developed to override the problems
prevailing in the practicing manual system. This software is supported to eliminate and in some
cases reduce the hardships faced by this existing system. More over this system is designed for the
particular need of the company to carry out operations in a smooth and effective manner.
1.1 PURPOSE
 The overall purpose of this system is gives new connection to user’s. User insert monthly
readings through this readings total consumed units are found and bill should be calculated.
System helps use to generated different types of reports. It helps use to speed up the work.
It reduced the manual work.
1.2 INTENDED AUDIENCE AND READING SUGGESTIONS

 This project is a prototype for the flight management system and it is restricted within the
college premises. This has been implemented under the guidance of college professors.
 This project is useful for the flight management team and as well as to the passenger.
 This project is a prototype for the Electricity Billing Management System and it is
restricted within the organization premises. We are developing our project electricity
Billing Management System that can be deployed in any organization.
 This SRS is mainly developed for the project development team. In this team there are the
project manager, developer, coder, and documentation writer and the user of the project
@GROUP ONE 1
1.3 PROJECT SCOPE

 This is desktop application that is designed for the electricity company. Electricity
Company Provide the meter to each user and assign consumer no. Admin is a super user
that provides login accounts to different department to access their modules. Computer
operator enters consumer number and its meter reading.
 System just calculates units and apply rates for calculate a bill. This system also calculates
the no. of units in a city and feeder. It also generated monthly and annual reports.
1.4 DEFINITIONS, ACRONYMS, AND ABBREVIATIONS.

 DBMS It stands for database management system.
 APBstands for automated power bill
 EBSIt stands for electricity billing system.
 GUI stands for graphical user interface.
 SRS Software Requirements Specification
 UMLUnified Modeling Language
 BRBusiness Requirement
1.5 OVERVIEW OF THE DOCUMENT

 The rest of a report consist the more detailed information about the system. Section two
consist the comparison of a project with older one, describe the user characteristics and
constraint that are apply on the system. Section three consist the functional, nonfunctional
requirements and their use case
2. THE OVERALL DESCRIPTION

2.1 PRODUCT PERSPECTIVE
 The Electricity billing system is a new system that is design to replace the manual billing
system EBS is a first version that overcomes the limitations of manual system. It speedup
the calculation of bills.
@GROUP ONE 2
2.2 OPERATIONS
 Admin and each user login to an application. Admin add or remove the user and employees
of an organization.
 Admin generated the different reports. Connection branch gives new connection to user.
He also modifies the personal information of the customer. He also checks the list of
connection in a particular feeder.
 Bill branch calculate, change and prints the bill. Also changes the rates per unit and taxes
.it also specify the list of customer that are not pay bill in a month. Finance branch paying
the bill of a consumer and also generate paid and unpaid list.
2.3 PRODUCT FUNCTIONS

 The main purpose of this product is to computerized the billing system, employee record
of a company.
 Admin register the employee of an organization and gives user ship to these registered
employees.
 Admin also add different feeders for some particular area. it also generated the different
type of reports. Connection branch gives connection to different consumers. There are two
types of meters such as home and commercial.
 Calculate the total home and commercial meters .it also activate the deactivate connections.
Billing branch defines rate per unit also define the late fee. It also defines the taxes.it also
calculate the bill and unit history. It generates the paper print of a bill. Computer operator
insert the readings. Fiancé officer paying bill, generate paid and unpaid list also generate
the total income report.
2.4 USER CHARACTERISTICS

 There are five different types of users. Admin is some kind of super user he adds other
users. He becomes a fully qualified and full control on database and different computer
application. Branch officer that is also a technical person who is fully trained. Third one is
computer operator that is knowledge of computer and he know how to use computer.
@GROUP ONE 3
2.5 GENERAL CONSTRAINTS

User and admin access their module when he has login account.
Admin gives only login account to a person who is employee of an organization.
Homes having domestic meter.
Shops and factories having commercial meter.
One consumer having one meter.
2.6 ASSUMPTIONS AND DEPENDENCIES

It totally computerized the billing system.
If the consumer uses less than 50 units then company gives him special discount.
3.SPECIFIC REQUIREMENTS
3.1 USER REQUIREMENTS
3.1.1. FUNCTIONAL USER REQUIREMENTS
Table 2: FR1: - Login
Req. ID: 01 Priority: high
Name: Login in to the system
Description: The system shall allow the system administrator to login to the system.
Source Rule
Related Req. 08
Table 3: FR2: add employee

Req.ID:02 Priority: high
Name: add employee
Description: The system shall allow the system administrator to add new employee to the
system.
Source Rule
Related Req. 03
@GROUP ONE 4
Table 4: FR3: Remove employee

Name: Remove employee
Description: The system shall allow the system administrator to remove employee from the
system.
Source Rule
Related Req 02
Table 5:FR4: view employee

Name: view employee
Description: The system shall allow the system administrator to view employee of the system.
Source Rule
Related Req. 05
Table 6: FR5: View list of login account

Name: View list of login account
Description: The system shall allow the system administrator to View list of login account to
the system.
Source Rule
Related Req. 04
@GROUP ONE 5
Table 7: FR6: Change taxes

Name: Change taxes
Description: The system shall allow the Billing Officer to manage taxes
Source Rule
Related Req. 07
Table 8: FR7: Change rates

Name: Change rates
Description: The system shall allow the Billing Officer to manage change in the rates of
the units.
Source Rule
Related Req. 06
Table 9: FR8: Change bill

Name: Change bill
Description: The system shall allow the Billing Officer answer consumer claims that his bill
is not correct.
Source Rule
Related Req. 07
@GROUP ONE 6
Table 10: FR9: Waiting List

Name: Waiting List
Description: The system shall allow the Finance Officer to see report of consumer who do not
pay bill.
Source Rule
Related Req. 10
Table 11: FR10: Calculate bill

Name: Calculate bill
Description: The system shall allow the computer operator to calculate bill.
Source Rule
Related Req. 09
3.1.2. NON -FUNCTIONAL REQUIREMENTS

Table 12: NFR1 Performance

Name: Performance
Description: The system shall allow the computer operator to calculate bill. Response to quires
not taking more time.
• Show confirmation message within the 4 seconds.
• Prints bill within the 7 seconds.
• It response quickly
Source Rule
Related Req. 6
@GROUP ONE 7
Table 13: NFR2 Reliability

Name: Reliability
Description The Electricity billing system is reliable than manual system. It consistently
performs the specified functions without failure. works are performed properly.
Source Rule
Related Req. 3
Table 14: NFR3 Security

Name: Security
Description: The user or admin only access the application when they login.
• They employees of an organization do not access the application without login
account.
Source Rule
Related Req. 2
Table 15: NFR4 Maintainability

Name: Maintainability
Description: There is also facility of maintenance in some time. Programmer adds some
features to maintain the application.
Source Rule
Related Req. 5
@GROUP ONE 8
Table 16: NFR5 Portability

Name: Portability
Description: The application is also portable from one system to another system
Source Rule
Related Req. 4
Table 17: NFR6 Availability

Name: Availability
Description: The system able to function during normal operating times.
Source Rule
Related Req. 1
3.2 SYSTEM REQUIREMENTS

3.2.1 ADD USER ACCOUNTS
3.2.1.1 Introduction
 In this admin gives login account to different peoples of an organization so that they access
their view.
3.2.1.2 Inputs
 Relevant user information such as name of the user and its department.
3.2.1.3 Processing
 The system checks that the employee is register or not.
@GROUP ONE 9
3.2.1.4 Outputs
 If the employee is registered, then system gives him login facility otherwise message show
that user is not registered.
3.2.1.5 Error Handling
 If admin enters such employee ids that is not register, then show error message that
employee is not register.
3.2.2 REMOVE USER

 In this step admin remove the user from the list.
3.2.2.2 Inputs
 Input the user id.
3.2.2.2 Processing
 Checks that user is available or not.
3.2.2.4 Outputs
 Show the message that user is removed or not available.
 Show error message that user is not register.
3.2.3 ADD EMPLOYEE

 In this section admin add the employee of an organization.
3.2.2.2 Inputs
 Input the personal information of the employee.
@GROUP ONE 10
3.2.2.3 Processing
 System adds that employee on employee list.
3.2.2.4 Outputs
 Show message that employee is registered.
 Employee already exists.
3.2.4 REMOVE EMPLOYEE

 In this section the employees are removed from the list of an organization.
3.2.4.2 Inputs
 Input the employee id.
3.2.4.3 Processing
 System checks that employee is existing or not.
3.2.4.4 Outputs
 Successfully removed from the list.
 This employee does not exist.
3.2.5 VIEW LIST OF EMPLOYEE

 In this admin view the list of employee that is part of an organization.
3.2.5.2 Inputs
 Admin input his login password.
@GROUP ONE 11
3.2.5.3 Processing
 System checks that his password is true.
3.2.5.4 Outputs
 Show the list of employee.
 Show error message that your password is not true.
3.2.6 VIEW LIST OF LOGIN ACCOUNTS

3.2.6.1 I NTRODUCTION
 In this section admin see the list of login accounts and their detail.
3.2.6.2 I NPUTS
 He enters only his login password.
3.2.6.3 P ROCESSING
 System checks that his password is match to enter password.
3.2.6.4 O UTPUTS
 Show the list of login accounts.
3.2.6.5 E RROR H ANDLING

 Show message that this is a wrong password.
3.2.7 TOTAL UNITS CONSUMED

 In this section admin checks the total number of units consumed in a month, 6 month and
year.
3.2.7.2 I NPUTS
 Input the month, year to which we want to check the unit consumed
3.2.7.3 P ROCESSING
@GROUP ONE 12
 System calculates the unit.
3.2.7.4 O UTPUTS
 Show the monthly, six month or annual report of unit consumed.

 Record of a particular time is not available.
3.2.8 GIVES NEW CONNECTION

 In this section we give new connection to user.
3.2.8.2 I NPUTS
 Enter the personal information such as name, address, CNIC no etc.
3.2.8.3 P ROCESSING
 System checks that user already exists or not. if not then registered him.
3.2.8.4 O UTPUTS
 Show message that connection is successfully registered.
3.2.8.5K E RROR H ANDLING

 Show error message if this user is already existing
3.02.9 DISCONNECTION
 In this section admin disconnect the connection of a particular consumer.
3.2.9.2 I NPUTS
 In this admin input the employee id.
3.2.9.3 P ROCESSING
 System checks that employee is registered or not.
3.2.9.4 O UTPUTS
 Show message that employee is successfully unregistered
@GROUP ONE 13
 Employee is not registered
3.2.10 MODIFY RECORDS

 In this section record of employee is modify.
3.2.10.2 I NPUTS
 Input the consume rid.
3.2.10.3 P ROCESSING
 System checks that is registered or not.
3.2.10.4 O UTPUTS
 Show message record is successfully updated.

 Show message that consumer is not available.
3.2.11 TOTAL CONNECTION

 In this section branch officer generated the total no. of connection detail.
3.2.11.2 I NPUTS
 Input his login password.
 Systems calculate the total no. of connection.
3.2.11.4 O UTPUTS
 Show the connections.

 You enter the wrong password.
@GROUP ONE 14
3.2.12 LIST OF CONSUMER IN A PARTICULAR FEEDER

 In this branch officer generate the report that consist list of consumer in a particular feeder.
3.2.12.2 I NPUTS
 Input the feeder name.
 Generated the report of consumer of a particular feeder.
3.2.12.4 O UTPUTS
 List of consumer of a particular feeder.

 Input feeder is not registered.
3.2.13 CALCULATE BILL

 Computer operator enters the reading of a particular meter to calculate the bill.
3.2.13.2 I NPUTS
 Enter the consumer id and meter reading of a meter.
 System checks that user is existing. if exist then make some calculation.
3.2.13.4 O UTPUTS
 Successfully enter the record.

 This user does not exist.
3.2.14 CHANGE BILL

 If there is some problem in bill, then this system provides facility to correct the bill.
@GROUP ONE 15
3.2.14.2 I NPUTS
 Enter the consumer id and correct meter reading
 System checks that user is existing or not. if exist then provide view
3.2.14.4 O UTPUTS
 Show message that bill is modified successfully.

 That consumer is not registered.
3.2.15 CHANGE RATES

 The billing officer changes the rates per units.
3.2.15.2 I NPUTS
 Enter his login account and then enter the new rates.
 System checks his login password and then changes the rates.
3.2.15.4 O UTPUTS
 Show message that is successfully modified.
 Your login password is incorrect.
3.2.16 BILL HISTORY

 In this billing officer see the billing history of a particular consumer.
3.2.16.2 I NPUTS
 Enter id of the consumer.
@GROUP ONE 16
 System checks that user is registered or not. if registers then show this bill history.
3.2.16.4 O UTPUTS
 Show his bill history.

 That consumer is not registered.
3.2.17 GENERATES BILL

 It also provides the facility of printing the bills.
3.2.17.2 I NPUTS
 Enter the consumer no or select the feeder.
 Checks that consumer is registered or not. if registered then prints his bill and prints the
bills of particular feeder.
3.2.17.4 O UTPUTS
 Prints the bills.

 That consumer or feeder is not registered.
3.2.18 PAY BILL

 In this computer operator pay the bills of particular consumer.
3.2.18.2 I NPUTS
 Enter the consumer id.
 Check that consumer is registered. If registered, then remove him from waiting list.
3.2.18.4 O UTPUTS
@GROUP ONE 17
 Show message that this bill is paid.

 That consumer is not registered or bill is also paid.
3.2.19 WAITING LIST

 This list consists list of consumer who do not pay bill.
3.2.19.2 I NPUTS
 To see this list branch officer login to his account.
 System checks that is a user of application if yes then generate the report that consist list
of consumer that not paid bill.
3.2.19.4 O UTPUTS
 Show the list of consumer who do not pay bill.

 Show error message that you have not login to this account
3.02 .1 USE CASE DIAGRAM

 Use Case Diagram captures the system's functionality and requirements by using actors
and use cases. Use Cases model the services, tasks, function that a system needs to perform.
 Use cases represent high-level functionalities and how a user will handle the system. Use-
cases are the core concepts of Unified Modeling language modeling.
@GROUP ONE 18
uc Use Case1
Use Case Diagram for Electricity billing system
Generate bill Pay the bill of a

consumer
Admin
Add Employee
Check total income

View list of employee
Finance officer
Remov e Employee «include» «include»
«include»
Waiting_list
«include» «include»
Change taxes «include»
«include»
«include»
Bill History Login

«include»
«include» Remov e the connection
«include»
Print the bill

«include»
«extend» «include»
«include»
Billing Officer Change rates
«include»
Registered the new
Logout connection
Connection Officer
Meter_Reading
calculate billl
Computer operator
Figure 1: use case diagram of Electricity Billing System
3.02.2 USE CASE DOCUMENTATION

Table 18: UD: LOGIN
Use Case ID: 01.0001
Use Case Name: Login
@GROUP ONE 19
Created By: Misganaw
Date Created: 12/03/2012
Updated By: Moti
Date Updated: 15/04/201
Actors: Admin, Billing Officer, Computer operator, Finance Officer, Connection

Officer
Description: The customer introduce his background information to the system when he/she
registered and using his/her account number the customer log in into the system
but the customer must registered first .
Trigger: The use case is being initiated when the user wants to login to the system.
Preconditions: User’s must have a legal account number (password and user name).
Normal Flow:  The admin writes the URL of the system in address bar of web browser
and press enter key from the key board.
 The system displays the system log in page on the user screen.
 The user clicks on the log in button.
 The system allows the customer/the user to enter his/her URL.
 The user fills his/her personal information and clicks on the sign button.
 The system displays the system home page.
Post conditions: The customer becomes a privileged user to the system
Alternative Flows:  “5.1” if the user fills wrong information the system displays an alert to
the user then go to line number five in the normal flow(5.1 indicates
the first alternative flow line number 5 in the normal flow).
Exceptions: If the customer fills wrong information: -
@GROUP ONE 20
 The system displays error message to the customer

 The system reminds to the customer to fills his/her personal information
again.
Priority: : High
Frequency of Use: Depends on the user interest
Business Rules: Unauthorized user cannot get an access to the system
Special Security
Requirements:
Assumptions: It is mandatory to the user to be registered first in the system
Notes and Issues( If the user attempts to use the system before he is registered to the system, he
fit criterion) cannot get an access. This is resolved by the Admin. Date due: 21/04/2012
Table 19: UD: Add employee
Use case ID 02.0002
Use Case Name: Add employee
Created By: Adem
Updated By: Mudesir
Actors: Admin
@GROUP ONE 21
Description: The admin wants to removed employee from the list of an organization
in order to facilitate its work .
Trigger: The use case is being initiated when the Admin wants to the system.
Preconditions: Employees have to provide their personal information to the concerned

body (i.e. to the Admin).
Normal Flow:  The admin login to the system using his account
 The system displays the system home page to the admin.
 The Admin selects add employee button and click on it.
 Input the personal information of the employee
 System adds that employee on employee list.
 Show message that employee is registered.
Post conditions: The customer becomes registered to the system
Alternative Flows:  “5.1” if the employee is registered before the system displays an alert to
the admin then go to line number five in the normal flow (Employee already
exists).
Exceptions: If the customer is already registered before: -

 The system displays error message (Employee already exists).
Priority: : High
Frequency of Use: When the admin wants to register new employees(depends on the
circumstances).
Business Rules: Registering an employee more than once is not allowed
Special Scalability
Requirements:
@GROUP ONE 22
Assumptions: The employee should be voluntary to work within the organization
Notes and Issues( The Admin have to refine the educational background of the employee
fit criterion) before registering him to the system. Date due: 27/04/2012
Table 20: UD: remove employee
Use case ID 03.0003
Use Case Name: Remove Employee
Created By: Moti
Updated By: Misganaw
Actors: Admin
Description: The admin wants to remove the employee from the organization for some
reasons.
Trigger: The use case is being initiated when the Admin wants to remove a particular
employee from the system.
Preconditions: Employee is being registered first to the organization
 The Admin selects remove employee button and click on it.
@GROUP ONE 23
 System removes that employee from employee list.

 Show message that employee is removed.
Post conditions: The customer becomes removed from the system
Alternative Flows:  “5.1” if the employee is not registered before the system displays an alert
to the admin then go to line number five in the normal flow (that employee
is not register).
Exceptions: If the customer is already removed before: -

 The system displays error message (Employee already removed).
Priority: : High
Frequency of Use: When the admin wants to remove existed employees(depends on the
circumstances).
Business Rules: an employee who violates the rule of the organization will be removed
Special Reliability
Requirements:
Assumptions: The employee may be involuntary to work within the organization
Notes and Issues( The Admin have to refine circumstances that results the employee is to be
fit criterion) removed. Date due: 29/04/2012
Table 21: UD: view employee
Use case ID 04.0004
Use Case view Employee

Name:
@GROUP ONE 24
Created By: Mudesir
Updated By: Adem
Actors: Admin
Description: The admin views the list of employee that is part of an organization.
Trigger: The use case is being initiated when the Admin wants to view list of employees
in the system.
Preconditions: The admin must register coworkers to the system
 The Admin selects view employee button and click on it.
 System display that employee information from employee list.
Post The admin viewed a particular customer information

conditions:
Alternative  “4.1” if the employee information is not stored in the database the system
Flows: displays an alert to the admin then go to line number four in the normal flow
(no Employee is registered ).
Exceptions: If the employee data is not existing in the system before: -

 The system displays error message (not registered).
@GROUP ONE 25
Priorit : High
y:
Frequency of When the admin wants to view existed employees(depends on the
Use: circumstances).
Business Rules: Employee must be registered first in order to be viewed
Special Usability
Requirements:
Assumptions: When the admin views the employee the system may display their list in
alphabetical order
Notes and Issues( The Admin have to give a unique ID to each customer. Date due: 30/04/2012
fit criterion)
Table 22: UD: Calculate bill
Use case ID 05.0005
Use ase Name: Calculate bill
Created By: Mudesir
Updated By: Adem
Actors: Computer operator
Description: . Computer operator enters the reading of a particular meter to calculate the bill.
@GROUP ONE 26
Trigger: The use case is being initiated when the Computer operator wants to calculate
the reading of a particular meter
Preconditions: Computer operator must register the exact reading of a particular meter in
KWH
Normal Flow:  The Computer operator login to the system using his account
 Enter the consumer id.
 System checks that user is existing. if exist then
 The Computer operator selects Calculate bill button and click on it.
 Input meter reading of a meter
 System calculates bill based on service charge postpaid.
 The system displays the amount of bill calculated
Post The Computer operator knows the amount of bill that a particular customer
conditions: payed.
Alternative  “4.1” if the Computer operator cannot get exact data of electric meter reading
Flows: the system displays an alert to him then go to line number four in the normal
flow (the data you entered is not correct ).
Exceptions: If the customer data is not existing in the system: -
The system displays error message (This user does not exist).
Priority: : High
Frequency of Monthly
Use:
Business Rules: Bill is calculated based on service charge post paid
@GROUP ONE 27
Special Performance
Requirements:
Assumptions: If the customer has not paid his bill in a prescribed period of time there might
be some penalty
Notes and If the customer has not paid his bill in a prescribed period of time he cannot
Issues( fit get bill service. Date due: 16/05/2012
criterion)
Table 23: UD: pay bill
Use Case Pay bill

Name:
Created By: Misganaw
Updated By: Moti
Actors: Finance Officer
Description: In this Finance Officer pay the bills of particular consumer
Trigger: The use case is being initiated when the Finance Officer wants to pay the bills of
particular consumer.
Preconditions: User’s must have an electricity invoices in order to pay their bill.
@GROUP ONE 28
Normal Flow:  The Finance Officer login to the system using his account
 The system displays the system home page to the Finance Officer.
 Enter the consumer id.
 System checks that user is existing. if exist then
 The Finance Officer selects pay bill button and click on it.
 Then remove him from waiting list
 The system Show message that this bill is paid.
Post The customer is being removed from the waiting list

conditions:
Alternative  “4.1” if the consumer is not exist the system displays an alert to the Finance
Flows: officer then go to line number four in the normal flow
Exceptions: If the customer fills wrong information: -
The system displays error message to the Finance officer (That consumer is not
registered or bill is also not paid).
Priority: : High
Frequency of Monthly
Use:
Business Rules: If the consumer will not pay his bill periodically he is under waiting list
Special Performance
Requirements:
Assumptions: If the customer has not paid his bill in a prescribed period of time there might be
some penalty
@GROUP ONE 29
Notes and If the customer has not paid his bill in a prescribed period of time he has to be in
Issues( fit waiting list. Date due: 5/04/2012
criterion)
Table 24: UD: Gives new connection
UseCase Name: Gives new connection
Created By: Moti
Updated By: Misganaw
Actors: Connection Officer
Description: In this section Connection Officer give new connection to user
Trigger: The use case is being initiated when the Connection Officer wants to give new
connection to user
Preconditions: Connection Officer should have network infrastructure such as LAN, WAN.
Normal Flow:  The Connection Officer login to the system using his account
 The system displays the system home page to the Connection Officer.
 The Connection Officer selects give new connection button and click on it.
@GROUP ONE 30
 Enter the personal information such as name, address

 System checks that user already exists or not. If not, then registered him.
 Show message that connection is successfully registered.
Post conditions: The user gets new connection
Alternative  “4.1” if the user is not exist then go to line number four in the normal flow
Flows: and the system registers him
Exceptions: Show error message if this user is already exist.
Priority: : High
Frequency of Once
Use:
Business Rules: If the connection is not available enough, the user have to notify to the concerned
body
Special Scalability
Requirements:
Assumptions: If large number of user uses the connection simultaneously the system might got busy
Notes and The connection Officer limits the number of user so as to safeguard the system from
Issues( fit becoming busy. Date due: 29/04/2012
criterion)
@GROUP ONE 31
3.2.3 BUSINESS RULE DOCUMENTATION

 BR-101Allow non-bank transactions to use cash accounts: - We recommend that you
never allow non-bank transactions to use cash accounts. However, we do offer the option
to allow non-bank transactions with this business rule.
 BR-102scheduled read date means the date upon which a particular distributor’s meter
is scheduled to be read.
 BR-103 Queue Business Rules: - select Queue on the left side of the Business Rules
page and make selections on the right.
 BR-104 working day means any day other than Sunday and holiday.
 BR-105customer bill means an invoice presented to a customer reflecting tariff and
energy charges.
3.2.4 TRACEABILITY MATRIX
 Shows the relationships between requirements. Requirements are listed along the
horizontal and vertical axes and relationships between requirements are marked in the table
cells. Traceability Table tables for showing requirements dependencies should be defined
with requirement numbers used to label the rows and columns of table.
List of requirements to be traced are: -
 The admin must be login before access their view(FR1)

 In this section the employees are removed from the list of an organization (FR2)
 The system should enable admin to view the list of employee that is part of an
organization(FR3)
 In this section Billing officer should generated the total no number of connection
detail(FR4)
 Billing officer should View bill history of a particular consumer. Starts when a consumer wants
to see his bill(FR6)
 The system must generate unpaid history(FR7)
 The Billing Officer must be login before access their view(FR8)
 The system should remove the connection(FR9)
 The system should generate report of total connection (FR10)
@GROUP ONE 32
Table 25: Traceability Table
Depends FR1 FR2 FR3 FR4 FR6 FR7 FR8 FR9

on
FR1 *
FR2 * *
FR3 *
FR4 *
FR6 *
FR7 *
FR8 *
FR9 *
FR10 *
4.EXTERNAL INTERFACE REQUIREMENTS

4.1 USER INTERFACES
• It works the products appearance and function
• UI design manages to style the structure and content – what the user sees during the
experience.
@GROUP ONE 33
Figure 2: Electricity sale bill
@GROUP ONE 34
Figure 3: Customer login form
@GROUP ONE 35
Figure 4: Customer Register form
@GROUP ONE 36
Figure 5: data view of meter details form
@GROUP ONE 37
Figure 6: Calculate electricity bill form
@GROUP ONE 38
4.2 HARDWARE INTERFACE
figure 7: Hardware Interfaces of billing system
4.3 SOFTWARE INTERFACES

 This application is interacting with Microsoft SQL Server.
4.4 COMMUNICATIONS INTERFACES

 . In communication studies, the notion of an interface in the work environment is used for
a point of interaction between a number of systems or work groups. In the environment,
the coordination and interaction between several work groups is used to communicate plans
and control production activity.
@GROUP ONE 39
5. ANALYSIS MODELS
In business, System Analysis and Design refers to the process of examining a business situation
with the intent of improving it through better procedures and methods.
System analysis and design relates to shaping organizations, improving performance and
achieving objectives for profitability and growth. The emphasis is on systems in action, the
relationships among subsystems and their contribution to meeting a common goal.
5.1 SEQUENCE DIAGRAMS

 UML Sequence Diagrams are interaction diagrams that detail how operations are carried
out. They capture the interaction between objects in the context of collaboration.
Sequence Diagrams are time focus and they show the order of the interaction visually by
using the vertical axis of the diagram to represent time what messages are sent and when.
Sequence Diagrams captures:
 the interaction that takes place in a collaboration that either realizes a use case or an
operation (instance diagrams or generic diagrams)
 high-level interactions between user of the system and the system, between the system
and other systems, or between subsystems (sometimes known as system sequence
diagrams)
@GROUP ONE 40
Figure 8: Sequence Diagram for generate bill
@GROUP ONE 41
Figure 9: Sequence Diagram for add employee
@GROUP ONE 42
Figure 10: Sequence Diagram for remove employee
@GROUP ONE 43
Figure 11: Sequence Diagram for calculate bill
@GROUP ONE 44
Figure 12: Sequence Diagram for bill history
5.2 ACTIVITY DIAGRAMS

 Activity Diagrams describe how activities are coordinated to provide a service which can
be at different levels of abstraction. Typically, an event needs to be achieved by some
operations, particularly where the operation is intended to achieve a number of different
things that require coordination, or how the events in a single use case relate to one
another, in particular, use cases where activities may overlap and require coordination.
 It is also suitable for modeling how a collection of use cases coordinates to represent
business workflows.
@GROUP ONE 45
act Generate_Bill
billing_Officer w ants to Enter the

see the billing history of a consumer no
particular consumer.
start Billing_Officer enter another consumer id
That consumer is
not registered.
Checks that consumer is registered or not
Prints the bills.for the

particular customer
end
Figure 13: Activity Diagram for generate bill
@GROUP ONE 46
act Remov e Employee
Input the
list of employees employee id.
are remov ed from
an organization.
start
This
employee
checks that employee is existing or not. does not
exist.
Successfully
remov ed from the
list.
end
Figure 14: Activity Diagram for remove Employee
@GROUP ONE 47
act View list of employee
admin w ants to v iew the Admin input his

list of employee that is login passw ord.
part of an organization.
Admin re_enter his password again
start
Show error
message that
System checks that his
your passw ord
password is true. is not true.
Show the list of employee.
end
Figure 15: Activity Diagram for list of Employee
act Add Employee
Input the
admin add the personal
employee of an information of
organization. the employee. Adm i n re_enter Non_Repeated user
start
an Employee
already exists
checksIs an Em pl oyee al ready exi sts?.
System adds that

employee on
employee list.
Show message that

employee is
registered.
end
Figure 16: Activity Diagram for add Employee
@GROUP ONE 48
act calculate_Bill
Computer operator enters Enter the

the reading of a particular consumer id and
meter to calculate the bill. meter reading of a
meter. Billing_Officer enter another user
start
This user
does not
System checks that user is exist exist.
then make some

Successfully enter
calculation.
the record.
end
Figure 17: Activity Diagram for calculate bill
5.3 CLASS DIAGRAM
 Class Diagram gives the static view of an application. A class diagram describes the types
of objects in the system and the different types of relationships that exist among them. This
modeling method can run with almost all Object-Oriented Methods. A class can refer to
another class. A class can have its objects or may inherit from other classes.
 UML Class Diagram gives an overview of a software system by displaying classes,
attributes, operations, and their relationships. This Diagram includes the class name,
attributes, and operation in separate designated compartments.
 Class Diagram helps construct the code for the software application development.
@GROUP ONE 49
class dd
Admin
{1} Billing_Branch_officer
{1..*}
- l ogi n_Account: i nt
+ name: char - l ogi n_Account: i nt
- name: Stri ng
- add_Empl oyees() : voi d
+ generated_Report() : voi d + Change_Late_Fee() : doubl e
- gi ves_Logi n_Acc_T o_Users.() : voi d - Change_Rates() : voi d
- remove_Empl oyees() : voi d - Change_T axes() : voi d
- Remove_Logi n_Acc() : char + Pri nt_Bi l l s.() : voi d
+ Vi ew_Li st_Of_Empl oyees() : voi d - Vi ew_Bi l l _Hi story() : voi d
+ Vi ew_Li st_Of_Users.() : voi d
Connection_Branch _Officer
{1..*} Billing_Computer_Opperator Finance_Officer
- l ogi n_Acc: i nt {1..*} {1..*}
+ name: char - l ogi n_Account: i nt - l ogi n_Account: doubl e
- name: i nt + name: Stri ng
+ generate_Report_Conn() : voi d
+ Regi stered_New_Conn() : voi d + metere_Readi ng() : voi d + pai d_Hi story() : voi d
+ remove_New_Conn() : voi d + Check_T otal _Income() : doubl e
+ Vi ew_Status_Of_Meter() : voi d + Pay_Bi l l _Of_Consumer() : voi d
+ unpai d_Hi story() : voi d
Figure 18: Class Diagram Electricity consumption and billing system
APPENDIX
I. Interviews the process that we used to gather information
II. Review of written materials
III. Mr. Robelthe name of the person we talked to
IV. www.Google.com
REFERENCE
www.google.com
International Standards for all electrical, electronic and related technologies available at
http://www.iec.ch.
http://www.bpdb.gov.bd/tariff.htm
Our course teacher
www.youtube.com
@GROUP ONE 50

Eleectricity Billing System

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Eleectricity Billing System

Uploaded by

Copyright:

Available Formats

Electricity Consumption and Billing System

Software Requirements Specification for Industrial project on

Submitted to Instructor ፡YOHANNES

Submission Date: - 23/05/2012

Table 1: Roles and Responsibilities of the Group Members

List of Tasks List members

Misganaw Moti Tullu Adem Abate Mudesir Maru

@GROUP ONE III

 Figure 1: use case diagram of Electricity Billing System

 Table 1: Roles and Responsibilities of the Group Members

 Table 4: FR3: Remove employee

@GROUP ONE VII

@GROUP ONE VIII

1.2 INTENDED AUDIENCE AND READING SUGGESTIONS

1.3 PROJECT SCOPE

1.4 DEFINITIONS, ACRONYMS, AND ABBREVIATIONS.

1.5 OVERVIEW OF THE DOCUMENT

2. THE OVERALL DESCRIPTION

2.3 PRODUCT FUNCTIONS

2.4 USER CHARACTERISTICS

2.5 GENERAL CONSTRAINTS

2.6 ASSUMPTIONS AND DEPENDENCIES

Name: Login in to the system

Table 3: FR2: add employee

Table 4: FR3: Remove employee

Table 5:FR4: view employee

Table 6: FR5: View list of login account

Req.ID:05 Priority: high

Table 7: FR6: Change taxes

Req.ID:06 Priority: high

Table 8: FR7: Change rates

Req.ID:07 Priority: high

Table 9: FR8: Change bill

Req.ID:08 Priority: high

Table 10: FR9: Waiting List

Req.ID:09 Priority: high

Table 11: FR10: Calculate bill

Req.ID:10 Priority: high

3.1.2. NON -FUNCTIONAL REQUIREMENTS

Req.ID:1 Priority: high

Table 13: NFR2 Reliability

Req.ID:2 Priority: high

Table 14: NFR3 Security

Req.ID:3 Priority: high

Req.ID:4 Priority: high

Table 16: NFR5 Portability

Req.ID:5 Priority: high

Table 17: NFR6 Availability

3.2 SYSTEM REQUIREMENTS

 The system checks that the employee is register or not.

3.2.1.5 Error Handling

3.2.2 REMOVE USER

 In this step admin remove the user from the list.

 Input the user id.

 Checks that user is available or not.

 Show the message that user is removed or not available.

3.2.2.5 Error Handling

 Show error message that user is not register.

3.2.3 ADD EMPLOYEE

 In this section admin add the employee of an organization.

 Input the personal information of the employee.

 System adds that employee on employee list.

 Show message that employee is registered.