How normancao2702/cmpt213-asgn5-courseplanner works
Project type and purpose
• This is a full-stack web application (“Course Planner”) built with Spring Boot.
• Purpose: load term/course data from CSV files into an in-memory model, expose REST endpoints for browsing courses, departments, offerings, watchers, stats, and serve a static JavaScript/HTML UI under “public.”
File structure
• Top-level
• build.gradle / gradlew* / gradle/… → standard Gradle/Spring Boot build
• src/main/java/ca/cmpt213/courseplanner → back-end code
• public → front-end static assets (HTML, CSS, JS)
• data → CSV files as the data source
• docs → curl examples and sample outputs
• Within src/main/java:
• controllers package → REST controllers (About, Department, CourseOffering, Stats, Watcher, DumpModel)
• dto package → Data Transfer Objects shaping JSON responses
• models package → domain classes (Department, Course, CourseOffering, Section, Watcher) and central ModelManager
• utils package → CSVDataProcessor, CSVReader, TermCodeConverter for data ingestion
README insights
• Five stages: project setup, core model, basic API, advanced watcher/stats features, testing
• Confirms MVC structure: models loaded via utils → controllers expose API → static UI calls those endpoints
Detail
• DTO translation step between model and HTTP response