Technical review
Timeline
- Topic selection: Oct. 13, 2025
- Report submission: Dec. 4, 2025 (further extended and firm deadline)
Technical reports can be done individually.
Deliverable
- Proposal (15%): one-pager (one line or a short paragraph) including the chosen topic and a list of example papers you plan to read.
- You can find a list of example topics on this Google doc: [link]
- Final report (85%): Formal survey of the technology with no less than 10 pages (format: 12-point font size on single-spaced 8.5" x 11" pages). You should clearly lay out different topics studied in your report.
- Example technical review: [pdf]
- See suggested format (not mandatory) below.
Suggested Format for Final Report
In general, a good paper summary/tech. review should cover 1) what open problem the paper addresses that prior research does not, 2) what approach the paper presents to solve the problem, and 3) evaluation result which shows how effective the approach solves the problem. A technical review is intended to systematize knowledge on a focused research/technical problem. The following is the suggested structure of final technical review.
- Section 1 Paper Summaries
- Subsection 1.1: Summary of Paper
P1- Problem studied in
P1 - Approach in
P1 - Evaluation in
P1 - What's new in
P1 - Your opnion on the strength and limitation of
P2
- Problem studied in
- Subsection 1.2: Summary of Paper
P2- Problem studied in
P2 - Approach in
P2 - Evaluation in
P2 - What's new in
P2 - Your opnion on the strength and limitation of
P2
- Problem studied in
- ...
- Subsection 1.n: Summary of Paper
Pn
- Subsection 1.1: Summary of Paper
- Comparative Framework
- Defining
mapplicable propertiesF1,F2,F3, ... - The table for comparison (example below) _ Open problems and your prediction of future work.
- Defining
F1 |
F2 |
... | Fm |
|
|---|---|---|---|---|
P1 |
✓ | ✗ | ... | ✓ |
P2 |
✗ | ✓ | ... | ✓ |
Pn |
✓ | ✗ | ... | ✓ |