Electricity Bill Project Report

Electricity Billing System
BANASTHALI UNIVERSITY
MASTER OF BUSINESS
ADMINISTRATION
[1st year (Batch - B)]
PROJECT IN
SYSTEM, ANALYSIS, DESIGN AND MIS
TOPIC
Billing Management System
Submitted to : Submitted by :
Ms. isha mittal Pallavi Gairola (7240)

Shruti Roopanwal (7307)
Smriti (7311)
Sonal Goel (7314)
Sonam Singh(7316)
Suman Kumari(7319)
ACKNOWLEDGEMENT
We would like to take this opportunity to express our gratitude towards all
the people who have in various ways, helped in the successful completion
of our project.
We convey our gratitude to Miss Isha Mittal for giving us the constant
source of inspiration and help in preparing the project work and providing
encouragement throughout the project.
We would also like to thank all our friends for steering us through the tough
as well as easy phases of the project in a result oriented manner with
concern attention.
TABLE OF CONTENTS
1) Introduction
2) Objective
3) Types of Reports
4) Future scope
5) Analysis of Present System
6) Problem of Existing System
7) Characteristic of Proposed System
8) Feasibility Analysis
i. Technical Feasibility
ii. Behavioral Feasibility
iii. Economic Feasibility
9) Data flow diagram
1. INTRODUCTION
The project Billing system is an application to automate the process of
ordering and billing of a Departmental store .This web based
application is designed considering the chain of departmental stores
which is located in various cities. This application also administrates its
users and customers.
2. OBJECTIVES
This project will serve the following objectives:-
Add and maintain records of available products.

Add and maintain customer details.
Add and maintain description of new products.
Add and maintain new entered category of products.
Provides economic/financial reports to the owner monthly or weekly
and yearly.
Provides a convenient solution of billing pattern.
A user friendly approach towards billing system.
3. TYPES OF REPORTS
Daily Sales Report
Monthly Customer Report
Daily Product Report
Due Date Report (Report of a particular Day)
4. FUTURE SCOPE
This project will help the store keeper in fast billing
This project enable store keeper to maintain a great database of all
customers visited and purchase product from store.
Project will enable to see report regarding product and category.
Easy to maintain in future prospect.
5. ANALYSIS OF PRESENT SYSTEM

Before we begin a new system it is important to study the system that will
be improved or replaced (if there is one). We need to analyze how this
system uses hardware, software, network and the people resources to
convert data resources, such as transaction data, into information
products, such as reports and displays. Thus we should document how the
information system activities of input, processing, output, storage and
control are accomplished.
6. PROBLEMS OF EXISTING SYSTEM

Inability of modification of data: The managing of huge data
effectively and efficiently for efficient results, storing the details of
the consumers etc. in such a way that the database can be modified as
not possible in the current system.
Not user friendly: The existing system is not user friendly because
the retrieval and storing of data is slow and data is not
maintained efficiently.
Difficulty in reports generating: Either no report is generated and if
generated it is with great difficulty.
Manual operator control: Manual operator control is there which
leads to a lot of chaos and errors.
Lot of paperwork: Existing system requires lot of paper work
Moreover any unnatural cause (such as fire in the organization) can
destroy all data of the organization. Loss of even a single paper leads
to difficult situations because all the papers are interrelated.
Inability of sharing the data: Data cannot be shared in the existing
system. This means that no two persons can use the same
data in existing system. Also the two departments in an organization
cannot interact with each other without the actual movement of data.
No support in decision-making: Existing system does not support
managerial decision-making.
7. CHARACTERSTICS OF THE PROPOSED SYSTEM

Ease in modification of data: The proposed system provides
managing of huge data effectively and efficiently for efficient
results, storing the details of the customers, employees etc. in such a
way that the database can be modified.
User friendly: The proposed system is user friendly because the
retrieval and storing of data is fast and data is maintained
efficiently. Moreover the graphical user interface is provided in
the proposed System, which provides user to deal with the system
very easily,
Reports are easily generated: Reports can be easily generated in the
proposed system which helps the managers in decisions-making
activity.
Sharing the data is possible: Data can be shared in proposed
system. This means that two or more persons can use the same data,
provided that they have right to access that data. Also the two or
more departments in an organization can easily interact with
each other without the actual movement of data.
No or very less paperwork: The proposed system either does
not require paper work or very less paper work is required. All the
data is fed into the computer immediately and various bills and
reports can be generated through computers. Since all the data is kept
in a database no data of the organization can be destroyed. Moreover
work becomes very easy because there is no need to keep data on
papers.
Computer operator control: There will be no or very less error as it
has computer operator control. Moreover storing and retrieving of
information becomes easy and work can be done speedily and on
time.
8. FEASIBILITY ANALYSIS
The feasibility study is carried out to test whether the proposed system is
worth being implemented. Feasibility study is a test of system
proposed regarding its work ability, its impact on the organization ability to
meet user needs and effective use of resources.
The key consideration involve in the feasibility study are:
Technical
Behavioral
Economic
TECHNICAL FEASIBILITY
Technical feasibility centers on the existing computer system
( hardware, software etc ) and to what extent it can support the
proposed system addition. For example, if the current system is operating
at 70% capacity ( an arbitrary value ), then another application could
overload the system or require additional hardware. If the budget is
serious constrain then the project is judged not feasible. This system
replaces the manual work into the computerized form. After the study we
found that this system is technically feasible.
BEHAVIOURAL FEASIBILITY:
An evaluation of the behavior of the end users, which may effect the
development of the system. People are inherently resistant to change and
computers know how to facilitate changes. An estimate should be made of
how strong a reaction of the user staff is likely to have towards the
development of a computerized system. It is a common knowledge that
a computer installation has something to do with turnover, transfer,
retraining and changes in employee job status, therefore the introduction of
a candidate system requires special effort to educate, sell and train the staff
on new ways of conducting business. The personnel of the user
organization will be affected by the proposed system. As the aim of the
system is only to satisfy the information needs, no employees will loose
their position by the proposed system. In fact the proposed system will
help the organization in reducing the voluminous work involved. Also the
involvement of users in every stage of the project is going to increase the
success factor.
ECONOMIC FEASIBILITY:
The procedure is to determine the benefits and savings that are
expected from a candidate system and compare it with the costs. If a benefit
outweighs costs, then the decision is made to design and implement
the system. Otherwise further alterations are made in the proposed system.
1. Manpower cost 2. Hardware cost 3. Software cost
4. Maintenance cost 5. Legal cost
COST BENEFIT ANALYSIS

