Online Phone Billing System
Online Phone Billing System
Online Phone Billing System
TELEPHONE
BILLING SYSTEM
CONTENTS
1) Introduction
i) Introduction of the Project
ii) Objective of the Project
2) System Analysis
i) Introduction
ii) Existing System
iii) Drawback of the Existing System
iv) Proposed System
v) Objective and Advantage of Proposed System
vi) Software Requirement Specification
vii) Data Flow Diagram
viii) Gantt Chart
3) System Design
i) Introduction
ii) Design Strategy
iii) Input Design
iv) Output Design
v) Table Design
4) Tools Chosen
i) Proposed System Environment
ii) About Front End
iii) About Back End
5) Source Code
6) Input And Output Screen
7) Testing And Debugging
8) Scope And Result Discussion
9) Bibliography
1) (i) INTRODUCTION OF THE
PROJECT
The purpose of the project is to present the requirement of the
Computerization of Telephone Billing System. The project thus calculates
the telephone bills automatically. It does almost every work which is
related to automatic telephone billing connection system via- new
connection , customer record modification, viewing customer records &
all works related to rate of bills, meter readings in addition to bill
calculation and bill generation. “Telephone Billing System” is developed
as per seeing the increasing requirement to speed up the work and
incorporate a new work culture. Thus a new software has been proposed
to reduce manual work, improving work efficiency, saving time and to
provide greater flexibility and user-friendliness as the system previously
followed was totally manual one with lots of errors.
1) (ii)OBJECTIVE OF THE PROJECT
System analysis is a vast field of study through which system analyst puts
his thoughts and searches for the solution of problem. He has to get a
clear idea of what he has in hand and what he has to produce. He has to
extract the essence of expectations. He has to satisfy the user in the very
possible way. System analysis needs and should include the following
steps of study:
1. Problem Definition
2. Feasibility Study
3. System Analysis
4. System Design
5. Implementation
6. Post Implementation
7. Maintenance
2) (ii) EXISTING SYSTEM
The existing system was a manual one. Whatever be the process
involved in the system were done through register (files) . There were lots
of complexities involved in the system. When any customer takes new
connections then separate files were maintained. Updating of data was
very tedious job. It was not easy to do several administrative works like
managing rates of calls, addition or modification of metered calls &
customer entries.
2) (iii) DRAWBACKS OF
EXISTING SYSTEM
In the existing system all the office works was done manually. The
manual work processes was time consuming and hence slow. Following
are the main drawbacks of the existing system:
increase consistency.
2) (vi) SRS
SRS (Software Requirement Specification) is a document that completely
describes what the proposed should do, without describing how the
software does it.
PURPOSE : The purpose of the project is to develop a system which
is user friendly, easy to use , maintain and satisfies all the
requirements of the user.
PERFORMANCE REQUIREMENT
1) The operation time should be small and the throughput should be high.
CONTEXT DIAGRAM
CUSTOMER RECORDS
AND RATES
ADMINISTRATOR
BILLING
SYSTEM
CUSTOMER
FIRST LEVEL DATA FLOW DIAGRAM
Login
Verification
Valid User
New Customer Details
New Customer
Details Customer Details
2 (Master File)
Processing of
(table 1)
new customer
information
Input Ratings
Rate Maintenance
ADMINISTRATOR 3
Processing of
( table 2)
ratings for Ratings
different types
of calls
Ratings
Generated
5 Bill
Generation of
Bill
Rate Maintenance
User
Customer Name And Address
Customer Details
(Masterfile)
SECOND LEVEL DATA FLOW DIAGRAM
Minute Reading
is multiplied
Customer Minute Details with
Ratings corresponding
( table 3) rating
Multiplied Result
Rate Maintenance
5.2
( table 2) Multiplied Result Multiplied Result
is inserted in
table
( table 4)
Bill is generated,
using this multiplied
Customer Name & Address result, monthly
rental, getting the
sum with customer
name & address
Customer Details
( Master file)
Generated Bill
2) (viii) PROJECT PLANNING
AND SCHEDULING
GANTT CHART
Problem Statement
& Analysis
Feasibility Study
3)(ii)DESIGN STRATEGY
The design strategy is a vital aspect of the system to be developed. The
design of the software reflects the basic understanding of the problem.
For designing a good system what we have to be is to get correct
definition of the problem and analyze the problem thoroughly.
The design of a system should be such that if a small portion is changed.
The rest of the system should be unaffected. This is the flexibility of the
system. Greater the system flexibility greater will be the system reliability.
While carrying out the job of designing of a new system one has to
consider many factors. These factors include the drawbacks and
limitations of the present manual system as well as of the features and
advantages of the proposed system. It should be designed in such a
manner that even a layman can run it without any difficulty.
1. CUSTOMER_RECORDS
custname Text
custadd Text
custphno Number
2. CALL_RATES
local Number
mobile Number
STD Number
ISD Number
MonthlyRental Number
3. CUSTOMER_METER_READING
custphno Text
mLocal Number
mmobile Number
mSTD Number
mISD Number
4. BILL_RECORD
custname Text
custphno Text
custadd Text
localmt Number
mobilemt Number
STDmt Number
ISDmt Number
5. LOGIN
LOGIN_ID AutoNumber
LOGIN_NAME Text
LOGIN_PASSWORD Text
4) (i) PROPOSED SYSTEM
ENVIRONMENT
The system environment can be classified into two categories –
Hardware environment
Software environment
Hardware Environment
Software Environment
The application front end will be designed using Visual Basic 6.0.
Toolbox: The Tool Box window differs from the tool bar. The Tool Box is a
collection of tool that acts as a repository of controls we can place on
forms. Some tools are Selection Pointer, Picture Box, Label, Text Box,
Frame Button, Command Botany, Check Box, Option Button etc.
Form: Visual Basic uses a window; controls are the widgets one place of
a form. In a form we will customize by adding controls such as command
buttons, list boxes to it. At the top of the black form is the little bar with its
caption.
Common Form properties:
There are several common properties to customize a form, these are: -
Caption: Caption is used as a title that the Microsoft Window for the
application icon when the user minimizes the application.
Name: This property is used to give the name that one want to use to
refer to the form.
Enabled: If user sets Enabled to false, the form cannot respond to any
events such as the user checking on the form.
Icon: The icon property determines the icon users application will display
when it is minimized on tool bar or turned into a stand-alone application
on windows desktop.
Visible: If the value of the property is set to false, it will no longer be
visible.
Text Boxes:
It is used to display text or to accept user input. Most of the code is written
to process the information users enter into them. Several properties of
text boxes are as follows: -
Text: The text property in text box is the analog of the caption property for
a command button or a form; it controls text the users see. It determines
whether text on the control such as label or command button, is left
justified, centered, or right justified on the control. The Alignment property
take one of the three values: 0-Left justify, 1-Right justify, 2-Center.
Multiline: This property determines whether a text box can accept more
than one line of text when the user runs the application, and it is usually
combine with resulting the value of the scrollbar property. If true the
property specifies the text box can hold more than a line of text.
Max Length: This property specifies the maximum number of characters
that the text box will accept. A value of 0 indicates that the user can enter
a value of any length.
Locked: This property determines whether the user can enter a value or
change the default value of the text box. If true, the user cannot change
the text box value until the program, at run time assigns a false to this
property.
Password char: The Password property lets us limit what the text box
displays.
Labels: Use Labels to display information programmer does not want the
user to be able to change. Most common use for Labels is to identify a
text box or other control by describing its contents. Another common use
is to display help information.
Message Boxes:
Message boxes display information in the dialog box superimposed on
the form. They want for the user to choose a button before return to the
application. User cannot switch to another form in programmers
applications as long as Visual Basic is displaying a message box.
ValueNamed constantDescription
0 vbOKOnly OK button
1 vbOKCancel OK and Cancel buttons
2 vbAboRetryIgnore Abort,Retry and Cancel buttons
3 vbYesNoCancel Yes and No and Cancel buttons
4 vbYesNo Yes and No buttons
MsgBox “ The message goes in codes”, 4
Frames:
Programmer usually frames passively to group images or controls.
Option Buttons:
They all work together. When the user chooses one button, all other
buttons in the group are turned off. The value property of the option
button tells us whether a button was selected by the user. If the value
property is true, the user selected that button; otherwise, its value
property is false.
Check Boxes:
Check Boxes differ from option button in that, regardless of how many
Check Boxes one places on a form, they can all be turned on and off
independently. If the user has selected Check Boxes, the value property
switches to true. It stays true until the user deselects that box.
List and Combo boxes:
Use list boxes when we have a fixed list of choices. Visual Basic
automatically adds vertical scroll bars when the list box is small for all
items it contains.
To allow users to input data as well as choices from a list, we use a
Combo Box.
Data List
Data Combo
Data Grid
Microsoft Flex Grid
Microsoft Hierarchical Flex Grid
Rich Textbox
Microsoft Chart
Date Time Picker
Image Combo
Dim i As Integer
Option Explicit
Public LoginSucceeded As Boolean
Private Sub cmdcancel_Click()
LoginSucceeded = False
Me.Hide
frmopt.Show
End Sub
Label2.ForeColor = RGB(r, g, b)
Label3.ForeColor = RGB(r, g, b)
Label4.ForeColor = RGB(r, g, b)
End Sub
Option Explicit
Option Explicit
Dim rs As Recordset
Dim con As Connection
Private Sub err_han()
Dim response As Integer
Select Case Err.Number
Case -2147467259
Call EDTB(Empty)
Call EmptyTB
MsgBox "Duplicate Record Entry", vbInformation + vbOKOnly,
"TELEBILL SOFTWARE"
Case Else
If Err.Number <> 0 Then
MsgBox Err.Number &" : "& Err.Description
End If
End Select
End Sub
Call EmptyTB
Call EDTB(False)
error_handler:
err_han
End Sub
Else
Call EDCmd(False)
End If
End Sub
Option Explicit
Dim con As Connection
Dim rs As Recordset
Dim sum1 As Double
Dim sum2 As Double
Dim sum3 As Double
Loop
Set rs = Nothing
Dim kk As Recordset
Set kk = New Recordset
kk.Open "select * from table2", con, adOpenDynamic, adLockOptimistic
If Not kk.EOF Then
txtlocal.Text = kk!Local
txtmobile.Text = kk!Mobile
txtstd.Text = kk!STD
txtisd.Text = kk!ISD
txtmonrent.Text = kk!MonthlyRental
Else
MsgBox "No Pulse rate entry!!!", vbInformation + vbOKOnly, "TBS
SOFTWARE"
Me.Hide
Set kk = Nothing
Exit Sub
End If
Set kk = Nothing
DTPicker1.Value = Format$(Now, "dd-MMM-yyyy")
Call EmptyTB
End Sub
With DataReport1
Set .DataSource = reco
.Sections("section1").Controls.Item("lbltelno").Caption = Combo1.Text
.Sections("section1").Controls.Item("lblname").Caption = txtname.Text
.Sections("section1").Controls.Item("lbladrs").Caption = txtadrs.Text
.Sections("section1").Controls.Item("lblmtrlocal").Caption =
txtmtrlocal.Text
.Sections("section1").Controls.Item("lblmtrmobile").Caption =
txtmtrmobile.Text
.Sections("section1").Controls.Item("lblmtrstd").Caption = txtmtrstd.Text
.Sections("section1").Controls.Item("lblmtrisd").Caption = txtmtrisd.Text
.Sections("section1").Controls.Item("lblmonrent").Caption =
txtmonrent.Text
.Sections("section1").Controls.Item("lbltotlocal").Caption = "Rs. "&
txttotlocal.Text
.Sections("section1").Controls.Item("lbltotmobile").Caption = "Rs. "&
txttotmobile.Text
.Sections("section1").Controls.Item("lbltotstd").Caption = "Rs. "&
txttotstd.Text
.Sections("section1").Controls.Item("lbltotisd").Caption = "Rs. "&
txttotisd.Text
.Sections("section1").Controls.Item("lbltot").Caption = txttot1.Text
.Sections("section1").Controls.Item("lbltax").Caption = txttax.Text
.Sections("section1").Controls.Item("lblafterdate").Caption = txtdue.Text
.Sections("section1").Controls.Item("lbldate").Caption =
Format$(DTPicker1.Value, "dd-MMM-yyyy")
.Show
End With
End If
Set reco = Nothing
End Sub
txtadrs.Text = Empty
txtmtrlocal.Text = Empty
txtmtrmobile.Text = Empty
txtmtrstd.Text = Empty
txtmtrisd.Text = Empty
End Function
Option Explicit
Dim choosemoddel As Integer
Dim rs As Recordset
Dim con As Connection
If choosemoddel = 0 Then
con.Execute "insert into table3 values('"& txtteleno.Text &"','"&
txtlocal.Text &"','"& txtmobile.Text &"','"& txtstd.Text &"','"& txtisd.Text &"')"
MsgBox "Records Inserted Successfully", vbInformation +
vbOKOnly, "TELEBILL SOFTWARE"
End If
Else
MsgBox "Check for Empty Boxes", vbInformation + vbOKOnly,
"TELEBILL SOFTWARE"
End If
Call EDSaveCancel(True, False)
Call EmptyTB
Call EDTB(False)
End Sub
If choosemoddel = 2 Then
If MsgBox("Are You Sure!!", vbDefaultButton2 + vbYesNo, "TELEBILL
SOFTWARE") = vbYes Then
con.Execute "delete from table2 where telno='"& txtteleno.Text &"'
and val(localm) ='"& txtlocal.Text &"' and val(mobile) = '"& txtmobile.Text
&"'and val(std) ='"& txtstd.Text &"' and val(isd) ='"& txtisd.Text &"'"
End If
Call EmptyTB
Call EDSaveCancel(True, False)
Call EDTB(False)
choosemoddel = 0
End If
End If
End Sub
Option Explicit
Dim rs As Recordset
Dim con As Connection
Private Sub err_han()
Text1.Text = "0.00"
Text2.Text = "0.00"
Text3.Text = "0.00"
Text4.Text = "0.00"
Text6.Text = "0.00"
End Sub
Private Sub cmdadd_Click()
con.Execute "insert into CALL_RATES values('"& Text1.Text &"','"&
Text2.Text &"','"& Text3.Text &"','"& Text4.Text &"','"& Text6.Text &"')"
MsgBox "Rate Changed Successfully", vbInformation +
vbOKOnly, "TELEBILL SOFTWARE"
cmdback.SetFocus
End Sub
Option Explicit
Dim choosemoddel As Integer
Dim rs As Recordset
Dim con As Connection
Private Sub err_han()
Dim response As Integer
Select Case Err.Number
Case -2147467259
Call EDSaveCancel(True, False)
Call EDTB(Empty)
Call EmptyTB
MsgBox "Duplicate Record Entry", vbInformation + vbOKOnly, "TBS
SOFTWARE"
Case Else
If Err.Number <> 0 Then
MsgBox Err.Number &" : "& Err.Description
End If
End Select
End Sub
Private Sub cmdok_Click()
If txtpwd.Text <>"Poonam Kumari" Then
MsgBox "Wrong password entered!!!", vbCritical + vbOKOnly, "TBS
SOFTWARE"
Call EDPwd(False)
Call EDTB(False)
Call EDSaveCancel(True, False)
Exit Sub
End If
Call EDPwd(False)
Call EDSaveCancel(False, True)
Dim list As ListItem
With lvwModDel
.ListItems.CLEAR
End With
Set rs = New Recordset
rs.Open "select * from CUSTOMER_RECORDS", con, adOpenDynamic,
adLockOptimistic
If rs.BOF Then
MsgBox "No Records", vbInformation + vbOKOnly, "TBS SOFTWARE"
Call EDSaveCancel(True, False)
Else
lvwModDel.Visible = True
Do While Not rs.EOF
Set list = lvwModDel.ListItems.Add
list.Text = rs(0)
list.SubItems(1) = rs(1)
list.SubItems(2) = rs(2)
rs.MoveNext
Loop
End If
Set rs = Nothing
End Sub
txtname.Text = Trim(rs.Fields(1))
txtaddress.Text = Trim(rs.Fields(2))
rs.MoveNext
Loop
Set rs = Nothing
End Sub
End Sub
End Sub
Tele Admin
3. WELCOME FORM
4. MDI Form
5. ENTRY FORM
6. CUSTOMER RECORD VIEWING FORM
UNIT TESTING
Unit testing focuses verification effort on the smallest unit of software
design, the module. It comprises the set of test performed by the
programmer prior to integration of the unit into larger system. The testing
was carried out during the coding stage itself. In this step each module is
found to be working satisfactorily as regards to the expected output from
the module.
INTEGRATION TESTING
# Bottom Up Integration
The first one is done where integration is carried out by addition of minor
modules to major modules. While Bottom Up integration follows
combination of smaller ones to large one. Here Bottom Up Integration
was encouraged. Even though correction was difficult because the
isolation of causes is complicated by the vastness of the entire program,
all the errors found in the system were corrected and then forwarded to
the next testing steps.
User acceptance of a system is the key factor for the success of any
system. The system under consideration was tested for users acceptance
by constantly keeping in touch with the perspective system user at the
time of developing and making changes wherever required. This is done
with the regards to the following points:
A system may be defined as a set of instruction combined in the same
form and directed to some purpose.
Before any development is undertaken certain specifications are prepared
which objectively describe the application system. The System
specifications are made after consulting the end user managers of the
relevantdepartments.
Software to be developed is planned on the basis of requirement of the
user. The problem definition statement description of present situation
and goal to be achieved by news system.
Even the best system developed has some flaws or others. There always
exist scope of further improvement in the system. The effect of
implementations of new computerized system is found remarkable.
The following are the major improvement of the new system over the
existing system.
b) The user can view the existing lists of customers, which already
have telephone connections.
c) The user can of course see bills & take billing statements.
Chapter – 9
Bibliography
BIBLIOGRAPHY
The great help from our faculty members and my project guide that led
the successful completion of the project. Besides that, I took the help of
some books and websites to develop the project. They are : --
1. VISUAL BASIC BLACK BOOK
--- Steven Holzner
SITES :
1. www.a1vbcode.com
2. www.google.co.in