Electricity Billing System

Download as docx, pdf, or txt
Download as docx, pdf, or txt
You are on page 1of 21

Electricity Billing System

CHAPTER 1
INTRODUCTION

Our project entitled “Billing System and Revenue Management” aims is to generate the
total number of electricity bill prepared, add new consumers and to collect revenue in a single
day. Manual system that is employed is extremely laborious and quite inadequate. It only
makes the process more difficult and hard.
The aim of our project is to develop a system that is meant to partially computerize the work
performed in the Electricity Board like generating monthly electricity bill, record of
consuming unit of energy, store record of the customer and previous unpaid record. Our
system has two types of accessing modes, administrator and employees. New bill preparation,
adding of new consumers, bill dispatch, revenue collected works are managed by the Sub-
division employees. When a division level employee logs in to the system he can only view
the number of bill prepared, bill dispatched, total revenue collected according to date-wise.
Employee username, passwords and creation of new sub-divisions are managed by the
administrator.
Electricity Billing System

CHAPTER 2
INITIAL SYSTEM STUDY

2.1Scope:
Our project aims at Business process automation, i.e. we have tried to computerize various
processes of Electricity Billing System. In the sector of electricity board, we have computerized their
department and stock maintenance.
Scope of any software depends upon the following things:

1. It satisfy the user requirement


2. Be easy to understand by the user and operator
3. Be easy to operate
4. Have a good user interface
5. Be expandable
6. Delivered on schedule within the budget.

We have tried to make such type of software, which satisfy the above given
requirement.

2.2 Objectives of the System:


The firm handles all of the work manually, which is very tedious and mismanaged.
The objective of our project is as follows:
a. To keep the information of Customer.
b. To keep the information of consuming unit of energy of current month.
c. To keep the information of consuming unit of energy of previous month.
d. To keep the information of employee working in the department. e. To maintain the
record of the department.
Electricity Billing System

Chapter 3
SYSTEM ANALYSIS

3.1 Identification of problems:


The old manual system was suffering from a series of drawbacks. Since whole of the system
was to be maintained with hands the process of keeping, maintaining and retrieving the
information was very tedious and lengthy. The records were never used to be in a systematic
order. There used to be lots of difficulties in associating any particular transaction with a
particular context. If any information was to be found it was required to go through the
different registers, documents there would never exist anything like report generation. There
would always be unnecessary consumption of time while entering records and retrieving
records. One more problem was that it was very difficult to find errors while entering the
records. Once the records were entered it was very difficult to update these records.

In present, work done in the electricity board is performed manually which is a great
headache for the department.The reason behind it is that there is lot of information to be
maintained and have to be kept in mind while running the business .For this reason we have
provided features Present system is partially automated (computerized), actually existing
system is quite laborious as one has to enter same information at three different places.

3.2 Feasibility Study:


Feasibility study is the phase in which the analyst checks that the candidate system
is feasible for the organization or not. This entails identification, description & evaluation of
the system. Feasibility study is done to select the best system that meets the performance
requirement.

If the feasibility study is to serve as a decision document, it must answer key


questions.

1. Is there a new and better way to do the job that will benefit the user?

2. What are the costs and savings of the alternatives?

3. What is recommended?

The most successful system projects are not necessarily the biggest or most visible
in the business but rather those truly meet user’s expectations.
Electricity Billing System

Feasibility considerations

Three key considerations are involved in the feasibility study. They are as follows: -

Economic Feasibility
Economic analysis is the most frequently used method for evaluating the effectiveness of the
candidate system.

We analyse the candidate system (computerized system) is feasible as than the manual system
because it saves the money, time and manpower. It also feasible according to cost benefits analysis.

Technical Feasibility
Technical feasibility centres around the technology used. It means the candidate system is
technically feasible i.e. it doesn’t have any technical fault and work properly in the given
environment. Our system is technically feasible; it is providing us required output.

