Course Information
- Courses: CSS 451 (Cloud Computing) and CSS 454 (Computer Security)
- Project Type: Term Project
Project Overview
Topic Selection
- Choose a topic from the provided list: 01 Term Project Topics
- Propose a design and implementation by applying:
- Techniques learned from the course
- External studies and research
- Reserve your topic: Topic Reservation Sheet
Project Milestones
1st Deliverable: February 10, 2026
Submission Requirements:
- Project Title
- Project Scope
- Contributions (team member responsibilities)
Analogy: This is like creating a blueprint before building a house—you need to know what you're building, why it matters, and who's doing what.
2nd Deliverable: March 5, 2026
Submission Requirements:
- System Model
- Process Design/Algorithms
Analogy: Now you're designing the actual structure and mechanisms—like drawing the architectural plans and engineering specifications for your house.
3rd Deliverable: 2 Weeks After Midterm Exam
Submission Requirements:
- Revised Process Design/Algorithms
- Evaluation and Experiment Design
Analogy: This is your iteration phase—like refining your designs based on feedback and planning how to test if everything works properly.
Final Deliverable: 1 Week Before Final Exam
Submission Requirements:
- Project presentation
- Final report
Final Submission Details
1. Final Report
Format Requirements:
- Paper Length Options:
- Short paper: 6-8 pages
- Long paper: 12-15 pages
- Format: IEEE double-column format
- Minimum References: 15 references
Report Structure:
- Abstract
- Background or Introduction
- Related Work
- Proposed Project
- Development or Experiment Details
- Conclusion
- References (minimum 15 refs)
Analogy: Think of the report structure like telling a complete story—start with what the problem is (intro), what others have tried (related work), your solution (proposed project), how you built it (development), and what you learned (conclusion).
2. Presentation File
- Prepare slides for oral presentation
- Should cover key aspects of your project
3. Source Code
Requirements:
- Source code of the program
- Executable code
Analogy: This is like providing both the recipe (source code) and the finished dish (executable) so others can replicate and use your work.
Team Structure
- Group Size: 3-4 students per group
Analogy: Like a startup team—small enough to be agile, large enough to divide complex work effectively.
Assessment Breakdown
\boxed{\text{Total Grade} = \text{Prototype/Simulation (50%)} + \text{Report (50%)}}
Components:
- Prototype System/Simulation: 50%
- Report: 50%
- Written paper
- Oral presentation
Analogy: Half your grade comes from building something that works (like showing a working prototype), and half from explaining it well (like a product pitch and documentation).
Bonus Opportunity
Publication Bonus:
- If your group publishes the research project in a recognized conference or journal within the semester
- Reward: Full marks for:
- Attendance
- Quizzes
- Assignments
- Term-Project
Analogy: This is the ultimate achievement bonus—like getting a full scholarship for publishing groundbreaking research. It's rare but incredibly rewarding!
Important Links
📎 Resources
Timeline Summary
| Deadline | Deliverable |
|---|---|
| Feb 10, 2026 | Project Title, Scope, Contributions |
| Mar 5, 2026 | System Model, Process Design/Algorithms |
| 2 weeks after midterm | Revised Design, Evaluation & Experiment Design |
| 1 week before final exam | Presentation & Final Report |
Tips for Success
- Start Early: Reserve your topic as soon as possible
- Collaborate Effectively: Divide work according to team member strengths
- Iterate Often: Use feedback from each deliverable to improve
- Document Everything: Keep detailed records for your report
- Aim High: Consider the publication bonus if your project is innovative
Analogy: Treat this project like launching a startup—plan well, build iteratively, document thoroughly, and aim for something publication-worthy!