Project Title & Definition Project Abstract Software /Hardware Requirement Process Model Detail Description of Modules UML

ML & DFD diagram Data Dictionary Actual Snapshots Conclusion & future work References
4/29/2013

Project Title & Definition

Project Title:- Customer Complain Handling process. Definition: Work allocation and reporting system for customer complain is developed for solve the customer complain. Customer call to phone operator for complaint registration / Customer direct do complain on web. Once complain registered by operator then it will check by head of operator then it will allocated to team leader according area. Once team leader of any area get complain then it analysis and then allocate it to proper engineer. Engineer attend customer and submit report. All process are online. At the end of day Engineer submit his report to TL, TL submit his report to HO.
Go Back

4/29/2013

Project Abstract
Every program contains at least one bug, and can be

reduced in length by at least one instruction. Customer complain handling is a web application which will be used for handle the customer complain. Customer complain handling process is module that handle the complain come form customer.

4/29/2013

Go Back

Hardware Requirement
HARDWARE REQUIRMENTS: SERVER CONFIGURATION

C2D or above 1 GB RAM or above 160 GB HDD or above IIS 7.0 or above C2D or above 1 GB RAM or above 160 GB HDD or above

CLIENT CONFIGURATION

4/29/2013

Next

Software Requirement
SOFTWARE REQUIRMENTS: SERVER CONFIGURATION

Window XP/NT 2000 SERVER or Above WAMP SERVER 2.0 Browser IE 8.0 or Above Google chrome or Firefox

CLIENT CONFIGURATION

Browser IE 8.0 or Above Google chrome or Firefox

4/29/2013

Go Back

Process Model

Complain Registration process Login Process Assign Complain Reporting At ER Site Reporting At TL Site Team Leader Engineer Phone Operator Handle Product Complain Process At HO Complain Process At TL
Go Back

4/29/2013

Complain Registration Process

Process
Name Purpose Input

Description
Complain Registration The objective of this process is that customer do complain on product having fault. All information filled by customer. Input are product number ,product name ,location ,selling date , warranty year ,customer name ,address ,phone no ,alternate phone no ,email id and Sort detail of Complain. After fill up, all the valid information customer do complain successfully on product otherwise display error.

Output

Description If complain done successfully , then get solution of the complain after few days. display one message like complain done succefully you get solution into 5 days

4/29/2013

Go Back

Login Process
Process
Name Purpose Input Output

Description
Login process for Head OF Distributer , Team Leader ,Engineer ,Phone Operator. The objective of this process is that valid HO ,TL ,ER ,PHO do login inside own work side. Input are User name ,Password ,Type is like HO or TL Or ER Or PHO. After fill up, if type is ho and username and password are correct then it will done login succefully same as for phone operator ,Team leader ,Engineer.

Description If username and password are correct for selected type user then it will go inside own work otherwise display message enter correct user name and password.

4/29/2013

Go Back

Assign Complain Process

Process
Name Purpose Input Output

Description
Assign Complain Process at HO side and also at TL side The objective of this process is that Assign HO complain to TL at HO side. TL assign complain to ER at TL side Input are CC id and TL id at HO side, CC id and ER id at TL side. After this output at HO side complain is assigned to TL. At TL side output will be complain assigned to ER.

Description HO will assign complain to TL. TL assign that complain to ER working in Team.

4/29/2013

Go Back

Reporting Process At ER Side

Process
Name Purpose Input Output

Description
Reporting process at ER side. The objective of this process is that ER send reporting to TL after visiting Customer. Input are CC id ,ER id ,Sort info of report for visited Customer ,Text document of Report ,Team leader id Reporting Date. Reporting will be sanded to TL

Description If inputted document is txt then reporting will be sanded to TL succefully. Otherwise give message like upload text document only.

4/29/2013

Go Back

Reporting Process At TL Side

Process
Name Purpose Input

Description
Reporting process at TL side. The objective of this process is that TL send reporting to HO after checking reporting of ER. Input are at TL site CC id ,ER id ,Sort info of report for visited Customer ,Text document of Report ,Team leader id, HO id Reporting Date ,replay message for ER. Reporting will be sanded to HO ,Or if TL wan send replay back to ER.

Output

Description In this TL send back replay to ER ,Also edit the reported document and sand report to HR.

4/29/2013

Go Back

Team Leader Process

Process
Name Purpose Input Output

