CUSTOMER RELATIONSHIP MANAGEMENT

For AGAM TECHNOLOGIES, COIMBATORE

PROJECT REPORT
Submitted in partial fulfillment of the requirement for the award of the Degree of

MASTER OF SOFTWARE SYSTEMS

Submitted by

VARUN DAS D.
REGISTER. No: 12MSS014
Under the Guidance of

Mr. R. S. Karthik MCA., M.Phil.,SLET

Assistant Professor, School of Computer Science

Since 1988

SCHOOL OF COMPUTER SCIENCE

CMS COLLEGE OF SCIENCE & COMMERCE
(AUTONOMOUS)
Re-Accredited at the A level by NAAC, with cGPA of 3.53 out of 4
(Affiliated to Bharathiar University)
Coimbatore 641 049.

OCT 2015
 SCHOOL OF COMPUTER SCIENCE
CMS COLLEGE OF SCIENCE & COMMERCE
(AUTONOMOUS)
Re-Accredited at the A level by NAAC, with cGPA of 3.53 out of 4
(Affiliated to Bharathiar University)
Coimbatore 641 049.

CERTIFICATE
This is to certify that the Project work entitled
CUSTOMER RELATIONSHIP MANAGEMENT
is a bonafide original record of work done by

VARUN DAS D.
12MSS014
in partial fulfillment of the requirements for the award of the degree of
MASTER OF SOFTWARE SYSTEMS

Submitted for Viva - Voce Examination held on _______________

Countersigned

Project Guide Director

Internal Examiner External Examiner

2
 COMPANY CERTIFICATE

3
 DECLARATION

I Mr. VARUN DAS D. [Reg.No: 12MSS014]hereby declare that the project work
entitled CUSTOMER RELATIONSHIP MANAGEMENTdeveloped at Clusters media
and technologies and submitted to Bharathiar University, Coimbatore in partial fulfillment of
the requirements for the award of the degree of MASTER OF SOFTWARE SYSTEMS, is
a record of original project work done by me during the period of [2014 2015], under the
supervision and guidance of Mr. R. S. Karthik MCA., M.Phil.,SLET., Assistant Professor,
School of Computer Science, CMS College of Science& Commerce, Coimbatore.

Place: Coimbatore049

Date: Signature of the candidate

VARUN DAS D.

4
 ACKNOWLEDGEMENT

5
 ACKNOWLEDGEMENT

I am very much grateful to the Almighty who has helped me all the way through the
project and who has moulded me in to what Im today.

I have been fortunate enough to be able to secure co-opration, guidance and

assistance from a number of people. I am at a loss of how to express the deep sense of
gratitude I have towards all of them. I am greatly indebted to
PRINCIPAL Dr. S. SANDHYA MENON, M.B.A,Ph.D who has given me the permission
for the fulfilment of this venture.

I would like to express my sincere gratitude to Mr. B. GUNALAN, M.Sc., M. Phil.,

PGDCA, Director, School of Computer Science, CMS College of Science & Commerce, for
his invaluable support and guidance during my project.

I would like to express my deep sense of gratitude to my guide

Mr. R. S. Karthik MCA., M.Phil.,SLET., Designation, School of Computer Science, for
the valuable encouragement and guidance he had given me for the successful completion of
this project. I am grateful to him/her in all the ways.

I would like to express my heart feel gratitude to all other faculty members, School of
Computer Science, for their guidance and support throughout my project.

Last but certainly not the least I would like to express my deep sense of gratitude to
my family members and beloved friends for their moral support and encouragement without
which I would not have been able to follow my dreams.

VARUN DAS D.

6
 SYNOPSIS

7
 SYNOPSIS

This project entitled as CUSTOMER RELATIONSHIP MANAGEMENT

(CRM) can help organizations manage customer interactions more effectively to maintain
competitiveness in the present economy.As more and more organizations realize the
significance of becoming customer-centric intodays competitive era, they adopted CRM as a
core business strategy and invested heavily.

CRM, an integration of information technology and relationship marketing,

provides the infrastructure that facilitates long-term relationship building with customers
at an enterprise-wide level. Successful CRM implementation is a complex, expensive and
rarely technical projects. This paper presents the successful implementation of CRM from
process perspective in a trans-national organization with operations in different segments.
This study will aid in understanding transition, constraints and the implementation process

8
 CONTENTS

9
 CONTENTS

Page No
1. Introduction
1.1 Project Overview -12
1.2 Objective of the Project -13
2. System Analysis
2.1 Existing System -15
2.2 Proposed System -16
2.3 Feasibility Study -18
2.4 Hardware Specification -21
2.5 Software Specification -21
3. System Design
3.1 Input Design -23
3.2 Output Design -24
3.3 Database Design -25
3.4 Code Design -26
4. System Testing -28

5. System Implementation& Maintenance -32

6. Scope for Future Enhancement -34

7. Conclusion -37

9. Bibliography -39

10. Appendix

A. Data Flow Diagrams -42

B. ER Diagrams -46
C. Table Design -47
D. Form Design -51
E. Reports -58

10
 INTRODUCTION

