Vous êtes sur la page 1sur 22

A PROJECT PROPOSAL

On
COMPLETE CONTACT BOOK
by
MRITYUNJAY AGRAWAL, VEENU GARG, VINITA
Under Guidance
of
Mr. Manoj Kumar
Submitted to the School of Computer and Information Science
in partial fulfilment of the requirements
for the degree of
Masters
Of
Computer Applications
Indira Gandhi National Open University
Regional Centre NOIDA
C-53, Sector 62, Institutional Area, Noida 201305 (U.P)


Table of Contents

1. Acknowledgment...............................................................................1
2. Introduction.......................................................................................2
3. Objectives...........................................................................................3
4. System analysis...................................................................................4
5. Software requirement specifications (SRS).....................................6
6. System Design.....................................................................................7
7. E-R Diagram.......................................................................................8
8. DFD......................................................................................................9
i. Zero Level....10
ii. Level 1 .11
iii. Level 2 .12
9. Project planning (Gantt chart)........................................................13
10. Project planning (Pert chart)...........................................................14
11. Project planning (Project Modules )...............................................15
12. Database design...............................................................................16
13. Dependencies....................................................................................18
14. Future Scope.....................................................................................19
15. Limitations........................................................................................20


P
a
g
e
1

Acknowledgement


We students of MCA from IGNOU, wish to convey my deep gratitude to Manoj Sir for
his constant encouragement, unbridled support and constructive criticisms at every step
of the project. He is an avid enthusiast of new technology and supported my decision to
take up the project. I also want to thank my study center those who help me where I need
them.


Submitted to:
IGNOU
Regional Center - Noida
Code: 2770 (P)






Submitted By:
Mrityunjay Agrawal (090591417)
Veenu Garg (093514420)
Vinita ( )
MCA 4
th
SEM



P
a
g
e
2

Introduction

This software is designed to automate the contact list of all the persons in our contact book.
Information for all people.
The software is creating to the needs of people using phones. With entry of various
Multinational companies, the dynamic market scenario prevailing today it is getting tougher to
sustain high performance levels consistently throughout. There is an increased we can get all the
details of the person we need on time.
This application is designed for to make the contact book as a digital device that is involved in
communication between two or more than two people. It stores all the possible addresses relating
to a person including number of addresses (like office, home, permanent) , different phones
(residence , mobiles , office phones, etc.), fax number, e-mail addresses, website addresses,
internet call addresses, etc. It also includes the names of the person, designation and company
name. Each person may be part of one or more groups like friends group , family group , official
group , etc.
The application is designed keeping in mind different levels of operations, of the contact book of
a phone. The kind of operational differences, work responsibility varies from level to level
At Level I ---- Supposedly, if a person wants to save a contact no, delete a no, edit a no.
At Level II --- He have to add the full details like his name, all numbers (residence , mobile ,
office , etc), his all addresses (office , home , permanent), fax number, e-mail addresses, website
address , internet call address , etc .
The software is designed based on usual working of a phone contact book . It is flexible in a
sense that it can be modified keeping in mind functional operations for a specific contact book.


P
a
g
e
3

Objective


The objective of this software is to completely automate the process of:


Save the new contact details.
Update the old contact details.
Delete the old contact details.
Search any contact details.
Arrange the contact details in different different groups.



P
a
g
e
4

SYSTEM ANALYSIS

I have used the Waterfall model because it suggests systematic, sequential approach to software
development that starts right form system level abd through analysis, design, coding, testing and
maintenance.

Waterfall Model
It is also called linear sequential model or classic life style.











The Waterfall Model
The Model covers the following Activities:-
System/Information Engineering and Modeling
Software is always part of a larger system; hence work begins by establishing
requirements for all system elements and then allocating some subset of the requirement
to software.

Analysis Design Code Test
Maintenance


P
a
g
e
5

Software Requirement Analysis
The requirement gathering process is intensified and focused specifically on software. To
understand the nature of program to be built the software engineer must understand
information domain for the software. As well as required function, behavior, performance
and interfacing. Requirements for both the system and the software are documented and
reviewed with the customer.

Design
Software design is actually a multistep process that focuses on four different attributes of
a program: Data Structure, Software Architecture, interface representations and
procedural details. The design process translates requirements into a representation of the
software that can be assessed for quality before code generation begins. The design is
documented and is part of the software configuration.

Code Generation
The Design must be translated into a machine readable form. The Code generation step
performs this task. All the coding is done in this step.

Testing
The Testing process focuses on the logical internals of the software, assuring that all statements
have been tested, and on functional externals thats is , conducting tests to uncover errors and
ensure that defined inputs will produce actual results that agree with required results.

Maintenance
Software will undoubtly will undergo change after it is delivered to the customer. Change will
occur because errors have been encountered, because the software must be adapted to
accommodate changes in its external environment or because the customer requires functional
or performance enhancements. Software maintenance reapplies each of the preceding phases to
an existing programme rather tan a new one.
Because of These step by step procedures, the Waterfall model is preferred. I consulted the
Waterfall model for building my application and followed the steps from beginning.


P
a
g
e
6


REQUIREMENT SPCIFICATIONS




2.1 HARDWARE REQUIREMENTS:


Processor Intel Pentium family

RAM 256 MB

Hard disc 16 GB

