CRM stands for Customer Relationship Management. It is a process or methodology used to learn more about customers' needs and behaviors in order to develop stronger relationships with them. There are many technological components to CRM, but thinking about CRM in primarily technological terms is a mistake. The more useful way to think about CRM is as a process that will help bring together lots of pieces of information about customers, sales, marketing effectiveness, responsiveness and market trends.
A CRM is a collection of people, processes, software, and internet capabilities that helps an enterprise manage customer relationship effectively and systematically.
Modules of project
01- Login Module
02- Customer Master
03- Employee Master
04- Customer/Employee Report
05- Ticket Master
06- Ticket Allocation
07- Service Detail
08- Service Report
02- Customer Master
03- Employee Master
04- Customer/Employee Report
05- Ticket Master
06- Ticket Allocation
07- Service Detail
08- Service Report
Project abstract
Introduction
CRM helps businesses use technology and human resources to gain insight into the behavior of customers and the value of those customers.
Objective
The goal of CRM is to understand and anticipate the needs of current and potential customer to increase customer retention and loyalty while optimizing the way product and services are sold.CRM stands for Customer Relationship Management.
Software requirements
Front End: - Microsoft Internet Explorer 6 or above.
Middleware: - Internet Information Services (IIS)-6, Microsoft .Net Framework 3.5, SMTP Server, SMS Gateway.
Back End: - Microsoft SQL Server 2005.
Development Tool: - Microsoft Visual Studio-2005,Adobe Photoshop-9, Cute FTP.
Analysis Tool: - COCOMOII2000, Code Counter
Software Engineering Model Applied
The S/W Engineering Model used here is a combination of Spiral Model and Component Based Model because no single model can serve all the purpose for the development of the software, that’s why we are considering some features of “Spiral Model” and some features of “Component Based Model”.
The combinations of these two models form a “Hybrid Model”.
The Spiral Model
The spiral model, proposed by Boehm, is an evolutionary software process model that couples the iterative nature of prototyping with the controlled and systematic aspects of the linear sequential model. It provides the potential for rapid development of incremental versions of the software. Using the spiral model, software is developed in a series of incremental releases. During early iterations, the incremental release might be a paper model or prototype. During later iterations, increasingly more complete versions of the engineered system are produced.
A spiral model is divided into six task regions:
• Customer communication—tasks required to establish effective communication between developer and customer.
• Planning—tasks required to define resources, timelines, and other project related information.
• Risk analysis—tasks required to assess both technical and management risks.
• Engineering—tasks required to build one or more representations of the application.
• Construction and release—tasks required to construct, test, install, and provide user support and training).
• Customer evaluation—tasks required to obtain customer feedback based on evaluation of the software representations created during the engineering stage and implemented during the installation stage.
The combinations of these two models form a “Hybrid Model”.
The Spiral Model
The spiral model, proposed by Boehm, is an evolutionary software process model that couples the iterative nature of prototyping with the controlled and systematic aspects of the linear sequential model. It provides the potential for rapid development of incremental versions of the software. Using the spiral model, software is developed in a series of incremental releases. During early iterations, the incremental release might be a paper model or prototype. During later iterations, increasingly more complete versions of the engineered system are produced.
A spiral model is divided into six task regions:
• Customer communication—tasks required to establish effective communication between developer and customer.
• Planning—tasks required to define resources, timelines, and other project related information.
• Risk analysis—tasks required to assess both technical and management risks.
• Engineering—tasks required to build one or more representations of the application.
• Construction and release—tasks required to construct, test, install, and provide user support and training).
• Customer evaluation—tasks required to obtain customer feedback based on evaluation of the software representations created during the engineering stage and implemented during the installation stage.
To view online demo of Customer Relationship Management System project leave a comment below with your Email id, or send us email at projects602@gmail.com we will send you link of online demo video of this project
Details of Purchasing This Project
Project Code :: 11
Project Code ::Web
Technology :: ASP.NET - C#,SQL Server,Java Script,Crystal Report
Project Cost :: Rs.(INR) 1200/-
>>Click Here to Buy<<
-------------------------------------------------------------------------------------------------
keywords
Readymade Project, Academic Projects in Visual Basic, VB.NET, C#, ASP.NET, SQL Server Source Code for final year student, project of BE, BSC-IT, BCA, MCA, MBA.Project Synopsis, Flow Chart, DFD, Requirement, Documentation,Live Project,Synopsis Academic Project Readymade Project BTech BCA MCA MBA Bsc-IT MS BIT ADIT DOEACC IGNOU SMU Live Project in Asp.NET,VB.NET, C#,Visual Basic
Readymade Project, Academic Projects in Visual Basic, VB.NET, C#, ASP.NET, SQL Server Source Code for final year student, project of BE, BSC-IT, BCA, MCA, MBA.Project Synopsis, Flow Chart, DFD, Requirement, Documentation,Live Project,Synopsis Academic Project Readymade Project BTech BCA MCA MBA Bsc-IT MS BIT ADIT DOEACC IGNOU SMU Live Project in Asp.NET,VB.NET, C#,Visual Basic
Posted in: ASP.NET Projects
