ONLINE ADDRESS BOOK

ABSTRACT:
People change their mobile numbers. Contacts lost due to lack of updating. Maintain address book. Overview: Updating the contact and letting people know about it is a headache. The proposed system aims to solve the problem of everyone updating personally and maintaining an user anytime, anywhere.

INTRODUCTION:
PURPOSE:
Stores, retrieve, update & deletion of contacts

SCOPE:
Keep track of contacts Search & modify the data

OBJECTIVES:
Efficiency Sending mail Centralized database Search ease Stores as many thousands numbers

Includes name & group

EXISTING SYSTEM:
Limitations of Existed system:
User able to store only limited contacts. User able to store only limited details about the person. It may be destroy after few years.

It is burden to user to carry handy address book.

 Whenever the user changes the number it is headache to him inform it to each and every contact members.

PROPOSED SYSTEM:
Advantages of proposed system:
Full featured and easy to use the address book. Password protected and secured interface for data safety. Multi users can create additional address book with full and limited access to the address book. No downloading required quick registration.

Keep all contact information with you.

MODULES:
Module 1: In the 1st module we include about the registration and login. Module 2: In the 2nd module we include creating the new contact, we can search for contact, we can edit the information of the contacts and we update the information in address book.

Module 3: In the 3rd module we include compose mail, inbox. Module 4: In this module we also include change password, by using this we can change the password. In this we also include logout.

UML DIAGRAMS:
General purpose visual modeling language. Used to understand the system to be constructed. Support high level development concepts. Independent of programming language.

1. USECASE DIAGRAM:
The main purpose of the Use-case diagram is to help visualize the functional requirements of a system. It provides the relationship of Actors to essential processes, as well as the relationships among different use-cases.

login

add contact details

delte contact details

edit contact details

send mail

user open existing address book

cretate new address book

offer to change

search address book

save address book

save address as

Fig 1: Usecase Diagram

2. CLASS DIAGRAM:
Describes type of objects & relationships. Model class structure & contents. Define static structure of a system.

Common contents:
1. Classes 2. Attributes 3. Operations 4. Relationships

Fig 2: Class Diagram

3. SEQUENCE DIAGRAM:
A kind of interaction diagram Represents object interactions A message sequence chart

Common contents:
1. Messages 2. Objects 3. Sequence number

1. ADD USER CONTACTS:

address book address controller book GUI 1: do add()

multi input pane

address book

person

2: show multi input dialogue() 3: get address book() 4: add person() 5: create()

6: set changed since last save()

Fig 3.1:Sequence Diagram For Add Contact Details

2. EDITING USER CONTACTS:

address address book book GUI controller 1: do edit() 2: get address book()

multi input pane

address book

user

3: return address book() 4: get information of person() 5: get first name() 6: return first name() 7: get last name() 8: return last name() 9: return full name of person() 10: get address() 11: return address() 12: get city() 13: return city() 14: get state() 15: return state() 16: get mobile number() 17: return mobile number() 18: return other name information 19: show multiple input dialogue() 20: return 21: update user() 22: update()

23: save changed since last save()

Fig 3.2: Sequence Diagram For Editing A User

3. SEARCHING CONTACT:

address book GUI

address book controller

address book

file sysstem

file chooser

1: get changed since last save() 2: return() 3: do offer save changes() 4: do open() 5: show open dialogue() 6: get selected file() 7: read file() 8: set changed since last save() 9: set file() 10: set address book()

Fig 3.3: Sequence Diagram For Searching Contact

4.SAVE ADDRESS:

addressbook GUI

addressbook controller dosav e()

addressbook

filesystem

getaddressbook()

getfile()

dosav eas() sav efile() setchangedsincelastsav e() setfile()

Fig 3.4: Sequence Diagram For Save Address

5. ACTIVITY DIAGRAM: Graphical representation of work flows. Used to represent step-by-step work flows of components. Captures the process flows. Common contents
1. Initial state 2. Final state 3. Action state 4. Activity state 5. Transition 6. Branching 7. Fork 8. join

1. ACTIVITY DIAGRAM FOR LOGIN:

Initial State

Open Website

Login

Register

Enter Uname&pwd

Validation

Object flow

:Validation (success)

View profile

If Logout

Yes

Logout

Final State

Fig 4.1: Activity Diagram For Login

2. ACTIVITY DIAGRAM FOR UPDATE:

Initial State

Open website

Enter uname&pwd

Validation

object flow

View profile

:Validation (success)

Read mail

Select Update No

Update operation

Update contact

Object flow

Object flow

If logout

:Operation (replace)

:Update (success)

Yes

Logout

Final State

Fig 4.2: Activity Diagram For Update

3. ACTIVITY DIAGRAM FOR SENT MAIL:

select sent mail wri te mail no select contact send mail

i f logout yes logout

final state

Fig 4.3: Activity Diagram For Sent Mail

4. ACTIVITY DIAGRAM FOR OTHER ACTIVITIES:

I nitial State

Login

No

I success f Y es View profile

Select any other activity no Start activity yes I Logout f

Log out

Final State

Fig 5.4: Activity Diagram For Other Activities

TESTING:
Code testing: It examines the logic of the program. In this testing each & every instruction is tested. Unit testing: It focuses on smallest part of the program. i.e. Module. Errors can be identified boundary of the module. Link testing: It focuses on compatibility on each module. like length, type etc. Integration testing: The goal is integrating all the modules without any errors. We can get main system. System testing: It is checked all requirements have been satisfied (or) not. Acceptance testing: It is focuses on missing operations, finding errors & complete verification to meet the customer requirements. White box testing: This is unit test method. Unit will be taken thoroughly to find & reduce maximum possible errors. Black box testing: In this testing, Module will be taken as black box. It can take some input & generate output. And forwarded to other modules.

SCREEN SHOTS:
REGISTRATION FORM:

Fig : Output Screen For Registration

LOGIN PAGE:

Fig : Output Screen For Login

HOME PAGE:

Fig : Output Screen For Home Page

COMPOSE MAIL:

Fig : Output Screen For Compose Mail

SEARCH RESULT:

Fig : Output Screen For Search Result

INBOX:

Fig : Output Screen For Inbox

CHANGE PASSWORD:

Fig : Output Screen For Change Password

ADD DETAILS:

Fig : Output Screen For Add Details

FUTURE SCOPE:
There is a scope to include pictures for individual profiles, and automatically send message to the contacts. Synchronize the contact details with mobile.

CONCLUSION:
Online address book is easy to use, yet powerful software that makes keep in track of your contacts. Using this software the user not only search the contact information using either the name or sur name but also modify the data base or existing records in the direct. User will get the person name contact number, mail id, address etc. user can easily change their profile and password, login id etc.

BIBILOGRAPHY:
The following are the details of books and the sites which have details regarding the servlet technology which is used in this project.

Servlet & Jsp by sun publications.

Web Sites: www.java.sun.com www.servlets.com www.oreilly.com www.vaannila.com