Economic feasibility is performed by doing cost benefit analysis which is
the process of identifying the financial benefit and cost associated with the
development of the project. Evaluation of the project is being done on the
following strategies
PAYBACK ANALYSIS
It is a process in which the organization identifies the time period in which
the system would payback for itself. The costs in the development of the
project and the profits attained are shown below.
Hardware Cost 10,000

Software Cost 6,000

Personnel Cost 10,000
Maintenance 4,000
Legal Cost 10,000
YEAR COST CUM.COST BENEFIT CUM.BENEFIT

0 40,000 40000 10000 10000
1 28000 68000 15000 25000
2 15000 83000 19000 44000
3 13000 96000 30000 74000
4 17000 113000 50000 124000
5 11000 124000 60000 184000
EXPLANATION OF PAYBACK ANALYSIS

By looking at the above payback analysis graph, it could be easily
concluded that the system would payback for it self in the 4 th year after its
development.
RETURN ON INVESTMENT ANALYSIS

ROI = (Total benefits Total costs) / Total costs
ROI = (184000-124000) / 124000
ROI = .48
EXPLANATION OF ROI
According to the working of the ROI, the organization is getting 48% return
on its investment.
9. DATA FLOW DIAGRAM

A data flow diagram is graphical representation that depicts the information

flow and the transforms that are applied as date moves from input to output.
It can be used to represent a software at any level of abstraction.
.
1. INTRODUCTION:
1.1 Introduction to Proposed System
Our project entitled Electricity Billing System aims is to generate
electricity bill with all the charges and penalty. 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.
We used Microsoft Visual Basic 6.0 as front end and MS-Access
2000 as back end for developing our project. Visual Basic is primarily
a visual design environment. We can create a VB application by
designing the form and that make up the user interface. Adding visual
basic application code to the form and the objects such as buttons and
text boxes on them and adding any required support code in additional
modular.
Microsoft Access 2000 is a powerful relational database
application with which a desktop user can efficiently create and
manipulate database systems. Access targets the desktop category and
works best for individuals and workgroup
Managing megabytes of data for multi-user access to the same
database, Access uses file-server architecture, rather than client-server
architecture.
Access is included in the professional and developer editions of

Microsoft office.
The overall project report is divided into some parts. These parts are
further divided into their subparts. In the parts we have described the
purpose, scope of the project, objective of the project i.e. approach
which used for developing this software. It includes the topics like the
problems with the existing system and the functionality of the
organization. Introduction to tools, design, coding, testing and
debugging of the system are discussed in very detail. We have also
provided the names of the books from which we have taken guidance
to complete the work. Last section contains the matter about the overall
work performed and the efforts taken to complete the project.
2. SYSTEM STUDY:
2.1 Scope:
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 computerizes 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.
3. SYSTEM ANALYSIS:
3.1 Identification Of Problem:
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.
Following points should be well considered-:
Documents and reports that must be provided by the new system: there
can also be few reports, which can help management in decision-
making and cost controlling, but since these reports do not get required
attention, such kind of reports and information were also identified and
given required attention.
Details of the information needed for each document and report.
The required frequency and distribution for each document.
Probable sources of information for each document and report.
With the implementation of computerized system, the task of keeping
records in an organized manner will be solved. The greatest of all is the
retrieval of information, which will be at the click of the mouse. So the
proposed system helps in saving the time in different operations and
making information flow easy giving valuable reports.
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 users
expectations.
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 analyze 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 centers around the technology used. It means the
candidate system is technically feasible i.e. it dont have any technical
fault and work properly in the given environment. Our system is
technically feasible; it is providing us required output.
Behavioral Feasibility:
Behavioral feasibility is the analysis of behavior of the
candidate system. In this we analyze that the candidate system is
working properly or not. If working than it communicating proper
with the environment or not. All this matters are analyzed and a good
candidate system is prepared. Due to the change of system what is the
change in behavior of the users, this factors are also analyzed.
4. SYSTEM DEVELOPMENT ENVIRONMENT:

System development environment shows the hardware and software
requirement, which is necessary for developing the software.
Necessary software and hardware requirement, which are necessary for
making this software are as follows:
4.1 Software Requirement:
Software requirement for developing this project is as follows:
Microsoft Visual Basic 6.0
Microsoft -Access 98 or higher version.
Windows 98 or higher version.
4.2 Hardware Requirement:
Hardware requirement for developing this project is as follows:
1. Intel Pentium Processor
2. 32 MB RAM or higher
3. 1.2 GB Hard Disk or greater.
4. Video Display Unit.
5. Keyboard.
6. Mouse.
7. One Printer for printing the electricity bill.
5. INTRODUCTION TO TOOLS:
5.1 Introduction of Visual Basic:

