Table of Contents

Acknowledgement.......................................................................................................................2
Introduction..................................................................................................................................3
Methodology................................................................................................................................4
Objective......................................................................................................................................5
Functionalities provided by the Contact Management System are as follows:.........................................5
Scope of Contact Management System.......................................................................................6
Features of Contact management system................................................................................6
Software Requirement Specification...........................................................................................7
The proposed system has the following requirements.............................................................7
Investigation and Analysis...........................................................................................................7
Identification of need...............................................................................................................8
Feasibility Study..........................................................................................................................9
The general tasks involved in the design process..................................................................10
User Interface Design................................................................................................................11
Following steps and guidelines for user interface design......................................................11
Implementation..........................................................................................................................11
Project Planning.........................................................................................................................12
For a successful software project, the following steps can be followed:...............................12
Cost estimation..........................................................................................................................13
Hardware and Software requirements.......................................................................................14
Project Profile............................................................................................................................14
Evaluation of product................................................................................................................24
Testing of the Project.............................................................................................................24
Implementation and Software Specification testing..................................................................26
Existing system of contact management system.......................................................................29
Proposed system of contact management system......................................................................29
Critical Evaluation of project.................................................................................................30
Limitations of Contact management system..............................................................................31
Conclusion.................................................................................................................................31
References..................................................................................................................................32
Table of Figures

Figure 1 MVC architecture------------------------------------------------------------------------------13

Figure 2 Hardware and Software requirement--------------------------------------------------------15
Figure 3 data flow symbols------------------------------------------------------------------------------22
Figure 4 ERD symbols-----------------------------------------------------------------------------------22
Acknowledgement

I would like to express my special thanks of gratitude to my Lecturer ______________ who

gave me this golden opportunity to complete this wonderful project that is based on Contact
Management System.

My special thanks to all who helped me complete this project, by doing this I came to know
about so many new things that I came to know about and I am really thankful to them

Secondly I would like to thank my parents and friends who has helped me a lot in finalizing
this project within the limited time frame

I acknowledge with thanks with the kind of patronage, loving inspiration and timely guidance
that I have received from my lecturer _____________ my family members and my friends,
with whose guidance, encouragement, suggestion and very constructed criticism has
contributed immensely to the evolution of my ideas carried towards the project.
Introduction

This certain project referred to as the Contact Management System is written in PHP, it's
considered as a straightforward project that's very easy to know and use. As i discussed about
the system, it contains all the desired functions that has adding, viewing, deleting and updating
contact lists. Therefore while adding the contacts of an individual, he or she should provide
name, last name, gender, address and other contact details. The user can even update the
contact list if he or she wants to. The system shows the contact details during a list view. And
also the user can easily delete any contact details.

This following project contact management system provides the best management of contact
details. it's been developed to override the issues prevailing within the system, thus it's
supported to eliminate in some cases to scale back the hardships that's been faced by this
existing system. Therefore it's designed for the actual need of the corporate so as to hold out
operations in an exceedingly smooth and effective manner. This application is reduced the
maximum amount as possible to avoid errors while entering the information. It also provides a
mistake message while entering invalid data. No formal knowledge is required for the user to
use this technique. Thus by this, all it proves its user friendly.

This contact management system can cause error free, secure, reliable and fast management
system. It can assist the user to focus on their other activities rather to focus on the record
keeping. Thus it'll help the subsequent organization within the better utilization of resources.
They need challenges they need to beat by managing information of each contact details
because every contact management system has different contact needs. Thus, it's designed to
help in strategic planning, which can help make sure that the organization is supplied with the
proper level of knowledge and details for your future goals, and it'll ultimately allow to
manage better resources
Literature review

Its main principle is to effectively retrieve and implement any information that a corporation
may wear a pre-existing customer. Therefore all the data associated with a selected customer
may be linked and archived only to be retrieved later. after they are required most, what
should be more noteworthy is that the incontrovertible fact that all of this may be arranged
over every single terminal and at an inexpensive cost. By the utilization of it, it can cater to the
wants of the customer better. It ensures that the method of contact management becomes more
efficient, profitable and cost-effective. Much of our daily communication actively involves
managing interpersonal communications and relationships. It confirms the importance of
contact management by revealing the issue of choosing important contacts from the massive
set of individuals with whom one communicates. Contact management is clearly complex
because the most important problem is that individuals are exposed to an unmanageable
number of potential contacts. this can be exacerbated by widespread use of distribution lists,
so it might be both onerous and unnecessary to store detailed information about of these
contacts.