Behavioural Feasibility
Behavioural feasibility is the analysis of behaviour of the candidate system. In this we
analyse that the candidate system is working properly or not. If working than it communicating
proper with the environment or not. All this matter is analysed and a good candidate system is
prepared. Due to the change of system what is the change in behaviour of the users, these factors are
also analysed.
Electricity Billing System

CHAPTER 4
SOFTWARE AND HARDWARE REQUIREMENT SPECIFICATION

4.1. REQUIREMENT SPECIFICATION

The final output is the requirements specification document (SRS). For smaller
problems or problems that can easily be comprehended; the specification activity might come
after the entire analysis is complete. However, it is more likely that problem analysis and
specification are done concurrently. All the information for specification activity follows the
analysis activity. The transition from analysis to specification should also not be expected to
be straightforward, even if some formal modelling is used during analysis.
Essentially, what passes from requirements analysis activity to the specification activity is the
knowledge acquired about the system. The modelling is essentially a tool to help obtain a
thorough and complete knowledge about the proposed system.

4.1.1. ANALYSIS OF FACTUAL DATA

Analysis of data is a process of inspecting, cleaning, transforming, and


modelling data with the goal of highlighting useful information, suggesting
conclusions, and supporting decision making. Data analysis has multiple facets and
approaches, encompassing diver se techniques under a variety of names, in different
business, science, and social science domains.

Data mining is a particular data analysis technique that focuses on modelling and
knowledge discovery for predictive rather than purely descriptive purposes.

4.1.2. IDENTIFICATION OF ESSENTIAL REQUIREMENT

Identification of essential requirement is an important task in developing the project. In


this system the essential requirements are identified through surveying. By surveying, the
important needs of the user in our website are known. In the surveying, the different
possibilities of tour information that have to be included in the website is given by
questionnaire.
Electricity Billing System

4.1.3. SELECTION OF REQUIREMENT STRATEGIES

From the survey analysis graph, it is clear that which are all the requirements
that the user requires the most. It is decided to include the required information
and omit the less priority ones.

4.2. DEFINITION OF INPUT REQUIREMENTS

4.2.1. EMPLOYEE LOGIN SYSTEM

Employee of the organisation will carry out his own login with username and password
providing by the admin to associate to their application. This will enable the system to
display
billing information and revenue when the employee logs in and certain information, such as
billing date and revenue collected, to be added to each application automatically. Here a sub-
division level employee can add new information such as new customers, new bill prepared
and new bill dispatched etc. Requiring a login process will also add greater security to the
system, as once a sub-division has logged in with their username and password, they will be
the only person able to update their information and the other employees can only view the
information.

4.2.2. ADMINISTRATION LOGIN SYSTEM

The login process will be as straightforward as possible, using an intuitive form layout,
with the necessary username and password. The admin will monitor the information and he
can change the username and password of other employees. He can also create new sub-
division under any circle.

4.3. DEFINITION OF PROCESSING REQUIREMENTS


Electricity Billing System

The user interface for this system will have to be simple and clear. Most importantly,
the pages must be easy to read, easy to understand and accessible. The colour scheme should
be appropriate to provide familiarity with the university and there should be no contrast
issues.

There are many functions the system can perform and these must be logically grouped
or displayed in an intuitive order to allow the user to perform tasks quickly and efficiently,
without getting lost in excessive amounts of text. The system must also display a large
amount of information and to avoid confusion this must be displayed in categories or in
different pages. Furthermore, a small amount of information may be displayed initially, for
example with a certain limit on date or amount, and the ability to view more in-depth
information on the subject should be apparent.

The different information displays and functionality objects should be individually


distinguishable, allowing the user to navigate through recognition, rather than recall in
addition, each function must provide the ability to cancel, leaving the user with the ability to
rectify mistakes, and every page should include the ability to return to a central location of
the system, ensuring that the user does not get lost within the system with no convenient way
to navigate.

The system will provide different views for different users, allowing multiple access
levels. For example, an employee can only login with the username and password provided
by admin, whereas an administrator can change the username and password of employees and
will have many more privileges. Being an online system, it will naturally be viewable from
any computer with an internet connection, allowing admissions from home, for example. This
will provide far more accessibility than if it were written in a language with only limited
online capability as any computer is a potential work station, rather than relying on the
program being installed.