Over past few years visual basic 6.0 (front end) the relational data
base management system has been fine-tuning it is offering a large
complex application in the relational market. Visual basic 6.0 is a front
end (i.e. uses graphical user interface) visual basic 6.0 uses windows
environment. It may use any DBMS or RDBMS as a back-end through
ODBC (open database connectivity).
For our purpose of development, in our project we used Visual Basic
6.0 because visual basic 6.0 has following outstanding features and
qualities.
Advantages Of Visual Basic:
1. Visual Basic applications are event driven. Event driven means the
user is in
Control of the application.
2. Visual Basic supports the principle of object-oriented design.
3. Visual Basic is a complete window application development system.
4. Visual Basic is infinitely extensible through the use of active x
controls dynamically linked libraries (dll's) and adds dins.
The Fast Track To Windows Development

Visual Basic is primarily a visual design environment. We can create a
VB application by designing the form and that make up the user
interface. Adding visual basic application code to the form and the
objects such as buttons and text boxes on them and adding any required
support code in additional modular.
Friendly Environment
Creating a form, adding controls to form and writing code behind the
form are all managed within a friendly environment.
Graphical User Interface
Application developed in DOS environment has to include its own set
of video, keyboard and printer drivers. in other words many DOS
programs provided virtually no user interface at all. Since windows is
preferable over DOS and Visual Basic is windows based hence
millions of users can use applications with no documentation or
training:
The graphical user interface provides a graphical environment to user
as front-end for their operating system through graphical objects and
therefore screen looks very attractive and almost has three-dimensional
qualities. The point and shoot use of a GUI (Graphical User Interface)
make use of the operating system and programming easy.
Visual basic 6.0 connect to number of back-end DBMS and RDBMS
such as SQL, FoxPro, Sybase, Oracle etc.
Open Database Connectivity
Visual basic 6.0 connects to any back-end DBMS system whose
DBMS cores follow the open database connectivity rules and this
connectivity is established by open database connectivity.
The data storage may belong to any DBMS engine specifically

supported by visual basic 6.0 driver or any DBMS that supported open
database connectivity.
The data entry and validation screens are created in visual basic 6.0
connects with whichever engine is specified at the time of screen was
created and manipulated data within that engine.
Client server computing and visual basic 6.0:
The client / server programming is also a distributed application
processing and co-operating application processing. It has three distinct
components, each focusing on specific job.
The three components are:
1. Client application
2. A Database Server
3. A network for connecting the first two components.
1. Client Application:
Client application (i.e. front end) is the part of the system that users
employ to interact with data. The work of client is requesting and
receiving information forms a database server (back-end). Client
application can be developed rapidly using visual basic 6.0.
2. A Database Server:
A Database server focuses on efficiently managing resources such as
the table in which data lies. The servers primary job is to manage the
data tables optimally among multiple clients that concurrently request
server for same resources. Visual basic can connect to a number of

RDBMS that are in trend.
3. Network for connecting the first two components:

A network and communication software are the vehicle that transports
the data between the clients and the server. The system both client and
server run communication software that allow them to talk across a
network.
Object Oriented Programming Approach:
The visual basic 6.0 uses the OOPS approach. In OOPS, a table is
treated as also object and the data being attached to as user specified
parameters the forms also treated as objects for this windows object for
this window object. The firing of code shippers based on events
occurring such as clicking on a button via a mouse.
Visual Basic Libraries:
When we create commercial application we create object such as
windows, data windows, menus etc. these objects that you create using
an appropriate visual basic pointer are stored in libraries files.
When application has to run visual basic there objects from their
libraries and visual basic gives you a library painter to help you
manage your libraries.
Events in Visual Basic:
Visual basic commercial applications are event driven. The user of the
application
Controls the flow of the application by the action they take.
Visual Basics Debugging tool:

To distribute application created in visual basic we create an executable
i.e. an exe file, also there is a distribution kit to distribute the
application.
Features of Visual Basic:
1. Visual basic provides a GUI which and therefore screen looks very
attractive.
2. Work on client / server computing model.
3. Object Oriented programming approach.
4. Visual basic provides several tool bars, which make working quick
and easy.
5. It is front end and DBMS as a back end so it uses all the features of
RDBMS like referential integrity foreign key etc.
6. It uses a micro help line, which visual basic uses to display starters
to display information through the session.
Feel Of Windows Environment
Microsoft Windows environment is built-in to Visual Basic application.
No need to work with any windows compatible hardware since
windows provides drivers for thousand of different printers video
adapter, modems and other peripherals.
5.2 Introduction of MS-Access

Over the past several years, relational database management system
have become the most widely accepted way to manage data relational
system often benefits such as:
1. Easy access to all data.

2. Flexibility in storage and modeling.
3. Reduced data storage and redundancy.
4. Independence of physical storage & logical data designs.
5. A high-level data manipulation language (SQL).
6. Tables & table operations are well defined because relational theory
is founded in set theory, relational algebra & relational calculus.
Our of this the reason for introducing relational model is to increase the
productivity of the application programmer by eliminating the need to
change application programs when a change is made to the database.
As the technologies associated with RDBMS have grown rapidly in
recent years, the appeal of relational databases has become apparent to
a much wider audience.
The phenomenal growth of the relational technology has led to
more demand for RDBMS in environments ranging from personal
computer to large highly secure CPU with users ranging from very
casual to very sophisticated.
Microsoft Access 2000 is a powerful relational database application
with which a desktop user can efficiently create and manipulate
database systems. Access targets the desktop category and works best
for individuals and workgroup
Managing megabytes of data for multi-user access to the same
database. Access uses File-server architecture, rather than client-server
architecture.
Access is included in the professional and developer editions of

Microsoft office.
As a leader in the desktop database category, Microsoft Access makes
it easy for users to find and manage their data to make better business
decision. With strong integration with Microsoft Office, Access offers a
similar appearance and functionality to that found in the popular
Microsoft word and Excel applications for general business users,
Access provides easy to use wizards throughout, such as the database
wizard for getting up and running quickly and the simple query
wizards for easily finding information from the data. The combination
of ease of use and power in access makes it the top choice among
developers who frequently use Access as a front end in a client server
scenario.
The only problem with MS-ACCESS is that it cannot provide strong
security features. But in front of its fast execution features this
drawback can be neglected as the firm does not need any type of
security whether it is operational, database, or any other security. But
in application development some restriction are made of some places
so that our database cannot be corrupted.
MS-ACCESS is therefore used for its fast execution speed and also
due to its fast connectivity.
Importance of database:
Growth in the usage of Computers in Business and Industrial sector
initiated development of modern Database Software. Database
softwares offers a number of potential advantages over traditional file-

processing system; some of them are as follows:
Program-Data Independence
The separation of data descriptions (metadata) from the application
programs that use the data is called data-independence. With the
database approach, data descriptions are stored in a central location
called repository. This property of the database systems allows an
organizations data to change and evolve without changing the
application programs that process that data.
Minimal Data-Redundancy
The design goal with database approach is that previously separate and
redundant data files are integrated into a single, logical structure. Each
primary fact is recorded in only one place in the database. The database
approach does not eliminate redundancy entirely, but it allows the
designers to carefully control the type and amount of redundancy.
Data Consistency
By controlling data redundancy, we greatly reduce the opportunities
for inconsistency. In database approach updating data values is greatly
simplified when each value is stored in one place only. Finally we
avoid the wasted storage space that results from redundant data
storage.
Data Sharing
Primary advantage of database approach is sharing of data. A database
is designed as a shared resource. Authorized users are granted
permission to use the database and each user is provided one or more
user views to facilitate this use. A user view is a logical description of

some portion of database that is required by the user to perform some
task.
Enforcement of Standards
When the database approach is implemented with full management
support, the database administration function should be granted single
point authority and responsibility of establishing and enforcing data
standards. These standards will include naming conventions, data
quality standards and uniform procedures for accessing, updating and
processing data. The data repository provides database administrators
with powerful tools for developing and enforcing such standards.
Reduced Program Maintenance
Stored data must be changed frequently for a variety of reasons: new
data item types are added; data formats ate changed and so on. In file
processing environment, the description of data formats and access
methods inevitably result in the need to modify application programs.
As a result in the change of data formats and access methods inevitably
results in the need to modify application programs. In a database
environment, data are more independent of application programs that
use them. Within limits, we can change either the data or the
application programs that use the data without necessitating the change
in other factors.
6. PRELIMINARY DESIGN OF PROPOSED

SYSTEM:
6.1 Data Design:
In most situations, many physical database design decisions are
implicit or eliminated when we choose the database management
technologies to use with the information system we are designing.
Since many organizations have standard for operating systems,
database management system and data access languages, we must deal
only with those choices not implicit in the given technologies.
The primary goal of database design is data processing efficiency.
Objective Of Database Design:
i) To decide on the organization of the database in computer
storage and define the physical structure of the database management
system.
ii) To outline the program to process transactions and to generate
anticipated management information and decision support reports.
Designing Fields: A field is the smallest unit of application data
recognized by system software
Choosing Data Types: A data type is a detailed coding schema
recognized by the system software, such as a DBMS, for representing
organizational data.
Selecting a data type involves four objectives that will have different
relative importance for different applications:
i.) Minimized Storage Space

