On this page

Synthesis: A web-based system that uses LLMs and Learning Analytics dashboards to provide automated, rubric-based feedback on student presentation slides. Developed by Becerra et al. (2026), AISSA addresses the scalability challenge of providing timely formative feedback in large university courses.

Key Findings

  1. AISSA combines LLMs (ChatGPT 5.2) with Learning Analytics dashboards to deliver rubric-based scoring and structured Feedback on presentation slides before students present.
  2. In a pilot with 46 final-year undergraduate students, AISSA reliably processed 90 presentations with end-to-end times of roughly 1–3 minutes per submission and no extraction or JSON-output errors.
  3. Students rated usability highly (average System Usability Scale score of 83.38) and adopted an iterative workflow of uploading drafts, reviewing feedback, revising, and resubmitting.
  4. The LLM integration proved economically feasible at an estimated $0.06–0.07 USD per evaluation, while students selectively applied recommendations, sometimes disregarding suggestions that conflicted with their planned visual design.

Background and Motivation

Feedback is a foundational pillar of effective teaching and learning: it lets students see the gap between current performance and intended goals, supporting reflection and self-regulation. Yet delivering timely, specific, and rubric-aligned feedback remains a persistent challenge in higher education, especially for oral presentations, where feedback often arrives as a final performance review too late to revise visual materials. In large, massified courses, teachers cannot realistically provide detailed formative review of every slide deck beforehand. AISSA is designed to close this gap by shifting automated Assessment earlier in the workflow, before the presentation itself.

The paper situates AISSA within three bodies of prior work: Automated Assessment (from test-case execution in programming to NLP-based short-answer grading and essay scoring), automated feedback oriented toward Scaffolding learning rather than only grading correctness, and learning analytics dashboards built around the questions of what data is visualized, for whom, why, and how it is represented and evaluated.

System Architecture

AISSA is built on a modular Python architecture using the Plotly Dash framework, organized into five modules:

  1. Visualization Module — provides student, teacher, and administration dashboards.
  2. Processing and Analysis Module — orchestrates the end-to-end evaluation workflow using asynchronous task queues and background workers to stay responsive during peak submission times.
  3. Data Persistence Module — a hybrid store combining PostgreSQL for structured transactional data with MongoDB (and GridFS) for the LLM JSON payloads, extracted slide features, and slide files.
  4. Extraction Module — extracts slide-level syntactic and visual features (word counts, font sizes, references, image edge density, and color dimensionality) from uploaded .pptx files.
  5. AI Module — manages interaction with the large language model through the OpenAI API.

The student dashboard lets students upload PowerPoint decks or revisit prior submissions, while the teacher dashboard provides a centralized control surface for configuring 5-point Likert-scale rubrics, managing cohorts, and monitoring engagement via activity logs. An administration dashboard supports batch imports of student lists, courses, and baseline rubrics from Excel.

AI Feedback Pipeline

The AI module transforms a teacher-defined rubric plus extracted slide features into structured output by dynamically building a constrained prompt adapted from the GePeTo framework. The prompt is organized into functional blocks: a System Role framing the model as an expert university evaluator, Calculation Rules for scoring logic, Input Data combining the rubric and slide features, an Expected Output JSON Schema, and Strict Output Constraints enforcing valid JSON only. Each rubric item is scored on a 1–5 Likert scale, from which the overall score and percentage are derived. Qualitative feedback is bilingual (Spanish and English) and organized into general feedback — three paragraphs covering strengths, areas for improvement, and concrete actions — plus criterion-level explanations of how to improve each rubric item. This grounding in established pedagogical feedback structures and strict output constraints reflect careful Prompt Engineering.

Pilot Deployment

AISSA was deployed at Universidad Autónoma de Madrid within the MOSAIC-F framework during the second trimester of 2026, involving 46 final-year undergraduate telecommunication engineering students. The real academic deployment tested both technical performance and the practical integration of generative AI for formative feedback. The asynchronous architecture held up under concentrated use before deadlines: 90 presentations were processed without service degradation, with 1–3 minute per-submission turnaround and consistent, correctly formatted JSON responses. The LLM integration was economically feasible, with an estimated $0.06–0.07 USD per evaluation driven by roughly 18,000 input tokens and 2,500–2,600 output tokens.

Student Experience and Perceived Usability

To assess perceived usability, the System Usability Scale (SUS) was administered to all 46 students, with 30 responses yielding an excellent average score of 83.38. Semi-structured interviews with a purposefully sampled subset of 20 students (chosen for gender parity and varied academic performance) found the platform highly intuitive: students adopted an iterative workflow of uploading drafts, refining work, and resubmitting without external technical support. Students perceived the AI-generated Feedback as fair and useful, especially for technical design elements such as font size, visual consistency, and bibliography formatting. Notably, several students intentionally disregarded some recommendations that conflicted with their planned visual design or presentation strategy — evidence of selective, agentic uptake of AI feedback rather than passive acceptance.

What this means for practice

  • Instructors. Move slide feedback ahead of the presentation deadline rather than after it: the pilot scored and commented on 90 presentation decks with end-to-end turnaround of roughly 1–3 minutes per submission, enough for students to upload, revise, and resubmit within the assignment schedule.
  • Instructors. Keep the final judgment with the teacher, because the tool's human-in-the-loop design has instructors review the automated evaluations against their own assessment, which is what preserves instructor authority over grades and Trust in the scoring.
  • Assessment designers. Write the rubric as explicit scoring rules before launch: AISSA converts a teacher-defined 5-point Likert rubric plus extracted slide features into criterion-level feedback, so any criterion left implicit is effectively skipped.
  • Instructional designers. Budget the marginal cost per submission: about $0.06–0.07 USD per evaluation, based on an average of 18,000 input tokens and 2,500–2,600 output tokens, with no extraction or JSON-output errors across the 90 presentations.
  • Administrators. Plan for selective uptake rather than compliance: several students intentionally disregarded recommendations that conflicted with their planned visual design or presentation strategy, so build in a step where students record which suggestions they accepted or rejected and why.

Limitations

  • Single-site, single-course pilot: 46 final-year telecommunication engineering students at Universidad Autónoma de Madrid over one trimester, so the 90 presentations processed, the per-submission turnaround, and the cost estimates are not evidence of what another course, level, or discipline would see.
  • The usability evidence is self-report from a partial sample — the System Usability Scale was administered to all 46 students but only 30 returned responses, and the qualitative findings come from 20 purposefully sampled interviews.
  • The study measured technical performance and perceived usability, not learning: no comparison against human teacher scores was run, and there is no evidence that iterative revision raised slide quality or presentation performance.
  • One model and one extraction pipeline were tested (GPT 5.2 through the OpenAI API, on features extracted from .pptx files), so how scores and feedback shift with other models or slide formats is unknown.

Citation

Becerra, A., Gomez, D., & Cobos, R. (2026). AISSA: AI-based Student Slides Analysis Tool for Academic Presentations.

Embed this page

Copy the code below to embed a chromeless version of this page in a learning management system or other website. The embedded view hides the site header, navigation, and footer.