Methodology
The first and also the most prominent step of building a contact management system is to
interact directly with the customer who is seeking an answer to his or her problem through the
merchandise or service the corporate is providing. Therefore it may be initiated by
implementing one in all the subsequent ways. They’re as follows:

 By asking the customer directly about the services the company promotes or
advertises.
 Regarding the possibilities of using internal or external references
 You can create estimates by conducting online surveys
 Starting a cold call is like calling a specific person to ask if the company is interested
in an initial project.

It is time to move forward with a strong recommendation to understand the breadth of

knowledge of regular interaction with customers. Ensures the customer that the company can
pay special attention to providing value-added benefits. Through direct communication with
the customer, the customer can directly meet the needs of the customer through the
conversation of their esteemed customers. All the necessary information can be stored in a
more powerful way in the central database. Through this method a company reaches more
customers. However, by collecting customer feedback regularly, they are able to highlight
their services so that the company pays special attention to customer preferences that connect
their products to customer needs.

Objective
The main purpose of this contact management system is to manage contact, credentials, and telephone, profile
and email details. It manages all information about contacts, mobiles and emails. The project is built entirely at
the administrative end, so access is only guaranteed to the administrator. The goal of this system is to create an
application program that minimizes the manual task of managing all resources while tracking all information.
Functionalities provided by the Contact Management System are as follows:

 Provides search features based on various factors such as contact, telephone, profile and email.
 The telecommunication management system manages all telephone details, including online and
email details for profile details.
 It tracks all the information like Credit Credentials, Mobile, and Profile etc.
 Maintain reliable information
 Contact Displays contact details and explanations
 It manages profile information and transaction monitoring
 Maintains contact information
 Improved the editing, insertion and updating of records that lead to optimal resource management of
contact data
 Profile Managing the profile information
 Email integration of all records of email

Scope of Contact Management System

This may help to gather better management in the details. In a very short time, the collection
will be clear, simple and correct. It helps a person to fully and clearly understand what has
been going on in the past year. It also supports current work related to the following system.
Cost collection is minimized through maintenance and collection procedures

Therefore, the main objectives of the contact management system are:

  In the computer system, the person has to fill the various forms and number of copies
of the forms that can be easily generated overtime

 The manifest does not need to be created, but we can print it directly, which saves us
time
 Assist officers to capture work spent in work-related areas
 Increase resource productivity and efficient utilization through resource automation
utility
 The system generates information that can be used for a variety of purposes
 It satisfies the consumer demand
 And the user and operator are easy to understand
 Opera is easy to operate
 The user has a good user interface
 Expand as expandable
 Distributed on a scheduled budget

Features of Contact management system

 Based on product and component
 Problems easily create and change problems
 Explore the problem list in depth at any depth
 Comprehensive reporting and charting
 User accounts to manage access by maintaining security
 Status Normal level and resolution
 Multi-level preferences and intensity
 Programs are goals and milestones that guide programmers
 Info attachments and additional comments for more information
 Database Strong database back end
 Filter Multiple level reports are available with multiple filter criteria
 It has excellent storage capacity
 Accuracy in work
 Retrieve information easily and quickly
  Well-crafted reports
 In the current manual system the man reduces the burden on the person involved
 Information is personal access to any information
 Work becomes very speedy
 Easy to update information

Software Requirement Specification

Software work attribute analysis is built at the end of the work. Modifies software
performance and performance as part of system engineering by establishing a complete
information description, detailed functional and behavioral description, indication of
performance requirements and design limitations, appropriate evaluation criteria and other
relevant data.
The proposed system has the following requirements

 The system should store information about new access to new contacts
 The system requires internal staff to store sensitive credential information and identify
it according to various queries.
 The system is required to maintain a system size record
 The system is required to maintain the record system of the telephone
 The system must be updated and removed
 The system requires a search area
 It requires a security system to block data

Investigation and Analysis

