Presentation Rubric

Clarity of Presentation (0-6 Points)

• 6 Points: The presentation is clear, well-structured, and easy to follow. The presenter(s) clearly explain the project’s purpose, overall architecture, and key technical decisions. Delivery is natural and unscripted; slides or brief notes are used as guidance.
• 4 Points: The presentation is mostly clear but may lack focus, smooth transitions, or technical depth in some places. The presenter(s) show some reliance on written text or partial script reading, which slightly affects clarity but does not dominate the presentation.
• 2 Points: The explanation is difficult to follow due to poor organization or unclear descriptions. Presenter(s) frequently read from slides or notes, limiting engagement and demonstrating weak command of the material.
• 0 Points: The presentation lacks a coherent explanation of the project, or is read almost entirely from a script with minimal understanding or engagement.

Core Technical Requirements (0-10 Points)

The presentation must clearly demonstrate that all core technical requirements of the web development project are implemented and functional, either in a local development environment or a deployed environment (if available).

Checklist (6 items)

Check each item the team demonstrates clearly during the presentation:

• TypeScript Usage: All frontend and backend application code is written in TypeScript.
• Frontend Implementation: A functional frontend built with React or Next.js, styled using Tailwind CSS and a component library (e.g., shadcn/ui), with responsive layout.
• Backend Implementation: A functioning backend using Next.js (full-stack) or Express.js, handling application logic and data access.
• Frontend–Backend Integration: Clear evidence of data flow between frontend and backend (API routes, requests, mutations, state updates).
• Relational Database Usage: Persistent data storage using SQLite or PostgreSQL, with meaningful queries and updates demonstrated.
• File Handling with Cloud Storage: Basic file upload/download functionality using cloud storage, integrated with application logic or database records.

Scoring Guidelines

• 10 Points: When everything is complete and integrated without major issues

  • All 6 boxes checked.
  • All core requirements clearly implemented and functioning.
  • Demo shows smooth interaction across frontend, backend, database, and storage.
  • Explanations are clear and technically correct.

• 7 Points: When the application is mostly complete and on track

  • 4–5 boxes checked.
  • Most requirements implemented, but one may be:
    • partially implemented,
    • working but weakly explained, or
    • missing minor functionality.
  • Overall system is coherent and largely functional.

• 4 Points: When the team has basic components but is significantly behind expectations

  • 2–3 boxes checked.
  • Several core components are missing, incomplete, or poorly integrated.
  • Demo shows noticeable issues (broken flows, missing persistence, unclear state handling).

• 2 Points: When only minimal progress on the core requirements is shown

  • 1 box checked, or multiple items attempted but none fully functional.
  • Demo is incomplete or difficult to understand.
  • Major gaps in frontend–backend integration or data persistence.

• 0 Points: When there is almost no demonstrable implementation

  • 0 boxes checked.
  • No functional implementation of core project requirements.

Advanced Features and Future Plan (0-4 Points)

• 4 Points: At least two advanced features are clearly presented, with strong explanations of their purpose and design. Full credit may be earned in either of the following cases:

  • The advanced feature(s) are already implemented and demonstrated (live or via short recording), or

  • The advanced feature(s) are not yet implemented, but are clearly explained, supported by a diagram, mockup, or partial implementation, and accompanied by a clear, realistic plan for completion by the final project deadline.

• 2 Points: Advanced features are identified, but explanations lack depth, clarity, or feasibility. Supporting materials or completion plans are vague or incomplete.

• 1 Point: Advanced features are mentioned with minimal explanation, little supporting material, or an unrealistic or generic completion plan.

• 0 Points: No advanced features or future plan are presented.