I hereby certify that the work which is being presented in the project entitled TELEPHONE BILLING SYSTM by rocky

katare, Zameer Khan, Prateek Singh and sameer balaiyain partial fulfillment of requirements for the award of degree of BACHELOR OF COMPUTER APPLICATION submitted in the Department of (COMPUTER APPLICATION) at GYANVEER MAHAVIDYALAYA SAGAR(M.P.) is an authentic record of my own work carried out during a period from JULY 2011 to under the supervision of MISS. Sarika jain.

Student Signature Sameer balaiya Rocky Katare Prateek singh rajpoot Dharmendra narwawriya Jameer khan

Under Guidance of Miss Sarika jain

This is to certify that the above declaration made by Rocky Katare,Sameer Balaiya, Prateek singh rajpoot,Jameer khan,Dharmendra narwariya is correct to the best of my knowledge. I approve this project for submission of the Bachelor of Engineering in the Department of Computer Application,Gyanveer mahavidyalaya Sagar, (M.P.).

Miss Sarika jain (Project Supervisior) Date : Place :

Pankaj Yadav (HOD Dept. of BCA)

ACKNOWLEDGEMENT
It gives me immense pleasure to express my deepest sense of gratitude and sincere thanks to my highly respected and esteemed guide Pankaj Yadav in department of BCA,Gyanveer mahavidyalaya for their valuable guidance, encouragement and help for completing this work. Their useful suggestions for this whole work and co-operative behavior are sincerely acknowledged. I would like to express my sincere thank to Dr. Mahesh Shukla for giving me this opportunity to undertake this project.

I also wish to express my indebtedness to my parents as well as my family member whose blessings and support always helped me to face the challenges ahead. At the end I would like to express my sincere thanks to all my friends and others who helped me directly or indirectly during this project work.

Place: Sagar Date:

Rocky katare Jameer khan Sameer Balaiya Prateek singh rajpoot Dharmendra narwariya

Table of contents
CHAPTER NO. TITLE Title Page Declaration of the Student Certificate of the Guide Acknowledgement List of Figures 1. INTRODUCTION 1.1 Overview 1.2 Objective 2. SYSTEM ANALYSIS 2.1 Introduction 2.2 Existing System 2.3 Drawback of the Existing System 2.4 Proposed System 2.5 Objective & Advantage of Proposed System 2.6 Data Flow Diagram 3. SYSTEM DESIGN 3.1 Introduction 3.2 Design Strategy 3.3 Input Design 3.4 Output Design 4. TOOLS CHOSEN 4.1 Proposed System Environment 4.2 Snapshots 4.3 Source Code 5. 6. CONCLUSION 5.1 Scope and Result Discussion BIBLIOGRAPHY PAGE NO. i ii iii iv vi 1-2 1 2 3-7 3 4 5 6 7 8-10 11-15 11 12-13 14 15 16-34 16 17-18 19-36 37-38 37-38 39

PROJECT WORK ON

TELEPHONE BILLING SYSTEM

SESSION: - 2011 SUBMITTED IN PARTIAL FULFILLMENT DEGREE OF BACHELOR OF COMPUTER APPLICATIONS
SUBMITTED TO PANKAJ YADAV GUIDED BY: Miss Sarika Jain SUBMITTED BY: Sameer balaiya Rocky katare Prateek singh rajpoot Dharmendra narwariya Jameer khan
5

CHAPTER-1
1 .INTODUCTION The purpose of the project is to present the Computerization of Telephone Billing System 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. The project TELEPHONE MANAGEMENT SYSTEM is to monitor the monthly bills of the telephones, provided to its employees and some outside agents by the organization. In this project the present manual process of maintaining the telephone bills is being computerized. Every telephone is allocated an upper limit of the monthly bills, which is predefined and is based on the salary of the user. So a user has to pay only the amount that exceeds the limit. Our system takes the monthly bill of each telephone as the input and produces the output reporting by how much a telephone is exceeding the limit. The master data for each phone is maintained which is permanent
6

and is altered only at the time of installation or deinstallation of a telephone. Only the monthly billing data is updated every month. In this system the facility of viewing the information about the telephones and entering information about their telephones, the operators enjoy the facility of modifying, deleting, adding new data to the existing database. 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 manual one with lots of errors. 1.2 OBJECTIVE OF THE PROJECT system previously followed was totally