It is the process of collecting, describing, diagnosing and consulting information about the
contact management system to recommend system improvements. This is a troubleshooting
activity that requires serious communication between system users and system developers.
The use of system analysis or practice is considered an important step in any system
development process. The system studies and analyzes to the smallest detail. The System
Analyzer plays the role of an interrogator and provides an in-depth understanding of system
performance. View the entire system and locate the input to the system. The results from the
companies can be known through various processes. System Analysis Awareness of problem,
identifies relevant and decisive variables, analyzes and integrates different components and
determines appropriate or less satisfactory solution or action plan. The process should be
studied in detail through various methods such as interviews and questionnaires. The data
collected from these sources should be examined to come to a conclusion. The end is to
understand how the system works. The system is called the current system. The current system
will be subject to further study to identify problem areas. The designer is now working on the
problem solver and trying to solve the problems the company is facing. Solutions are provided
as hints. It weighs the existing system analytically and selects the best one. Therefore,
preliminary study is the process of gathering and explaining facts using information for further
study of the system. This is called troubleshooting, which requires intense communication
between system users and system developers. It conducts various feasibility studies. These
studies provide an approximate estimate of system performance, from which decisions can be
made about strategies to be followed for effective system study and analysis.
Identification of need
The old manual system is plagued with many errors. Since the entire system has to be
maintained, storing, maintaining and retrieving information can be very laborious and lengthy.
Documents were never used in systematic order. There are many difficulties in associating any
particular transaction with a particular context. If you want to find any information, you have
to go through different registers where there is nothing like Records Report Generation. There
is always unnecessary time for giving and retrieving records. Another problem is that it is
difficult to detect errors when providing records. It is very difficult to update these records
after the records have been entered.

The reason behind this is that a lot of information needs to be maintained and remembered
while doing business. For this reason it gives us features. The current system is partially
automated (computerized). The current system is very labor intensive as the same system has
to be provided in three different locations

Following points should be well considered:

 System documents and reports required for the new system.

  There may be some reports that help management in decision making and cost control,
but these reports are not qualified, and such reports and information have been
identified and given due attention.
 Document Details of information required for each document and report
 Document requires frequency and distribution for each file

 Document Information sources for each document and report

 Implementing a computerized system solves the task of keeping records organized.
 The best way to retrieve information is by mouse click.
 Therefore, the proposed system will save time for various activities and make it easier
to provide information by providing valuable reports.

Feasibility Study

After setting up the system contact management system and studying and analyzing all the
current or required functions of the system, the next task is to make a feasible study for this
system. All projects are practical - given unlimited resources and infinite time

Possible study examines all the ways to solve a given problem. The proposed solution should
meet all customer needs and be flexible so that future changes can be easily made depending
on future needs.

Financial feasibility - This is a very important factor when developing a project. We

determined the technology based on the lowest cost factor possible

 Hardware All hardware and software costs are borne by the company
 Overall, we anticipate that the benefits to the organization from the proposed system
will outweigh the initial costs and maintenance costs of the next system.

Technical feasibility - This involves the study of performance, performance, and limitations
that affect the ability to achieve an acceptable system. For this feasibility study, we studied the
full functionality of the system as described in the System Requirements specification and
tested whether everything is possible using different types of front end and backend palmists.
Functionality - There is no doubt that the specific system is user friendly and all inputs should
be self-explanatory even to the average person. In addition, users are properly trained to
communicate the essence of the system so that they feel comfortable in the new system. In our
study, clients lost their weight and were more comfortable and happy as they worked.

Design

At this stage, a logical system is constructed to meet the given requirements. The design phase
of software development is to transform the client's needs into a logical working system.
Generally, it is designed in two stages:

Basic design phase

At this point, the system is designed at the block level. Blocks are created based on
analysis performed during the problem identification phase. Different blocks can be
created for different functions, providing them to reduce the flow of information
between blocks. Therefore, all activities that require further intervention are stored in a
single block
Secondary design phase
The second step is the detailed design of each block. The general tasks involved in the
design process

 The system designs different blocks for the entire system processes

 Create small, compact and functional modules in each block

 Database Create different database structures

 Specify the details of the programs to achieve the desired function

 Generate the shape of the input and system outputs

 Perform design documentation

 System reviews

User Interface Design

User interface design is concerned with the dialog between a user and the computer. It is
concerned with everything from starting the system or logging in to it. Eventually by
presenting the desired inputs and outputs. The overall flow of screens and messages is called a
dialog.

