I.

Easy-level Topics
Topic 1: Campus Notice & Reading Feedback
System
Difficulty: Easy

The Campus Notice & Reading Feedback System is designed for daily
information publishing and management scenarios in schools, colleges,
and classes. It aims to address issues in traditional notice delivery
methods such as unclear target audiences, difficulty in tracking
reading status, and inability to identify students who haven't read
notices in a timely manner. Through a web application, the system
implements online notice publishing, category management, targeted
delivery, student viewing, read confirmation, and reading statistics.

This system primarily serves three types of users:

administrators, teachers, and students. Administrators are
responsible for maintaining basic information such as users, classes,
and notice categories. Teachers can publish notices to all students,
designated classes, or designated students as needed. After logging
in, students can view notices relevant to them and perform “confirm
read” actions for important notices. The system records students'
reading times and provides teachers with statistics such as read
count, unread lists by class, and class reading rates.

Through the development of this topic, students can

comprehensively apply web development technologies such as Java,
Servlet/JSP, JDBC, MySQL, HTML, CSS, JavaScript, and Ajax to build an
information publishing and feedback system with practical application
value. Although the overall business logic is not complex, this topic
requires students to implement targeted publishing, read
confirmation, statistical analysis, and permission control on top of
basic CRUD operations, making it suitable as an easy-to-medium
difficulty web application system design training topic.

Main Features

1. User Login & Role Differentiation

o Administrator
o Teacher
 o Student
2. Notice Publishing
o Title, Content, Category, Publish Time
o File attachment support
o Selectable target audience: all students, designated
class, designated user
3. Notice Display
o Students view notices visible to themselves
o Support query by title, category, and time
o Support paginated display
4. Read Confirmation
o Student clicks "Confirm Read"
o System records reading time
o Prevent duplicate confirmation
5. Reading Statistics
o Teacher or admin views read count
o View list of unread students
o Calculate reading rate by class
6. Backend Management
o Edit and delete notices
o Manage notice categories
o Manage users and classes

Recommended Technologies

Servlet + JSP + JDBC + MySQL

or Spring Boot + JSP / Thymeleaf + MySQL
Frontend: HTML, CSS, JavaScript, Ajax.

10-Day Workload Schedule

DURATI
PHASE TASKS
ON
JAVA Design User, Notice, ReadRecord, ClassInfo
FOUNDATION 3 days classes; implement notice object and
TRAINING reading record logic
WEB Implement login, notice publishing,
DEVELOPMENT 6 days targeted display, read confirmation,
TRAINING reading statistics, backend management
Prepare system demo, database design, test
FINAL DEFENSE 1 day
cases, and defense PPT

Minimum Acceptance Requirements

 1. Can log in and differentiate roles
2. Teacher or admin can publish notices
3. Students can only see notices relevant to themselves
4. Students can confirm read
5. Teachers can view reading statistics
6. Has database design and test cases

Bonus Features

1. File upload
2. Ajax real-time refresh of reading status
3. Unread reminders
4. Excel export of unread list

Topic 2: Class Student Info & Growth Portfolio

Management System
Difficulty: Easy

The Class Student Info & Growth Portfolio Management System is

designed for university class student management and student growth
process recording scenarios. It aims to achieve centralized,
standardized, and digital management of basic student information,
award records, competition experiences, volunteer service, leadership
positions, disciplinary records, and other content. The system helps
homeroom teachers, counselors, or instructors gain a more
comprehensive understanding of student growth, and also facilitates
students' continuous recording and maintenance of their personal
growth experiences.

This system primarily includes three types of users:

administrators, teachers, and students. Administrators are
responsible for maintaining classes, users, and basic data. Teachers
are responsible for viewing student information, reviewing growth
portfolio records submitted by students, and managing related
materials. Students can log into the system to view personal
information, submit growth records such as awards, competitions, and
volunteer service, and upload corresponding supporting documents.
After teacher approval, the relevant records are officially added to
the student's growth portfolio.
 This topic not only requires students to complete basic student
