1.1 Introduction To Proposed System
1.1 Introduction To Proposed System
1.1 Introduction To Proposed System
1. INTRODUCTION:
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:
We have tried to make such type of software, which satisfy the above
given requirement.
The firm handles all of the work manually, which is very tedious and
mismanaged.
3. SYSTEM ANALYSIS:
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.
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.
The most successful system projects are not necessarily the biggest
or most visible in the business but rather those truly meet user’s
expectations.
Feasibility considerations
Three key considerations are involved in the feasibility study. They are
as follows:-
Economic Feasibility:
Technical Feasibility:
Behavioral Feasibility:
5. INTRODUCTION TO TOOLS:
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).
Friendly Environment
Creating a form, adding controls to form and writing code behind the
form are all managed within a friendly environment.
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 server’s 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.
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.
Importance of database:
Growth in the usage of Computers in Business and Industrial sector
initiated development of modern Database Software. Database
software’s offers a number of potential advantages over traditional fileprocessing
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
organization’s 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.
· 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.
· 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:
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.
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:
The Analyst finds out whether current technical resources, which are
available in the organization, is capable of Handling user requirements.
Economical Feasibility:
Operational Feasibility:
Detailed investigation
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
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.
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.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.
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
Electricity Billing System
MDI FORM OF PROJECT
Electricity Billing System
DESCRIPTION FORM FOR ELECTRIC
CHARGES
Electricity Billing System
DOMESTIC BILL CALCULATION FORM
Electricity Billing System
COMERCIAL BILL CALCULATION FORM
Electricity Billing System
DOMESTIC CUSTOMER RECORD FORM
Electricity Billing System
COMMERCIAL BILL RECORD FORM
Electricity Billing System
DOMESTIC BILL REPORT FORM
Electricity Billing System
COMMERCIAL BILL REPORT FORM
Electricity Billing System
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
Electricity Billing System
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.
Electricity Billing System
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:
9.2 Coding of MDI Form:
9.3 Coding of Commercial Bill Calculation Form
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
cmd4Last.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
cmd1First.Enabled = True
cmd4Last.Enabled = True
If adocom.Recordset.AbsolutePosition = adPosBOF And
adobill.Recordset.AbsolutePosition = adPosBOF Then
MsgBox ("no other record")
adocom.Refresh
adobill.Refresh
End If
End Sub
Private Sub cmd4Last_Click()
adocom.Recordset.MoveLast
Electricity Billing System
adobill.Recordset.MoveLast
cmd1First.Enabled = True
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
Electricity Billing System
adobill.Refresh
End If
End Sub
Private Sub comerfram_DragDrop(Source As Control, X As Single, Y As Single)
End Sub
Private Sub Form_Load()
DataGrid1.Visible = False
End Sub
9.4 Coding of Description Form:
Private Sub cmdExit_Click()
Unload Me
End Sub
Private Sub cmdOk_Click()
If detailcb.ListIndex = 0 Then
Text1.Text = "1.30 Rs"
Text2.Text = "3.00 Rs"
Text3.Text = "3.50 Rs"
Text4.Text = "60.00 Rs"
ElseIf detailcb.ListIndex = 1 Then
Text1.Text = "4.00 Rs"
Text2.Text = "4.25 Rs"
Text3.Text = "4.50 Rs"
Text4.Text = "100.00 Rs"
End If
End Sub
Private Sub Form_Load()
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
Electricity Billing System
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
Private Sub cmdDelete_Click()
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
Private Sub cmdExit_Click()
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
Electricity Billing System
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
Private Sub cmdOk_Click()
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
Electricity Billing System
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
Private Sub cmdprevious_Click()
MDIForm1.Show
Unload Me
End Sub
Private Sub cmdSave_Click()
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
Private Sub cmd1First_Click()
adocust.Recordset.MoveFirst
cmd1First.Enabled = False
cmd4Last.Enabled = True
End Sub
Private Sub cmd2Next_Click()
adocust.Recordset.MoveNext
cmd1First.Enabled = True
cmd4Last.Enabled = True
If (adocust.Recordset.AbsolutePosition) = adPosEOF Then
MsgBox ("no other record")
adocust.Refresh
End If
Electricity Billing System
End Sub
Private Sub cmd3Previous_Click()
adocust.Recordset.MovePrevious
cmd1First.Enabled = True
cmd4Last.Enabled = True
If adocust.Recordset.AbsolutePosition = adPosBOF Then
MsgBox ("no other record")
adocust.Refresh
End If
End Sub
Private Sub cmd4Last_Click()
adocust.Recordset.MoveLast
cmd1First.Enabled = True
cmd4Last.Enabled = False
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
Private Sub cmd1First_Click()
adocust.Recordset.MoveFirst
cmd1First.Enabled = False
cmd4Last.Enabled = True
End Sub
Private Sub cmd2_Click()
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
MsgBox ("no other record")
End If
adodesc.Refresh
End Sub
Private Sub cmd2Next_Click()
adocust.Recordset.MoveNext
Electricity Billing System
cmd1First.Enabled = True
cmd4Last.Enabled = True
If adocust.Recordset.AbsolutePosition = adPosEOF Then
MsgBox ("no other record")
adocust.Refresh
End If
End Sub
Private Sub cmd3_Click()
adodesc.Recordset.MovePrevious
cmd1.Enabled = True
cmd4.Enabled = True
If adodesc.Recordset.AbsolutePosition = adPosBOF Then
MsgBox ("no other record")
adodesc.Refresh
End If
End Sub
Private Sub cmd3Next_Click()
dombillcalfrm.Show
Unload Me
End Sub
Private Sub cmd3Previous_Click()
adocust.Recordset.MovePrevious
cmd1First.Enabled = True
cmd4Last.Enabled = True
If adocust.Recordset.AbsolutePosition = adPosBOF Then
MsgBox "no other record"
adocust.Refresh
End If
End Sub
Private Sub cmd4_Click()
adodesc.Recordset.MoveLast
cmd1.Enabled = True
cmd4.Enabled = False
End Sub
Private Sub cmd4Last_Click()
adocust.Recordset.MoveLast
cmd1First.Enabled = True
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
adocust.Recordset.Delete
Electricity Billing System
adodesc.Recordset.Delete
MsgBox "Record is Deleted"
adocust.Refresh
adodesc.Refresh
Else
adocust.Refresh
adodesc.Refresh
End If
End Sub
Private Sub cmdExit_Click()
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
cmdlast.Enabled = True
If adodesc.Recordset.AbsolutePosition = adPosEOF Then
MsgBox ("no other record")
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()
Electricity Billing System
adocust.Recordset.AddNew
adodesc.Recordset.AddNew
txtname.SetFocus
End Sub
Private Sub cmdPrev_Click()
MDIForm1.Show
Unload Me
End Sub
Private Sub cmdprevious_Click()
adodesc.Recordset.MovePrevious
cmdfirst.Enabled = True
cmdlast.Enabled = True
If adodesc.Recordset.AbsolutePosition = adPosBOF Then
MsgBox ("no other record")
adodesc.Refresh
End If
End Sub
Private Sub cmdlast_Click()
adodesc.Recordset.MoveLast
cmdfirst.Enabled = True
cmdlast.Enabled = False
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
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
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.
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.
10. 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.
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.