Final Exam Information (Functional Programming)
Final Exam - Week 16
Submission Deadlines
Please submit the revised version of your code in the markdown file. We will only check the markdown file for taking the overall scores of your final projects.
- Class A: 7 December 2025
- Class B: 11 & 13 December 2025
Class A Presentation
8 December 2025
| Group | Start | End |
|---|---|---|
| 8 | 12:30 | 13:00 |
| 1 | 13:00 | 13:30 |
| 2 | 13:30 | 14:00 |
| 3 | 14:00 | 14:30 |
| 4 | 14:30 | 15:00 |
| 5 | 15:00 | 15:30 |
| 6 | 15:30 | 16:00 |
| 7 | 16:00 | 16:30 |
Class B Presentation
11 December 2025
| Group | Start | End |
|---|---|---|
| 1 | 07:30 | 08:00 |
| 2 | 08:00 | 08:30 |
| 3 | 08:30 | 09:00 |
| 4 | 09:00 | 09:30 |
| 5 | 09:30 | 10:00 |
| 6 | 10:00 | 10:30 |
13 December 2025
| Group | Start | End |
|---|---|---|
| 7 | 08:30 | 09:00 |
| 8 | 09:00 | 09:30 |
| 9 | 09:30 | 10:00 |
Important: Students who arrive late or miss their scheduled time will not be allowed to participate in the final exam. If you have a serious scheduling conflict, you must inform the lecturer before the presentation day so an alternative can be arranged. Late communication cannot be accommodated!
Preparation – Week 15
Before the final examination, each group is required to obtain feedback from the lecturer during Week 15. To accomplish this, you must print your source code and submit the corresponding Markdown file through the provided link.
Requirements
- The printed source code must include line numbers and be printed on a white background for readability.
-
Submit the Markdown file online as instructed. Google Drive: Submission Class A Submission Class B - Place the printed version on my desk.
- You may generate a PDF version from your Markdown file for printing.
Submission Deadlines
- Class A: 28 November 2025
- Class B: 1 December 2025
Note: The feedback stage contributes 20% of your final exam score. The score will be assigned in Week 16 based on the quality of your revisions after receiving feedback.
If You Have a Schedule Conflict
If you have a serious scheduling conflict, you must inform the lecturer before the presentation day so an alternative can be arranged.
Late communication cannot be accommodated.
—
Class A Presentation
1 December 2025
| Group | Start | End |
|---|---|---|
| 1 | 13:00 | 13:20 |
| 2 | 13:20 | 13:40 |
| 3 | 13:40 | 14:00 |
| 4 | 14:00 | 14:20 |
| 5 | 14:20 | 14:40 |
| 6 | 14:40 | 15:00 |
| 7 | 15:00 | 15:20 |
| 8 | 15:20 | 15:40 |
Class B Presentation
4 December 2025
| Group | Start | End |
|---|---|---|
| 1 | 07:20 | 07:40 |
| 2 | 07:40 | 08:00 |
| 3 | 08:00 | 08:20 |
| 4 | 08:20 | 08:40 |
| 5 | 08:40 | 09:00 |
| 6 | 09:00 | 09:20 |
| 7 | 09:20 | 09:40 |
| 8 | 09:40 | 10:00 |
| 9 | 10:00 | 10:20 |
Important: Students who arrive late or miss their scheduled time will not be allowed to participate in the feedback session. Missing this session results in losing the 20% component of the overall course score.
Markdown Format
# Title of the Project
_A Functional Programming Approach with Rust_
**Authors:** Name 1, Name 2, Name 3
---
## Abstract
Provide a concise summary of the project, its goals, the technologies used (Rust + Axum/Rocket/GTK4+/Tauri), and how functional programming principles were applied.
---
## Introduction
Explain the motivation behind the project:
- What problem does your application solve?
- Why did you choose Rust?
- Why integrate functional programming concepts?
- What makes your solution unique or interesting?
---
## Background and Concepts
Introduce key concepts relevant to the project:
### Technology Stack
- Rust
- Framework (Axum, Rocket, GTK4+, or Tauri)
- Async runtime (Tokio, if used)
- Supporting crates (serde, anyhow, thiserror, etc.)
Each concept should give readers enough context to understand your design.
## Important...!
*Avoid LLM/ChatGPT/Claude code..! any unethical conduct will results in E overall score!*
---
## Source Code and Explanation
## Screenshot
## Conclusion