ii.) Represent All Possible Values
iii.) Improve Data Integrity
iv.) Support All Data Manipulations
Data Type Description

Text Valid String
Date/Time Valid calendar date and time
Number Number with a specified number of digits
Controlling Data Integrity

For many DBMS, data integrity controls can be built into the physical
structure of the fields and controls enforced by the DBMS on those
fields. Some other typical controls that a DBMS may support are the
following:-
Default Values:
A default value is the value a field will assume unless a user enters
an explicit value for an instance of that field. Assigning a default value
to a field can reduce data entry, time since entry of the value can be
skipped and it can also help to reduce data entry errors for the most
common value.
Range Control:
Range control limits the set of permissible value a field may assume.
The range may be a numeric lower to upper bound or a set of specific
values. It is better to implement any range controls through a DBMS

since range control in programs may be inconsistently enforced and it
is more difficult to find and change them.
Null Value Control:
A null value is an empty value each primary key must have an
integrity control that prohibits a null value. Any other required field
may also have a null value control placed on it if that is the policy of
the organization.
Referential Integrity:
Referential integrity on a field is a form of range control in which the
value of that field must exist as the value in some field in another row
of the same or different table.
Record is a group of a fields stored in adjacent memory location and
retrieve together as a unit. The design of a physical record involves
choosing the sequencing of fields into adjacent storage location to
achieve two goals that are efficient use of secondary storage of data
processing speed.
We have used five different tables for storing different record. There
are five tables customer table , Bill table, Bill charge table, service
centre table, commercial table. Their design view are shown as
follows:
Table Name: BILL

Field Name Data Type Size Constraint
Bill_no Number Auto Primary key
BillDate Date
Amount Number Auto
City Text 30
In this table there are no multivalued attributes. So this is in First

Normal Form.
2. Table Name : Customer

Customer First Name Text 10
Customer Middle Text 10
Name
Customer Last Name Text 10
Cust_id Number Auto Primary Key
Service_Centre Text 20
Street Text 20
City Text 20
City Code Number Auto
State Text 20

Normal Form.
Service Centre Table:
Cust_id Number Auto Foreign Key
Service_Centre Text 20
Street Text 20
City Text 20
City Code Number Auto
Code
Design Design Code Test
State Text 10

Normal Form.
Bill Charge Table:

Bill_no Number Auto Primary Key
Fix _charge Number Auto
E_duty Number Auto
Total Charge Number Auto
Total Unit Number Auto

Normal Form.
Commercial Bill Table:

Customer Name Text 20
Shop_no Text 20 Primary Key
Street Text 20
Bill_no Integer Auto Foreign Key
Bill Amount Integer Auto
Bill Date Date
These are the tables, which are used in the project development for
storing different record. Every table has a primary key for storing
unique record . we have also used foreign key for making relationship
between the tables.
Code
Design Design Code Test
6.2 Input Stream:

Input stream shows the way by which information are passed in to the
table as record. We have used mainly two forms in the project inputting
the record in the table first is commercial bill record form and second
is domestic bill record form. By these form we input the records of the
table name, address, service centre, customer_id etc
6.3 Output Stream:
Input stream shows the way by which information viewed by the user
which are stored in the database.
Commercial bill calculation form and domestic bill calculation forms
are used as an output stream we can see the record and also can see the
name , bill_date,total_bill etc.
Commercial report form and home report form are used for getting the
total record of the domestic bill and commercial bill in printed form.
7. ARCHITECTURAL DESIGN:
7.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

5. Development Of Software
6. System Testing
7. System Implementation
8. System Maintenance
1. Preliminary Investigation (Feasibility Study):