4.4. DEFINITION OF OUTPUT REQUIREMENTS

The most important function is to show the list of bills prepared and revenue collected
under the circumstances made by the sub divisions.
Electricity Billing System

4.5. OBJECTIVE OF SRS

The objective of this SRS document is to specify software requirements of


the electricity billing and revenue management. It is intended to be a complete
specification of what functionality the billing management provides. The main purpose of the
system is to view the task carried out by different peoples in the organization according to
date wise. Specific design and implementation details will be specified in a future document.

4.6. OVERVIEW OF SRS

SRS will include two sections.


Overall Description will describe major components of the system, interconnection and
external interfaces.
Specific Requirements will describe the functions of actors, their role in the system and
constraints.

4.6.1. OVERALL DESCRIPTION

The SRS document will give further details on the overall product description,
including the hardware, software, and communications interfaces, product functions, user
characteristics, and any assumptions that will be made.

4.6.2. SPECIFIC REQUIREMENTS

The SRS document will also include the specific requirements needed. These will
include the functions, performance, design, and software attributes. This document is
organized in a logical manner and is easy to follow. Readers should refer to the table of
contents, appendices, or index if looking for something in specific. Otherwise, reading this
document from start to finish will start with a vague description and get more specific and
detailed as changing sections and reading further.
Electricity Billing System

4.7. HARDWARE CONFIGURATION

- System : Multimedia PC
- Processor : Pentium 4 or above
- Memory :512MB RAM
- Hard Disk : 80GB or above
- Keyboard : 104 standards
- Monitor : SVGA
- Modem : Dial up/Broadband

4.8. SOFTWARE CONFIGURATION

- Front end : PHP,HTML


- Back end : MYSQL
- Host: Apache server
- Operating System: Windows , LINUX, MAC
Electricity Billing System

CHAPTER 5
SYSTEM DESIGN

The system design develops the architectural detail required to build a system or
product. As in the case of any systematic approach, this software too has undergone the best
possible design phase fine tuning all efficiency, performance and accuracy levels. The first
step in system designing is to determine how the output is to be produced and in what format.
Samples of the output and input are also presented. In the second step, input data and master
files are to be designed to meet requirement of the proposed output. The processing phases
are handled through program construction and testing, including a list of the programs needed
to meet the system’s objectives and complete documentation.

5.1. DESIGN METHODOLOGY

System design is the solution to the creation of a new system. This phase is composed
of several systems. This phase focuses on the detailed implementation of the feasible system.
It emphasis is on translating design specifications to performance specification. System
design has two phases of development logical and physical design.
During logical design phase the analyst describes inputs (sources), out puts (destinations),
databases (data sores) and procedures (data flows) all in a format that meats the uses
requirements. The analyst also specifies the user needs and at a level that virtually determines
the information flow into and out of the system and the data resources. Here the logical
design is done through data flow diagrams and database design. The physical design is
followed by physical design or coding. Physical design produces the working system by
defining the design specifications, which tell the programmers exactly what the candidate
system must do. The programmers write the necessary programs that accept input from the
user, perform necessary processing on accepted data through call and produce the required
report on a hard copy or display it on the screen.

5.1.1. LOGICAL DESIGN


Electricity Billing System

Logical design of an information system shows the major features and also how they
are related to one another. The first step of the system design is to design logical design
elements. This is the most creative and challenging phase and important too. Design of
proposed system produces the details of the state how the system will meet the requirements
identified during the system analysis that is, in the design phase we have to find how to solve
the difficulties faced by the existing system. The logical design of the proposed system
should include the details that contain how the solutions can be implemented. It also specifies
how the database is to be built for storing and retrieving data, what kind of reports are to be
created and what are the inputs to be given to the system. The logical design includes input
design, output design, and database design and physical design.

