SSM framework project sharing "CRM customer management system" Spring+Mybatis+SpringMVC framework project actual combat

Time:2022-8-5

First of all, let's take a look at what is a CRM customer management system?

The CRM system includes some core customer relationship management business functions, such as: potential customers, customer management, visit management, business opportunity management, order management and other modules, to meet the requirements of enterprise customer relationship informatization, and to help enterprises improve the management efficiency of customer resources, Can clearly understand the progress of each project through the project view, and master the overall project data through rich statistical reports

  • CRM is a necessary management system for high enterprises
  • Learning CRM You Can Help Your Business
  • Realize the close connection between business and customers
  • Help companies to increase market share
  • Capture value from a customer's full cycle

https://www.bilibili.com/video/BV1tZ4y1d7kg

The specific technical goals are as follows:

  • Understand the project development process and the main documents and outputs of each stage of project development
  • Master the mainstream SSM framework
  • Learn to use the project management tool Maven
  • Learn to use the version control tool Git
  • Master the deployment of projects under the Linux operating system
  • Master database design principles and techniques
  • Learn how to use cache in your project
  • Master how data is displayed on the page through charts
  • Master the processing of excel files in Java
  • Familiar with front-end development technology and common special effects

From the project you also realize your own value

Helping the management of the enterprise to facilitate the enterprise can treat you badly?

Iron juice~


Function

1. User management module: including user login and logout, save login information, and use encryption to ensure data security.

2. Dictionary module: Manage dictionary types and dictionary values. Store common dictionary types and corresponding dictionary values ​​in redis to improve operating efficiency.

3. Marketing activities: management of marketing activities, support batch processing of marketing activities information using excel file import and export.

4. Lead module: including the management of business leads, remarks related to leads and associated marketing activities. Tracking of leads, converting leads to customers and supporting deal generation at the same time.

5. Statistical chart: Provides a sales funnel function based on the ECharts chart function, and you can view the number of sales opportunities at each stage. At the same time, various charts are provided to show the monthly and weekly growth of leads and the ranking of customer transactions.

6. Deploy online: deploy the operating environment required for the entire project, and install the necessary operating environment (java, MySQL, tomcat, redis) under Linux

Technical point:

  • Front-end: BootStrap+jQuery+date control+bs paging plugin
  • Backend: SpringMVC+MyBatis+Spring+Redis+Echarts+POI
  • Running: Linux(Centos7)+MySQL

Employment advantages:

This project includes basic modules with complete functions, which can be competent for daily development work in actual work. It also includes modules with complex business, which will lay a solid foundation for improving students' logical thinking and dealing with more complex business in future work.

Through the study of the project, I also learned about the process of enterprise software development and code writing specifications, which can enable students to quickly integrate into the development team after employment and become excellent developers who can stand alone.

Course Catalog

• 001.CRM: Course Introduction

• 002.CRM: Introduction to Phases

• 003.CRM: Technical Architecture 1

• 004.CRM: Technical Architecture 2

• 005.CRM: Technical Architecture 3

• 006.CRM: Stage Teaching Purpose

• 007.CRM: Software Development Statement Cycle 1

• 008.CRM: Software Development Statement Cycle 2

• 009.CRM: Software Development Statement Cycle 3

• 010.CRM: Software Development Statement Cycle 4

• 011.CRM: Software Development Statement Cycle 6

•012.CRM: Introduction to CRM Core Business 1

•013.CRM: Introduction to CRM Core Business 2

• 014.CRM: Physical Model Design 1

• 015.CRM: Physical Model Design 2

• 016.CRM: Physical Model Design 3

•017.CRM: Building a Development Environment 1

•018.CRM: Building a Development Environment 3

•019.CRM: Building a Development Environment 5

•020.CRM: Homepage function analysis and design

•021.CRM: Homepage function realizes Controller layer

• 022.CRM: Home page function realizes page layer

•023.CRM: Homepage function test and analysis and design of jumping from homepage to landing page

•024.CRM: Jump from the home page to the login page to realize the Controller layer

• 025.CRM: Jump from the home page to the login page to realize the page layer

• 026.CRM: Login function analysis and design

•027.CRM: Build Mybatis reverse engineering operating environment

• 028.CRM: Run Mybatis reverse engineering to generate UserMapper layer code