The existing organization has a well structure with modern machinery and computers. Since the number of telephones allocated by the organization is very large and also they are increasing at a raped rate, the maintenance of each record manually is very difficult and also cery much error prone hence the entire process is being computerized. It also increases the performance the organization.of

The main objective while implementing the project Telephone Billing System was to minimize the work and at the same time increase the speed of the work done.
7

This new system is built with the following objective: Information retrieval will become easy.

Maintenance of database as well as overall project will become easy. Security increased. Data redundancy will be greatly reduced because this new system is built using C++. It entails looking into duplication of efforts, bottlenecks and inefficient existing procedures.

CHAPTER-2 2. SYSTEM ANALYSIS 2.1 INTRODUCTION System analysis is the performance management and documentation of activities related to the four life cycle phases of any software namely: The Study Phase The Design Phase The Development Phase The Operators Phase 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: Study of current methods, the basic inputs available and output desired. The splitting of a variable inputs into (.dat) files so as to reduce redundancy and increase consistency. Give the idea of key field (if any) .
9

 Ideas regarding code generation. Software Analysis starts with a preliminary analysis and later switches on to a detailed one. During the preliminary analysis the Analyst takes a quick look at what is needed and whether the cost benefits. Detailed analysis studies in depth all the cornered factors, which builds and strengthens the software. 2.2 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. The existing organization has a well structure with modern machinery and computers. Since the number of telephones allocated by the organization is very large and also they are increasing at a raped rate, the maintenance of each record manually is very difficult and also cery much error prone hence the entire process is being computerized. It also increases the performance of the organization.

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.
10

2.3 DRWABACK OF THE EXIXTING 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. Updating is very tedious job. There is no central database from where one can get different statistical data at one place. The above facts, figures and drawbacks clearly indicate that there is need for computerization and thus decided to computerize the TELEPHONE BILLING SYSTEM. Since the existing system was totally manual which has lots of complexities, shortcomings in itself and all the data was being stored in registers, files etc thus to overcome the
11

limitation of the existing system, the new computerized system was needed, so that information can be provided to the user more quickly, easily and more accurately. 2.4 PROPOSED SYSTEM

The new system titled TELEPHONE BILLING SYSTEM was hence proposed to remove all the drawbacks discussed above. Information is a vital ingredient for the operation and management of any organization. Thus any system should have the ability to provide error free filtered information after processing the required data. This system has been taken up with a view for developing a more sophisticated system that can be easily handled by any kind of users. The proposed system aims at efficient and timely information for decision-making, integrate with other functions, and reduce redundant work. Important features of this proposed system are: Consistent user interface with high economic features built into it. System design in modular and structured way so as to make the integration with other subsystems easier. User has complete control as it provides and accept only appropriate and valid data. User-friendly error messages are provided wherever necessary. Addition, deletion, modification of records as when needed. Providing connections to new customers. Bill generation for customers.
12

2.5 OBJECTIVE & ADVANTAGE OF PROPOSED SYSTEM To reduce workload of staff. To reduce the delay in processing time. To reduce the delay in bill generation. To provide the user-friendliness in all possible ways. To provide greater flexibility. Make maintenance changes easy. To store data in a centralized location to reduce redundancy and increase consistency. Easy and efficient way of maintaining the records o each and every telephone. It can be monitored easily which phone is exceeding the limit permitted to it and by how much. Various reports can be generated about the data as per the requirements. New data entry is easy. Even deinstalled the telephone records are also maintained. The data modification procedures are easy It is built such a manner that ay one can understand it and use it. Easy to install on computers and has very minimal hardware and software requirements.

13

2.6 DATA FLOW DIAGRAM

CONTEXT DIAGRAM

CUSTOMER RECORDS AND RATES

ADMINISTRATOR

TELEPHONE BILLING SYSTEM GENERATED BILL

CUSTOMER

14

 FIRST LEVEL DATA FLOW DIAGRAM

1 Input Username And Password
Login Verificatio n

Valid User New Customer Details Customer Details (Master File) (table 1)
2

Input Ratings

Processing of new customer information

ADMINISTRATOR

3
Processing of ratings for different types of calls

