SURESH GYAN VIHAR UNIVERSITY, JAIPUR

Project Report On “Telephone Directory System”

1

Submitted By: Guided To: Birendra k. Rathor Bright KESWANI M.C.A. (iv sem) (HOD CA Dept..)

CERTIFICATEThis is to certify that this report embodies the original work done by Birendra k. Rathor during this project submission as a partial fulfilment of the requirement for the System Design Project of Masters of Computer Application IV Semester, of the Suresh Gyan Vihar University, Jaipur

Bright Keswani(HOD of M.C.A Dept.)Suresh Gyan Vihar Universe

2

ACKNOWLEDGEMENTThe satisfaction that accompanies that the successful completion of any task would be incomplete without the mention of people whose ceaseless cooperation made it possible, whose constant guidance and encouragement crown all efforts with success.We are grateful to our project guide Mr. Bright Keswani for the guidance, inspiration and constructive suggestions that helpful us in the preparation of this project. Birendra k.Rathor MCA (4th sem)

3

Table of ContentsChapter 1:- 1.1 Introduction 5 1.2 Objective 5 1.3. Application 6 1.4. Feature 6 1.5. DFD 7 1.5. Overview 8

Chapter 2:- 2.1. System Description 9 2.2. Block Diagram 11

Chapter 3:- 3.1. Technologies Used 13 3.2. Basic Components 16 3.3 . Liquid Crystal Display 18

Chapter 4:- 4.1. Feasibility Study 19

Chapter 5:-

4

5.1. Data Tables 21

Chapter 6:- 6.1. Cost estimation 23 6.2. Conclusion 26

CHAPTER: 1

1.1 Introduction A telephone directory (also called a telephone book and phone book) is a listing of telephone subscribers in a geographical area or subscribers to services provided by the organization that publishes the directory. It consists of the name as well as the telephone number of people added as contact in the directory. Name and telephone number are displayed in alphabetical order.

1.2 ContentSubscriber names are generally listed in alphabetical order, together with their postal or street address and telephone number. In principle every subscriber in the geographical coverage area is listed, but subscribers may request the exclusion of their number from the directory, often for a fee. Their number is then said to be "unlisted" American English, "ex-directory" English or "private" Australia and New Zealand. Practices as to the display of Caller-ID on calls made by unlisted subscribers vary by jurisdiction. Sometimes the Caller-ID on outbound calls is not shown; in other jurisdictions unlisted numbers are displayed unless the caller dials a blocking code; in others the customer may request automatic blocking by the telephone company. In the US, under current rules and practices, mobile phone and Voice over IP listings are not included in telephone directories. Efforts to create cellular directories have met stiff opposition from several fronts, including a significant percentage of subscribers who seek to avoid telemarketers.In 1991 the

5

U.S. Supreme Court ruled (in Feist v. Rural) that telephone companies do not have a copyright on telephone listings, because copyright protects creativity and not the mere labor of collecting existing information. Within the geographical reach of the Court, the Feist ruling has resulted in the availability of many innovative telephone directory services on CD-ROM and the World Wide Web.

1.3 Objectives We are determined to design a system which is intended in saving name and number of desired persons. The main objective of telephone directory is to add, search, edit and delete various contacts.

1.4 Applications Telephone directory has been frequently in use in our daily life. Wecommonly see telephone directory installed in PSTN telephone sets, mobile phone etc. Telephone Directory application provides the ability to search, view, and manage entries in a directory. Mobile Directory application should allow any subscriber with any type of mobile device that supports GPRS to instantly search telephone contact number of any individual . The search result data loads directly to the mobile screen and gives the user option :-

CALL,

SAVE,

VIEW,

SEND TO FRND or

DISCARD. Mobile Directory eliminates the need to call any other call center.

6

1.5 Features:-

Secure Easy to use Reliable and accurate No need of remember

1.6 Data Flow Diagram :-

7

1.7 Overview of Project :- The report is organized in chapters; each dedicated to explaining the project in easier way. Although detailed information is not provided due to security reasons of the project and its replication protection, but the chapters are brief enough to convey the work done. In the chapter, a brief introduction of the project is presented. The second deals with the system description of the project where we have describe the block diagram of the project and hardware and software portion of the project. In the third , we have described the detail information of project where function of each hardware components and software portion is described. Fourth deals with observation. Fifth deals with limitation and further implementation of project. And finally it gives conclusion to the project.

CHAPTER 2

2.1 SYSTEM DESCRIPTION:- The main aim of the project is to create a directory that is able to provide the ability to search, view, and manage entries in a directory about various individuals. 2.1 Block Diagram The basic block diagram of the project which shows how ‘Telephone Directory’ works is shown below.

2.2 Diagram:-

8

9

2.2 Block Diagram :-