11
 1.INTRODUCTION

1.1 PROJECT OVERVIEW

Customer relationship management (CRM) is a widely implemented model

for managing a companys interactions with customers, clients, and sales prospects. It
involves using technology to organize, automate, and synchronize business processes
principally sales activities, but also those for marketing, customer service, and technical
support. The overall goals are to find, attract, and win new clients, service and retain those
the company already has, entice former clients to return, and reduce the costs of marketing
and client service. Customer relationship management describes a company-wide business
strategy including customer-interface departments as well as other departments.

Measuring and valuing customer relationships is critical to implementing this

strategy.To be successful in todays competitive marketplace, enterprises must seamlessly
interact and extend information beyond the walls of their organization. This android
application System end-to-end enterprise mobile solution makes a real time possible of giving
business managers significant advantage of remote and instant access to information from
anywhere, anytime. Our CRM solution in Google android delivers a rich user experience and
drives overall usage of your CRM system by enabling remote access for your sales, service
and management teams.

12
1.2 OBJECTIVE OF THE PROJECT

MODULES IN THE PROJECT:

Administrator (Server)
Sales maintenance module
Customer data maintenance module

ADMINISTRATOR

Administrator module is designed separately for the use to help administrator for
control the entire activities by the administrator. The administrator can store the information
like salesperson details, product details, customer details.

SALES MAINTENANCE MODULE:

This module is responsible for taking order by the customer and updating of different
tables such as bill details, transaction, and inventory and salesperson performance. Whenever
any customer place order for any product firstly the salesperson checks whether the product is
available in the inventory or not. If there is sufficient amount of product in the inventory then
unique bill number is generated and record is saved in bill details and transaction table .This
modules also generates bill.

CUSTOMER DATA MAINTENANCE:

This module is responsible for management of customer data. This data is accessed and
maintained by the salesperson. If product is sold to a new customer than data of new
customer can be added in the database. If there is any change in the customer record such as
change of address, phone number, etc. Then the sales person can edit their records with the
help of this module.

13
 SYSTEM ANALYSIS

14
 2. SYSTEM ANALYSIS

2.1 EXISTING SYSTEM

There is not any existing system for client side. So all the work are handling
manually and have to be noted down in some register and also taking care of that
documentation. They are arranged meeting by call and if any update occurred then
again call client and update meeting schedule, its wasting the time and as well as
money also and also the disturb the valuable clients

Disadvantages of the existing system are:-

CRM is a fully manual where in all the day to day event of call log, automation of
email, customer interaction it was not possible to develop a centralized system.
Delayed and distorted information.
Lack of proper communication and data collecting process.
Customer queries will send the courier, and send the mail possibilities only. Its not
possible to all customers.
Absence of factual, reliable and accurate reports to management

15
2.2 PROPOSED SYSTEM

The CRM is a new technique in marketing and management where the owner tries to
develop them as life time customer.CRM aims to make the customer climb up the ladder of
loyalty.

The company first tried to determine who are likely prospects i.e. the people who
have a strong potential interest in the product and ability to pay for it. The company hopes to
convert many of its qualified prospects into first time customers in to life time clients. They
are those people who buy only from the company in the relevant product categories. The next
challenge for the company is to convert this client into advocates. Advocates are those clients
who praise the company and encourage others to buy from it.

The use of the CRM system will confer several advantages to the company
Quality and efficiency
Decreased in overall costs
Decision support
Enterprise agility
Customer Attention

The overall goals are to find, attract and win new clients, nature and retain those the company
already has, entice former clients back into the fold, and reduce the cost of marketing and
client service.

16
FEATURES:

1. Automatic management of data.

2. To retrieve fast and accurate data
3. Elimination of data redundancy
4. Customers easy to share the queries in management to using the android mobile.
5. Improve the customer in management.
6. Easy to update the day-to-day customer details.

NEED OF PROPOSED SYSTEM:

Large volumes of data can be performed with ease

Maintenance of file is flexible
Record stored and updated occasionally
Stored data can be edited as per needed

17
2.3 FEASIILITY STUDY