Rate Maintenance ( table 2) Ratings

15

Valid Customer Number Minute reading Input Meter / Minute Reading For Verification of Customer
4

valid customer and processing of minute reading

Customer Minute Details

( table 3)

16

FIRST LEVEL DATA FLOW DIAGRAM (continued)

Valid customer number and Minute details Ratings

Rate Maintenance Customer Name And Address

5 Generation of Bill

Generated Bill

User

17

Customer Details (Masterfile) CHAPTER - 3 3 SYSTEM DESIGN 3.1 INTRODUCTION 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( algorithms etc) 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.

18

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. 3.2 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.
19

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. First activity deals with understanding the problem , the foal and the constraints. The second activity focus is on clearly specifying what has been found during analysis. Issues such as rerp, spec, language and tools and checking the specification are addressed during this activity. Requirement analysis is done in ordered to understand the problem that the software system has to solve. The emphasis is requirement analysis is in identifying what I needed for the system and now how the system will achieve its goal. The task is complicatedly the fact that there are at least two parties involved in software development- the client and developer. The developer has to develop the system to satisfy the client problem, domain and the client often does now understand the issues involved in software systems. This causes communication gaps that has to be bridged during requirement analysis.

20

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 whos 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.

21

3.3 INPUT DESIGN Input design is the process of converting user-originate inputs to a computer-based format. The goal of design input data is to make data entry as easy, logical and free. The most common source of data processing errors is inactive input data. Effective design of the input data minimizes the error made by data entry operators. Catching errors on input is far less costly than correcting after data storage is complete. User-friendly input design enables quick error detecting and correction. Verification and validation is the most important in input design. Since the system is used interactively, it has two types of inputs. Interactive input-which is the point contact of the user with the system and the input to the internal system i.e. Databases. For full efficiency of the system, it is necessary that the input must be accurate. Since the user of the system may not be a technical person and may not know input concepts so it is required that he warn, prevent and correct invalid data entry. There are many ways that can be designed to handle such a situation. We can prevent the user entering invalid data into the databases by
22

warning, neglecting or messaging appropriately. The user is then allowed to input correct data. Some help provisions may aid the user to point out the error. In this system inputs are collected from terminals through keyboard. 3.4 OUTPUT DESIGN Output design has been an ongoing activity from the very beginning of the project. The objective of the output design is to convey the information of all past activities, current status and to emphasize important events. The output generally refers to the results and information that is generated from the system. The output design of the system is accomplished keeping in mind the following activities: Determine what information is to display. Decide whether to display or print the information retrieved, processed, generated from the system. Arrange the presentation of information in an acceptable format. Decide how to distribute the output to the intended recipients. 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.
23

CHAPTER -4 4 TOOLS CHOSEN 4.1 PROPOSED SYSTEM ENVIORNMENT

The system environment can be classified into two categories Hardware environment Software environment Hardware Environment

The application front-end (client) will be designed on machines with Windows 98/ Window XP, Pentium III processors, 64/128 MB RAM. The database will be running on Windows OS, Pentium III processors, 64 MB RAM. Keyboard Software Environment

The application front end will be designed using Visual Basic 6.0.
24

The database has been designed on Microsoft Access

(Office Package).

4.2

SNAPSHOT

25

26

CHAPTER-5 5 CONCLUSION 5.1 SCOPE & RESULT DISCUSSION 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. A fully menu driven user-friendly computerized system has been developed where the user can perform task like entering data, deleting and updating the information with great ease. All the operations are carried automatically preventing a lot of manual work.

27

 Additional checks have also been incorporated into the system to avoid duplications of data as far as possible. SCOPE FOR FURTHER IMPROVEMENT 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: Our system is not online so further it can be improved. The security is limited so some additional arrangement could be made to provide more security to the system. There is no provision of complain handling so further it can be added.

MAIN ACHIEVEMENT OF THE SYSTEM This project gives an overview of the Telephone Billing System. After entering into the project, user is left with several options via

a) The user can take new connections. b) The user can view the existing lists of customers, which already
28

have telephone connections. 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.

29

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. LET US C ---- Yashwant Kanetkar 2. LET US C++ ---- Yashwant Kanetkar SITES: www.google.co.in www.wikipedia.com

30