An important outcome of this preliminary investigation is determining
whether the System requested is feasible or not.
The major purpose of this study are listed below:
Identify the responsible users and develop an initial scope of the

system.
Identify current deficiencies in the users environment determine
objectives for the new system
Determine whether it is feasible to automate the system and if so
suggest some acceptable options:
The three major areas to consider while determining the feasibility
of a project are:
Technical Feasibility
Economical Feasibility
Operational Feasibility
Technical Feasibility:
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
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:
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
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.
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.
7.2 DFD(Data Flow Diagram):
They are the versatile diagramming tools used for structured system
analysis. They are specifically used for process modeling 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.
7.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
8. DETAIL DESIGN OF PROPOSED SYSTEM:
8.1 MODULE:
There are mainly four module in our project. These are as follows:
1. Domestic bill information module.
2. Commercial bill information module.
3. Domestic customer record module.
4. Commercial customer record module.
1. Domestic Bill Information Module:

In this module, we can see information related to the domestic bill
like customers name, address, its customer id, service centre, his
electricity bill description, which contain bill no, bill date, total bill etc.
we can also calculate total bill of the customer according to total unit,
bill charge of the bill.
2. Commercial Bill Information Module:

There is no difference between domestic bill information module and
this module except that, this module is for commercial purpose. We can
see information related to the commercial bill like customers name,
shop no, address, its customer id, service centre his electricity bill
description, which contain bill no, bill date, total bill etc. we can also
calculate total bill of the customer according to total unit, bill charge of
the bill.
3. Domestic Customer Record Module:

In this module, we can create the record related to the domestic
customer like his name, address, customer id. This module can also
perform deleting a record modifying existing record etc
4. Commercial Customer Record Module:

In this module, we can create the record related to the customer like his
name, address, customer id. This module can also perform deleting a
record, modifying existing record etc. We can also see the existing
record by next and previous button.
LOGIN FORM
MDI FORM OF PROJECT

DESCRIPTION FORM FOR ELECTRIC

CHARGES
DOMESTIC BILL CALCULATION FORM

COMERCIAL BILL CALCULATION FORM

DOMESTIC CUSTOMER RECORD FORM

COMMERCIAL BILL RECORD FORM

DOMESTIC BILL REPORT FORM

COMMERCIAL BILL REPORT FORM

8.2 DATA DICTIONARY:
This is normally represented as the data about data. It is also termed as

metadata some times which gives the data about the data stored in the
database. It defines each data term encountered during the analysis and
design of a new system. Data elements can describe files or the
processes.
Following are some major symbols used in the data dictionary
= equivalent to
+ and
[] either/ or
() Optional entry
Following are some rules, which defines the construction of data

dictionary entries:
1. Words should be defined to understand for what they need and
not the variable need by which they may be described in the
program .
2. Each word must be unique. We cannot have two definition of the
same client.
3. Aliases or synonyms are allowed when two or more enters
shows the same meaning. For example a vendor number may
also be called as customer number.
4. A self-defining word should not be decomposed. It means that
the reduction of any information in to subpart should be done
only if it is really required that is it is not easy to understand

directly.
Data dictionary includes information such as the number of records in
file, the frequency a process will run, security factor like pass word
which user must enter to get excess to the information.
9. CODING:
9.1 Coding of Login Form:
Private Sub cmdCancle_Click()
End
End Sub
Private Sub cmdOk_Click()

If txtPassword.Text = "reema" Then
Loginform.Hide
MDIForm1.Show
Else
MsgBox "invalid password", vbOKOnly, "alert"
txtname.Text = ""
txtPassword.Text = ""
txtname.SetFocus
End If
End Sub
9.2 Coding of MDI Form:
Dim RetVal
Private Sub MDIForm_MouseUp(Button As Integer, Shift As Integer, X As Single, Y As
Single)
If Button = vbRightButton Then
MDIForm1.PopupMenu mnuEnd
End If
End Sub
Private Sub mnuEndexit_Click()

Unload Me
End Sub
Private Sub mnuExit_Click()

End
End Sub
Private Sub mnuFileCombilFrm_Click()

Comercialbillfrm.Show
End Sub
Private Sub mnufilecomreport_Click()

comercialreport.Show
End Sub
Private Sub mnuFileCusRecfrm_Click()

domRecfrm.Show
End Sub
Private Sub mnuFileDBillfrm_Click()

dombillcalfrm.Show
End Sub
Private Sub mnuFileDesfrm_Click()

descriptionfrm.Show
End Sub
Private Sub mnufilehomerep_Click()

homebillreport.Show
End Sub
Private Sub mnufileopencomercialrec_Click()

comercialrecfrm.Show
End Sub
Private Sub Toolbar1_ButtonClick(ByVal Button As MSComctlLib.Button)

Select Case Button.Key
Case Is = "topen"
descriptionfrm.Show
Case Is = "texit"
Unload Me
End Select
End Sub
9.3 Coding of Commercial Bill Calculation Form

Dim u, u1 As Long
Dim X, Y, s, d1, d2, d, f As String
Private Sub cmdcclear_Click()
txtcfix.Text = ""
txtced.Text = ""
txtctotal.Text = ""
txtced.Text = ""
txtcsc.Text = ""
txtcec.Text = ""
txtcunit.Text = ""
txtcunit.SetFocus
End Sub
Private Sub cmdcexit_Click()

End
End Sub
Private Sub cmdclear_Click()

txtName.Text = ""
txtAddress.Text = ""
txtScenter.Text = ""
txtBillmonth.Text = ""
txtBilldate.Text = ""
txtBddate.Text = ""
txtTotalbill.Text = ""
txtShopno.Text = ""
txtBillpay.Text = ""
End Sub
Private Sub cmdcOk_Click()