2.3 Description of the block diagram :- The above block diagram describes the project architecture. From the block diagram we can understand the flow of the system. As shown above first of all number and name are entered via keypad .These data are displayed regularly in

10

the lcd connected to a port of microcontroller.These contact of the individual can be stored in the external memory (EEPROM). As further these records can be further manipulated by retrieving them from the EEPROM. These contacts can be edited, deleted, also searched as required by the user

. There are mainly two parts in the block diagram.

a. Software part

b. Hardware part

Software part ;-

Software enables us to perform specific tasks. Software is a tool that interfaces with hardware and implements the user specifications. For interfacing between microcontroller and LCD, microcontroller and Keypad and EEPROM various software tools are used.

The software tools used are as follows:

a. C-programming

b. SDCC

c. EZ-Downloader

d. Top view simulator

e. Proteus

a. C-programming ;- The C programming is a popular and widely used high level programming language for creating computer programs. Programmers around the world embrace C because it gives maximum concomponents used while developing program. c. Proteus is mainly used in simulation, a simple model of ckt was created and with particular program it was loaded to view output.

Hardware part :- The hardware parts of the project includes

a. Microcontroller

11

b.LCD display

c. EEPROM

d.Keypad

CHAPTER 3

3.1 TECHNOLOGIES USED Front end as:HTML

Back end as:Advance Java

Server:Apache tomcat 6.0

Database:Microsoft access

12

Querying language:Sql

3.2 Basic Components :-

It is important to get acquainted with the integral components and its purpose that is used in this project before going through the project details. The list of the major components that are used are as follows:

Hex Keypad :- Keypads are a part of Human Machine Interface and play really important role in a small embedded system where human interaction or human input is needed. Matrix keypads are well known for their simple architecture and ease of interfacing with any microcontroller.

Microcontroller (AT89c51)

Features :-

The AT89C51 microcontroller provides the following standard features:

1. 4KB of Flash memory

2. 128 bytes of RAM

3.32 I/O lines with two 16-bit timer/counters

4.Five vector two-level interrupt architecture

5.Full duplex serial port

6. 0n-chip oscillator and clock circuitry.

13

3.3 Liquid Crystal Display(LCD) Introduction

LCD is a Liquid Crystal Display. A LCD is a thin, flat panel used for electronically displaying information such as text, images, and moving pictures. Its uses include monitors for computers, televisions, instrument panels, and other devices ranging from aircraft cockpit displays, to every-day consumer devices such as video players, gaming devices, clocks, watches, calculators, and telephones.

LCD Pin Description :-

14

Table of LCD pin:-

3.4 MICROCONTROLLER (AT89C55) DESCRIPTION:- The AT89C55 is a low-power, high-performance CMOS 8-bit microcomputer with 20K Bytes of Flash programmable and erasable read only memory (PEROM). The device is manufactured using Atmel’s high-density

15

nonvolatile memory technology and is compatible with the industry-standard 80C51 instruction set and pin out.

Microcontroller Board:-

The microcontroller board consists of one crystal oscillator whose function is to create an electrical signal with a very precise frequency. This frequency is commonly use to keep track of time, to provide a stable clock signal for digital integrated circuits, and to stabilize frequencies forradio transmitters.

3 Keypad and LCD Interfacing To scan the keypad completely, we need to make rows low one by one and read thecolumns. If any of the buttons is pressed in a row, it will take the correspondingcolumn to a low state which tells us that a key is pressed in that row. If button 1 of arow is pressed then Column 1 will become low, if button 2 then column2 and so on.

Each button of Keypad is assigned with various functions. We have assigned keyswith alphabets and number. Some keys have been allocated for special function likemenu, delete, back. When these keys are pressed various special functions such asadd, edit, search etc has been generated with certain functions in programming. Whencontact has to be added we insert name as well as number using keypad. Keypad isconnected to P2 through which input is given to microcontroller. These datas areconcurrently displayed in the LCD.

LCD is connected to P1 and P3, which serves as output device. First of all LCD is

initialized with following control codes as shown in the table. When data bus of LCD is provided with 8-bit data then certain output is generated.

16

3.5 RESULT and DISCUSSION : DESCRIPTION OF FINDING:- Working in this project led us to many findings which initially we were unaware of. We not only got chance to implement our theoretical knowledge into practical but also got opportunity to learn new programming languages. This project has helped us to enhance our knowledge about electronics components, software development and wireless communication. Working in LCD we found out that to display alphanumeric value in LCD we can either use LCD table which provides us hex. code corresponding to the data that is to be displayed or we can use ASCII value of that data. While interfacing Keypad with Microcontroller we found out that same port must be used for both column and rows. While interfacing of EEPROM addressing is the key factor and using proper delay is very essential for output generation.

Limitations:-

This project on “TELEPHONE DIRECTORY” has following limitations

• Delay in pressing the keys cannot be achieved perfectly.

