> For the complete documentation index, see [llms.txt](https://emory.gitbook.io/nlp-essentials/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://emory.gitbook.io/nlp-essentials/projects/live-demonstration.md).

# Live Demonstration

Your team will participate in an interactive demonstration session where you will present your final project to multiple groups of classmates. The session will follow a rotation format, with each team hosting their station while other students move between presentations in 10-minute intervals.

## Logistics

* Time per rotation: 10 minutes (5 minutes presentation + 5 minutes interaction).
* Format: Station-based demonstrations using your laptop.
* Audience: 6-7 different groups will visit your station.

## Preparation

### Technical Setup

* Ensure your laptop is fully charged and bring your charger.
* Test all features of your project thoroughly.
* Prepare a backup plan (e.g., screenshots, video recording) in case of technical issues.
* Have all necessary software installed and running properly.

### Demonstration Script

Create a concise 5-minute presentation that includes:

* Project overview.
* Key features and functionality.
* Technical highlights or innovative solutions.
* Implementation challenges and solutions.
* Future improvements or extensions.

### Interactive Component

Prepare for the 5-minute interaction period:

* Design 2-3 hands-on activities for visitors to try.
* Create a clear set of instructions for each interactive element.
* Prepare sample data or test scenarios that showcase different aspects of your project.
* Consider potential questions and prepare concise answers.

## Submission

Create a 5-10 minute video demonstrating your system and submit it to Canvas

## Rubric

* **Technical Achievement & Innovation** (1 point):
  * Achievement looks at the technical complexity level and how well it's executed - did you tackle challenging problems? Did you use advanced techniques appropriately?
  * Innovation evaluates creative solutions and novel approaches - did you solve problems in unique ways? Did you combine technologies creatively?
* **Documentation & Communication** (0.5 points):
  * Assesses how clearly the team explains your technical implementation during the demo.
  * Evaluates your ability to communicate complex concepts to different audience levels.
  * Includes quality of any supporting materials (diagrams, architecture drawings, user guides).
* **Project Impact & Problem Solving** (1 point):
  * Examines the problem definition and how well the solution addresses it.
  * Evaluates whether you understood their target users/market.
  * Considers the potential real-world applicability of the solution.
* **Testing & Quality Assurance** (1 point):
  * Evaluates how thoroughly the project was tested.
  * Includes handling of edge cases and error conditions.
  * Assesses performance under various conditions.
* **User Experience & Interface Design** (0.5 points):
  * Examines how intuitive and user-friendly the interface is.
  * Evaluates the clarity of user workflows.
  * Assesses visual design and consistency.
* **Video Submission** (2 points)
  * Project overview
  * Key features demonstration
  * Technical highlights
  * Use case examples


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://emory.gitbook.io/nlp-essentials/projects/live-demonstration.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.