information management, but also requires implementation of growth
portfolio submission, teacher review, categorized querying, and data
statistics. Through system development, students can train abilities
in Java object-oriented modeling, database design, form submission,
file upload, role-based permission control, and data statistics. This
topic is suitable for groups with relatively average foundations who
wish to complete a relatively complete business system.

Main Features

1. User Login & Role Management

o Administrator
o Homeroom Teacher / Instructor
o Student
2. Student Basic Information Management
o Student ID, Name, Gender, Class, Contact Info
o Home Address, Dormitory, Email, and other extended info
3. Growth Portfolio Management
o Award Records
o Competition Experience
o Volunteer Service
o Disciplinary Records
o Leadership Position Experience
4. Students maintain partial personal info
o Edit contact info
o View personal growth portfolio
o Upload supporting documents
5. Teacher reviews portfolio records
o Approve
o Reject
o Provide review comments
6. Conditional Query & Statistics
o Query by class
o Query by award type
o Statistics on student growth record count by academic
year
o Statistics on award recipients by class

Recommended Technologies

Servlet + JSP + JDBC + MySQL

Spring Boot optional.
Frontend can use Ajax for student ID duplicate detection and dynamic
queries.

10-Day Workload Schedule

PHASE DURAT TASKS

ION
JAVA 3 Design Student, ArchiveRecord, Award,
FOUNDATION days Punishment, User classes
TRAINING
WEB 6 Complete student management, portfolio
DEVELOPMENT days submission, teacher review, query
TRAINING statistics, file upload
FINAL DEFENSE 1 day Prepare project report, data tables, flow
charts, demo data

Minimum Acceptance Requirements

1. Student info CRUD

2. Student growth record submission
3. Teacher review
4. Conditional query
5. Simple statistics
6. Permission control

Bonus Features

1. File upload
2. Portfolio record export
3. ECharts chart statistics
4. Operation log recording

II. Medium-level Topics

Topic 3: Course Assignment Publishing,
Submission & Grading Feedback System
Difficulty: Medium

The Course Assignment Publishing, Submission & Grading Feedback

System is designed for assignment management needs in university
course teaching processes. It aims to address issues in traditional
homework assignment, submission, grading, and score feedback
processes such as low efficiency, difficult statistics, and
incomplete process records. Through a web platform, the system
implements complete workflows including teacher assignment
publishing, student online submission, teacher grading and feedback,
student score viewing, and submission statistics.
This system primarily serves three types of users:
administrators, teachers, and students. Administrators manage course,
class, and user information. Teachers can create course assignments,
set assignment content, deadlines, maximum scores, whether late
submission is allowed, and whether resubmission is allowed. Students
can view course assignments, fill in assignment content online or
upload attachments, and view submission status, teacher comments, and
scores. Teachers can view student submission status, grade
assignments, write feedback, and return assignments requiring
students to resubmit.
The core of this topic lies in complete assignment status flow
and process management, including statuses such as unsubmitted,
submitted, late, graded, and returned. Additionally, the system
should provide statistical functions such as submission rate, late
submission count, average score, and score distribution. Through the
development of this topic, students can master typical web
application techniques involving multi-role collaboration, time-based
judgment, status management, file uploads, data statistics, and
exception handling, making it suitable as a medium-to-upper
difficulty training topic.

Main Features
 1. Role Management
o Administrator
o Teacher
o Student
2. Course & Class Management
o Manage courses
o Manage classes
o Teacher binds to course
o Student joins class or course
3. Assignment Publishing
o Assignment title, content, attachments
o Start time, deadline
o Maximum score
o Allow late submission
o Allow resubmission
4. Student Submission
o Online text entry
o Upload attachments
o View submission status
o Support resubmission with historical version retention
5. Teacher Grading
o View submission list
o Grading
o Write comments
o Mark excellent assignments
o Return for resubmission
6. Status Management
o Not Started
o In Progress
o Closed
o Unsubmitted
o Submitted
o Graded
o Returned
7. Statistical Analysis
o Submission rate
o Late submission count
o Average score
o Score distribution statistics
o List of students who haven't submitted