If txtcunit.Text = "" Then
MsgBox "please enter unit"
txtcunit.Text = 0
End If
txtcfix.Text = "Rs 100.00"
f = 100
u = CInt(txtcunit.Text)
If u <= 100 Then
X=u*4
txtcec.Text = "Rs " & X
txtcsc.Text = "Rs " & CStr(u * 0.1)
s = u * 0.1
d = (X * 11) / 100
txtced.Text = "Rs " & d
txtctotal.Text = "Rs " & (X + s + f + d)
ElseIf u > 100 Then
X = 100 * 4
d1 = (X * 11) / 100
u1 = u - 100
Y = u1 * 4.25
d2 = (Y * 11.5) / 100
d = d1 + d2
txtcec.Text = "Rs" & (X + Y)
s = u * 0.1
txtcsc.Text = "Rs" & s
txtced.Text = "Rs" & d
End If
txtctotal.Text = "Rs" & (X + Y + s + d + f)

End Sub

If txtBillpay.Text = "" Then
txtTotalbill.Text = txtctotal.Text
Else
txtTotalbill.Text = "Rs" & (X + Y + s + d + f) - Val(txtBillpay.Text)

End If
End Sub
Private Sub cmdprevious_Click()

Comercialbillfrm.Hide
MDIForm1.Show
End Sub
Private Sub Form_Load()
End Sub
9.3 Coding of Domestic Bill Form:

Private Sub cmd1First_Click()
adocom.Recordset.MoveFirst
adobill.Recordset.MoveFirst
cmd1First.Enabled = False
cmd4Last.Enabled = True
End Sub
Private Sub cmd2Next_Click()

adocom.Recordset.MoveNext
adobill.Recordset.MoveNext
cmd1First.Enabled = True
If (adocom.Recordset.AbsolutePosition) = adPosEOF And
adobill.Recordset.AbsolutePosition = adPosEOF Then
MsgBox ("no other record")
adocom.Refresh
adobill.Refresh
End If
End Sub
Private Sub cmd3Previous_Click()

adocom.Recordset.MovePrevious
adobill.Recordset.MovePrevious
If adocom.Recordset.AbsolutePosition = adPosBOF And
adobill.Recordset.AbsolutePosition = adPosBOF Then
adocom.Refresh
adobill.Refresh
End If
End Sub
Private Sub cmd4Last_Click()

adocom.Recordset.MoveLast
adobill.Recordset.MoveLast
cmd4Last.Enabled = False
End Sub
Private Sub cmdDelete_Click()

Dim res As String
res = MsgBox("you want to delete the record", vbYesNo + vbQuestion, "alert")
If res = vbYes Then
adocom.Recordset.Delete
adobill.Recordset.Delete
MsgBox "Record is Deleted"
adocom.Refresh
adobill.Refresh
Else
adocom.Refresh
adobill.Refresh
End If
End Sub
Private Sub cmdlastfive_Click()

DataGrid1.Visible = True
Adodc1.RecordSource = "select top 5 billm,totalbill from cosbdes where=" &
Val(txtShopn)
'Adodc1.Refresh
DataGrid1.Refresh
End Sub
Private Sub cmdNew_Click()

adocom.Recordset.AddNew
adobill.Recordset.AddNew
txtCname.SetFocus
End Sub
Private Sub cmdSave_Click()

Dim res As String
res = MsgBox("you want to save the record", vbYesNo + vbQuestion, "alert")
If res = vbYes Then
adocom.Recordset.Update
adobill.Recordset.Fields("shop_no") = adocom.Recordset.Fields("shop_no")
adobill.Recordset.Update
MsgBox "Record is Updated"
adocom.Refresh
adobill.Refresh
Else
adocom.Recordset.CancelUpdate
adobill.Recordset.CancelUpdate
adocom.Refresh
adobill.Refresh
End If
End Sub
Private Sub comerfram_DragDrop(Source As Control, X As Single, Y As Single)
End Sub

DataGrid1.Visible = False
End Sub
9.4 Coding of Description Form:

Private Sub cmdExit_Click()
Unload Me
End Sub

If detailcb.ListIndex = 0 Then
Text1.Text = "1.30 Rs"
ElseIf detailcb.ListIndex = 1 Then
End If
End Sub

detailcb.AddItem ("DOMESTIC 0")
detailcb.AddItem ("COMERCIAL 1")
End Sub
9.5 Coding of Domestic Bill Calculation Form:
Dim u, u1, u2 As Long
Dim X, Y, z, p, d, f As String
Private Sub cmd1exit_Click()
Unload Me
End Sub
Private Sub cmdAdd_Click()

adodesc.Recordset.AddNew
bmtxt.SetFocus
End Sub
Private Sub cmdCancle_Click()

bmtxt.Text = ""
bdtxt.Text = ""
tbtxt.Text = ""
bntxt.Text = ""
bntxt.Text = ""
pdtxt.Text = ""
txtbp.Text = ""
End Sub
Private Sub cmdclear_Click()

txtfix.Text = ""
txted.Text = ""
txttotal.Text = ""
txted.Text = ""
txtsc.Text = ""
txtec.Text = ""
txtunit.Text = ""
tbtxt.Text = ""
txtunit.SetFocus
End Sub

Dim res As String
res = MsgBox("u w to delete the rec!", vbYesNo, "alert")
If res = vbYes Then
adodesc.Recordset.Delete
MsgBox "record is deleted"
adodesc.Refresh
Else
adodesc.Refresh
End If
End Sub

bmtxt.SetFocus
End Sub
Private Sub cmdFilter_Click()

Dim res
res = InputBox("Enter The Criteria", "Filter")
adodesc.RecordSource = "select * from Billdec where" & res

End Sub
Private Sub cmdFind_Click()

Dim res As String
res = InputBox("enter the criteria for a rec", "find")
adodesc.Recordset.Find res, , adSearchForward, 1
End Sub