5.1.2. PHYSICAL DESIGN

The process of developing the program software is referred to as physical design. We


have to design the process by identifying reports and the other outputs the system will
produce. Coding the program for each module with its logic is performed in this step. Proper
software specification is also done in this step.

5.1.3. MODULAR DESIGN

A software system is always divided into several sub systems that makes it easier for
the development. A software system that is structured into several subsystems makes it easy
for the development and testing. The different subsystems are known as the modules and the
process of dividing an entire system into subsystems is known as modularization or
decomposition.

A system cannot be decomposed into several subsystems in any way. There must some
logical barrier, which facilitates the separation of each module. The separation must be
simple but yet must be effective so that the development is not affected.

The system under consideration has been divided into several modules taking in
consideration the above-mentioned criteria. The different modules are-
Electricity Billing System

1. User module
2. Administrator module

5.2. INPUT DESIGN

The input design is the link between the information system and the user. It comprises
the developing specification and procedures for data preparation and those steps are
necessary to put transaction data into a usable form for processing data entry. The activity of
putting data into the computer for processing can be achieved by inspecting the computer to
read data from a written or printed document or it can occur by having people keying the data
directly into the system. The design of input focuses on controlling the amount of input
required, controlling errors, avoiding delay, avoiding extra steps and keeping the process
simple.

The system needs the data regarding the asset items, depreciation rates, asset
transfer, and physical verification for various validation, checking, calculation and
report generation. The error raising method is also included in the software, which
helps to raise error message while wrong entry of input is done. So in input design
the following things are considered.

What data should be given as input?


How the data should be arranged or coded?
Methods for preparing input validations and steps to follow when error occur.

5.3. OUTPUT DESIGN

Computer output is the most important and direct information source to the user.
Output design is a process that involves designing necessary outputs in the form of reports
that should be given to the users according to the requirements. Efficient, intelligible output
design should improve the system's relationship with the user and help in decision making.
Since the reports are directing referred by the management for taking decisions and to draw
conclusions they must be designed with almost care and the details in the reports must be
simple, descriptive and clear to the user. So, while designing output the following things are
to be considered.
Electricity Billing System

Determine what information to present.


Arrange the presentation of information in an acceptable format.
Decide how to distribute the output to intended receipts.

Depending on the nature and future use of output required, they can be displayed on the
monitor for immediate need and for obtaining the hardcopy.
Electricity Billing System

CHAPTER 6
ARCHITECTURAL DESIGN
6.1 SDLC (System Development Life Cycle):

System development life cycle is a sequence of events carried out by analyst, designers and
users to develop and important an information system.
Activities are carried out in different stages.

The phases are as follows:

1. Preliminary Investigation (Feasibility Study)


2. Determination of System Requirement
3. Design of The System
4. Development of Software
5. System Testing
6. System Implementation
7. System Maintenance
The Analyst finds out whether current technical resources, which are available in the
organization, is capable of Handling user requirements.

Economical Feasibility:

Economical or financial feasibility is second part of resource determination. Basic


resources to consider are:
Management time
Time spent by system analysis team
Cost of doing the full system study
Estimated cost of hardware
Estimated cost of software

Operational Feasibility:
Operational feasibility is dependent upon determining human resources for the project.
It refers to projecting whether the system will operate and be used once it is installed.
The document to be produced at the end of this activity is called
“FEASIBILITY STUDY REPORT”
Electricity Billing System

2. Determination of Requirements (Analysis)

Determination of system requirement involves studying the current business system in


Great detail to find out how it works and where improvements have to be made.
This activity is carried out in two phases:
Detailed investigation
Analysis or determination of system requirement

Detailed investigation

The heart of the system analysis is aimed at having a detailed understanding of all-
important facts of the project under consideration. Analyst working closely with employees
and managers must be able to answer the following key question:
What is being done by the current system? How is being done?
How frequently does it occur?
How big is the volume of transactions or decisions? How well is the task being
performed?
Does a problem exist?
If problem exists, how serious is it?
If a problem exists, what is the underlying cause?