Recommended Technologies
Servlet + JSP + JDBC + MySQL
or Spring Boot + MySQL.
Recommend using Ajax for assignment status refresh and submission
detection.

10-Day Workload Schedule

DURAT
PHASE TASKS
ION
JAVA Complete User, Course, Homework, Submission,
3
FOUNDATION Score class design; focus on time-based
days
TRAINING judgment and status flow
WEB Complete assignment publishing, submission,
6
DEVELOPMENT historical versions, grading, return,
days
TRAINING statistical analysis
Prepare complete demo workflow, test cases,
FINAL DEFENSE 1 day
project management description

Minimum Acceptance Requirements

1. Teacher can publish assignments

2. Student can submit assignments
3. System can determine late submission
4. Teacher can grade and give feedback
5. Student can view scores
6. Teacher can view submission statistics

Bonus Features

1. Assignment file attachment upload

2. Multi-version submission records
3. Excel export of scores
4. Chart display of score distribution
5. Ajax submission status detection

Topic 4: Campus Activity Registration, Review

& Points Management System
Difficulty: Medium

The Campus Activity Registration, Review & Points Management

System is designed for campus activity management scenarios such as
second classroom activities, club activities, volunteer services, and
lecture registration in universities. It aims to achieve full-process
information management of activity publishing, student registration,
registration review, on-site check-in, points recording, and activity
statistics. The system improves campus activity organization
efficiency, reduces manual statistical workload, and provides data
support for students' comprehensive quality evaluation.

This system primarily includes three types of users: students,

activity organizers, and administrators. Administrators manage users,
activity categories, and system basic information. Activity
organizers can publish activities, set activity time, location,
maximum registration count, registration deadline, activity points,
and activity categories. Students can browse activity information and
register online. The system needs to determine whether a student has
registered multiple times, whether registration exceeds the maximum
limit, and can further determine whether the activity time conflicts
with activities the student has already registered for. After the
activity organizer approves the registration, students can officially
participate in the activity.

After the activity ends, the system supports activity check-in

and points distribution. Students who successfully check in receive
corresponding activity points. The system records student activity
participation and provides functions such as personal points inquiry,
activity registration statistics, check-in count statistics, absence
count statistics, and points leaderboard. Through this topic
development, students can train abilities in complex business process
design, registration rule judgment, review process control, check-in
management, points calculation, and data statistical analysis, making
it suitable as a medium-to-upper difficulty web application system
training topic.

Main Features

1. User Login & Role Management

o Student
o Activity Organizer
o Administrator
2. Activity Publishing
o Activity name
o Activity location
o Activity time
o Registration start and end time
 o Maximum participants
o Activity points
o Activity category
3. Activity Registration
o Student registers for activity
o Check if maximum capacity exceeded
o Check for duplicate registration
o Check for time conflict with registered activities
4. Registration Review
o Activity organizer reviews registration
o Approve, Reject
o Provide review comments
5. Activity Check-in
o Activity organizer manually checks in
o Or use check-in code
o System records check-in time
6. Points Management
o Receive activity points after successful check-in
o Student views personal points
o Admin views points ranking
7. Data Statistics
o Activity registration count
o Check-in count
o Absence count
o Participant count by activity type
o Student points leaderboard

Recommended Technologies

Servlet + JSP + JDBC + MySQL

or Spring Boot + MySQL.
Can use Ajax for real-time registration count updates.

10-Day Workload Schedule

PHASE DURA TASKS

TION
JAVA 3 Design Activity, ApplyRecord, SignRecord,
FOUNDATION days PointRecord, User classes; implement
TRAINING registration conflict detection
WEB 6 Complete activity publishing, registration,
DEVELOPMENT days review, check-in, points, ranking,
TRAINING statistics
FINAL DEFENSE 1 Prepare activity workflow demo, test data,
 day and defense materials