Following steps and guidelines for user interface design

 The system user should always be aware of what to do next
 The screen should be formatted so that various types of information, instructions and
messages always appear in the same general display area.
 Messages, instructions or information should be displayed long enough to allow the
system user to read them.
 Use display attributes sparingly.
 Default values for fields and answers to be entered by the user should be specified.
 A user should not be allowed to proceed without correcting an error.
 The system user should never get an operating system message or fatal error.
Implementation
Model view controller or MVC as it is popularly called is a software design pattern for
developing web applications. A model view controller pattern is made up of the following
three parts.

 Model – The lowest level of the pattern which is responsible for maintaining data.
 View – This is responsible for displaying all or a portion of the data to the user.
 Controller – Software code that controls the interactions between the model and view.

MVC is popular as it isolates the application logic from the user interface layer and supports
separation of concerns. Here the controller receives all requests for the application and then
works with the Model to prepare any data needed by the view. The view then uses the data
prepared by the controller to generate a final presentable response. The MVC abstraction can
be graphically represented as follows:

MVC architecture

Figure 1 MVC architecture

Project Planning
Software project plan can be viewed as the following:
  Within the organization – how the project is to be implemented? What are the
various constraints (time, cost, and staff)? What is market strategy?
 With respect to the customer – weekly or timely meetings with the customer with
presentation on status reports. Customers feedback is also taken and further
modification and developments are done. Project milestones and deliverables are also
presented to the customer

For a successful software project, the following steps can be followed:

 Select a project
o Identifying project’s aims and objectives
o Understanding requirements and specification
o Methods of analysis, design and implementation
o Testing techniques
o Documentation
 Project milestones and deliverables
 Budget allocation
o Exceeding limits within control
 Project estimates
o Cost
o Time
o Size of code
o Duration
 Resource Allocation
o Hardware
o Software
o Previous relevant project information
o Digital library
 Risk management
o Risk avoidance
o Risk detection
Cost estimation
Software cost comprises a small percentage of overall computer-based system cost. There are
a number of factors, which are considered and can affect the ultimate cost of the software such
as human technical, hardware and software availability etc.

The main point that was considered during the cost estimation of this system was its sizing. In
spite of complete software sizing, function point and approximate lines of code were also used
to size each element of the software and their costing

The cost estimation done by me for this project also depend upon the baseline metrics
collected from past projects and these were used in conjunction with estimation variables to
develop cost and effort projections

We have basically estimated this project mainly on two bases –

 Effort estimation – this refers to the total man-hours required for the development of
the project. It even includes the time required for doing documentation and user
manual
 Hardware required estimation – this includes the cost of the PC’s and the hardware
cost required for the development of this project

Hardware and Software requirements

Software requirements

Name of component Specification

Operating System Windows 7, 8 and 10
Language PHP
Database Xampp
Browser Mozilla Firefox, Chrome etc
Web server Tomcat 7

Hardware requirements

Name of component Specification

Processor Pentium IV 630MHz
RAM 128 MB
Hard disk 20 GB
Monitor 15” color monitor
 Keyboard 122 keys
Figure 2 Hardware and Software requirement

Project Profile
There has been continuous effort to develop tools, which can ease the process of software
development. But, with the evolving trend of different programming paradigms today’s
software developers are really challenged to deal with the changing technology. Among other
issues, software re-engineering is being regarded as an important process in the software
development industry. One of the major tasks here is to understand software systems that are
already developed and to transform them to a different software environment. Generally, this
requires a lot of manual effort in going through a program that might have been developed by
another programmer. This project makes a novel attempt to address the issue of program
analysis and generation of diagrams which can depict the structure for software engineering
design process. It provides several diagramming tools that can express different
aspects/characteristics of program such as:
 Use cases – elicit requirements from users in meaningful chunks. Construction
planning is built around delivering some use cases for each interaction basis for system
testing
 Class diagrams – shows static structure of concepts, types and class. Concepts how
users think about the world, type shows interfaces of software components whereas
classes shows implementation of software components
 Interaction diagrams – shows how several objects collaborate in single use case
 Package diagram – shows group of classes and dependencies among them
 State diagram – shows how single objects behaves across many use cases
 Activity diagram - shows behavior with control structure. Can show many objects