If txtunit.Text = "" Then
MsgBox "please enter unit"
txtunit.Text = 0
End If
txtfix.Text = "Rs 60.00"
f = 60
u = CInt(txtunit.Text)
If u <= 50 Then
X = u * 1.3
txtec.Text = "Rs " & X
txtsc.Text = "Rs " & CStr(u * 0.1)
p = u * 0.1
d = (X * 14) / 100
txted.Text = "Rs " & d
txttotal.Text = "Rs " & (X + p + f + d)
ElseIf (u > 50 And u <= 300) Then
X = 50 * 1.3
u1 = u - 50
Y = u1 * 3
txtec.Text = "Rs" & (X + Y)
p = u * 0.1
txtsc.Text = "Rs" & p
If u <= 100 Then
d = ((X + Y) * 15) / 100
Else
d = ((X + Y) * 23) / 100
End If
txted.Text = "Rs" & d
txttotal.Text = "Rs" & (X + Y + p + d + f)
ElseIf u > 300 Then
X = 50 * 1.3
Y = 250 * 3
z = (u - 300) * 3.5
txtec.Text = "Rs" & (X + Y + z)
p = CStr(u * 0.1)
txtsc.Text = "Rs" & p
If u <= 100 Then
d = ((X + Y + z) * 15) / 100
Else
d = ((X + Y + z) * 23) / 100
End If
txted.Text = "Rs" & d
txttotal.Text = "Rs" & (X + Y + z + p + d + f)
End If
End Sub
Private Sub cmdoko_Click()

If txtbp.Text = "" Then
tbtxt.Text = txttotal.Text
Else
tbtxt.Text = "Rs" & (X + Y + z + p + d + f) - Val(txtbp.Text)
End If
End Sub

MDIForm1.Show
Unload Me
End Sub

Dim res As String
res = MsgBox("u w to save the rec", vbYesNo + vbQuestion, "alert")
If res = vbYes Then
adodesc.Recordset.Update
MsgBox "record is updated"
'adodesc.Refresh
Else
adodesc.Recordset.CancelUpdate
adodesc.Refresh
End If
End Sub
Private Sub Form_Activate()

txtName.SetFocus
End Sub
adocust.Recordset.MoveFirst
End Sub

adocust.Recordset.MoveNext
If (adocust.Recordset.AbsolutePosition) = adPosEOF Then

adocust.Refresh
End If
End Sub

adocust.Recordset.MovePrevious
If adocust.Recordset.AbsolutePosition = adPosBOF Then
adocust.Refresh
End If
End Sub

adocust.Recordset.MoveLast
End Sub
9.6 Coding of Commercial Bill Record Form:

Private Sub cmd1_Click()
adodesc.Recordset.MoveFirst
cmd1.Enabled = False
cmd4.Enabled = True
adodesc.Refresh
End Sub

adocust.Recordset.MoveFirst
End Sub

Dim i As Integer
If adocust.Recordset.Fields("cus_id") = adodesc.Recordset.Fields("cus_id") Then
adodesc.Recordset.MoveNext
cmd1.Enabled = True
cmd4.Enabled = True
End If
If adodesc.Recordset.AbsolutePosition = adPosEOF Then
End If
adodesc.Refresh
End Sub
adocust.Recordset.MoveNext
If adocust.Recordset.AbsolutePosition = adPosEOF Then
adocust.Refresh
End If
End Sub
adodesc.Recordset.MovePrevious
cmd1.Enabled = True
cmd4.Enabled = True
If adodesc.Recordset.AbsolutePosition = adPosBOF Then
adodesc.Refresh
End If
End Sub
dombillcalfrm.Show
Unload Me
End Sub

adocust.Recordset.MovePrevious
If adocust.Recordset.AbsolutePosition = adPosBOF Then
MsgBox "no other record"
adocust.Refresh
End If
End Sub

adodesc.Recordset.MoveLast
cmd1.Enabled = True
cmd4.Enabled = False
End Sub

adocust.Recordset.MoveLast
End Sub

Dim res As String
res = MsgBox("you want to delete the record", vbYesNo + vbQuestion, "alert")

If res = vbYes Then
adocust.Recordset.Delete
adodesc.Recordset.Delete
MsgBox "Record is Deleted"
adocust.Refresh
adodesc.Refresh
Else
adocust.Refresh
adodesc.Refresh
End If
End Sub

Unload Me
End Sub
Private Sub cmdfirst_Click()

adodesc.Recordset.MoveFirst
cmdfirst.Enabled = False
cmdlast.Enabled = True
End Sub
Private Sub cmdnext_Click()

adodesc.Recordset.MoveNext
cmdfirst.Enabled = True
If adodesc.Recordset.AbsolutePosition = adPosEOF Then
adodesc.Refresh
End If
End Sub
Private Sub cmdFilter_Click()

Dim res As String
res = InputBox("Enter The Criteria", "Filter")
'adodesc.Recordset.Fields("cus_id") = adocust.Recordset.Fields("cus_id")
adocust.RecordSource = "select * from bill where" & res
'adodesc.RecordSource = "select billdec.billmonth,billdec.totalbill from billdec where" &
res
End Sub
Private Sub cmdlastfive_Click()

DataGrid1.Visible = True
Adodc1.RecordSource = "select top 5 totalbill,billmonth from billdec where cus_id =" &
Val(txtcusid)
Adodc1.Refresh
DataGrid1.Refresh
End Sub
Private Sub cmdNew_Click()

adocust.Recordset.AddNew
adodesc.Recordset.AddNew
txtname.SetFocus
End Sub
Private Sub cmdPrev_Click()

MDIForm1.Show
Unload Me
End Sub

adodesc.Recordset.MovePrevious
If adodesc.Recordset.AbsolutePosition = adPosBOF Then
adodesc.Refresh
End If
End Sub
Private Sub cmdlast_Click()

adodesc.Recordset.MoveLast
cmdlast.Enabled = False
End Sub

Dim res As String
res = MsgBox("you want to save the record", vbYesNo + vbQuestion, "alert")
If res = vbYes Then
adocust.Recordset.Update
adodesc.Recordset.Fields("cus_id") = adocust.Recordset.Fields("cus_id")
adodesc.Recordset.Update
MsgBox "Record is Updated"
adocust.Refresh
adodesc.Refresh
Else
adocust.Recordset.CancelUpdate
adodesc.Recordset.CancelUpdate
adocust.Refresh
adodesc.Refresh
End If
End Sub
10. TESTING AND DEBUGGING:
Testing is vital for the success of any software. no system design is