• 029.CRM: The login function implements the Mapper layer and the Service layer

• 030.CRM: Login function implements Controller layer

•031.CRM: The login function realizes the page layer and optimizes the login implementation code

•032.CRM: After successful login, the main business page and name will be displayed

• 033.CRM: Realize Enter Login

• 034.CRM: Implement remember password

• 035.CRM: Test remembering passwords

• 036.CRM: Analysis requirements and design of safe exit function

•037.CRM: Implementation of safe exit function

•038.CRM: Requirement analysis of login verification function

•039.CRM: Technical analysis of login verification function

•040.CRM: Implement login verification function

• 041.CRM: Implement login verification function 1

• 042.CRM: Implement login verification function 2

•043.CRM: Test login verification function and analyze page segmentation technology

• 044.CRM: Analyze Workbench Page Structure and Display Workbench Pages

•045.CRM: Realize click on the workbench menu to display the workbench page and market activity demand analysis

• 046.CRM: Introduction to modal windows and their use

• 047.CRM: Design and display the main page of the campaign and the backend of the page

• 048.CRM: Realize the front page of displaying the main page of the campaign

• 049.CRM: Design Save Create Campaign

• 050.CRM: Realize save and create campaign Mapper layer and Service layer

• 051.CRM: Realize Save Create Campaign Controller Layer

• 052.CRM: Realize Save Create Campaign Front Page 1

• 053.CRM: Realize Save Create Campaign Front Page 2

• 054.CRM: Realize Save Create Campaign Front Page 3

• 055.CRM: Test Create Campaign

• 056.CRM: Clear the last created form data when creating a campaign

•057.CRM: Introduction to js calendar plugin and its use

• 058.CRM: Demo bs_datetimepicker calendar plugin

• 059.CRM: Continue to demonstrate bs_datetimepicker calendar plugin

• 060.CRM: Add calendar functionality to create campaigns

•061.CRM: paging query market activity demand analysis

•062.CRM: Paginated Query Marketing Campaign Design

• 063.CRM: Paging query marketing activities to achieve query marketing activities list Mapper layer

• 064.CRM: Paging query marketing activities to achieve query marketing activities list Service layer

•065.CRM: Paging query marketing activities to achieve the total number of query marketing activities Mapper layer and Service layer

• 066.CRM: Paging query marketing activities to achieve Controller layer

• 067.CRM: Paging query campaign front page

• 068.CRM: Paginated Query Campaign Test

• 069.CRM: Realize conditional query marketing activities

• 070.CRM: Review the content of the last lesson

• 071.CRM: Retrofit paging query function

•072.CRM: Realization of CRM Analysis Page Turning Function

• 073.CRM: Introducing the bs_pagination plugin

• 074.CRM: Demonstrate the use of the bs_pagination plugin

• 075.CRM: Detailed explanation of bs_pagination plugin parameters

•076.CRM: Realize page turning query of marketing activities

• 077.CRM: Realize that the number of pieces displayed per page of bs_datetimepicker remains unchanged

•078.CRM: Realize that the number of displayed items per page remains unchanged when refreshing the campaign list

• 079.CRM: Delete Marketing Activity Demand Analysis

• 080.CRM: Remove Campaign Design

• 081.CRM: Realize the selection and cancellation of all marketing activities 1

• 082.CRM: Implementing select-all and deselect-all marketing campaigns 2

• 083.CRM: Implementing select-all and de-select-all marketing campaigns 3

• 084.CRM: Implementing select-all and deselect-all marketing campaigns 4

• 085.CRM: Review Delete Campaign Process

• 086.CRM: Delete marketing activities to implement Mapper layer and Service layer

• 087.CRM: Remove Campaign Implementation Controller Layer

• 088.CRM: delete campaign to achieve front page

• 089.CRM: Modify Marketing Activity Demand Analysis

• 090.CRM: Revise Campaign Design

• 091.CRM: Modify marketing activities to achieve Mapper layer and Service layer

• 092.CRM: Modify the campaign to implement the Controller layer

• 093.CRM: Modify the marketing activities to realize the front page

• 094.CRM: Design Save Modified Campaigns

• 095.CRM: Realize the Mapper layer and Service layer for saving and modifying the marketing activities

• 096.CRM: Implement the campaign Controller layer that saves changes

• 097.CRM: Realize the front page of the campaign to save the modifications

