Presentations
All presentations must be in English.
- Project Pitch
- Each pitch should be in 6 minutes including Q&A, and it is STRONGLY recommended the presenters leave enough time for Q&A.
- Grading criteria:
- clear definition of the problem
- convincing argument of why the problem is important and/or interesting
- overall presentation quality, including the slides
- passion
- presentation teamwork
- Presentation Order:
- Team 1: 김영석/김재헌/박재준 material: [pptx]
- Team 2: 김예준/박찬수/안석찬 material: [zip]
- Team 3: 류호빈/이승우/정수빈 material: [pdf]
- Team 4: 박연하/이현종/이혜진 material: [pdf]
- Team 5: 신준형/안남조/이승우 material: [pptx]
- Team 6: 이주영/지수환/홍영규 material: [pdf]
- Team 7: 이준성/정창제/최낙현 material: [pdf]
- Midterm Presentation
- Each pitch should be in 10 minutes including Q&A, and it is STRONGLY recommended the presenters leave enough time for Q&A.
- Grading criteria:
- Problem (30%)
- Problem definition: refresh the audience what problem you're solving. If you changed the problem since the pitch, must also present why the new problem is important
- Project scope: state what exactly you aim to deliver in the end. What would your product or demo look like?
- Progress (50%)
- Solution: describe your design space and your solution. Why is your solution better than existing work? What is your secret sauce?
- Implementation: report how far along you are in implementation. Show a live demo if you have it (demo here is optional)
- Plan: provide concrete plan for implementation and testing. Are you facing unexpected challenges? How do you plan to overcome those issues? Convince the audience that you're on track to deliver.
- Presentation (20%)
- Delivery: show competence in overall organization and flow, articulation and clarity of the presentation
- Visual aids: make your slides readable and use effective visual aids and examples
- Presentation Order:
Final Presentation
- Each pitch should be in 10 minutes including Q&A, and it is STRONGLY recommended the presenters leave enough time for Q&A.
- Grading criteria:
- Problem (30%)
- Problem definition (10%): Is the refined final problem well-defined?
- Design goals & rationale (20%): Are the major design goals (specifications) and rationale for the selected approach clear?
- Progress (50%)
- Solution (20%): Does the final product improve any existing solutions?
- Implementation & functionality (30%): Does it provide a live demo? Does the implementation realize the initial specifications?
- Presentation (20%)
- Delivery (10%): Does the presentation well-organized? Does it flow well? Is the story clear?
- Visual aids (10%): Are the slides readable? Does the presentation use visual aids and examples effectively?
- Presentation Order:
Poster Session
- Evaluation: CS408 lecturers except mentors and four external reviewers
- Each team should prepare a demo scenario of less than 4 minutes, which contains the functional components and actual use scenario of the project product. The demo scenario should be reproducible for different reviewers.
- Each team will have a booth with its poster and laptops+alpha for demos. TAs will install the booths on June 1st (Friday).
- Grading criteria:
- Poster (50%, 1-5 scale)
- (5%) The poster is well structured (title, team members, etc.).
- (15%) The poster states the problem clearly.
- (15%) The poster delivers the core functional requirements clearly.
- (15%) The poster delivers the technical challenges clearly.
- Demonstration (50%, 1-5 scale)
- (15%) The demonstration shows the key functionalities of the software clearly.
- (15%) The functionalities of the software is implemented completely.
- (10%) The demonstration successfully illustrates the actual usage scenario.
- (10%) The implemented interfaces provides acceptable usability.