|
9 | 9 | - Expand database schemas to support additional timetable customization and AI assistant interactions by Feburary 28, 2025 |
10 | 10 |
|
11 | 11 | - **`timetable` schema**: |
12 | | - - The `timetables` table should have columns for `id`, `created_at`, `timetable_title`, `user_id`, and `updated_at`. |
13 | | - - The `course_events` table should have columns for `id`, `created_at`, `calendar_id`, `updated_at`, `event_name`, `event_day`, `event_start`, `event_end`, `event_description`, and `offering_id`. |
14 | | - - The `user_events` table should have columns for `id`, `created_at`, `event_name`, `event_description`, `event_day`, `event_start`, `event_end`, `calendar_id`, and `updated_at`. |
| 12 | + - The `timetables` table should have columns for `id`, `created_at`, `timetable_title`, `user_id`, and `updated_at`. |
| 13 | + - The `course_events` table should have columns for `id`, `created_at`, `calendar_id`, `updated_at`, `event_name`, `event_day`, `event_start`, `event_end`, `event_description`, and `offering_id`. |
| 14 | + - The `user_events` table should have columns for `id`, `created_at`, `event_name`, `event_description`, `event_day`, `event_start`, `event_end`, `calendar_id`, and `updated_at`. |
15 | 15 |
|
16 | 16 | - Develop enhanced scheduling features for the demo by March 7th, 2025: |
| 17 | + |
17 | 18 | - Ability to insert, update, and delete timetable entries. |
18 | 19 | - Automatic and customized timetable generation based on user constraints. |
19 | 20 | - Custom colour customization for timetable entries. |
|
26 | 27 | ### 1.2 Metrics for Measurement |
27 | 28 |
|
28 | 29 | - **Database Schema Expansion** |
| 30 | + |
29 | 31 | - Ensure the `timetable` schema supports new features. |
30 | 32 | - Verify referential integrity and indexing for efficient queries. |
31 | 33 |
|
32 | 34 | - **Timetable Management** |
| 35 | + |
33 | 36 | - Users can create, modify, and delete timetable entries without errors. |
34 | 37 | - Timetable generation respects user constraints (e.g., time preferences, course exclusions). |
35 | 38 | - Custom colour selections persist across sessions. |
|
43 | 46 | ## 2. Release Scope |
44 | 47 |
|
45 | 48 | - **Timetable Management** |
| 49 | + |
46 | 50 | - Add, update, and delete timetable entries. |
47 | 51 | - Generate an optimized schedule based on user preferences. |
48 | 52 | - Customize timetable entry colours. |
|
74 | 78 |
|
75 | 79 | - The AI assistant relies solely on the internal course database and does not fetch web-based content. |
76 | 80 | - Users must be logged in to access timetable and chat features. |
77 | | - |
|
0 commit comments