Description
New Team Leader creation process. The objective of this process is HO create new team leader. All details Inputted by HO. Input are TL name ,address ,location ,phone no ,email id ,username ,password ,ho no. After fill up ,if all type data inputted by HO will be correct then output will be new team leader created succefully ,otherwise display error message.

Description If team leader created succefully then HO will assign CC to TL also add engineer in the team.

4/29/2013

Go Back

Engineer Process
Process
Name Purpose

Description
New Engineer creation process. The objective of this process is HO create new Engineer in team.

Input

All details Inputted by HO. Input are like first select location as per location it will display TL name working in that location then after fill ,address ,location ,phone no ,email id ,username ,password ,ho no.
After fill up ,if all type data will be correct then output will be new engineer created succefully in selected team ,otherwise display error message.

Output

Description If Engineer created succefully then TL will assign CC to TL also add check reporting of engineer in the team.

4/29/2013

Go Back

Phone Operator Process

Process
Name Purpose Input

Description
New Engineer creation process. The objective of this process is that HO create new Phone operator. All details Inputted by HO. Input are PHO name ,address ,location ,phone no ,email id ,username ,password ,ho no.

Output

After fill up ,if all type data will be correct then output will be new Phone Operator created succefully ,otherwise display error message.

Description If Phone operator created succefully then pho handle phone and do complain as per handled phone also search complain from complain view currently status of searched complain

4/29/2013

Go Back

Product Process
Process
Name Purpose Input

Description
New product creation process. The objective of this process is that create new product by ho. Input are product no, image of product ,product name ,price ,feature ,review.

Output

After fill up, all the detail are filled correct then new product will be added succefully.

Description If new product will be added succefully the it will be display at home of CCHP website and also get complain from customer related that product.

4/29/2013

Go Back

Complain Process AT HO
Process
Name Purpose Input Output

Description
Complain process at HO. The objective of this process is that HO view not assigned complain and assign it to TL. Input are CCID , Selected TL id. Complain is assigned to TL succefully.

Description If complain is assigned succefully to TL. In this process first select not assigned complain view details and then click on assign TL then display TL available in that location after select that TL then also view the currently load of TL and then assign the complain to selected TL.

4/29/2013

Go Back

Complain Process AT TL
Process
Name Purpose Input Output

Description
Complain process at HO. The objective of this process is that TL view not assigned complain and assign it to ER. Input are CCID , Selected ER id working in Team. Complain is assigned to ER succefully.

Description If complain is assigned succefully to ER. In this process first select not assigned complain view details and then click on assign ER then display ER working in team . TL then also view the currently load of ER and then assign the complain to selected ER.

4/29/2013

Go Back

Detail Description of Modules

Customer Phone Operator

Head Of Department(Admin)
Team Leader Engineer

4/29/2013

Go Back

Customer
Customer Role Visit site View product Do complain on product Do inquiry

4/29/2013

Go Back

Phone Operator (PHO)

Phone Operator Role IF any customer call to phone operator for register complain then phone operator do registration of customer complain Search customer complain detail vise product number and customer name. View list of customer complain register by phone operator.

4/29/2013

Go Back

Head of Department (Admin)

Head of Department Role Complain Handling Product Handling Team Leader Handling Engineer Handling Phone Operator Handling Location Handling

4/29/2013

Go Back

Complain Handling
Complain Handling View Customer Complain ,like solve complain ,unsolved complain ,all complain. View details of Customer Complain as location assign it to team leader. View reporting of team leader related customer complain. View currently status of customer complain. Search Customer Complain.

4/29/2013

Go Back

Product Handling
Product Handling Add /Update product. Delete product when if have not any unchecked complain related that product. Search product .

4/29/2013

Go Back

Team Leader Handling

Team Leader Handling. Create new Team leader. Delete Team leader if not any engineer in team and not any customer complain assign to that team. Edit team leader/Add engineer into Team. Assign CC to Team Leader. View reporting of Team Leader. Replay back to Team leader for reporting. View work load of team leader. Total assigned complain to Team Leader
4/29/2013 Go Back

Engineer Handling
Engineer Handling Create new Engineer. Delete/Edit Engineer. View List of Engineer. Search Engineer form list.

4/29/2013

Go Back

Phone Operator Handling

Phone Operator Handling Add new phone operator. Edit phone operator. Delete phone operator. View list of phone operator

4/29/2013

Go Back

Location Handling
Location Handling Add new location. Edit/Delete location. View all location. Select any location then view detail of location like complain of that location ,Team leader of that location.

4/29/2013

Go Back

Team Leader (TL)