Minimum Acceptance Requirements

1. Can publish activities

2. Student can register
3. System can check max capacity and duplicate registration
4. Activity organizer can review
5. Can check in
6. Can generate points and rankings

Bonus Features

1. Time conflict detection

2. Check-in code
3. Activity points leaderboard
4. ECharts statistical charts
5. Excel export of activity participant list

III. Difficult-level Topics

Topic 5: Online Exam, Question Bank &
Intelligent Test Assembly System
Difficulty: Difficult

A typical online exam system can be quickly completed by large

language models, so additional requirements such as "question bank
categorization, difficulty coefficients, test assembly rules, exam
records, automatic grading, and score analysis" are added here.

Main Features

1. Role Management
o Administrator
o Teacher
o Student
2. Question Bank Management
o Single Choice
o Multiple Choice
o True/False
o Fill-in-the-blank
 o Question categorization
o Difficulty level
o Score setting
3. Exam Paper Management
o Teacher creates exam paper
o Support manual question selection
o Support rule-based test assembly
o E.g., 10 single choice, 5 multiple choice, 5 true/false
o Support setting exam time, duration, and total score
4. Online Exam
o Student enters exam
o Display countdown timer
o Save answer records
o Auto-submit when time expires
o Prevent duplicate submission
5. Automatic Grading
o Auto-grade objective questions
o Fill-in-the-blank can be matched against standard answers
o Auto-calculate total score
6. Score Analysis
o Student views scores
o Teacher views class scores
o Average, highest, lowest scores
o Correct rate per question
o Score range statistics
7. Wrong Answer Records
o Student views wrong answers
o Display correct answers
o Display question explanations

Recommended Technologies

Servlet + JSP + JDBC + MySQL

or Spring Boot + MySQL.
Frontend uses JavaScript for countdown, Ajax for temporary save or
submission detection.

10-Day Workload Schedule

PHASE DURATI TASKS

ON
JAVA 3 days Design Question, Paper, Exam, AnswerRecord,
FOUNDATION ScoreRecord classes; implement grading
TRAINING algorithm and test assembly logic
WEB 6 days Complete question bank, test assembly, exam,
DEVELOPMENT submission, grading, score analysis, wrong
TRAINING answer records
FINAL DEFENSE 1 day Prepare test papers, exam process demo,
database design, and test report

Minimum Acceptance Requirements

1. Teacher can maintain question bank

2. Teacher can create exam paper
3. Student can take online exam
4. System can auto-grade
5. Student can view scores
6. Teacher can view score statistics

Bonus Features

1. Difficulty-proportional test assembly

2. Countdown auto-submit
3. Wrong answer notebook
4. Question correct rate statistics
5. Exam score charts

Features NOT Recommended

1. No facial recognition
2. No tab-switching prevention
3. No AI-based essay grading
4. No complex online proctoring

Topic 6: Lab Equipment Reservation, Borrowing

& Maintenance Closed-loop Management System
Difficulty: Difficult

This topic is more complex than a regular reservation system, with

emphasis on "reservation conflict detection, approval status flow,
borrow/return registration, maintenance process, and usage rate
statistics."

Main Features

1. User Login & Role Management

 o Student
o Teacher
o Lab Administrator
o System Administrator
2. Equipment Information Management
o Equipment ID
o Equipment name
o Equipment category
o Belongs to lab
o Current status
o Purchase date
o Responsible person
3. Reservation Application
o User selects equipment
o Select reservation date and time slot
o Fill in purpose of use
o Upload related materials
4. Reservation Conflict Detection
o Same equipment cannot be reserved for the same time slot
o Equipment under maintenance cannot be reserved
o Borrowed equipment cannot be reserved
o Limit further reservations when user has unreturned
equipment
5. Approval Process
o Admin reviews reservation application
o Approve
o Reject
o Return for modification
o Record approval comments
6. Borrow Registration
o Register borrowing after reservation approval
o Record borrow time
o Record expected return time
o Update equipment status to 'Borrowed'
7. Return Registration
o Register actual return time
o Determine if overdue
o Record if equipment is intact
o Restore equipment to reservable status
8. Maintenance Management
o Admin marks equipment as under maintenance
o Fill in fault description
o Record maintenance start and end time
o Restore equipment status after maintenance completion
 9. Data Statistics
