Anzeige
Anzeige

Más contenido relacionado

Anzeige

Customer relationship management

  1. CUSTOMER RELATIONSHIP MANAGEMENT (For An Automobile Industry) TECNIA INSTITUTE OF ADVANCED STUDIES SESSION: 2014-2015 SUBMITTED BY: ROHIT GUPTA SUBMITTED TO: GURU GOBIND SINGH INDRAPRATHA UNIVERSITY
  2. OBJECTIVE AND SCOPE OBJECTIVE IS: • To simplify marketing and sales process. • To provide better customer service. • The scope of the project CRM system is concerned with the development and maintenance of mutually beneficial relationships with some system. This system can help to attract new customers which can help in increasing the sales of the products of the Automobile Industry. Due to automation of many loopholes that exist in the manual maintenance of the records can be removed. The speed of obtaining and processing the system will be fast.
  3. TASKS PERFORMED • Automobile Industry Management System. • List of Brands and Models of the Automobile Industry. • Customer List Management System. • Parts of Automobiles Management System. • Work System and Management of an Automobile Industry. • Insurance system of the vehicle. • Bill Management system
  4. EASY TO USE: • Fill the login form by administrator. • Choose the task to be performed. • The task you chose, select to search for the data or enter and update the new data in the database. • Save the records of the customer. • Save the records of the vehicle which came for servicing. • Open the insurance form and fill the details to make the Insurance of the vehicle used by the customer if needed. • Make the bill of the vehicle of the customer using Bill Management system.
  5. SYSTEM ANALYSIS • If the feasibility study is to serve as decision document, it must answer three key questions: - • * Is there new and better way to do a job that will benefit the user? • * What are the cost and saving of the alternatives? • * What is recommended?
  6. • The most successful system projects are not necessary or most visible in business but rather those that truly need user expectations. More projects failed because of inflated expectations than for any other reasons.
  7. SYSTEM DESIGN • Data design: It transforms the information domain model created during analysis into the data structure that will be required to implement the software. • Architectural Design: It defines the relationship among major structural elements of the program. • Interface Design: It describes how the software communicates within itself, to systems that interoperate with it and with humans who use it. • Procedural design: It transforms the structure elements of the program architecture into a procedural description of software components.
  8. HARDWARE SPECIFICATION HARDWARE REQUIREMENT PROCESSOR Compatible with PENTIUM P4 processors and above. RAM 64MB or more
  9. SOFTWARE SPECIFICATION OPERATING SYSTEM WINDOWS 98/2000/XP/VISTA/7 or WINDOWS 2000 SERVERS TECHNOLOGY JAVA S.E. 7.0 DATABASE SERVER SQL SERVER SOFTWARE NETBEANS 7.0 or ECLIPSE
  10. SYSTEM IMPLEMENTATION • The implementation phase is less creative than system design. It is primarily concerned with user training and site preparation and file conversion. When the system is linked to terminal or remote sites, the telecommunication network and test of the network along with the system are also included under implemented. • During the final testing, user acceptance is tested, followed by use training. Depending on the nature of the system, extensive user training may be required. • Conversion usually takes place at about the same time the user is being trained or later.
  11. SOFTWARE DEVELOPMENT LIFE CYCLE
  12. ER DIAGRAMS Admin CRM System process Output
  13. SCREEN-SHOTS
  14. LOGIN FORM
  15. ADMIN FORM
  16. VEHICLE FOR SERVICE FORM
  17. DEPARTURE FORM
  18. CUSTOMER FORM
  19. BRAND FORM
  20. VEHICLE FORM
  21. MODELS FORM
  22. PARTS FORM
  23. SERVICE FORM
  24. INSURANCE FORM
  25. DEPARTMENT FORM
  26. DESIGNATION FORM
  27. EMPLOYEE FORM
  28. BILL MANAGEMENT FORM
  29. TESTING • Black box testing methods focus on the functional requirements of the software. That is black box testing enables the software engineer to derive sets of input conditions that will fully exercise all functional requirements for a program. This approach is likely to uncover a different class of errors than white box methods.
  30. • Black box testing attempts to find errors in the following categories: • Incorrect or missing functions • Interface errors • Error in data structures or external database access. • Performance errors. • Initialization and termination errors
  31. • Unlike white box testing, which is performed early in the testing process, black box testing tends to be applied during later design Tests to designed to answer the following questions.  What classes of input will make good test cases?  How is functional validity tested?  Is the system particularly sensitive to certain input values?  How are the boundaries of a data class isolated?  What data rates and data volume can the system tolerate?  What effects will specific combinations of data have on system operations?
  32. CONCLUSION • Finally concluding this project and project report we hereby declare that this application is definitely going to help to the people who are intended to study the data structures as subject. Product will give the clear knowledge to the users about how the data structure algorithms are performed. In this way with the help of this project a teacher will be able to explain the logics of the algorithms and student will be able to understand them. In this module the section of linear data structure are taken in implementation. Linear and non- linear data structures with insertion and deletion algorithms are implemented successfully. • The application is extremely user friendly. Even a person having no knowledge of the different software used can easily access it. The entire application supports Graphical User Interface which further enhances its utility.
  33. BIBLOGRAPHY • www.w3cschools.com • www.wikipedia.com • www.java.sun.com • Introduction to Data Structures using ‘C’ by R.S.Salaria • The Complete Reference “JAVA” • Internet & java programming by R.Krishnamoorthy • Software Engineering –A practitioners approach by Pressman S. Roger • Software Project Management: A practitioner’s Approach by Bennatan, E.M.
Anzeige