Team Leader View customer complain assign by HO. Analysis customer complain then assign it to engineer working in team. TL view list of engineer work in team. View load of engineer work in team. View reporting of engineer. Edit reporting of engineer and send it to HO and also give reply back to ER.
4/29/2013

Go Back

Engineer (ER)
Engineer View customer complain assign by Team Ladder. View detail of cc and then visit customer for solve complain. After visiting do reporting to TL of visited customer.

4/29/2013

Go Back

UML & DFD Diagram

USE CASE Diagram Sequence Diagram Class Diagram DFD Diagram

4/29/2013

Go Back

USE CASE diagram

Customer Head of Distributer Team Leader Engineer Phone operator

4/29/2013

Go Back

USE CASE for Customer

4/29/2013

Go Back

USE CASE for HO(ADMIN)

4/29/2013

Go Back

USE CASE for Team Leader

4/29/2013

Go Back

USE CASE for Engineer

4/29/2013

Go Back

USE CASE for Phone operator

4/29/2013

Go Back

Sequence Diagram
HO sequence TL sequence

4/29/2013

Go Back

HO sequence

4/29/2013

Go Back

TL sequence

4/29/2013

Go Back

Class diagram

4/29/2013

Go Back

4/29/2013

Go Back

Data Dictionary
Customer Complain
Engineer detail HO Detail

Location
Phone Operator Product Detail Reporting Detail Team Detail
4/29/2013

Go Back

Customer Complain
Sr. no
1 2 3 4 5 6 7

Column name
cc_id pr_no pr_name c_name Address ph_no aph_no

Data Type
Int (10)

Constraints Description
Primary Key Unique id and Primary key for CC , auto increment Product id from product detail Product name Customer name Address of Customer Phone number of Customer Alternate phone number of customer

Varchar (40) Foreign key Varchar (30) Varchar(30) Varchar(50) Varchar(10) Varchar(10) Not Null Not Null Not Null Not Null Not Null

4/29/2013

Next

Customer Complain(Continued)
Sr. no
8 9

Column name
e_id location

Data Type
Varchar(30) Int(30)

Constraints Description
Not Null Foreign key Email id of customer Loca_id of location and customer location

10
11 12 13 14

s_date
w_year Query C_date Ho_status

Date
Int(4) Varchar (50) Date Int

Not null
Not Null Not Null Not Null Foreign key

Selling date of product

Warranty year of product Query of product Complain Date Ho id of ho detail This will be set when ho view cc

4/29/2013

Next

Customer Complain(Continued)
Sr. no
15

Column name
Tl_status

Data Type
Int(11)

Constraints Description
Foreign key TL id of team leader detail. This will be set when HO assign complain to TL This contain id of ER when this complain is assigned by TL This will be set as 1 when engineer check CC and do reporting This will be set as 1 when reporting checked by TL and send it HO

16

Er_status

Int(11)

Foreign Key

17

C_status

Int(11)

Not Null

18

T_status

Int(11)

Not Null

4/29/2013

Next

Customer Complain(Continued)
Sr. no
19 20

Column name
H_status regi_id

Data Type
Int(11) Int(11)

Constraints Description
Not Null Not Null This will be set as 1 when HO confirm reporting of TL This contain id of phone operator if complain registered online directly by customer then it will be 0 otherwise it contain phone operator id. Complain solve date

21

Solvedate

Date

Not Null

4/29/2013

Go Back

Engineer Detail
Sr. no 1 Column name e_no Data Type Int(10) Constraints Description Primary key Id of Engineer Detail

2
3 4

teamno
ho_no name

Int(11)
Int(11) Varchar(20)

Foreign key
Foreign key Not null

Team number form teamdetail

Hoid of hodetail Name of ER

5
6

address
location

Varchar(50)
Int(11)

Not null
Foreign key

Address of ER
Engineer Loca_id from location

4/29/2013

Next

Engineer Detail (Continued)

Sr. no 1 7 2 8 3 9 4 10 5 11 6 12 Column name e_no ph_no teamno aph_no ho_no e_id name username address password location join date Data Type Int(10) Varchar(20) Int(10) Varchar(20) Int(10) Varchar(30) Varchar(20) Varchar(20) Varchar(50) Varchar(20) Int(30) Date Constraints Description Primary Not Nullkey Foreign key Not Null Foreign key Not null Not null Not null Not null Not null Foreign key Not null Id of Engineer Phone number Detail of ER Team number form Alternate phone number teamdetail of ER Hoid of hodetail Email id of ER Name of Er Username of ER Address of Er Password of ER Engineer Loca_id from location Date of join