over many uses, many objects in single use case, or implementations methods
encourage parallel behavior etc.

The end-product of this project is a comprehensive tool that can parse any program and extract
most of the object oriented features inherent in the program such as polymorphism,
inheritance, encapsulation and abstraction

What is UML?
UML stands for Unified Modeling Language, it is considered as the successor to the wave of
object oriented analysis and design methods that appeared in the late 80’s. The UML is called
a modeling language, not a method. Most methods consist at least in principle of both a
modeling language and a process. The modeling language is that notation that is used for
methods is used to express design

Notations and meta-models

The notation is the graphical stuff, it is the syntax of the modeling language. For instance,
class diagram notation defines how items are concepts such as class, association and
multiplicity is represented. These are:

Class diagram – the class diagram technique has become truly central within object-oriented
methods. Virtually every method has included some variation on this technique. Class diagram
is also subject to the greatest range of modeling concept. Although the basic elements are
needed by everyone, advanced concepts are used less often. A class diagram describes the
types of objects in the system and the various kinds of static relationship that exist among
them. There are two principle kinds of static relationship

 Association
 Subtype

Class diagram also shows the attributes and operations of a class and the constraints that apply
to the way objects are connected

 Association – it represents between instances of class. From the conceptual

perspective association represents conceptual relations between classes. Each
association has two roles. Each role is a direction on the association. A role also has
multiplicity, which is a indication of how many objects may participate in the given
relationship
 Generalization – a typical example of generalization evolves the personal and
corporate customer of a business. They have differences but also many similarities.
The similarities can be placed in generalization with personal customer and corporate
customer sub type
  Aggregation – aggregation is the part of relationship. It is like saying a car has engine
and wheels as its parts. This sounds good, but difficult thing is to consider and that is
the main difference between aggregation and association
 Interaction – these diagrams are models that describes how group of objects
collaboration in some behavior. Typically it captures the behavior in a single use case.
It shows a number of example objects and messages that are passed between these
objects in use cases. There are following approaches with simple use case that exhibits
the following behavior. Objects can send a message to another. Each message is
checks with given item.
 Package diagram – one of the oldest questions in software methods is how do you
break down a large system into smaller systems. It becomes difficult to understand to
the changes we make to them.

Structured methods uses functional decomposition in which the overall system was mapped as
a function broken down into sub function, as it is further broken down into sub function and so
forth. The separation of process data is gone as well as the functional decomposition is gone,
but the old question still remains. One idea is to group the classes together into higher-level
unit, as it is applied very loosely, it appears in many objects. In UML, this grouping
mechanism is package. The term package diagram is a diagram that shows packages of classes
and the dependencies among them. Therefore a dependency exists between two elements as it
changes the definition to one element that may cause to another. With classes, dependencies
exist for various reasons. For example one class sends a message to another, whereas another
class has another part of its data, another mentions another as a parameter to an operation. A
dependency between two packages exists and other dependencies exist between any two
classes in the package.

State diagram – this is a familiar technique to describe the behavior of a system. They
describe all the possible states, a particular object that can get into and how the objects state
changes as a result of events that reach the objects.in most techniques, state diagrams are
drawn for a single class to show the lifetime behavior of a single object. They are many forms
of state diagrams, each with slightly different semantics.

Use Case Model

The use case model for any system consists of use cases. As it represents different ways in
which the system can be used by the user. A simple way to find all the use case of a system is
to ask the questions “What the user can do by using the system?” The use cases partitions the
system behavior into transactions such that each transaction performs some useful action from
the user’s point of view.

The purpose of the use case is to define a piece of coherent behavior without revealing the
internal structure of the system. It typically represents a sequence of interaction between the
user and the system. These interactions consists of one main line sequence that represents the
normal interaction between the user and the system. It is an important analysis and design
artifact. Whereas use cases can be represented by drawing a use case diagram and writing an
accompany text elaborating the drawing

In the use case diagram, each use case is represented by an ellipse with the name of the use
case that is written inside the ellipse. All the ellipses of the system are enclosed within a
rectangle which represents the system boundary. The name of the system being molded
appears inside the rectangle. The different users of the system are represented by using the
stick person icon. The stick person icon is normally referred to as an actor. The line
connecting the actor and the use cases is called the communication relationship. When a stick
person icon represents an external system it is annotated by the stereo type “external system”