o Equipment reservation count
o Equipment borrowing count
o Overdue return count
o Equipment maintenance count
o Equipment usage rate per lab

Recommended Technologies

Servlet + JSP + JDBC + MySQL

or Spring Boot + MySQL.
Can use Ajax for real-time reservation conflict prompts.

10-Day Workload Schedule

PHASE DURATI TASKS

ON
JAVA FOUNDATION 3 days Design Equipment, Reservation, BorrowRecord,
TRAINING RepairRecord, User classes; implement status
flow and conflict detection
WEB DEVELOPMENT 6 days Complete equipment management, reservation
TRAINING application, review, borrowing, return,
maintenance, statistical analysis
FINAL DEFENSE 1 day Prepare complete business process demo,
exception testing, database design
documentation

Minimum Acceptance Requirements

1. Admin can maintain equipment

2. User can submit reservation
3. System can detect reservation conflicts
4. Admin can approve reservations
5. Can complete borrow and return
6. Can handle equipment maintenance status
7. Can view reservation and borrowing records

Bonus Features

1. Overdue return reminder

2. Equipment usage rate chart
3. Reservation record export
4. User credit score
5. Ajax real-time conflict detection
Below are the more concise "General Requirements" version suitable
for placement at the end of the appendix. Key required content is
retained without excessive detail.

IV. General Requirements

1. Basic Requirements
Each group selects one of the six topics and completes a functional
web application system. The system should, based on the topic
requirements, implement user login, role management, core business
processing, data querying, statistical display, and system testing.

This training topic mainly assesses Java Web application system

design and development capabilities. Students should comprehensively
use Java, databases, frontend pages, and web development-related
technologies to complete system design, coding implementation,
testing, and defense presentation. The six topics in the appendix all
provide main features, recommended technologies, minimum acceptance
requirements, and bonus features, based on which students should
complete their projects.

2. Recommended Technologies
Choose one of the following technical paths based on the group's
foundation:

Option 1: Basic Path

Suitable for groups with average foundation:

 Java
 Servlet
 JSP
 JDBC
 MySQL
 HTML
 CSS
 JavaScript
 Ajax
Option 2: Advanced Path

Suitable for groups with strong foundation:

 Spring Boot
 MyBatis / MyBatis-Plus
 MySQL
 Vue / Thymeleaf / JSP
 Element Plus
 ECharts

Frontend-backend separation is not mandatory, but the system must be

able to start, run, and be demonstrated normally.

3. Functional Requirements
Each system should at least complete the following:

1. User Login
Users can log into the system, with different roles entering
different functional pages.
2. Role & Permission Management
The system should contain at least 2 types of user roles.
Medium and difficult topics are recommended to include 3 or
more types of user roles.
3. Basic Data Management
Ability to add, delete, modify, and query basic data from the
topic.
4. Core Business Process
Must complete one complete business process. Examples:
o Notice Publishing → Student Viewing → Confirm Read →
Reading Statistics
o Assignment Publishing → Student Submission → Teacher
Grading → Score Viewing
o Activity Publishing → Student Registration → Review →
Check-in → Points Statistics
o Equipment Reservation → Review → Borrow → Return →
Maintenance Management
5. Conditional Query
System should support querying by conditions such as name,
category, time, status, class, and user.
 6. Statistical Functions
The system should provide statistical results related to the
topic, which can be displayed in tables or charts.

