CONTENTS OF SYNOPSIS

SL N0 TOPIC
PAGE NO

1. TITLE OF THE PROJECT

2. INTRODUCTION & OBJECTIVES
3. DFD’S
4. MODULES OF PROJECTS
5. DATA STRUCTURE(TABLES)
6. PROCESS LOGIC
7. TOOLS PALTEFORM USED
8. REQUIREMENT SPECIFICATION
9. SECURITY MECHANISM
10. CONCLUSION
11. FUTURE SCOPE & ENHANCEMENT
 TITLE OF PROJECT

Customer relationship
management
 Introduction of C.R.M.
Customer relationship management is a broadly recognized, widely-
implemented strategy for managing and nurturing a company’s
interactions with customers and sales prospects. It involves using
technology to organize, automate, and synchronize business processes—
principally sales related activities, but also those for marketing,
customer service, and technical support. The overall goals are to find,
attract, and win new customers, nurture and retain those the company
already has, entice former customers back into the fold, and reduce the
costs of marketing and customer service.

Product to customer’s satisfaction.

Earlier, there was no automated process to organize the series of activities that
take place. The customer has to wait for a long time to be entertained by an executive. An
executive could not differentiate which customer to entertain first. There was no
procedure to monitor the efficiency of the workers. Long queue used to exist, just for
getting the invoice. There was no process which could recheck the work that has been
done for a particular Product (when required, the official would browse through all the
slips and related documents. This was error-prone and time consuming).
Despite of heavy investment and all modern facilities, the company faced decline in sales
and profits.

PROJECT CATEGORY

CRM (customer support) is being made as web-application

DFD

The Data flow Diagram shows the flow of data. It is generally

made of symbols given below:-

A square shows the Entity.

A Circle shows the Process

An open Ended Rectangle shows the data store.

An arrow shows the data flow.

The DFD can be up to several levels. The 0 level DFD states the
flow of data in the system as seen from the outward in each
module.

The first level DFD show more detail, about the single process of 0
levels DFD
Table Structures of CRM
ER-Diagram of CRM
 MODULES AND THEIR DESCRIPTION

• Customer Module - Function of this module is to firstly registered the

customer and send customer Query.

• Employee Module -The function of the Employee Module is to show all

kinds of information related to the employee. This module will also View the
customer query.

• Operational Module – This module View the customer query. Add, Update,
Delete The schema. Mail to the Customer.

• Administrator and Security Module—Security shall be implemented

to control access to functions and processes within the sub-systems as well
as by assigning individual table access rights to each employees. This would
ensure full control over the updating or extraction of information within the
customer care web application. The default access for all employees at all
times will be “read only”. When a employees runs a specific process the
tables updated by that process shall be “opened” for the duration of the
session only. The reason is that with open database connectivity employees
can access the database using spreadsheets, internet tools etc. which may
lead to inadvertent change of the data. The access rights to specific tables
must be altered in a controlled way by the process that updates these tables
and re-set to read only at the end of the process.
 Process Logic

• In a Web Application Customer can use it in a two ways firstly if customer want to
use to find out the some customer care service center in a particular location and
the other if customer send the query. Then this process firstly creates a
registration account in a web application and then all officially employees of
service center provide service in a proper way.

• Employee is to show all kinds of information related to the employee. This

module will also View the customer query.

• Admin control all actions in this customer care web application and responsible
for the service of customer products

.
 Design Pattern:

This software based on concept of the Model View Controller (MVC) design
pattern.

View renders the data from the Model in response to the request made to the
model by controlled events made by user interaction.

Model View Controller is a design approach to separate the application object

model from GUI, originally invented around 80s. Then later on it has become a
widely accepted common design pattern. The main objective behind this pattern
is to decouple the view of the data (presentation layer) from the actual data
processing so that the same model can be used for various views. This is
achieved by using three different types of objects that interact with each other in
loosely coupled manner with their discreet set of tasks.

These three objects are known as Model, View and Controller.

VIEW:

View is the graphical data presentation (outputting) irrespective of the real data
processing. View is the responsible for look and feel, some custom formatting,
sorting etc. View is completely isolated from actual complex data operations. For
example, online product catalog view is completely separated from database
connection, query, tables etc. It simply gets final row-data from the model and
puts some cosmetics and formatting before displaying it in browser. View
provides interface to interact with the system. The beauty of MVC approach is
that it supports any kind of view, which is challenging in today’s distributed and
Multi-platform environment. A MVC model can have multiple views, which are
controlled by controller. View interface can be of WEB-FORMS, HTML, XML/XSLT,
XTML, and WML or can be Windows forms etc.

MODEL:

Model is responsible for actual data processing, like database connection, querying
database, implementing business rules etc. It feeds data to the view without worrying
about the actual formatting and look and feel. Data provided by Model is display-neutral
so it can be interfaced with as many views without code redundancy; this eases your
code maintenance and reduces bugs and allows code -reuse at good extent. Model
responds to the request made by controllers and notifies the registered views to update
their display with new data.
CONTROLLER:

Controller is responsible for Notice of action. Controller responds to the mouse or

keyboard input to command model and view to change. Controllers are
associated with views. User interaction triggers the events to change the model,
which in turn calls some methods of model to update its state to notify other
registered views to refresh their display.

Benefits:

Following are the few of the benefits of MVC design pattern..

• Since MVC handles the multiple views using the same enterprise model it
is easier to maintain, test and upgrade the multiple system.
• It will be easier to add new clients just by adding their views and
controllers.
• Since the Model is completely decoupled from view it allows lot of
flexibilities to design and implement the model considering reusability and
modularity. This model also can be extended for further distributed
application.
• It is possible to have development process in parallel for model, view and
controller.
 SECURITY MECHANISM

In the software security there are two levels of security. The 1st level of
security, which is provided by the FRONT END and 2nd level of security
provided by the database which is being used.

FRONT END SECURITY:-

This security level is developed or designed by the s/w developer or
designer. S/he provides her/his s/w the security for the system, by
considering many factors regarding to the particular s/w.
In this software following are used to provide security.

LOGIN CHECKING:
There are two login’s are provided in this software
one for employees and one for applicants. In order to avail the services of
software employees have to provide a valid id and password and only after
entering correct id and password employee will get entry otherwise they will
be blocked from accessing any services of this site. Similarly a login check is
provided for user applying for job. In order to enter recruitment zone user
have to enter id and password which they got after registration , in this way
security have been provided for both employee section and applicant section.
There is also provision to change the password in case password is known by
other.

BACK END SECURITY:-

In this particular software our back end used is SQL server 2000. So all
the inbuilt security aspects provided by the SQL server 2000 database is
used as it is. It will provide the strong feature of security so that it will be
difficult to change, modify any personal or university data. Information is vital
to success, but when damaged or in the wrong hands, it can threaten
success. SQL server 2000 provides extensive security features to safe guard
your information from both unauthorized viewing and intentional or
inadvertent damage. This security is provided by granting or revoking
privileges on a person- by- person and privilege-by-privilege basis. There are
six ways by which security regarding to the database can be provided. They
are as follows-
CREATE USER , DELETE USER , MODIFY USER
 TOOLS/PLATFORM USED:

Front End Active Server Pages (ASP.Net)

• User friendly
• GUI
• Separation of work
(designing & coding)
• Written once run anywhere
Middle-Tier

• Asp.Net APIs

Back End Sql-Server

• Security
• Performance
• Scalability
• Reliability
• Support RDMS concepts

The system specification is the final work produced by the system and
requirements engineer. It serves as the foundation for hardware engineering,
software engineering, database engineering and human engineering.

Once requirements have been gathered explore each requirements in

relationship to others, examine requirements for consistency, omissions and
ambiguity.
Hardware Specification

It is recommended that the minimum configuration for clients is as appended

below:-
Suggested Configuration of Windows clients:-

Microprocessor : Pentium-2 class processor, 450 megahertz MHz)

Ram : 128 MB of RAM
Hard Disk : 2.5 gigabytes (GB) on installation drive, which
Includes 500 MB on system drive.

CD ROM Drive : 52 X CD ROM Drive

Software Specifications
Operating System : Windows 2000XP/Windows 2000 NT
RDBMS : Sql Server 2000
Front End : Microsoft Visual Studio.NET
 CONCLUSION

This is the best online customer care web application for providing the warranty period
products and customer can reuse their damage product after using the service center
supports, and using the work flow of this web application very secure and properly
maintain the customer products warranty periods details in database application and it
can be easily upload in local IIS Server or any space service provider server, not and
further tools require for the supports of this web application.
 DEPENDENCIES

 It doesn’t matter how efficiently the application works, if the bandwidth is

not sufficient the transaction will take more time then expected.
 .Net Framework for execution environment and Ado.Net Provides for
database connectivity.
 IIS server 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
LIMITATIONS
• This system can’t provide on line product replacement process facility for their
customers.

• This system not providing facility for online credit cards payment for the help of
customers.

• This system developed only one language (en-us) English and not support
different language.

REFERENCES

• Pro C# with .NET 3.5 (Andrew Troelsen) - by Apress publication

• Pro ASP.NET 3.5 in C# 2008 - by Apress publication
• Java Script Programming - by Wrox publication