Dataflow diagram

Data flow diagram is the starting point of the design phase that functionally decomposes the
requirement specification. A DFD consists of a series of bubbles joined by lines. The bubbles
represent data transformation and the lines represent data flows in the system. A DFD
describes what data flow or rather how they are processed so does the hardware, software and
data structure. A data flow diagram is a graphical representation of the flow of data through an
information system. DFD’s can also be used for the visualization of data processing. A data
flow diagram is a significant modeling technique for analyzing and constructing information
processes. DFD literally means an illustration that explains the course or movement of
information in a process. DFD illustrates this flow of information in a process based on the
inputs and outputs. A DFD can be referred to as a process model. Unlike details flow chart,
DFD’s don’t supply the detail descriptions of modules that graphically describe a system’s
data and how the data interact with the system

There are seven rules to construct a data flow diagram

 Arrows should not cross each other

 Squares, circles and files must wear names
 Decomposed data flows must be balanced
 No two data flows, squares or circles can be the same names
 Draw all data flows around the outside of the diagram
 Choose meaningful name for data flows, processes and data stores
 Control information such as record units, password and validation requirements are not
penitent to a data flow diagram

Additionally, a DFD can be utilized to visualize data processing or a structured design.

Therefore a DFD can be disintegrated to a lower level diagram demonstrating smaller steps
exhibiting details of the system that is being modeled. On a DFD, data items flows from an
external data source or an internal data store to an internal data store via the internal process. It
is a common practice to draw a context level data flow diagram, which shows the interaction
between the system and external agents. On the context diagram, the systems interactions with
the outside world are modeled purely in terms of data flows across the system boundary. It
shows the entire system as a single process, but gives no clues as to its internal organization.
This context level DFD is exploded to produce a Level 1 DFD that shows some of the details
of the system being modeled. The level 1 DFD shows how the system is divided into sub
systems. And where each one of it deals with one or more of the data flows that together
provides all of the system functionality as a whole. The level 1 DFD is further spreaded and
split into more descriptive and detailed description about the project as level 2 DFD. The level
2 DFD can be a number of data flows that will finally show the entire description of the
software project.

Entity Relationship Diagram

The ER model is a popular high level conceptual data model. This model and its variations are
frequently used for the conceptual design of database application and many database design
tools may employ its concept. A database confirms that an ER diagram can be represented by
a collection of tables in the relational system. The mapping of the ER diagram to the entities
are

 Attributes
 Relations
o Many to Many
o Many to one
o One to many
o One to one
 Weak entities
 Sub type and super type

The entities and their relationships between them are shown using the following conventions

 An entity is shown in a rectangle

 A diamond represents the relationship among number of entities
 The attributes shown as ovals are connected to the entities or relationships by lines
 Diamond, oval and relationships are labeled
 Model is an abstraction process that hides super details while highlighting details
related to application at end
 A data model is a mechanism that provides this abstraction for database application
 Data modeling is used for representing entities and their relationship in the database
 Entities are the basic units used in modeling database entities that can have concrete
existence or constitute ideas or concepts
 Entity type or entity set is a group of similar objects that concerns an organization in
which it is possible to maintain data
 Properties are characteristics of an entity known as attributes
 A key is a single attribute or combination of 2 or more attributes of an entity that is
used to identify one or more instance of the set
 In relational model we represent the entity by relating and using tuples to represent an
instance of the entity
  Relationship is used in data modeling to represent association between an entity set
 An association between two attributes indicates that the value of the associated
attributes are independent

DFD and ERD diagram symbols

DFD symbols

Figure 3 data flow symbols

ERD symbols

Figure 4 ERD symbols

Diagrams
Screenshots of system
Evaluation of product
The first step in the system development life cycle is the preliminary investigation to
determine the feasibility of the system. The purpose of the preliminary investigation is to
evaluate project requests. It is not a design study nor does it include the collection of details to
describe the business system in all respect. Rather, it is the collection of information that helps
committee members to evaluate the merits of the project request by making an informed
judgement about the feasibility of the proposed project

Testing of the Project

Testing is vital for the success of any software, no system design is ever perfect. Testing is
also carried in two phases, the first phase is during the software engineering that is during the
module creation, second phase is after the completion of software, this system testing verifies
the whole set of programs handed together