To answer the above question system analyst talks to a variety of people to gather
details about the project. Questionnaires are used to collect this information from large
groups of people who Cannot be interviewed individually. Detailed investigations also
require the study of Manual and reports, actual observation of work activities and collection
of existing Forms and document to fully understand the project.
Analysis or determination of system requirement
It is during this phase that the analyst and the user come to an agreement on
what Functions the proposed system has to perform.

A detailed document has to prepare by system analyst containing the following:


Electricity Billing System

Inputs that must be received by the system


The outputs to be produced by the system
The data to be retained
The procedures to get the output from the given inputs
Audit and control requirements
System acceptance criteria
This detailed document is called functional specification or proposed procedures.

3. Design Of The System

The design process should take care of the following: Identification of reports and
outputs the new system should produce.
Scrutinize the data present on each report/output

Sketch the form or display as expected to appear at the end of completion of the system.
This may be done on paper or on a computer display using one of the automated system
design tools description of data to be input calculated or stored individual data items and
calculation procedure written in detail.
The procedures written should tell how to process the data and produce the output
The document produced at the end of this activity is called design specification

4. Development Of Software
In this stage the actual coding / writing of the program is done. Analyst

– programmers do analyst and designs well as code programs programmers are


responsible for documenting the program including comments that explain both
how and why certain procedure was coded in specific way. Programs are individually
tested using some test data. Documentation is also essential to test the programs and carry
out maintenance once the application has been installed.
This activity of system development life cycle produces tested programs.
Electricity Billing System

5. System Testing
Once the programs are tested individually the system as a whole needs to tested. During
testing the system is used experimentally to ensure that the software does not Fail that it will
run according to its specifications and in the way user accept it too. special test data is
prepared as input for processing and the result are examined to Locate unexpected result.

6. System Implementation
In this stage the system analyst uses new software, which has been tested into use.
user personnel are trained and any files of data needed by the new system are constructed.
Thus new software is installed and then used.

7. System Maintenance
Once installed the software is often used for many years. However both the
organization and user change. The environment may also change over a period of time;
therefore, the software has to be maintained.

6.2 DFD (Data Flow Diagram):


They are the versatile diagramming tools used for structured system analysis. They are
specifically used for process modelling which involves graphically representing the function
or process, which captures, manipulate, store, and distribute data between a system and its
environment and between components within a system.

6.3 CONTEXT DIAGRAM:


This is the start point of data flow diagramming process. It is denoted as the highest-
level diagram. It gives an overview of an organizational system that shows the system
boundaries, external entities that interact with the system and the major information flows
between the entities and the system.
Electricity Billing System

CHAPTER 7
TECHNOLOGY SPECIFICATION

7.1. PHP (PHP: Hypertext Preprocessor)

PHP, which stands for “PHP: Hypertext Preprocessor" is a widely-used Open Source
general-purpose scripting language that is especially suited for Web development and can be
embedded into HTML. Its syntax draws upon C, Java, and Perl, and is easy to learn. The
main goal of the language is to allow web developers to write dynamically generated web
pages quickly, but you can do much more with PHP.

Security

PHP is a powerful language and the interpreter, whether included in a web server as a
module or executed as a separate CGI binary, is able to access files, execute commands and
open network connections on the server. These properties make anything run on a web server
insecure by default. PHP is designed specifically to be a more secure language for writing
CGI programs than Per l or C, and with correct selection of compile time and runtime
configuration options, and proper coding practices, it can give you exactly the combination of
freedom and security you need. As there are many different ways of utilizing PHP, there are
many configuration options controlling its behavior. A large selection of options guarantees
you can use PHP for a lot of purposes, but it also means there are combinations of these
options and server configurations that result in an insecure setup.

The configuration flexibility of PHP is equally rivaled by the code flexibility. PHP can
be used to build complete server applications, with all the power of a shell user, or it can be
used for simple server-side includes with little risk in a tightly controlled environment. How
you build that environment, and how secure it is, is largely up to the PHP developer.