4. Database Requirements
Each system must use a database to store data, with MySQL
recommended.

Database design requirements are as follows:

1. Reasonable table structures;

2. Table names and field names should be as standardized as
possible;
3. Each table should have a primary key;
4. Relationships between important data should be reflected;
5. Cannot use a single table to implement all functionality;
6. Must submit table creation SQL files and test data.

Recommended number of tables:

DIFFICUL RECOMMENDE
TY D TABLE
COUNT
EASY- About 5
LEVEL tables
TOPICS
MEDIUM- 6-8 tables
LEVEL
TOPICS
DIFFICUL 8-10
T-LEVEL tables
TOPICS

5. Page Requirements
The system should have complete web pages; completing only backend
APIs or databases is not acceptable.

Should at least include:

1. Login page;
 2. Homepage or system main page;
3. Data list page;
4. Add and edit pages;
5. Query page;
6. Statistics display page;
7. Personal info or personal business records page;
8. Admin management page.

Pages do not need to be highly polished, but should have clear

layout, convenient operation, and complete functionality.

6. Chart Requirements
Each system should complete at least a certain number of statistical
charts, with ECharts recommended.

Difficul Required
ty Chart Count
Easy-
level At least 2
Topics
Medium-
level At least 3
Topics
Difficul
t-level At least 4
Topics

Chart content should be related to the system's business, such as

reading rate statistics, score distribution, activity registration
count, points ranking, equipment usage rate, exam correct rate, etc.

7. Testing Requirements
Each group needs to test the system and describe the testing
situation in the report.

Testing content should include at least:

1. Login testing;
2. Permission testing;
3. Add, modify, delete, query testing;
 4. Core business process testing;
5. Abnormal input testing;
6. Statistical result testing.

Recommended number of test cases:

DIFFICUL MINIMUM TEST

TY CASES
EASY- 8 cases
LEVEL
TOPICS
MEDIUM- 10 cases
LEVEL
TOPICS
DIFFICUL 12 cases
T-LEVEL
TOPICS

8. 10-Day Progress Suggestions

PHASE DURA MAIN TASKS
TION
TOPIC SELECTION & 1 Clarify topic, roles,
REQUIREMENTS day functions, and division of
ANALYSIS work
DATABASE & PAGE 2 Design database, page
DESIGN days prototypes, and business
processes
BASIC FEATURE 2 Complete login, permissions,
DEVELOPMENT days and basic data management
CORE FEATURE 2 Complete the core business
DEVELOPMENT days process required by the topic
STATISTICAL CHARTS 1 Complete queries, statistical
& PAGE REFINEMENT day charts, and page optimization
TESTING & FIXES 1 Write test cases, fix issues
day
DEFENSE 1 Prepare report, PPT, and demo
PREPARATION day video

9. Submission Materials
Each group should ultimately submit the following materials:

1. Project source code;

2. Database table creation SQL;
3. Test data SQL;
4. System design document;
5. Test cases and test results;
6. Practice report;
7. Defense PPT;
8. System demonstration video;
9. Group division of work description;
10. Large model tool usage description.

10. Large Model Tool Usage Instructions

Large model tools are allowed to assist in completing code, pages,
test cases, and reports, but group members must understand the
system's main functions and core code.

The report should briefly explain:

1. Which large model tools were used;

2. What content was completed with the help of large models;
3. Which code underwent manual modification and testing;
4. Group members' understanding of core functions.

During the defense, the teacher may randomly ask students to explain
database design, core business processes, permission logic,
statistical chart data sources, or specific core code segments.

11. Important Notes

1. The system must be runnable and demonstrable on-site;
2. Do not submit only static pages;
3. Do not complete only login and simple CRUD;
4. Do not submit projects that cannot run;
5. Do not plagiarize other groups' work;
6. Report content should be consistent with the actual system;
7. Bonus features should be implemented after completing the
minimum acceptance requirements;
8. Pages can be simple, but core functionality must be complete.