White box testing

In this technique, the close examination of the logical parts through the software are tested by
cases that exercise species based on sets of conditions or loops. All logical parts of the
software are checked once. Errors can be corrected using this technique are considered as
typographical errors. Logical expressions should be executed once as they may get executed
more than once as error results by using wrong controls and loops. Within the box testing tests
all independent parts within a module based on logical decisions that are true and false are
executed. All loops and bounds within their operational bounds are exercised and internal data
structure is ensured that the validity is exercised once.

Black Box Testing

This method enables the user to set and input techniques that fully exercise all functional
requirements for a program. Black box testing tests the input, the output and the external data.
It checks whether the input data is correct and whether they are getting the desired output
Alpha Testing

Acceptance testing is also sometimes called alpha testing. Systems are developed for a single
customer. The alpha testing proceeds until the system developer and the customer agree that
the provided system is an acceptable implementation of the system requirements

Beta Testing

On the other hand, when a system is to be marked as a software product, another process
called beta testing is often conducted. During beta testing, a system is delivered among a
number of potential users who agree to use it. The customers then report problems to the
developers. This provides the product for real use and detects errors that may have not been
anticipated by the system developers

Unit Testing

Each module is considered independently. It focuses on each unit of software as implemented

in the source code. This is known as white box testing

Integration Testing

Integration testing aims at constructing the program structure while at the same constructing
tests to uncover errors associated with interacting the modules. Modules are integrated by
using the top down approach

Validation testing

Validation testing was performed to ensure that all the functional and performance
requirements are met

System testing

It is executing programs to check logical changes made in it with intention of finding errors.
The system is tested for online responses, volume of transaction, recovery from failure etc.
system testing is done to ensure that the system satisfies all the user requirements.
Implementation and Software Specification testing

This phase of the systems development life cycle refines hardware and software specifications
establishes programming plans, trains users and implements extensive testing procedures, to
evaluate design and operating specifications by providing the basis for further modification

Technical design

This activity builds upon specifications produced during new system design, adding detailed
technical specifications and documentation

Test specifications and planning

This activity prepares detailed test specifications for individual modules and programs, job
streams, subsystems and for the system as a whole

Programming and testing

This activity encompasses actual development, writing and testing of program units or
modules

User training

This activity encompasses writing user procedure manuals, preparation of user training
materials, conducting training programs and testing procedures

Acceptance testing

A final procedural review to demonstrate a system and secure user approval before a system
becomes operational

Installation Phase

In this phase, the new system is installed as the conversion to new procedures is fully
implemented and the potential of the new system is explored

System installation

The process of starting the actual use of a system and training user personnel in its operation
Review phase

This phase evaluates the successes and failures during a systems development project and to
measure the results of a new system in terms of benefits and savings projected at the start of
the project

Development recap

A review of a project immediately after completion to find successes and potential problems in
the future

Post implementation review

A review conducted after a new system has been in operation for some time, to evaluate actual
system performance against original expectations and projections for cost-benefit
improvements. Also identifies maintenance projects to enhance or improve the system

The steps in software testing

The steps involved during unit testing are as follows:

 Preparation of test cases

 Preparation of the possible test data with all the validation checks
 Complete code review of the module
 Actual testing done manually
 Modifications done for the errors found during testing
 Prepared the test result scripts

The unit testing done included the testing of the following items

 Functionality of the entire module/forms

 Validations for user input
 Checking of the coding standards to be maintained during coding
 Testing the module with all the possible test data
 Testing of the functionality involving all type of calculations etc.
 Commenting standards in the source files
After completing the unit testing of all the modules, the whole system is integrated with all its
dependencies in that module. With system integration, they have integrated the modules one
by one and tested the system at each step. This has helped in reduction of errors at the time of
the system testing.

The steps involved during system testing are as follows:

 Integration of all the modules in the system

 Preparation of test cases
 Preparation of the possible test data with all the validation checks
 Actual testing done manually
 Recording of all the reproduced errors
 Modifications done for the errors found during testing
 Prepared the test result scripts after rectification of the errors

The system testing done included the testing of the following items:

 Functionality of the entire system as a whole

 User interface of the system
 Testing the dependent modules together with all the possible test data scripts
 Verification and validation testing
 Testing the reports with all its functionality