Operating System Windows 2000/ XP Server and above


2.2 SOFTWARE REQUIREMENTS:


Front End Java swing

Back End Oracle 10g

Languages Java using JDBC



P
a
g
e
7

System Design

The system design exercises make a high-level of the system. The system design phase provides
the understanding and the procedural details necessary for implementation the system
recommended study.

The target system is arranged into sub-system based upon the analyzed structure and proposed
architecture.
The design process translates requirement into a representation of the software that can be
accessed for the qulity before the code generation begins.
The system design decides the system parpmeters, which must optimizec, choose a strategy for
solving the problem and make tentative resource allocation.
The design phase covers the following procedure:
Review of the current physical system.
Preparation of the input specification, which include the determining of the flow of data
from the input data actual input location.
Preparation output specification

Entity-Relationship Diagram

An ER Diagram can be expressing the overall logical structure of the database
graphically.

Such a diagram of the following components:
Rectangle, which represent entity sets.
Ellipse, which represent attributes.
Diamond, which represent relationships sets.
Lines, which links attributes to entity sets to relationships sets.





P
a
g
e
8

ENTITY-RELATIONSHIP DIAGRAM

The overall logical structure of the database can be expressed graphically by an
E-R diagram.




P
a
g
e
9

DATA FLOW DIAGRAM

DFD is the important tools used by System analyst. The main merits of DFD is that it can
provides an overview of what data are don, what files are used and where the result flow. The
graphical representation of the system makes it a good communication tools between user and
analyst. DFDs are structure in such away starting from simple diagram which provides broad
overviews at glance more and details.
Source: Source and destination of data (External Entity)





As we name suggest they do not fall within system boundary. Hence the name
defined as source or destination of data.
Rounded rectangle/circles: process









Open ended Rectangle/Parallel lines:

Data store







This symbolically represents a place where data is stored. The data can be stored for
future processing it can be processed for future references. Any place where data is called data
store.


P
a
g
e
1
0

DATAFLOW CAN TAKE PLACE:-
1. Between processes
2. File to process
3. External entity
4. Process to file.


Zero Level DFD
It is first level of DFD. This shows a overview of the project in a short form. If we want
to show a detailed functions of project we can make level 1 , level 2 DFD and so on.
according to the need of Project.





P
a
g
e
1
1

Level 1 DFD
This level of DFD shows a little detailed pictorial description of the project.


P
a
g
e
1
2

Level 2 DFD
This is the last phase of dfd according to the need of this project. The level 2
DFD is as follows




P
a
g
e
1
3


PROJECT PLANNING

GANTT CHART
Gantt chart are a project control technique that can be used for sevral purpose including schedulingand
planning. Gantt chart is also known bar chart with each box representing an activity.

Tasks
Week 1 Week 2 Week 3 Week 4 Week 5 Week 6 Week 7 Week 8
Requirements Gathering
SRS Creation
Low level Design
High Level Disgin
(Interface, Data Design)

Procedural Design
Coding
Testing (Module and Integrated)
Implementation




P
a
g
e
1
4

PERT CHART
Pert stands for program evaluation and review technique. A pert chart is a network of boxes and arrows.
Starting and ending for activities.



Start Project
Day 1
Assemble Team

Preliminary
Investigation
Days 2-5


SRS Creation
Days 3-7


Design
Days 5-8


Coding
Days 7-12


Testing and
Debugging
Days 10-15



P
a
g
e
1
5

COMPLETE
CONTACT BOOK
ADD Module DELETE Module SEARCH Module UPDATE Module GROUP Module
Project Modules



P
a
g
e
1
6


Data Structure

Table 1 : Basic Details
FIELD_NAME DATA_TYPE
Id Int
Contact_name Varchar
Designation Varchar
Company_name Varchar

Table 2 : Contact Details








Table 3 : Address Details









FIELD_NAME DATA_TYPE
Id Int
Contact_name Varchar
Mobile_number Varchar
Residence_number Varchar
Office_number Varchar
FIELD_NAME DATA_TYPE
Id Int
Contact_name Varchar
Permanent_address Varchar
Residence_address Varchar
Office_address Varchar


P
a
g
e
1
7

Table 4 : Other Details
FIELD_NAME DATA_TYPE
Id Int
Contact_name Varchar
Email_id Varchar
Website_address Varchar
Fax_number Varchar


P
a
g
e
1
8

DEPENDENCIES

It doesnt matter how efficiently the application works, if the bandwidth is not
sufficient the transaction will take more time then expected.

Sql Server and Sql Server drivers for connectivity.
Java Servlets is required for the application.
Although this software is architecturally independent but following hardware
resources are required. For i.e. any IBM compatible PC or any other workstation
with.

Mouse support and relevant software.


P
a
g
e
1
9

SCOPE OF ENHANCEMENT


Presently the software is handling only two hierarchical levels. It can be further enhanced
to handle four-five hierarchical levels. The functionality for user is restricted to just
filling in contact details, it can be enhanced to be able to access other information such as
e-mail address , other numbers , etc.
It can be further enhanced to handle much wider Contacts range.
It can be further enhanced to take direct contact details.


P
a
g
e
2
0

LIMITATIONS


Presently the software is handling only two hierarchical levels.
Only able to handle restricted contacts range.

No direct access to the person other than the owner.

User should be able to access more information.