4/29/2013

Go Back

Head of Distributer
Sr. no
1 2 3

Column name
id name address

Data Type
Int(10) Varchar(20) Varchar(30)

Constraints Description
Primary key Not null Not null Id of ho detail Name of head distributer Address of HO

4
5 6

ph_no
aph_no email_id

Varchar(20)
Varchar(20) Varchar(30)

Not null
Not null Not null

Phone number of HO
Alternate phone number of HO Email id of HO

7
8 9

username
password joindate

Varchar(20)
Varchar(20) Date

Not null
Not null Not null

Username of ER
Password of ER Date of join

4/29/2013

Go Back

Location
Sr. no 1 2 Column name loca_id loca_name Data Type Int(11) Varchar(20) Constraints Description Primary Key Not null Id of location. Location name

4/29/2013

Go Back

Phone Operator
Sr. no 1 2 3 4 5 Column name p_id name address location p_no Data Type Int(10) Varchar(30) Varchar(50) Int(30) Varchar(20) Constraints Description Primary key Not Null Not Null Foreign key Not null Number of phone operator Name of phone operator Address of phone operator Location of phooperator from loca_id of location phone no of Phooperator

4/29/2013

Next

Phone Operator (Continued)

Sr. no 6 7 8 9 Column name e_id Username Password Joindate Data Type Varchar(40) Varchar(30) Varchar(30) Date Constraints Description Not Null Not Null Not Null Not null Email id of phone operator Username of phone operator Password of phone operator Join date of phone operator

4/29/2013

Go Back

Product Detail
Sr. no 1 2 3 4 5 Column name product_no Productname Price Features Pipath Data Type Int(10) Varchar(30) Int(10) Varchar(40) Varchar(40) Constraints Description Primary key Not Null Not Null Not null Not null Unique Number of product Product name Price of product Feature of product Product image path

4/29/2013

Go Back

Reporting Detail
Sr. no 1 2 3 4 5 6 7 8 Column name r_id cc_id ho_id teamno er_no Reporting rpath date Data Type Int(10) Int(10) Int(10) Int(10) Int(10) Constraints Description Primary key Foreign key Foreign key Foreign key Foreign key Id of reporting Id from ccdetail HO id from ho detail Team id from teamdetail ER id from engineer detail Reporting of visited customer reporting document path of visited customer Date of reporting

Varchar (300) Not null Varchar(30) Date Not null Not null

4/29/2013

Next

Reporting Detail (Continued)

Sr. no 9 10 11 Column name t_replay h_replay t_cr Data Type Varchar(300) Varchar(300) Int(100) Constraints Description Null Null Null Team leader replay to ER for reporting Ho replay to TL for reporting Currently 0 when team leader send replay of report then it will be set to 1 when ER check replay of tl then it will be set as again 0 This will be same as t_cr but work for TL and HO

12

h_cr

Int(100)

Null

4/29/2013

Go Back

Team Detail
Sr. no 1 2 Column name Id Ho_no Data Type Int(10) Int(10) Constraints Description Primary key Foreign key Unique Id of TL detail and also auto increment Id of hodetail

3
4 5

Name
Address Location

Varchar(20)
Varchar(30) Int(10)

Not null
Not null Foreign Key

Name of team leader

Address of team leader Location of team leader form loca_id of location

Ph_no

Varchar(20)

Not null

Phone number of TL

4/29/2013

Next

Team Detail (Continued)

Sr. no 7 8 Column name Aph_no E_id Data Type Varchar(20) Varchar(30) Constraints Description Not null Not null Alternate phone number of TL Email id of TL

9
10 11

username
Password Join date

Varchar(20)
Varchar(20) Date

Not null
Not null Not null

Username of TL
Password of TL Date of join

4/29/2013

Go Back

Snapshots
Cilick Here To View Short Demo Of project

4/29/2013

Go Back

Conclusion & Future Work

Conclusion This site work perfectly at HO , TL , ER, Phone Operator and customer side. Customer do complain succefully. All explained functionality in each module work succefully. Future Work Online Chat in between HO to TL ,TL to Er ,HO to Phone operator ,Customer To Phone operator. Provide feedback facility. Provide selling facility.
4/29/2013 Go Back

Reference
Books Complete Reference for PHP PHP manual EN PHP,MYSQL&FLASH Website www.google.com www.php.net www.w3school.com www.wikipedia.org
4/29/2013 Next

4/29/2013

Finish