project.01
project.01
project.01
Submitted By:
Umar Tahir AS22CHA0326
Faizan Naseer AS22CHA0330
Mudassar Hussain AS22CHA0343
Hamid Raza AS22CHA0338
STATEMENT OF SUBMISSION
This is certify that Umar Tahir Roll No. AS22CHA0326 and Faizan Naseer Roll
No.AS22CHA0330and Mudassar HussainRoll No. AS22CHA0343 successfully
completed the project named as: Telecom billing management, at the Department
of Computer Science & Information Technology, Riphah International College
Chishtian, to fulfill the requirement of the degree of ADP Cs.
Table of Contents
1. Introduction ...............................................................................................................................2
i) Introduction of the Project ...........................................................................................................3
ii) Objective of the Project ...............................................................................................................4
2. System Analysis.........................................................................................................................5
i) Introduction ...................................................................................................................................6
ii)Existing System ...........................................................................................................................7
iii) Drawback of the Existing System .............................................................................................8
iv) Proposed System ........................................................................................................................9
v) Objectives and Advantages of Proposed System .......................................................................10
vi) Software Specifications ..................................................................................................................... 11
vii) Data Flow Diagram ..................................................................................................................12
viii)Gantt Chart ..............................................................................................................................13
3.System Design ...........................................................................................................................14
i) Introduction ................................................................................................................................15
ii) Design Strategy .........................................................................................................................16
iii)Input Design ..................................................................................................................................17
iv) Output Design ...........................................................................................................................18
v) Table Design............................................................................................................................................ 19
4. Tools Chosen ............................................................................................................................20
i) Purposed System Environment ...................................................................................................21
ii)About Front End .........................................................................................................................22
iii) About Back End .......................................................................................................................23
5. Source Code ....................................................................................................................................... 25
6. Input and Output Screen ............................................................................................................ 26
7. Testing and Debugging .........................................................................................................27
8. Scope and Result Discussion ..............................................................................................28
9. Bibliography .............................................................................................................................29
Chapter – 01
Introduction
1) (i) INTRODUCTION 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:
The existing system is totally manual thus there are chances of error in
processing.
The basic and major drawbacks in the existing system are the speed of
retrieval of data from files, which leads to delay.
Maintenance of voluminous data is very cumbersome and laborious job.
The manual jobs such as calculation are more error prone.
There are plenty of chances of duplicity of data and information.
The new system titled “TELEPHONE BILLING SYSTEM” was hence proposed
to remove all the drawbacks discussed above.
2) (vi)SRS
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
Valid User
New Customer Details
New Customer
Details Customer Details
2 (Master File)
Processing of
new customer (table 1)
information
Input Ratings
Rate Maintenance
Processing of
ratings for different (table 2)
Ratings
ADMINISTRAT types of calls
OR
Ratings
Generated
5 Bill
User
Customer Name And Address
Customer Details
(Masterfile)
SECOND LEVEL DATA FLOW DIAGRAM
Minute Reading is
multiplied with
Customer Minute Details corresponding
Ratings
rating
( table 3)
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
System design is the second step in the system life cycle, in which overall design
of the system is achieved. The functionalities of the system is designed and studied
in this phase. The first step is designing of program specification. This determines
the various data inputs to the system, data flow and the format in which output is to
be obtained.
Design phase is a transmission phase because it is a transition from user oriented
document to computer data. The activity in the design phase is the allocation of
functions to manual operations, equipment and computer programs. Flow charts
prepared in the study time received and decomposed until all functions in the
system perform evidently.
Design is a multistep process that focuses on data structures, software architecture,
procedural details( algorithmsetc.) and links between the modules. The design
process goes through logical and physical stages. In logical design reviews are
made linking existing system and specification gathered. The physical plan
specifies any hardware and software requirement, which satisfies the local design.
Modularization of task is made in the mode. The success of any integrated system
depends on the planning of each and every fundamental module. Usually a project
is revised in step by step sequence. Inter phase management of such module is also
important.Software design methodology changes continually as new methods,
better analysis and broader understanding evolve.
Various techniques for software design do exit with the availability of criteria for
design quality. Software design leads three technical activities-design, code and
test.
The techniques for software design do exit with the availability of criteria for
design quality. Software design leads three technical activities-design, code and
test that are required to build and verify software. Each activity transforms
information, which validates the software. The design system converts theoretical
solution introduced by the feasibility study into a logical reality.
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.
An important quality of a software must enjoy is “user friendliness”. It can be
achieved in many ways like providing menu, giving context sensitive help, doing
automatic validation to input data, etc. Another main factor is speed efficiency. In
order to achieve speed efficiency, the program should be designed accordingly and
the user is provided with a compiled copy of the software package with necessary
data file format rather than source code.
Design of input and output formats is equally important for any design. The output
format should be designed in such a way that it must reflect all the required
information in detail. The design of the database itself such as type of data stored,
size of data etc. Some of the decisions made during database design are:
Which data items are to be recorded and in which database.
Length of each record based on the characteristics of the data items on
which it is based.
Data that’s unauthorized change must be prevented.
Data, which must be avoided from redundancy.
Maintenance of data integrity etc.
Avoid over writings.
Prevents invalid data access and changes.
Having all this, a positive interaction with clients at every stage of development is
the core around which the software is built.
In the output design phase one or more output media can be selected. Out of which
the most common ones are CRT displays and print out. Here only CRT display has
been attempted. A rapid enquiry is obtained from CRT displays. From design is
made interesting and attractive. Easy understanding and effectiveness is made
possible.
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
Chapter – 04
Tools Chosen
4) (i) PROPOSED SYSTEM
ENVIRONMENT
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 user’s 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 is 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
MICROSOFT ACCESS
Database: -A database is a set of data, organized for easy access. The database is
the actual data. It is the database that you will be accessing when you need to
retrieve data.
Data Dictionary: -The data dictionary is a set of tables Access uses to maintain
information about the database. The data dictionary contains information about
tables, indexes, clusters, and so on.
DBA (Database Administrator): -The DBA is the person responsible for the
operation, configuration, and performance of the database. The DBA is charged
with keeping the database operating smoothly, ensuring that backups are done on a
regular basis (and that the backups work), and installing new software. Other
responsibilities might include planning for future expansion and disk space needs,
creating databases and tablespaces, adding users and maintaining security, and
monitoring the database and retuning it as necessary. Large installations might
have teams of DBAs to keep the system running smoothly; alternatively, the tasks
might be segmented among the DBAs.
Microsoft Access is a very effective DBMS tool which is generally used by all the
users. It is compatible with all types of systems & can be installed and used as and
when required.
Chapter – 05
Source Code
5) SOURCE CODE
*******************Code For Start Form*******************
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
Private Sub cmdadd_Click()
On Error GoToerror_handler
If Text1.Text <> Empty Or Text2.Text <> Empty Then
con.Execute "insert into table1 values('" & Text1.Text & "','" & Text3.Text &
"','" & Text2.Text & "')"
MsgBox "Records Inserted Successfully", vbInformation +
vbOKOnly, "TELEBILLING SOFTWARE"
Else
MsgBox "Check for Empty Boxes", vbInformation + vbOKOnly,
"TELEBILLING SOFTWARE"
End If
Call EmptyTB
Call EDTB(False)
error_handler:
err_han
End Sub
Else
rs.MoveNext
End If
Loop
If match = False Then
MsgBox "No such record is there!!!",vbInformation + vbOKOnly,
"TELEBILL SOFTWARE"
rs.MoveFirst
Else
Call LocateMtr
Call Display
End If
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
Public Function TotalBill()
txttotlocal.Text = Val(txtlocal.Text) * Val(txtmtrlocal.Text)
txttotmobile.Text = Val(txtmobile.Text) * Val(txtmtrmobile.Text)
txttotstd.Text = Val(txtstd.Text) * Val(txtmtrstd.Text)
txttotisd.Text = Val(txtisd.Text) * Val(txtmtrisd.Text)
sum1 = Val(txttotlocal.Text) + Val(txttotmobile.Text) + Val(txttotstd.Text) +
Val(txttotisd.Text)
txttot.Text = "Rs. " & sum1
sum3 = Val(txtmonrent.Text)
sum2 = sum1 * 0.08
txttax.Text = "Rs. " &Int(sum2)
txttot1.Text = "Rs. " &Int(sum1 + sum2 + sum3)
txtdue.Text = "Rs. " &Int(sum1 + sum2 + sum3 + 50)
End Function
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
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
Main Screen
LOGIN FORM
Main Menu
Add Record Menu
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
Integration testing is a systematic technique for constructing the program structure
while at the same time conducting tests to uncover error associated within the
interface. The objective is to take unit tested modules and build a program
structure that has been dictated by design. All modules are combined in this step.
The entire program is tested as whole. And chaos in interfaces may usually result.
A set of errors is encountered in such a case.
# 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 user’s 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.
Every project whether large or small has some limitations no matter however
diligently developed. In some cases limitations is small while in other cases they
may be broad also. The new system has got some limitations. Major areas where
modifications can be done are as follows:
c) The user can of course see bills & take billing statements.
d) The user can also do several administrative works like managing rates of
calls, addition or modification of metered calls & customer entries.
It is a computerized system, which can be used very easily & effectively by the
administrators of the telephone billing system.
Chapter – 9
Bibliography
8.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: --
SITES :
1. www.a1vbcode.com
2. www.google.co.in