This feasibility was conducted to investigate and recommend measures i.e.,(customer

relationship Management system(CRM) that will correct the issues of companys decrease in
growth over the years. We will cover operation, technology and economic consideration
which deal with functionality of the company.

The implementation of customer relationship management (CRM) is a system for

managing a company interaction with current and future customer. Its often involves using
technology to organize, automate and synchronize sales, marketing, customer service, and
technical support. It was noted that CRM will be important accessory to companys because of
all the good it will do the company as it relate to marketing, finical operational and
technology overall.

TECHNICAL FEASIBILITY

Upgraded technological capability will be required for company to move toward

offering an online marketplace from which customer may purchase their products as well as
give feedback.

Customer demand a simple and easy way by which to conduct online transactions and
it is important that all transactions and it is important that all transactions are conducted in a
secure manner, while company maintains a web site with product list and descriptions, it does
not currently allow for customer interaction to be done online. This functionally must be
integrated with their current web site to allow for effective communication between company
and customer. Additionally, new online marketing functionally must be considered in order to
target existing and potential customer through methods such as E-mailing list, promotional
advertisements, and loyalty discounts.

18
 We recommend that this work is contracted out to an internet marketplace provider
who can work with company to meet needs within the determined timeframe and budget. It
should be noted that the technology exists and is in use throughout the marketplace which
lowers the risk of this concept considerably.
Company maintains a high speed internet connection, web server, and the latest software with
the addition of a customer relationship management system(CRM)it is expected that there
will be an overall cost increase of 5-10% for web server operations and maintenance costs.

OPERATIONAL FEASIBILITY

As said in the above technology considerations the system is already in use so its not
a major risk as long as the feedback from the customer is read and given serious
consideration the system is expected to perform perfectly that being said it will be necessary
for new staff to be hired they will mainly handle and take care of the online system
companies online venture is not anticipated too significantly affected the organizational
structure of the company. However, there are staffing additions required to successfully
implement the (CRM).all of these positions will work within existing departments and report
to department managers.

Staffing position 1
Online sales manager, this full time position will lead sales staff in identifying sales
opportunities and converting these opportunities to actual sales. This person will report to
companies Director of sales and will work at headquarters.

Staffing position 2
Online marketing manager, this full time position will lead marketing staff in
identifying target customer groups/markets and conducting online advertise/marketing efforts
to maximize traffic to companies online marketplace. This person will report to companies
director of marketing and will work at headquarters

19
Staffing position 3

Online customer manager ,this is a full time position will be in charge of analyzing
the output of the CRM to help give a realistic figure of what products there should be more
of. This person will report to companys director of marketing and will work at headquarters.
It is expected that grace has an existing network specialist who will maintain the system.

ECONOMIC FEASIBILITY

A large majority of companys customer base are retuning customer and referrals
from exiting customers. By providing a more convenient means of purchasing our products
online it is expected that we will retain these customers while conducting online marketing
campaign for new customers as well. Company will distribute online purchase via direct
shipping from the nearest store location. This will allow company to provide timely shipping
from the nearest store location. This will allow company tom provide timely shipping and
eliminate the need for a central warehouse to facility from which to store and ship its
products. Such a facility would require a significant capital investment as well as increase
operation and maintenance costs. However, based on anticipated growth projections,
company must ensure that all store locations maintain adequate inventories on hand to satisfy
customer demand. companys will implement customer e mailing list in order to send product
promotions, sales advertisements, and other special offering to customers who register.

Additionally, companys will offer referral incentives to customers who refer our
products to friend and family in order to provide additional incentives. Company will also
maintain a customer database in order to determine its target customer groups and
geographical regions. Grace will research marketing intelligence providers to determine the
benefits and cost of gather customer information using the CRM for bulk email campaigns as
well. Another important consideration of companys online marketing strategy is cost.
Electronic marketing communication cost is very small in comparison to direct mail
marketing which company currently utilizes .however, the additional revenue from online
sales to greatly outweigh these additional electronic marketing costs.

20
 It is important to note that company current marketing and sale staff will require
training in online marketing and sales practices. This training will need to be contracted to
training provide as part of our startup cost and schedule.

2.4 HARDWARE SPECIFICATION

RAM : 4GB.
Hard Disk Drive : 1 TB.
Keyboard : Logitech.
Device : Android Smart Phone.
Mouse : Logitech.
Processor : Intel(R) Core(TM) i5-4210U CPU @ 1.70GHz 2.40 GHz
Mother Board : Mercury.

2.5 SOFTWAEW SPECIFICATION

3. System Design Front End : Java (J2SE) with Android SDK

Back End : SQLite 3, MS ACCESS(Server End)
Editor : Eclipse Indigo.
Documentation : MS-Word2010, MS-Paint.

21
 SYSTEM DESIGN

22
 3.SYSTEM DESIGN

3.1 INPUT DESIGN

The input design is the process of converting the user-oriented inputs in to the
computer-based format. The goal of designing input data is to make the automation as easy
and free from errors as possible. For providing a good input design for the application, each
data input and selection features are adopted.

Login page form

The user can enter the login details such as username and

password

Master home page form

It is a navigation form which helps to switch either sales management

form or customer data management

Home page of sales management form

It is also a navigation page which contains three buttons such as first

meeting,second meeting,sales order

Customer registration form

This form allows to ADD new customer to our database. The user can enter

his/her name,type,address,reference,mobile number,email address .

First meeting form

The user can enter the details of very first meeting with the customer such as

date,customer name,product name,details

23
 Quotation or second meeting form

In this form the user can confirm the deal with costumers .And it as some

details such as customer name,product name,date,price,unit,grand price .

Sales form

The billing and delivery has been done with perfect details of customer such

as name,date,product,price,unit,discount,tax,total,check details,signature oof

customer

Home page of customer management

We can view and delete the registered customers

3.2 OUTPUT DESIGN

Design output to serve the intended purpose essentially, this means

that the systems objectives should be met but the objectives should be linked to the business
tactics. Design output to fit the user, design for the person, not the position; remember human
information processing differences; issue of detail versus summery. Delivering the
appropriate quantity of output, dont create over load, create enough to perform business
tactics and make anything else optional.Two kinds of output designs:

External output: It travels outside the system boundaries to customers or vendors. One
major form of external output is the turnaround document which can identify transactions.

Internal outputs: It can be include detail, summery, exception reports. It should be only
negative exceptions may or may not be included.

24
3.3 DATABASE DESIGN

The backbone of the application depends on the database management system. The
database selected must be reliable and must be protected against unauthorized access. I have
chosen SQLite as the database.

Database Management System allows the data to be protected and organized separately
from other resources. It also provides recovery facilities, privacy control and a specific data
accessing language to be used by the programs. The main objectives of DBMS are data
accessibility, data consistency, data integrity and data independence.

The Normalization tables of CRM is given below

1. User details

2. Product details

3. Sales details

4. Customer details

5. First meeting details

6. Second meeting details

25
3.4 CODE DESIGN

Code is an ordered collection of symbols designed to provide unique identification of

an attribute.Codes can be used for various purposes.they can specify objects physical or
performance characteristrics and they can be used to give operational instructions.they also
can show interrelationship and may sometimes used to achieve secrecy or
confidentially.codes are designed for optimum human-oriented use and machine
efficiency.Codes posses uniqueness,expandability,conciseness,uniform size and
formate,simplicity,stability.meaningfulnesss and operability.

Sufficient effort and time is spent in the preliminary study od the problem to design
an efficient code.active server scripting is object oriented.the source code is designed so that
it can do transcation efficiently .it is the code that does all the updations,modifications,etc. for
all object used in the project there exist an associated source code,which explains the work of
that object.it also describes the flow of the project.

26
 SYSTEM TESTING

27
 4. SYSTEM TESTING

The purpose of testing is to discover errors. Testing is the process of trying to

discover every conceivable fault or weakness in a work product. It provides a way to check
the functionality of components, sub assemblies, assemblies and/or a finished product it
is the process of exercising software with the intent of ensuring that the software system
meets its requirements and user expectations and does not fail in an unacceptable manner.
There are various types of test. Each test type addresses a specific testing requirement.

Software testing methods are traditionally divided into white box, black box testing.

WHITE BOX TESTING:

White box testing strategy deals with the internal logic and structure of the code.
White box testing is also called as glass, structural, open box or clear box testing. The tests
written based on the white box testing strategy incorporate coverage of the code written,
branches, paths, statements and internal logic of the code etc... White box test also needs the
tester to look into the code and find out which unit/statement/chunk of the code is
malfunctioning. Various testing types that fall under the White box Testing strategy are:

BOX TESTING:
Black Box Testing is not a type of testing; it instead is a testing strategy, which does
not need any knowledge of internal design or code etc. As the name "black box" suggests, no
knowledge of internal logic or code structure is required. The types of testing under this
strategy are totally based/focused on the testing for requirements and functionality of the
work product/software application. Black box testing is sometimes also called as "Opaque
Testing", "Functional/Behavioral Testing" and "Closed Box Testing".

The base of the black box testing strategy lies in the selection of appropriate data as
per functionality and testing it against the functional specifications in order to check for
normal and abnormal behavior of the system. Now a days, it is becoming common to route
the testing work to a third party as the developer of the system knows too much of the
internal logic and coding of the system, which makes it unfit to test the application by the
developer. Various testing types that fall under the Black Box Testing strategy are

28
Unit Testing:

Unit testing is usually conducted as part of a combined code and unit test phase of the
software lifecycle, although it is not uncommon for coding and unit testing to be conducted as
two distinct phases. Test strategy and approach Field testing will be performed manually and
functional tests will be written in detail. Test objectives all field entries must work properly.
Pages must be activated from the identified link. The entry screen, messages and responses
must not be delayed. Features to be tested Verify that the entries are of the correct format No
duplicate entries should be allowed all links should take the user to the correct page.

Integration Testing:

Software integration testing is the incremental integration testing of two or more

integrated software components on a single platform to produce failures caused by
interface defects. The task of the integration test is to check that components or
software applications, e.g. components in a software system or one step up software
applications at the company level interact without error.

Test Results: All the test cases mentioned above passed successfully. No defects
encountered.

System testing:

System testing ensure that the entire integrated software system meets requirements.It test a
configuration to ensure known and predictable result.An example of system testing is the
configuration oriented system integration test.system testing is based on process descriptions
and flows,emphasizing pre-driven process links and integration points.

System testing tests the integration of each module in the system.its also tests to find
discreption. The primary concern is the compatibility of individual modules. Entire system is
working properly or not will be tested here,and specified path ODBC connection will

29
 connection will correct or not. These verification and validation and validations are done by
given input value to the system.

Acceptance Testing:

User Acceptance Testing is a critical phase of any project and requires

significant participation by the end user. It also ensures that the system meets the functional
requirements.

Test Results: All the test cases mentioned above passed successfully. No defects
encountered.

Testing Report:

Testing phases performed on system.

Test Cases Test Description Expected Result Observed result

Database connectivity Connection string From Login page to (fails) Cannot login
(Unit Test) Check (login) match page due to error in
connection string
declaration
Validate the UserName UserName & Enter into home page (fails) cannot login
& PassWord PassWord Check due to incorrect
UserName
User Acceptance test Checks the values Accept and save the (fails)mismatch error
given by user values occurs
User Acceptance test Checks the values Accept and save the (pass) store the
given by user values values
Integration Test Check and integrate Display All the (pass) Every
every screen based screens without any Transaction done
on the project flow. issue. without any mistake.

30
SYSTEM IMPLEMENTATION &
MAINTENANCE

31
 5. SYSTEM IMPLEMENTATION & MAINTENANCE

IMPLEMENTATION PROCEDURE

Implementation of the software refers to be final installation of the package in its

real environment .To The satisfaction of the users and operation of the system. In many
organization someone who will not be operating it, will commission the software
development project . In the initial stage ,they doubt about the software but we have to ensure
that the resistant does not build up as one has to make sure that the active user must be aware
of the benefit of the system . Their confidence in the software is buildup . Proper guidance
is imparted to the user so that he is comfortable in using the application . Based going
ahead and viewing the system, The user must know that for viewing the result.

SYSTEM MAINTANANCE

The maintenance phase of the software cycle is the time in which a software product
useful work. After a system is successfully implemented, it should be maintained in a proper
manner. System maintenance is an important aspect in the software development life cycle.
The need for system maintenance is for it to make adaptable to the changes in the
environment. There may be social, technical and other environment changes, which affect a
system, which is being implemented. Software product enhancement may involve providing
new functional capabilities, improving user displays and mode of interaction, upgrading the
performance characteristics of the system. so only through proper system maintenance
procedures, the system can be adapted to cope up with these changes.

Software maintenance is of cause, far more than finding mistakes. We may define
maintenance by describing for activities that are undertaken to after a program is released for
use. The first maintenance activity occur because it is unreasonable to assume that software
testing will uncover all latent errors in a large software system. During the use of any larger
program, errors will occur and be reported to the developer.

32
 The process that includes the diagnosis and correction of one or more errors is called
corrective maintenance. The second activity that contributes to a definition of maintenance
occurs of because of the rapid change that is encountered in every aspect of computing.
Therefore, adaptive maintenance an activity that modifies software to properly interfere with
a changing an environment is both necessary and common place.

The forth maintenance activity occurs when software is changed to improve future
maintainability or reliability, or to provide a better basis for future enhancement and re-
engineering techniques

33
 SCOPE FOR FUTURE
ENHANCEMENT

34
 6. SCOPE FOR FUTURE ENHANCEMENT

The future CRM market are beginning to appear. Certainly analytics software will
become more broadly used in making informed business decisions as well as tailoring point-
of-sale promotions. Clearly, the number of wireless applications will increase in field service
and sales. Whether the marketers dream of location targeted advertising on cellular
telephones will be realized in the next few years is dependent on business models more than
technology. It will certainly be possible for an advertiser to target an advertisement to a
consumer based on the location of his GPS-enabled communication device. Who will pay for
the service and how much it will cost are still open questions.

Now that all the major software packages are Web-based, a number of new
opportunities arise.

Expect companies to invest in new initiatives like the following:

Companies will increase their focus on automating critical business

processes not just individual functional organizations
Companies will increasingly automate their extended demand chain not just
to sales partners, but to their supply chain
B2B companies will increasingly market and sell to their partners and the
partners employees
Service employees will increasingly become sales representatives

CRM functionality will increasingly be available as Web services, but not

necessary commercially hosted services
Identity management, security and trustworthy computing will become
decision criteria for new CRM purchases.

Similarly, developing joint customer acquisition programs with members in the

overall value chain is largely uncharted territory. Sharing customer data, developing cross
35
company business processes, and promoting complementary products to consumers (or other
businesses) when done at all, are makeshift operations at best. As internal CRM systems are
deployed and analytical applications come on line, the opportunities for joint marketing will
become boundless. Personalized customer service (the holy grail of CRM) creates endless
opportunities for personalized selling. This is recreating the role of service representatives.
Service leverages CRM technology like no other function. From a technology perspective,
CRM will certainly follow the greater trends in the marketplace, but two in particular deserve
discussion.

The first involves what have become known as Web services. These include programs
and data that are accessible from standard interfaces for other functions, businesses,
individuals or other Web-connected programs. These kinds of services are based XML, Web
Services Description Language (WSDL), Simple Object Access Protocol (SOAP), and using
Uniform Resource Identifies (URI). CRM functions will increasingly be available as Web
services within companies and applications that touch customers and partners. Web services
will increasingly be used both as the foundation for a new generation of existing enterprise
software, and as an opportunity to reinvent the way corporations implement software. In the
latter instance, Web services are already finding their way into what is inelegantly called
business process software. The central insight of this concept is that companies dont really
want to simply automate functions (marketing, sales, service, manufacturing, supply chain
logistics, human resources, etc.), they want to improve the cross-functional business
processes on which the company is built.

36
 CONCLUSION

37
 7. CONCLUSION

This project entitled CUSTOMER RELATIONSHIP MANAGEMENT

SYSTEM IN ANDROID is successfully implemented with android and tested in all
ways. The project objectives were realized and successfully implemented. This is
completely certified that user friendly system which can be operated by an end user.
Validation can be done at all levels to avoid errors. This project is useful for project
development team with excellent design and flow. This project is mainly useful for
customer to interact with management who want to get their products by bidding. The
system would hold good flexibility for future enhancements

38
 BIBILOGAPHY

39
 8.BIBILOGAPHY

BOOK REFERENCES:

1. Professional Android 4 Development-By Reto Meier

2. Beginning Android 4 Development-By Wei-Ming Lee

3. Pro Android 4-By Satya Komatineni, Dave MacLean

4.Khera, Mandeep 2000, Customer Relationship Management Beyond the Buzz, CRM
Knowledge Base, 1st June, ITtoolbox, viewed 26th January 2004, Khera, Mandeep: Customer
Relationship Management

5.Mills, Josh 2001, CRM Overview, CRM Knowledge Base, 2nd September, ITtoolbox,
viewed 18th February 2004, Mills, Josh: CRM Overview

WEB REFERENCE:
1. www.wikipedia.com
2. www.learnmore.com
3. www.android.com

40
 APPENDIX

41
 10.APPENDIX

A.DATAFLOW DIAGRAM FOR SALES PERSON:

LEVEL 0

add add

user CRM customer

view view

LEVEL 1

add
SALESMAN
ADMIN

verify
LOGIN
view
view

SALES MANAGEMENT CUSTOMER DATA

MANAGEMENT

42
 LEVEL 2

add
ADMIN

Sales Person

Verify
Login

view view

SALES MANAGEMENT CUSTOMER DATA

MANAGEMENT

First Sales
Meeting Second Order
Meeting

Add Sale the

Customer Sales man product and
Details to get the to get
quotation signature

tblCustomer tbl Quotation tblSales

43
LEVEL 2.1

add
ADMIN

Sales Person

Verify
Login

view view

SALES CUSTOMER DATA

MANAGEMENT MANAGEMENT

View the Delete the

Customer Customer
details

tblSales

44
LEVEL 2.2

Product

SERVER DB Sales person

view

customer
add

add
ADMIN

Sales Person

Verify
Login

CRM

45
 B.ER DIAGRAM

sid

Pname pwrd
Pid
login DOB
sid sname
item designation
product
has salesman
category DOJ

quanti
price Scontact
ty Saddress

has
has
view
has

cname caddress

cid
Sample product

cid
customer
cemail
First meeting view
cperon
ccontact
cname date
order

date pid
cname

cid pname
quotation

has
quantity uprice
has tprice

sid cid
gtot
cname
tax
caddress
quantity
Sales

price
ccontact
pname pid sdate
46
C.TABLE DESIGN

LOGIN TABLE
This table is used to store the username and password of all the users.
SNO Field/Column Name Data Type Description
1 UserName Text RepId

2 PassWord Text Both alphabets and

nos

REP TABLE

This table is used to Store the all the Representatives Details.

Sno Field/Column Name Data Type Description
1 Repid Text PrimaryKey

2 Name Text Refers Rep name

3 Date_of_Birth Text Refers Rep DOB

4 Designation Text Refers the position of User

5 Date_of_Join Text Refers the DOJ of Rep

6 Contact No Text Refers Reps phone no

7 Address Text Refers Reps Address

PRODUCT TABLE

This table used to store the product Information. Done by any dataEntry operator with the
help of Admin.
Sno Field/Column Name Data Type Description
1 ProductId Text PrimaryKey

2 ProductName Text Refers Product Name

3 ProductItem Text Refers ProductItem

4 ProductCategory Text Refers Product Category

5 Price Text Refers Product price

6 Quantity Text Refers Total Quantity of the

product

47
SALES TABLE

This table is used to Store the Representative Reports of Sales.

Sno Field/Column Name Data Type Description
1 RepId Text Refers the Rep Id

2 CusId Text Refers the Customer Id

3 CusName Text Refers the Customer Name

4 CusAddress Text Refers the Customer Address

5 CusPhone Number Refers the Customer phone

No.
6 Date1 Text Refers Sales Date

7 ProductId Text Refers product Id

8 ProductName Text Refers product Name

9 Price Number Refers products price

10 Quantity Number Refers products quantity

11 Discount Number Refers discount amount

12 Tax Number Refers Tax amount

13 GrandTotal Number Refers Grand Total

14 currentLocation Text Refers Reps Current location

during sales.

48
MOBILE END

CUSTOMER TABLE

This table is used to Store the Customer details.

Sno Field/Column Name Data Type Description
1 CusId Text PrimaryKey

2 CusName Text Refers the Customer Name

3 CusType Text Refers the Customer Type

4 CusAddress Text Refers the Customer Address

5 cusContactPerson Text Refers Contact Person for customer

6 cusPhone Text Refers Customer phone

7 CusEmail Text Refers Customer Email

FIRST MEETING TABLE

This table is used to Store the First Meeting datas.

Sno Field/Column Name Data Type Description
1 CusId Text Refers Customer Id

2 CusName Text Refers the Customer Name

3 Date Text Refers the First Meeting Date

4 SampleProduct Text Refers the Sample Product

49
QUOTATION TABLE

This table is used to Store theQuotation processDatas.

Sno Field/Column Name Data Type Description
1 CusId Text PrimaryKey

2 CusName Text Refers the Customer Name

3 Date Text Refers the Quotation Date

4 productId Text Refers the Product Id

5 productName Text Refers Product Name

6 unitPrice Text Refers Unit Price

7 Quantity Text Refers Product Quantity

8 TotalPrice Text Refers Total Price Amount.

50
D.FORM DESIGN

LOGIN

51
HOME SCREEN FOR USER/SALESMAN

NAVIGATION:

52
ADD CUSTOMER DETAILS

FIRST MEETING

53
QUOTATION

54
SALES

55
56
FIRST MEETING REPORT

SECOND MEETING REPORT

57
E. REPORTS

FIRST MEETIING

58
SECOND MEETING

59
SAMPLE CODE

SQLITE CODING FOR CREATE TABLE:

DBAdaptor:

package com.crm.pack.database;
import
public class DbAdapter {
private static final String dbName = "MedicoMarketing";

private static final String tblCustomer="tblCustomer";

//private static final String TABLE_CUSTOMER_TYPE="tblCustomer_type";
private static final String tblFirstMeeting="tblFirstMeeting";
private static final String tblQuotation="tblQuotation";
private static final String tblSales="tblSales";
public static final String userName = "usrName";
public static final String passWord = "passWord";
public static String cus_name = "cus_name";
public static String date = "date";
public static String cus_id = "cus_id";
public static String sample_product = "sample_product";
public static String cus_type = "cus_type";
public static String cus_address = "cus_address";
public static String cus_contact_person = "cus_contact_person";
public static String cus_phone = "cus_phone";
public static String cus_email = "cus_email";
public static String prod_id = "prod_id";
public static String prod_name = "prod_name";
public static String unit_price = "unit_price";
public static String quantity = "quantity";
public static String total_price = "total_price";
public static String discount = "discount";
public static String description = "description";
public static String tax="tax";
60
 public static String grand_Total="grand_Total";
private static final int db_version = 2;
public String[] pId,pName,pItem,pCategory,price,qty;
public int totalProducts=0;
public String newIp;
private static final String create_tblCustomer="CREATE TABLE IF NOT EXISTS
tblCustomer"+
" (cus_id INTEGER,cus_name TEXT,cus_type TEXT,cus_address
TEXT,cus_contact_person TEXT,cus_phone TEXT,cus_email TEXT,PRIMARY
KEY(cus_id ASC));";

private static final String create_tblFirstMeeting="CREATE TABLE IF NOT

EXISTS tblFirstMeeting"+
" (cus_id INTEGER,date TEXT,cus_name TEXT,sample_product
TEXT, description TEXT,cus_phone TEXT,cus_address TEXT,cus_email TEXT);";
private static final String create_tblQuotation="CREATE TABLE IF NOT EXISTS
tblQuotation"+
" (cus_id INTEGER,cus_name TEXT,date TEXT,prod_id
TEXT,prod_name TEXT,unit_price TEXT,quantity TEXT,total_price TEXT);";

