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:
      1. automaTA: 이창윤/진형욱/한동훈 slides, video
      2. Brogrammers: Bolat Ashim/Azamat Smagulov/Adi Yerembessov slides, video
      3. CreamBears: 강현우/김지석/홍재민 slides, video
      4. CS4CS: 권태형/신은혁/조인영 slides, video
      5. GoatskiN: 김경원/박지희/최민엽 slides, video
      6. Hurricane: 김현수/설윤아/함형록 slides, video
      7. Reflection: 김현수/이건/이녕우 slides, video
      8. Team Herald: 김태수/정찬주/허세준 slides, video
  • 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.