Features
Electricity Billing System

PHP manages freeing all resources. Users does not required to free file handle resource,
database resources, memory, etc, unless programmer need to free resource during script
execution. All resources are released after script execution PHP4 also have reference count
feature. For example, memory for variables is shared when it assigned to other variable. If
contents have been changed, PHP4 allocate new memory for it. Programmer does not have to
use pass by reference for large parameters for better performance with
PHP4.It would be a nice section for new PHP user s, if there is "Resource Handling" section
or like. Explanation about reference count feature in PHP4 would be very helpful to write
better PHP4 scripts also.

7.2. My SQL

My SQL query () sends a unique query (multiple queries are not supported) to the
currently active database on the server that's associated with the specified link_identifier. The
query string should not end with a semicolon. If the link identifier is not specified, the last
link opened by My SQL connection is assumed. If no such link is found, it will try to create
one as if mysql_connect() was called with no arguments. If by chance no connection is found
or established, an E_WARNING level warning is generated.

7.3. Bootstrap
Bootstrap is a powerful front-end framework for faster and easier web development. It
includes HTML and CSS based design templates for common user interface components like
Typography, Forms, Buttons, Tables, Navigations, Dropdowns, Alerts, Modals, Tabs,
Accordion, Carousel and many other as well as optional JavaScript extensions.

Appealing Features of Bootstrap


Bootstrap has a lot of features. These features not only make it stand out, but they also make
it more popular even among those web designers who like to take things in a very
conventional way.

1. Easy to Begin With


It is pretty easy, to begin with. Being easy to get started with is probably the first quality
which makes Bootstrap very appealing.

2. LESS as Well as CSS Files


Bootstrap not only offers LESS files but also includes the old CSS files.
Electricity Billing System

3. Easily Customizable
Despite the fact that Bootstrap is designed in responsive 12-column grids, layouts, and
components, it is also very easy to customize. Whether you need a fixed grid or a responsive
one, it can be made possible by making a few changes. Offsetting and nesting of columns are
also easy to do in both CPU-based and mobile-based browser grids.

4. Responsive Utility Classes


Another prominent feature of Bootstrap is its responsive utility classes. Using responsive
utility classes, a particular piece of content can be made to appear or hide only on devices
depending on the size of the screen being used. This feature is extremely helpful for designers
who want to make a mobile and tablet-friendly version of their websites.

5. Components of Bootstrap
Some of the components that come pre-styled in Bootstrap are:

Drop-downs

Button

Navigation

Badges Alerts

Progress Bar

6. Drop-Down Component Menu


The drop-down component menu is a responsive additive feature of a website. To include it
in a website, a lot of different plugins, mostly Java-based, are tested. But, via Bootstrap and
its easy customizing options, this can easily be done in a matter of minutes.

7. Bootstrap Templates
The readily available templates make it easier for inexperienced users to create a website
following a simple tutorial or demo available on the Bootstrap.

7.4. HTML (Hypertext Markup Language)

Hypertext Markup Language (HTML) is a programming tool that uses hypertext to


establish dynamic links to other documents. It is known as the Web's programming language
and provides a general structure for creating webpages. All webpages are actually HTML
files. HTML documents are simply text documents that contain the content of your webpage
as well as special instructions called tags. Tags provide instructions on how to display text or
graphics and control user inputs. Tags are enclosed in brackets: < >. Typically, there is a
starting and ending tag around text. For example, if we wanted to bold a heading, our starting
Electricity Billing System

tag is a 'b' in brackets followed by the heading and concluding with the end tag '/b' in
brackets: <b>'Heading'</b>. All HTML documents begin with HTML in brackets and end
with the forward slash and HTML in brackets: <html> and </html>. These tags tell the Web
browser that the content between the tags should be assembled into an HTML document.
There are programs such as Dreamweaver designed to help you create HTML code for a
webpage. The application provides a graphical user interface that enables one to click, drag
and copy parts of the webpage. The application generates the HTML code for the user.

You might also like