• EDIT option in this project could not be implemented.

• Memory management is a great drawback.

• This unit is having problem when back button is pressed.

17

Problem Occurred During Programming

• If we don’tuse the same portfor key pad entry then problem occurred…

• While storing the flipped char in the array name[rr] all the flipped characters

were also stored so a new name1[tt] array was made and the last value stored

in name[rr] after each case was stored..eg..a,b,c was pressed then another

button pressed then at (!=)case values was interchanged..

• Problem occurred when tried to break out of while loop

• Calculation of particular delay was difficult.

During Hardware Testing

• Cables created were very fragile and ultimately we used glue stick to fix it.

• Zip Socket is troubled us with it’s pin holdings.

• Problem in Voltage regulation for microcontroller was fetched

. • Interfacing of EEPROM was a great challenge.

Further Implementation:- This architecture is a basic backbone for other electronics projects.

• The concept of “Telephone Directory “can be implemented with interfacing of MMC cards using SPI (Serial Peripheral Interface).

• This architecture can be used in systems such as

1.Password Based door lock

2.Restaurant Automation System

This architecture can be implemented in all systems that uses input as Keypad and Output as LCD

CHAPTER 418

FEASIBILITY STUDY

4.1 ECONOMIC FEASIBILITY:-

Economic analysis is most frequently used for evaluation of the effectiveness of the system. More commonly knows as cost/benefit analysis the procedure is to determine the benefit and saving that are expected from a system and compare them with costs, decisions is made to design and implement the system.This part of feasibility study gives the top management the economicjustification for the new system. This is an important input to themanagement the management, because very often the top management does not like to get confounded by the various technicalities that bound to be associated with a project of this kind. A simple economic analysis that gives the actual comparison of costs and benefits .

4.2 TECHNICAL FEASIBILITY:-

Technical feasibility centers on the existing manual system of the test management process and to what extent it can support the system. According to feasibility analysis procedure the technical feasibility of the system is analyzed and the technical requirements such as software facilities, procedure, inputs are identified. It is also one of the important phases of the system development activities. The system offers greater levels of user friendliness combined with greater processing speed. Therefore, the cost of maintenance can be reduced. Since,processing speed is very high and the work is reduced in the maintenance point of view management convince that the project is operationally feasible.

4.3 BEHAVIOURAL FEASIBILITY :-

19

People are inherently resistant to change and computer has been known tofacilitate changes. An estimate should be made of how strong the user islikely to move towards the development of computerized system. These arevarious levels of users in order to ensure proper authentication andauthorization and security of sensitive data of the organization.

20

CHAPTER 5

TABLE DESIGN 

5.1 Customer: Table

S.No.  Field NameData Type

1 Id Number

2 Name Text

3 Addreess Text

4 Provider Text  

5.2 Service Provider : Table 

S.No.  Field Name Data Type

21

1 Id Number

2 Plan Number

3 Issue_date Date/time

4 Due_date Date/time

5 Providername Text

5.3 Directry: Table 

S.No.  Field Name

Data Type

1 add new Number

2 Group Number

3 Move Number

4 Copy Number

 

22

CHAPTER 6

6.1 Cost estimation:-

Software cost estimation is the process of predicting the effort required to develop a softwaresystem. Many estimation models have been proposed over the last 30 years. This paper provides a general overview of software cost estimation methods including the recent advances in the field. As a number of these models rely on a software size estimate as input, we first provide anoverview of common size metrics. We then highlight the cost estimation models that have beenproposed and used successfully. Models may be classified into 2 major categories: algorithmicand non-algorithmic. Each has its own strengths and weaknesses. A key factor in selecting a costestimation model is the accuracy of its estimates. Unfortunately, despite the large body ofexperience with estimation models, the accuracy of these models is not satisfactory. The paperincludes comment on the performance of the estimation models .

6.1 Software sizingThe software size is the most important factor that affects the software cost. This sectiondescribes five software size metrics used in practice. The line of code and function point are themost popular metrics among the five metrics.

Line of Code: This is the number of lines of the delivered source code of the software, excludingcomments and blank lines and is commonly known as LOC [10]. Although LOC is programminglanguage dependent, it is the most widely used software size metric. Most models relate this

23

measurement to the software cost. However, exact LOC can only be obtained after the project hascompleted. Estimating the code size of a program before it is actually built is almost as hard asestimating the cost of the program.A typical method for estimating the code size is to use experts' judgement together with atechnique called PERT [3]. It involves experts' judgment of three possible code-sizes: Sl, thelowest possible size; Sh the highest possible size; and Sm, the most likely size. The estimate of thecode-size S is computed as:S=S1+Sn+Sm/6

