CHAPTER 1

OVERVIEW OF THE PROJECT 1.1 INTRODUCTION

Telephone billing system project is to present the requirement of Computerization of the

Billing System. The project thus calculates the telephone bills

automatically. It does almost every wor which is related to automatic telephone billing connection system via! new connection " customer record modification" viewing customer records # all wor s 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 wor and incorporate a new wor culture. Thus a new software has been proposed to reduce manual wor " improving wor efficiency" saving time and to provide greater fle&ibility and user!friendliness as the system previously followed was totally manual one with lots of errors. Since it is directly associated with the database" so there is very little maintainability problem with this tool. Since there is very limited usage of separate forms" this tool is very much portable. This tool uses several canvases on the same form.This tool is very much fle&ible for future enhancements. The main objective while implementing the project Telephone Billing System were to minimize the wor and at the same time increase the speed of the wor done and also the information retrieval will become easy. In this project the maintenance of database as well as overall project will become easy. 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 of the specified system. Security measure will be adopted" by maintaining the login of username and the password. 'ata redundancy will be greatly reduced because this new system is built using (isual Basic ).* as front!end. It entails loo ing into duplication of efforts bottlenec s and inefficient e&isting procedures.

1.2 MODULE DESIGN

+ur project is implemented using the following modules. Input 'esign. +utput 'esign. Table 'esign.

1.2.1 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 ma e data entry as easy" logical and free. The most common source of data processing errors is inactive input data. ,ffective design of the input data minimizes the error made by data entry operators. (erification and validation is the most important in input design. -ser!friendly input design enables quic error detecting and correction. .e can prevent the user entering invalid data into the databases by 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 eyboard.

1.2.2 OUTPUT DESIGN

+utput 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.In the output design phase one or more output media can be selected. +ut of which the most common ones are C/T displays and print out. 0ere only C/T display has been attempted. 1 rapid enquiry is obtained from C/T displays. 2rom design is made interesting and attractive.

1.2.3 TABLE DESIGN

In this table design we are created tables such as customer records table"call rates table"customer metre reading table" bill record table and the user login table for the easy and effective understanding. 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 of the specified system.

1. CUSTOMER RECORDS
Custname Custadd Custphno Te&t Te&t 3umber

2. CALL RATES
4ocal 5obile ST' IS' 5onthly/ental 3umber 3umber 3umber 3umber 3umber

3. CUSTOMER METER READING

Custphno 54ocal 5mobile 5std 5isd Te&t 3umber 3umber 3umber 3umber

4. BILL RECORD
custname Custphno Custadd 4ocalmt 5obilemt ST'mt IS'mt Te&t Te&t Te&t 3umber 3umber 3umber 3umber

5. LOGIN
4+6I37I' 4+6I37315, 4+6I3781SS.+/' 1uto3umber Te&t Te&t

CHAPTER 2
SYSTEM ANALYSIS 2.1 EXISTING SYSTEM
The e&isting system was a manual one. .hatever be the process involved in the system were done through register 9files: . There were lots of comple&ities involved in the system. .hen any customer ta es new connections then separate files were maintained. -pdating of data was very tedious job. It was not easy to do several administrative wor s li e managing rates of calls" addition or modification of metered calls # customer entries.

2.2 DRAWBACKS OF EXISTING SYSTEM

In the e&isting system all the office wor s was done manually. The manual wor processes was time consuming and hence slow. 2ollowing are the main drawbac s of the e&isting system; The e&isting system is totally manual thus there are chances of error in 8rocessing. The basic and major drawbac s in the e&isting system are the speed of retrieval of data from files" which leads to delay. 5aintenance of 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. -pdating is very tedious job. There is no central database from where one can get different statistical data at one place. Since e&isting system was totally manual which has lots of comple&ities" shortcomings in itself and all the data was being stored in registers" files .Thus to overcome the limitations of e&isting system" the new computerized system needed" so that information can be provided to the user more quic ly and more accurately.