ever perfect. Testing is also carried in two phases. first phase is during
the software engineering that is during the module creation. second
phase is after the completion of software. this is system testing which
verifies that the whole set of programs hanged together.
10.1 White Box Testing:
In this technique, the close examination of the logical parts through the
software are tested by cases that exercise species sets of conditions or
loops. all logical parts of the software checked once. errors that can be
corrected using this technique are typographical errors, logical
expressions which should be executed once may be getting executed
more than once and error resulting by using wrong controls and loops.
When the box testing tests all the independent part within a module a
logical decisions on their true and the false side are exercised , all loops
and bounds within their operational bounds were exercised and internal
data structure to ensure their validity were exercised once.
10.2 Black Box Testing:

This method enables the software engineer to device sets of input
techniques that fully exercise all functional requirements for a
program. black box testing tests the input, the output and the external
data. it checks whether the input data is correct and whether we are
getting the desired output.
10.3 Alpha Testing:
Acceptance testing is also sometimes called alpha testing. Be spoke
systems are developed for a single customer. The alpha testing
proceeds until the system developer and the customer agree that the
provided system is an acceptable implementation of the system
requirements.
10.4 Beta Testing:
On the other hand, when a system isto be marked as a software
product, another process called beta testing is often conducted. During
beta testing, a system is delivered among a number of potential users
who agree to use it. The customers then report problems to the
developers. This provides the product for real use and detects errors
which may not have been anticipated by the system developers.
Testing Approaches:
Unit Testing:
Each module is considered independently. it focuses on each unit of
software as implemented in the source code. it is white box testing.
Integration Testing:
Integration testing aims at constructing the program structure while at
the same constructing tests to uncover errors associated with
interfacing the modules. modules are integrated by using the top down
approach.
Validation Testing:
Validation testing was performed to ensure that all the functional and
performance requirements are met.
System Testing:
It is executing programs to check logical changes made in it with
intention of finding errors. a system is tested for online response,
volume of transaction, recovery from failure etc. System testing is done
to ensure that the system satisfies all the user requirements.
11. CONCLUSION
We have tried to develop a system that can be a great help for the
owner of the referred electricity department to receiving bill from the
customer. Despite all our efforts there are some bugs in the system,
which are still to be removed. This is possible by the testing being done
in the system.
We have left all the options open so that if there is any other future
requirement in the system by the user for the enhancement of the
system then it is possible to implement them.
In the last we would like to thanks all the persons involved in the
development of the system directly or indirectly. We are also thankful
to the Rajendra Nagar South Division Electricity Department for so
much taken by them in helping to develop the system.
We hope that the project will serve its purpose for which it is develop
there by underlining success of process.
12. FUTURE ANALYSIS:

We have left all the options open so that if there is any other future
requirement in the system by the user for the enhancement of the
system then it is possible to implement them.
In the last we would like to thanks all the persons involved in the
development of the system directly or indirectly. We are also thankful
to the Rajendra Nagar South Division Electricity Department for so
much taken by them in helping to develop the system.
We hope that the project will serve its purpose for which it is develop
there by underlining success of process.

Electricity Bill Project Report

Hochgeladen von

Dokumentinformationen

Originalbeschreibung:

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Electricity Bill Project Report

Hochgeladen von

Copyright:

Verfügbare Formate

Electricity Billing System

Ms. isha mittal Pallavi Gairola (7240)

Add and maintain records of available products.

5. ANALYSIS OF PRESENT SYSTEM

6. PROBLEMS OF EXISTING SYSTEM

7. CHARACTERSTICS OF THE PROPOSED SYSTEM

COST BENEFIT ANALYSIS

Hardware Cost 10,000

Software Cost 6,000

YEAR COST CUM.COST BENEFIT CUM.BENEFIT

EXPLANATION OF PAYBACK ANALYSIS

RETURN ON INVESTMENT ANALYSIS

9. DATA FLOW DIAGRAM

A data flow diagram is graphical representation that depicts the information

Access is included in the professional and developer editions of

2.2 Objectives Of The System:

c. To keep the information of consuming unit of energy of previous

The old manual system was suffering from a series of drawbacks.

3.2 Feasibility Study:

4. SYSTEM DEVELOPMENT ENVIRONMENT:

5.1 Introduction of Visual Basic:

The Fast Track To Windows Development

The data storage may belong to any DBMS engine specifically

server for same resources. Visual basic can connect to a number of

3. Network for connecting the first two components:

Visual Basics Debugging tool:

5.2 Introduction of MS-Access

1. Easy access to all data.

Access is included in the professional and developer editions of

softwares offers a number of potential advantages over traditional file-

user views to facilitate this use. A user view is a logical description of

6. PRELIMINARY DESIGN OF PROPOSED

i.) Minimized Storage Space

Data Type Description

Controlling Data Integrity

values. It is better to implement any range controls through a DBMS

Table Name: BILL

In this table there are no multivalued attributes. So this is in First

2. Table Name : Customer

In this table there are no multivalued attributes. So this is in First

In this table there are no multivalued attributes. So this is in First

Bill Charge Table:

Field Name Data Type Size Constraint

In this table there are no multivalued attributes. So this is in First

Commercial Bill Table:

6.2 Input Stream:

7.1 SDLC(System Development Life Cycle):

3. Design Of The System

1. Preliminary Investigation (Feasibility Study):

Identify the responsible users and develop an initial scope of the

The document to be produced at the end of this activity is called

2. Determination Of Requirements (Analysis)

A detailed document has to prepare by system analyst containing the

8. DETAIL DESIGN OF PROPOSED SYSTEM:

4. Commercial customer record module.

1. Domestic Bill Information Module:

2. Commercial Bill Information Module:

3. Domestic Customer Record Module:

4. Commercial Customer Record Module:

MDI FORM OF PROJECT

DESCRIPTION FORM FOR ELECTRIC

DOMESTIC BILL CALCULATION FORM

COMERCIAL BILL CALCULATION FORM