A 55-page system report for an intelligent e-commerce recommendation application, covering recommendation logic and end-to-end software design.
55p
system report
04
behaviour types
Top-N
recommendation output
01 / Overview
What this package actually contains.
The intelligent e-commerce coursework implements a Spring Boot application with product browsing, user behaviour tracking, ratings and multiple recommendation strategies, including user-based collaborative filtering and fallback hot-product recommendations.
Objectives
01Track views, favourites, cart activity and purchases as weighted behaviour signals.
02Implement user-user collaborative filtering with a Pearson correlation similarity.
03Provide product-based, personalised and fallback recommendations in a web application.
Product mechanics
User surface, mechanism, automation.
The system is explained through its modules and the behaviour they enable.
Module01
Spring Boot UI
Product, profile, rating and recommendation screens.
Module02
Behaviour events
View, favourite, cart and purchase signals with scores.
Module03
User-item matrix
Aggregated ratings and behaviour weights by user/product.
Module04
Similarity
Pearson correlation over users with common products.
Module05
Ranking
Weighted candidate scores, normalisation and Top-N output.
02 / Package highlights
What this work demonstrates.
Connects recommendation algorithms with application structure and user flows.
Shows a larger software-engineering deliverable beyond notebook analysis.
Includes the full report and source archive for technical review.
03 / Mechanism
How the product works end to end.
01
Behaviour becomes a rating
Explicit ratings and implicit actions are combined into a user-product score matrix. Each event type contributes a different weight, so a purchase can count more strongly than a view while still being normalised through the recommendation formula.
02
Collaborative filtering
For a target user, the service calculates Pearson correlation against every other user who shares at least two products. Positive similarities are retained, unseen products are scored by similarity × rating, and the final candidate score is divided by the sum of absolute similarities.
A minimum of two common products avoids unstable correlations.
Products already seen by the target user are excluded.
If collaborative filtering cannot produce enough candidates, hot-product recommendation is used as a fallback.
03
Application integration
The recommendation service is wired into Spring MVC controllers, MyBatis mappers, Thymeleaf templates and MySQL. This makes the project a complete application rather than an isolated algorithm notebook.
04 / Key code
Key product and contract logic.
Only verified source excerpts and pseudocode taken from the project papers are shown.
Verified project codeJava
Pearson similarity
Original Java excerpt from the recommendation service.