• 098.CRM: Test Modification Campaign

•099.CRM: Analysis and export of application scenarios of marketing activities

• 100.CRM: Export market activity demand analysis

• 101.CRM: Analyse the realization of export marketing activities

• 102.CRM: Introducing the apache-poi plugin

• 103.CRM: Introduce the use of apache-poi plugin

• 104.CRM: Demonstrate the use of apache-poi to generate excel files

• 105.CRM: Use apache-poi to modify the effect of excel files

• 106.CRM: Demo file download

• 107.CRM: Test file download function

• 108.CRM: Design Export Marketing Campaign

• 109.CRM: Realize export marketing activity Mapper layer and Service layer

• 110.CRM: Implement Export Campaign Controller Layer 1

• 111.CRM: Implement Export Campaign Controller Layer 2

• 112.CRM: Realize Export Campaign Controller Layer 3

• 113.CRM: Realize the export of the front page of the marketing campaign

• 114.CRM: Test Export Campaign

• 115.CRM: Optimizing export marketing activities

• 116. CRM: Analysis Selection Export Marketing Campaign

• 117.CRM: Import Marketing Activity Demand Analysis

• 118. CRM: Analysis of the implementation of import marketing activities

• 119.CRM: Presentation file upload 1

• 120.CRM: Presentation file upload 2

• 121.CRM: Presentation file upload 3

• 122.CRM: Presentation file upload 4

• 123.CRM: Demonstrate parsing excel files using apache-poi

• 124.CRM: Design and import marketing activities

• 125.CRM: Realize importing campaign Controller layer

• 126.CRM: Realize the front page of importing marketing activities

• 127.CRM: Optimizing Import Marketing Activities

• 128.CRM: Realize the Mapper layer and the Service layer to view the details of the marketing activities and query the remarks information

• 129.CRM: Realize the front page of viewing the details of marketing activities

• 130.CRM: Add campaign notes to implement Controller layer

• 131.CRM: Add marketing activity notes to realize the front page

• 132.CRM: Delete campaign notes to implement Mapper layer and Service layer

• 133.CRM: Modify the design of marketing activities

• 134.CRM: Realize the front page of saving the modified marketing activity notes

• 135. CRM: Design and Use of Analytical Data Dictionary Tables

• 136.CRM: Create leads to achieve display lead main page front page

• 137.CRM: Analyze the relationship between leads and marketing activities

• 138.CRM: Realize the Mapper layer and Service layer associated with viewing lead details and query related marketing activities

• 139.CRM: Lead Relevance Marketing Campaign Design

• 140.CRM: Test Lead Relevance Campaign Search Campaign

• 141.CRM: Implement the Controller layer for saving leads associated with marketing activities

• 142.CRM: Disassociate leads from marketing activities to implement Controller layer

• 143. CRM: Lead Conversion Demand Analysis

• 144. CRM: Design campaign feeds to be searchable

• 145. CRM: Realize that the campaign source is searchable on the front page

• 146. CRM: Realize save leads conversion backend

• 147.CRM: Realize Save Lead Conversion Background 2

• 148.CRM: Realize save lead conversion backend 6

• 149.CRM: Realize save lead conversion backend 9

• 150.CRM: Test Lead Conversion

• 151.CRM: Realize the creation of transaction display transaction main page Controller layer

• 152. CRM: Analysis possibilities are configurable

• 153.CRM: Implementation possibility is configurable Controller layer

• 154.CRM: Demonstrate the bs_typeahead auto-completion plugin

• 155.CRM: Realize the transaction service layer created by saving

• 156.CRM: View transaction details design

• 157.CRM: View transaction details to achieve front page

• 158.CRM: Realize the display of transaction icon information

• 159.CRM: Introduction to Statistical Icon Technology

•160.CRM: Interpretation of Echarts funnel chart parameters

• 161.CRM: Demo Echarts display funnel chart

•162.CRM: Transaction Statistics Icon Design

• 163.CRM: The transaction statistics icon is implemented to display the transaction statistics icon page

• 164.CRM: The transaction statistics icon implements the Mapper layer

• 165.CRM: The transaction statistics icon realizes the Service layer

• 166.CRM: transaction statistics icon to implement Controller layer

• 167.CRM: The transaction statistics icon realizes the front page

• 168.CRM: Test transaction statistics icon