Evaluator — Instructor/Stakeholder

Role: Assessing project scope, technical depth, and polish

Background

Reviews the project for course completion. Needs to understand what was built, what LLM techniques were applied, and how the pieces fit together. Evaluates both the product and the engineering approach.

Goals

• Understand project scope and capabilities
• Assess technical depth beyond basic API usage
• Evaluate systematic approach to LLM experimentation
• See evidence of course material application

Needs

• High-level overview of what was built
• Architecture and design decisions
• LLM integration points and experimentation
• Evidence of systematic evaluation (metrics, trade-offs)
• Live demos of key capabilities
• Clear presentation of completed user stories

How the Catalog Helps

• Project Overview: Personas, user stories, status
• Architecture: System design, data model, decisions
• LLM Integration: Baseline + experiments with metrics
• Experiments: Comparative evaluations with trade-off analysis
• Live Demos: Interactive examples and form previews
• Story Progress: Completed vs. planned capabilities

Pain Points

• Limited time to understand the full system
• Needs to assess technical depth, not just surface features
• Must evaluate engineering approach and decision-making
• Requires clear narrative from problem to solution