Professional Documents
Culture Documents
An Introduction
1 . A b ou t O r gan iz ation :
2. About Project:
Since the advent of computer and information
technology in the last two decades, every organization and
The Online Customer Care Service
individual wants the web-based services as it is convenient to
use and easily accessible from any where in the world. The
computerization has many benefits. Primarily a computer is
helpful in four major aspects of any kind of organization:
• Time Efficiency
• Cost Effective
• Huge data storage capacity and
• Simple operation
Project Objective
P ROJECT CATEGORY
What is ASP.NET?
ASP.NET is a programming framework built on the common
language runtime that can be used on a server to build
powerful Web applications. ASP.NET offers several important
advantages over previous Web development models.
REQUIREMENT SPECIFICATION
Platform : Windows
The Operating System :Windows 2000 Server/XP/NT
Family
Framework :ASP.NET FRAMEWORK 1.1
Front-End Tool :ASP.NET With VB.NET
Editing tool :MICROSOFT Visual Studio Dot
Net
Scripting :C#
Interface :HTML, XML(STYLE SHEET (.XSL),XML
Server :Internet Information Server
Back-End Tool :SQL SERVER 2000
HARDWARE
Processor :Intel Pentium III, IV 2.1 GHZ
PROGRAM STRUCTURE
Analysis Report:
Registration
• User may register itself to get the services against any
product or services.
• He gets registered with the unique id and
password.
The Online Customer Care Service
• One can register for one or more product or
services.
• At the end of registration if the user is a general user
(Customer) he is linked to the e transaction module where
he could pay the requisite amount to be the proud member of
the site, which is being specified on the main page. If he
successfully pays the fee then he is given his login and
password to access the site and if not then he is provided
access for a trial period of a month and asked to pay the
fee through draft or do a e transaction as he is linked
directly to his bank website and all the necessary status
is taken so to know the genuinely of the user.
0 LEVEL D.F.D.:-
This is the context level D.F.D. of the proposed system the
whole system has been depicted in a single bubble, primary
input and output has been carefully noted and depicted in the
way so that information flow continuity should not be lost in
the next level. The purposed system is shown as a whole
process and the inputs and outputs are shown with incoming and
outgoing arrow from the system.
Control panel
display
Display email
Project Modules
The proposed website will have its main page and will be
mainly divided into
14 Modules partially dependent and partially independent
Modules are
1. LOGIN MASTER
2. USER REGISTRATION MASTER
3. THE MASTER MAINTAINANCE
4. ONLINE COMPLAIN REGISTRATION
5. ONLINE COMPLAIN MANAGEMENT
6. ONLINE SUPPORT SERVICES
7. ONLINE MONITORING SYSTEM
Modules are divided in two parts first seven part is taken by
my team member and rest is taken by me.
TECHNICAL SPECIFICATIONS
This module is one of the biggest of all and will contain many
sub modules basically dealing with interaction between end
user and customer care executive. This module contains the array
manipulation technology and frame based information
maintenance for a viable interactive chat system.
VALIDATION MASTER
DOCUMENT MODELER
Site Summary
1. USER MASTER
2. PRODUCT MASTER
3. SERVICES MASTER
4. SERVICE PROVIDER MASTER
4.AUTHORITY MASTER
5. STATE MASTER
6. COUNRY MASTER
7. PRODUCT SEARCH PAGE
The Online Customer Care Service
9. SERVICES SEARCH PAGE.
10. PRODUCT SPECIFICATION PAGE.
11. SERVICES DETAIL PAGE
12. CONTROL PANEL
14. SERVICE PROVIDER INFORMATION PAGE
a. USER INFORMATION PAGE.
B. LOCAL MAIL PROMPTER
C. INBOX PAGES
D. MAIL COMPOSER
e. CHAT INTERACTION PAGES.
Most of the page, which are dynamically created when
the client request for the page using the robustness
of ASP.NET framework (VB.NET) blended with the
simplicity of HTML and versatility of XML.
Table Structure: There will be 16 tables, the form of the table with their structure is
described as under: -
Table 1: User Details
Table 2: UserMaster
Table 3: ServiceProviderMaster
Table 5: Authorization
Table 7: Country
Table 8: State
FUTURE SCOPE
It is directly dependent on the lay stone of the project
that is we will have to design a system which when the time
passes having a better system initially should not become a
joke later.
It is highly likely that the scope will change as the web
application project moves forward; the web e-process model
should be incremental. This allows the development team to
“freeze” the scope for one increment so that an operational
web application release can be created. The next increment
may scope changes suggested by a review of the preceding
increment, but once the second increment commences, scope
is again frozen temporarily. This approach enables the Web-
App team to work without having to accommodate a continual
stream of changes but still recognizes the continuous
evolution characteristics of most web application. Besides
that, the following basic quality in the software always
safeguards the future scope of the software.