Cost estimationThere are two major types of cost estimation methods: algorithmic and non-algorithmic.Algorithmic models vary widely in mathematical sophistication. Some are based on simplearithmetic formulas using such summary statistics as means and standard deviations [9]. Othersare based on regression models [38] and differential equations [30]. To improve the accuracy ofalgorithmic models, there is a need to adjust or calibrate the model to local circumstances. Thesemodels cannot be used off-the-shelf. Even with calibration the accuracy can be quite mixed.We first give an overview of non-algorithmic methods.

Non-algorithmic Methods

Analogy costing: This method requires one or more completed projects that are similar to thenew project and derives the estimation through reasoning by analogy using the actual costs ofprevious projects. Estimation by analogy can be done either at the total project level or atsubsystem level. The total project level has the advantage that all cost components of the systemwill be considered while the subsystem level has the advantage of providing a more detailedassessment of the similarities and differences between the new project and the completedprojects. The strength of this method is that the estimate is based on actual project experience.However, it is not clear to what extend the previous project is actually representative of theconstraints, environment and functions to be performed by the new system. Positive results and adefinition of project similarity in term of features were reported in [33].

Expert judgment: :-This method involves consulting one or more experts. The experts provideestimates using their own methods and experience. Expert-consensus mechanisms such as Delphitechnique or PERT will be used to resolve the inconsistencies in the estimates. The Delphitechnique works as follows:1) The coordinator presents each expert with a specification and a form to record estimates.2) Each expert fills in the form individually (without discussing with others) and is allowedto ask the coordinator questions.3) The coordinator prepares a summary of all estimates from the experts (including mean ormedian) on a form requesting another iteration of the experts’ estimates and the rationalefor the estimates.4) Repeat steps 2)-3) as many rounds as appropriate.

24

A modification of the Delphi technique proposed by Boehm and Fahquhar [5] seems to bemore effective: Before the estimation, a group meeting involving the coordinator and experts isarranged to discuss the estimation issues. In step 3), the experts do not need to give any rationalefor the estimates. Instead, after each round of estimation, the coordinator calls a meeting to haveexperts discussing those points where their estimates varied widely.

Parkinson: Using Parkinson's principle “work expands to fill the available volume” [28], the cost is determined (not estimated) by the available resources rather than based on an objectiveassessment. If the software has to be delivered in 12 months and 5 people are available, the effortis estimated to be 60 person-months. Although it sometimes gives good estimation, this method is not recommended as it may provide very unrealistic estimates. Also, this method does notpromote good software engineering practice.

Price-to-win: The software cost is estimated to be the best price to win the project. Theestimation is based on the customer's budget instead of the software functionality. For example, if a reasonable estimation for a project costs 100 person-months but the customer can only afford person-months, it is common that the estimator is asked to modify the estimation to fit 60 personmonths’ effort in order to win the project. This is again not a good practice since it is very likely to cause a bad delay of delivery or force the development team to work overtime.

Bottom-up: In this approach, each component of the software system is separately estimated andthe results aggregated to produce an estimate for the overall system. The requirement for thisapproach is that an initial design must be in place that indicates how the system is decomposedinto different components.

Top-down: This approach is the opposite of the bottom-up method. An overall cost estimate forthe system is derived from global properties, using either algorithmic or non-algorithmicmethods. The total cost can then be split up among the various components. This approach ismore suitable for cost estimation at the early stage.

Algorithmic methods:-The algorithmic methods are based on mathematical models that produce cost estimate as afunction of a number of variables, which are considered to be the major cost factors. Anyalgorithmic model has the form:Effort = f(x1, x2, …, xn)where {x1, x2, …, xn} denote the cost factors. The existing algorithmic methods differ in twoaspects: the selection of cost factors, and the form of the function f. We will first discuss the costfactors used in these models, then characterize the models according to the form of the functionsand whether the models are analytical or empirical.

Cost factors:-Besides the software size, there are many other cost factors. The most comprehensive set of cost

25

factors are proposed and used by Boehm et al in the COCOMO II model [6]. These cost factorscan be divided into four types:

Product factors: required reliability; product complexity; database size used; requiredreusability; documentation match to life-cycle needs;

Computer factors: execution time constraint; main storage constraint; computer turnaroundconstraints; platform volatility;

Personnel factors: analyst capability; application experience; programming capability;platform experience; language and tool experience; personnel continuity;

Project factors: multisite development; use of software tool; required development schedule.The above factors are not necessarily independent, and most of them are hard to quantify. Inmany models, some of the factors appear in combined form and some are simply ignored. Also,some factors take discrete values, resulting in an estimation function with a piece-wise form.

6.1 CONCLUSION;- The aim of this project was to build an Telephone directory through which allowed to add,search, delete contacts of individual andaccess toexternal memorydevice. At the completion of this project we are able to add, search and delete contacts hence the project is completed successfully. A approximate model of Telephone Directory was assembled using keypad, lcd, microcontroller and EEPROM.

26