After the completion of system testing, the next following phase was the acceptance testing.
Clients at their end have accepted the system with appreciation. Thus, we reached the final
phase of the project delivery

There are other six tests, which fall under special category are described below:

 Peak load test – it determines whether the system can handle the volume of activities
that occur when the system is at the peak of its processing demand. For example by
testing the system by activating all terminals at the same time
 Storage testing – it determines the capacity of the system to store transaction data on a
disk or in some other file
  Performance time testing – it determines the length of time system used by the
system to process transaction data. This test is conducted prior to implementation to
determine how long it takes to get a response to an inquiry, make a backup copy of a
file or send a transmission by getting a response
 Recovery testing – this testing determines the ability of user to recover data or restart
system after failure. For example load backup copy of data and resume processing
without data or integrity loss
 Procedure testing – it determines the clarity of documentation on operation and uses
of system by having users do exactly what manual requests for example powering
down system at the end of the week
 Human factors testing – it determines how users will use the system when processing
data or preparing reports

Existing system of contact management system

In the existing system the system is done manually but in proposed system we have to
computerize the exams using this application

 Lack of security in data

 More manpower
 Time consuming
 Consumes large volume of spare work
 Needs manual calculations
 No direct role for higher officials

Proposed system of contact management system

The aim of this proposed system is to develop a system that consists of improved facilities.
The proposed system can overcome all the limitations of the existing system. The system
provides proper security and reduces the manual work

 Security of data
 Ensures data’s accuracy
 Proper control of the higher officials
 Minimize manual data entry
  Minimum time needed for the various processing
 Greater efficiency
 Better service
 User friendliness and interactive

Critical Evaluation of project

Ina a nutshell, it can be summarized so that the future scope of the project circles around when
it comes to maintaining information that mainly regards on the following points:

 We can add a printer in future

 By giving more advance software for contact management system includes more
facilities
 By hosting the platform to make it accessible online
 Integrate multiple load balancers to distribute the loads of the system
 Creating the database structure to reduce the overload of the database queries
 Implementing the backup mechanism for taking backup of code and database

The above mentioned points are the enhancements which can be done to increase the
applicability and usage of this project. By maintaining the records of contact managing
system, it can be seen that they are versatile so that means that there is a scope for introducing
a method to maintain the contact management system. Therefore enhancements can be done to
maintain all contact details

We have left all the options open so that if there is any other future requirement in the system
by the user it could enhance the system so it is possible to implement them. Finally I would
like to thank all the persons involved in the development of the system directly or indirectly
and we hope that the project will serve its purpose to which it can develop by underlying
success of process
Limitations of Contact management system

Although I have put my best effort to make the software flexible, it is easy to operate but
limitations cannot be ruled out even by me. Though the software presents a broad range of
options to its users some intricate options that could not be covered into it. Partly because of
logistic and partly due to lack of sophistication. Paucity of time was also a major constraint,
thus it was not possible to make the software foolproof and dynamic. Lack of time also
compelled me to ignore some part such as storing old result of the candidate etc. Considerable
efforts have been made to make the software easy to operate even for the people that are not
related to the field of computers but it has been acknowledged that it could be a little
problematic at the first instance. Therefore the user is provides help at each step based for their
convenience when it comes to working with the software

Conclusion
Our project is only a humble venture to satisfy the needs that is needed to manage the project
work. Thus it proves to be a powerful package in satisfying all the requirements. The main
objective is to provide a framework that enables them to make reasonable estimates that could
be created within a limited time frame that could occur at the beginning of the software and
could be updated regularly as the project progresses
At the end it is concluded that we have made the following efforts based on the specific
points:
 A description of the background and context of the project as it is related to work done
in the area
 Making the statement that consists of the aims and objectives of the project
 The description of purpose, scope and applicability
 By defining the problem while working on the project
 Describing the requirement specifications of the system and the actions that can be
done on these things
 To understand the problem domain and by producing a model of the system that
describes operations that can be performed on the system
 Designing user interface and security issues related to system
  Finally the system is implemented and tested according to test cases

References

Scribd. 2020. Contact Management System | Databases | Software Testing. [ONLINE]

Available at: https://www.scribd.com/document/379538942/Contact-Management-System.
[Accessed 31 October 2020].