private static final String create_tblSales="CREATE TABLE IF NOT EXISTS tblSales"+

" (cus_id INTEGER,cus_name TEXT,cus_address TEXT,cus_phone
TEXT,date TEXT,prod_id TEXT,prod_name TEXT,unit_price TEXT,quantity
TEXT,discount TEXT,tax TEXT,grand_Total TEXT);";
private final Context context;
private SQLiteDatabase db1;
private DatabaseHelper dbhelper;
public DbAdapter(Context ctx) {
this.context = ctx;
dbhelper=new DatabaseHelper(context);
newIp=GiveUrl.ipAddress;
}
private static class DatabaseHelper extends SQLiteOpenHelper
{
61
 private static final String TAG = null;
public DatabaseHelper(Context context) {
super(context, dbName, null, db_version);
}
@Override
public void onCreate(SQLiteDatabase db)
{
try{
db.execSQL(create_tblCustomer);
db.execSQL(create_tblFirstMeeting);
db.execSQL(create_tblQuotation);
db.execSQL(create_tblSales);
System.out.println("tables created success...");
}
catch(SQLException e){
e.printStackTrace();
}
}
@Override
public void onUpgrade(SQLiteDatabase db, int oldVersion, int newVersion) {

Log.w(TAG, "upgrading databse from version"+oldVersion+"to"

+newVersion+",which will destroy all old data");
db.execSQL("DROP TABLE IF EXITS tblLogin");
onCreate(db);
}
}
public DbAdapter open() throws SQLException{
dbhelper = new DatabaseHelper(context);
db1 = dbhelper.getWritableDatabase();
return this;
}
public void close(){
dbhelper.close();
62
 }