2.3 PROPOSED SYSTEM

The new system titled $T,4,80+3, BI44I36 S<ST,5% was hence proposed to remove all the drawbac s 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 ta en up with a view for developing a more sophisticated system that can be easily handled by any ind of users. The proposed system aims at efficient and timely information for decision! ma ing" integrate with other functions" and reduce redundant wor . I !"#$%&$ '(%$)#(* "' $+,* !#"!"*(- *.*$( Consistent user interface with high economic features built into it. System design in modular and structured way so as to ma e the integration with other subsystems easier. -ser has complete control as it provides and accept only appropriate and valid data. -ser!friendly error messages are provided wherever necessary. 1ddition" deletion" modification of records as when needed. 8roviding connections to new customers. Bill generation for customers.

2.4 OBJECTIVES OF THE PROPOSED SYSTEM

To reduce wor load 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 fle&ibility. 5a e maintenance changes easy. To store data in a centralized location to reduce redundancy and increase consistency.

2.5 SOFTWARE SPECIFICATION 2.5.1 HARDWARE RE/UIREMENTS

8rocessor /15 0ard dis 5onitor Deyboard 5ouse

; =>) Compatible processor with ?.@ 60z Cloc speed ; A?B 5B or more ; ; ; ; B* 6B or more (61CS(61 ?*E Deys B buttonsC F buttons RE/UIREMENTS .indows B***C=8 (isual Basic ).* 5S 1CC,SS

2.5.2 SOFTWARE +perating System ; 2ront end Bac end ; ;

CHAPTER 3
SYSTEM IMPLEMENTATION 3.1 ABOUT VISUAL BASIC 0.1
(isual Basic ).* is an enjoyable language due to its visual environment. Building a windows program in (isual Basic requires dragging and dropping graphic objects on to the screen from a toolbo&. Thus (isual Basic is the efficient 6-I tools to develop some e&citing windows!based application. (isual Basic ).* is much more than just a programming language. The programming language forms the bac ground of all that ta es place in a running (isual Basic program. The language is a secondary consideration to the user interface. 1 windows program offers a high degree of user interaction using the graphical elements that forms the objects on the window the user sees .If the user interface is not correct" user will not li e the program. (isual Basic lets one add menus" te&t bo&es" command buttons" option buttons 9for ma ing e&clusive choice:" chec bo&es" list bo&es" scroll bars and file and directory bo&es to blac windows. +ne can use (isual Basic to communicate with other applications" running under windows. (isual Basic offers; 5ore Internet features" better support for data base development" more language feature to ma e programming job easier.

SOME TOOLS OF VISUAL BASIC 0.1

'ata access features allow creating databases" front!end applications and scalable server side components for most popular databases formats including 5icrosoft SG4 server and other enterprise level databases. 1ctive = technology allows using functionality provided by other applications such as 5icrosoft .ord" 5icrosoft ,&cel and other applications and objects could be created using the 8rofessional ,nterprise editions of (isual Basic. Internet capabilities ma e it easy to provide access to documents and applications across the Internet or Intranet server applications. The finished applications are a true .e&e files that uses a (isual Basic virtual machine that can be freely distributed.

SIGNIFICANCE FEATURES OF VISUAL BASIC 0.1

Toolbo&; The Tool Bo& window differs from the tool bar. The Tool Bo& is a collection of tool that acts as a repository of controls we can place on forms. Some tools are Selection 8ointer" 8icture Bo&" 4abel" Te&t Bo&" 2rame Button" Command Botany" Chec Bo&" +ption Button etc. T(3$ B"3(*4 It is used to display te&t or to accept user input. 5ost of the code is written to process the information users enter into them. Several properties of te&t bo&es are as follows; ! T(3$4 The te&t property in te&t bo& is the analog of the caption property for a command button or a formH it controls te&t the users see. It determines whether te&t on the control such as label or command button" is left justified" centered" or right justified on the control. The 1lignment property ta e one of the three values; *!4eft justify" ?!/ight justify" B!Center. M%3 L(&5$+4 This property specifies the ma&imum number of characters that the te&t bo& will accept. 1 value of * indicates that the user can enter a value of any length. L"67(-4 This property determines whether the user can enter a value or change the default value of the te&t bo&. If true" the user cannot change the te&t bo& value until the program" at run time assigns a false to this property. L%8(9*4 -se 4abels to display information programmer does not want the user to be able to change. 5ost common use for 4abels is to identify a te&t bo& or other control by describing its contents. 1nother common use is to display help information. M(**%5( B"3(*4

5essage bo&es display information in the dialog bo& superimposed on the form. They want for the user to choose a button before return to the application bo&.

3.2 ABOUT MICROSOFT ACCESS

D%$%8%*(4 1 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. D%$% D,6$,"&%#.: The data dictionary is a set of tables 1ccess uses to maintain information about the database. The data dictionary contains information about tables" inde&es" clusters" and so on. DBA ;D%$%8%*( A- ,&,*$#%$"#<4 The 'B1 is the person responsible for the operation" configuration" and performance of the database. The 'B1 is charged with eeping the database operating smoothly" ensuring that bac ups are done on a regular basis and installing new software. +ther responsibilities might include planning for future e&pansion and dis space needs" creating databases and tablespaces" adding users and maintaining security" and monitoring the database and retuning it as necessary. 4arge installations might have teams of 'B1s to eep the system running smoothlyH alternatively" the tas s might be segmented among the 'B1s. DBMS "# RDBMS: The 'atabase 5anagement System is the software and collection of tools that manages the database. 1 /elational 'atabase 5anagement System is a 'B5S that is relational in nature. This means that the internal wor ings access data in a relational manner. 1ccess is an /'B5S. /)(#.

1 query is a read!only transaction against a database. 1 query is generated using the

S,4,CT

statement. -sers generally distinguish between queries and other transaction types

because a query does not change the data in the database.

CHAPTER 4
SYSTEM DESIGN 4.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. 'esign 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. 2low charts prepared in the study time received and decomposed until all functions in the system perform evidently. 'esign is a multistep process that focuses on data structures" software architecture" procedural details9 algorithms etc: and lin s between the modules. The design process goes through logical and physical stages. In logical design reviews are made lin ing e&isting system and specification gathered. The physical plan specifies any hardware and software requirement" which satisfies the local design. 5odularization of tas is made in the mode. The success of any integrated system depends on the planning of each and every fundamental module. -sually 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. (arious techniques for software design do e&it with the availability of criteria for design quality. Software design leads three technical activities!design" code and test.The techniques for software design do e&it with the availability of criteria for design quality. Software design leads three technical activities!design" code and test that are required to build

11

and verify software. ,ach activity transforms information" which validates the software. The design system converts theoretical solution introduced by the feasibility study into a logical reality.

4.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. 2or 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 fle&ibility of the system. 6reater the system fle&ibility greater will be the system reliability. .hile carrying out the job of designing of a new system one has to consider many factors. These factors include the drawbac s 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. 1n important quality of a software must enjoy is $user friendliness%. It can be achieved in many ways li e providing menu" giving conte&t sensitive help" doing automatic validation to input data" etc. 1nother 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 pac age with necessary data file format rather than source code. 'esign 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; .hich data items are to be recorded and in which database. 4ength of each record" based on the characteristics of the data items on which it is based. 'ata whoIs unauthorized change must be prevented.

11

'ata" which must be avoided from redundancy. 5aintenance of data integrity etc. 1void over writings. 8revents invalid data access and changes.

4.3 PROJECT DESCRIPTION 4.3.1 DATAFLOW DIAGRAM

C-ST+5,/ /,C+/'S 13' /1T,S 1'5I3IST/1T+/

T,4,80+3, BI44I36 S<ST,5

6,3,/1T,' BI44

C-ST+5,/

12

13