Short summary
The public demo shows the interface and the flow with no server behind it. The full prototype does process and store real requests, to test the logic end to end.
Real purpose
Pitch the solution to UANL so it can be integrated with their systems: what the tool does, which steps it automates, and what rescheduling management gains from it. No frills, with the working prototype as evidence.
What it does
- Walks through the full rescheduling flow, from request to response.
- The prototype processes and records requests on the backend; the demo shows the interface and the flow right in the browser.
- Validates every step and gives immediate feedback when something is missing.
Key features
- Two deliverables: a demo with no backend and a prototype with one, for real testing.
- State handling and validations on the client, with clear messages.
- The prototype's backend carries the business logic and persistence; there are scripts for deploying and testing.
- Forms with explicit steps, built so nobody gets lost.
Technologies
Frontend: JavaScript, HTML, CSS.
Backend: Java, Spring Boot.
Helper scripts in Shell and Python.
Deployment
Public demo: Cloudflare Pages.
Full prototype: GitHub CI/CD to deploy backend and frontend on Azure.
Design and accessibility
Visible controls, clear hierarchy, short messages. The goal was for administrative staff to get the flow on the first try and make fewer mistakes.
Challenges and lessons
- Keeping the same flow in the demo and the prototype without mixing up the versions.
- Turning an administrative procedure into validations and states the system can handle on its own.
- Coordinating client and server to reproduce real usage conditions.
Impact
It shows, in practice, that this paperwork can be automated and made transparent within the university's infrastructure. With the prototype in hand, evaluating whether to integrate it into existing systems gets much easier.