public long addCustomer(String cus_name1,String cus_type1,String

cus_address1,String cus_contact_person1,String cus_phone1,String cus_email1){
ContentValues values = new ContentValues();
System.out.println(cus_name1);
System.out.println(cus_type1);
values.put(cus_name,cus_name1);
values.put(cus_type, cus_type1);
values.put(cus_address, cus_address1);
values.put(cus_contact_person, cus_contact_person1);
values.put(cus_phone, cus_phone1);
values.put(cus_email, cus_email1);
return db1.insert(tblCustomer, null, values);
}
public long addFirstMeeting(String cusId1,String date1,String cusName1,String
cusPhone1,String cusAddress1,String cusEmail1,String sampleProd1,String description1){
ContentValues values = new ContentValues();
values.put(cus_id,cusId1);
values.put(date,date1);
values.put(cus_name, cusName1);
values.put(cus_phone, cusPhone1);
values.put(cus_address, cusAddress1);
values.put(cus_email, cusEmail1);
values.put(sample_product,sampleProd1);
values.put(description,description1);

return db1.insert(tblFirstMeeting, null, values);

public long addQuotationDatas(String cus_id1,String cus_name1,String date1,String

prod_id1,String prod_name1,String unit_price1,String quantity1,String total1){
long result=0;
63
 try{

ContentValues values = new ContentValues();

values.put(cus_id, cus_id1);
values.put(cus_name, cus_name1);
values.put(date, date1);
values.put(prod_id, prod_id1);
values.put(prod_name, prod_name1);
values.put(unit_price, unit_price1);
values.put(quantity,quantity1);
values.put(total_price,total1);
db1.insert(tblQuotation, null, values);
result=1;
}catch(Exception e){

}
return result;
}

public long addSalesDatas(String cus_id1,String cus_name1,String cus_addr1,String

phone1,String date1,String prod_id1,String prod_name1,String unit_price1,String
quantity1,String discount1,String tax1,String grandTotal1){
ContentValues values = new ContentValues();
values.put(cus_id, cus_id1);
values.put(cus_name, cus_name1);
values.put(cus_address, cus_addr1);
values.put(cus_phone, phone1);
values.put(date, date1);
values.put(prod_id, prod_id1);
values.put(prod_name, prod_name1);
values.put(unit_price, unit_price1);
values.put(quantity,quantity1);
values.put(discount,discount1);
values.put(tax,tax1);
64
 values.put(grand_Total,grandTotal1);
return db1.insert(tblSales, null, values);
}
public Cursor fetchCustomerDetails(){
Cursor cursor = db1.query(tblCustomer, new
String[]{cus_id,cus_name,cus_type,cus_address,cus_contact_person,cus_phone,cus_email},
null, null, null, null, null);
if(cursor!=null)
cursor.moveToFirst();
return cursor;
}
public Cursor fetchCustomerDetails1(String phone){
Cursor cursor = db1.query(tblCustomer, new
String[]{cus_id,cus_address,cus_phone,cus_email}, cus_phone+"='"+phone+"'", null, null,
null, null);
if(cursor!=null)
cursor.moveToFirst();
return cursor;
}
public Cursor fetchFirstMeetingDetails(){
Cursor cursor = db1.query(tblFirstMeeting, new
String[]{date,cus_name,sample_product,description,cus_phone,cus_address,cus_email}, null,
null, null, null, null);
if(cursor!=null)
cursor.moveToFirst();
return cursor;
}
public Cursor fetchSecondMeetingDetails(){
Cursor cursor = db1.query(tblQuotation, new
String[]{cus_name,date,prod_id,prod_name,unit_price,quantity,total_price}, null, null, null,
null, null);
if(cursor!=null)
cursor.moveToFirst();
return cursor;
65
 }
public String deleteCustomer(String cusId){
String result="0";
try{
db1.delete(tblCustomer, cus_id+"='"+cusId+"'", null);
db1.delete(tblFirstMeeting,cus_id+"='"+cusId+"'", null);
db1.delete(tblQuotation, cus_id+"='"+cusId+"'", null);
db1.delete(tblSales, cus_id+"='"+cusId+"'", null);
result="1";
}
catch(Exception e){
result="0";
}
} return result;

public int getDatafrmServer(){

String response=null;
try
{
response =
HttpConnector.getPlatformObject("http://"+newIp+":8080/WebServiceForCRM/api/Product/
ProductDetails");
String res = response.toString();
JSONObject json = new JSONObject(res);
JSONArray jarray = json.getJSONArray("ProductDetails");
totalProducts=jarray.length();
System.out.println("array_size="+totalProducts);
pId=new String[totalProducts];
pName=new String[totalProducts];
pCategory=new String[totalProducts];
price=new String[totalProducts];
qty=new String[totalProducts];
for(int i=0; i<totalProducts; i++)
66
 {
JSONObject obj = jarray.getJSONObject(i);// to get arrays one-by-one
pId[i]=obj.getString("PID").trim();
pName[i]=obj.getString("PNAME");
pCategory[i]=obj.getString("CAT");
price[i]=obj.getString("PRICE");
qty[i]=obj.getString("PQUANTITY")
}
}
catch(Exception e)
return totalProducts;
}

67