What to Build

Your team must design and implement a system that allows:

• Coorditators to submit justification requests with supporting evidence.
• Automatic detection of impacted classes based on student schedules.
• Dean of Engineering to approve or reject requests.
• Storage and queries handled efficiently using MongoDB.  

Bonus points for integrating:

• Dashboards or analytics (e.g., number of approvals, response time).
• Authentication and roles.
• Deployment on MongoDB Atlas + Render/Vercel.  

Detailed Description of Additional Documents

General Guidelines

"Entrevista" (Stakeholder Interview)

This document contains a conversation with the primary stakeholder or end-user of the process.
It includes:

• Their needsPain points
• Current workflow challenges
• Expected improvements
• Constraints and must-have features

Purpose:
To help teams identify real functional and non-functional requirements directly from the user perspective.
This is the foundation for:

• Defining scope
• Prioritizing features
• Creating user stories
• Guiding the overall solution design

"Kiosko Interview" (Executive Kiosk Template)

This is a structured template that teams will use to document their analysis, system design, and requirement specification.
The template typically includes sections like:

• Actor definitions
• Functional and non-functional requirements
• System objectives
• Data flow
• High-level architecture Key endpoints
• Expected outputs or system behavior

Purpose:
To standardize documentation so all teams present their system in a clear, comparable, and professional format.
It ensures teams think through system behavior before coding.

"Ejemplo de Llenado" (Filled Example Template)

This document shows a completed sample of the Kiosko Directivo template.
It demonstrates:

• How each section should be written
• The level of detail expected
• How to document requirements correctly
• How to structure diagrams or explanations
• What a complete analysis looks like

Purpose:
To serve as a reference or guide, helping teams properly document their work even if they have little experience with requirement specification.

"srvlistas.htm" (Students Schedules & Class Data) 

This file contains raw HTML data with student schedules, classes, groups, and time slots.
Inside, teams will find:

• Student IDs
• Names
• Courses
• Groups
• Days and times of classes
• Assigned professors

Purpose:
This serves as the primary dataset teams will use to build their system. It guarantees every team is working with the same raw data, leveling the playing field.