CASE STUDY · ACADEMIC TEAM PROJECT · WEB APPLICATION
Fichero Online
Web attendance system with QR clock-in, location validation, and a live dashboard. Supervised Professional Practice project (UTN FRH, 2025), developed by a team of 5 with Scrum.
Video de presentación de Fichero Online.
Context
In stores, offices, workshops, construction sites, and small businesses, attendance is still tracked with spreadsheets, paper, or time clocks. These methods create errors, fraud, and a great deal of wasted administrative time.
Fichero Online provides web-based attendance tracking with QR-code clock-in and location validation, designed for organizations with multiple branches. It was the UTN FRH Supervised Professional Practice project (2025): a team of 5, with Scrum roles and 8 weeks of work.
What we built
What the system does
- Role-based access: authentication with PHP sessions and three roles (Administrator, HR, and Employee) with differentiated permissions.
- QR and location clock-in: the employee scans the QR code at their branch, and the system validates their location against the branch coordinates before recording entry or exit.
- Daily attendance dashboard: indicators, charts, recent movements, and daily details, with filters by branch, shift, and department, plus manual actions (manual clock-in, justification, and notes).
- Administration: employees, users, roles, departments, positions, shifts, and branches, with a QR code for each branch.
- Reports: filtered previews and PDF export, plus quarterly trends for attendance, overtime, and late arrivals.
- Public landing page with a contact form and light and dark modes.
Architecture
Layered application: PHP and HTML views, interface logic in JavaScript services, a router (api/index.php), controllers, repositories, and a MySQL database.
How we worked
My contribution
- Analysis and documentation: I wrote the project’s functional documentation: user stories with acceptance criteria, a business model (Business Model Canvas), competitor analysis, screen prototypes, and the test plan.
- Development: I programmed user-role management.
- Demo version: I prepared the portfolio version: README, public landing page, and fictitious test data.
- Product video: I created the Fichero Online promotional video: watch it on YouTube.
Process
- Scrum for 8 weeks, with defined roles (Scrum Master, Product Owner, Business Analyst, and Dev Team) and three retrospectives: September, October, and November 2025.
- User-story backlog with acceptance criteria in Given / When / Then format. 8 of the 10 stories were completed.
- Bug tracking in Jira and a test plan with scenarios such as clocking in outside the permitted area or exporting reports.
Problems that came up and what we changed
- Local environment: configuring XAMPP and the database connection took time. We consolidated everything into a single SQL script and a README with installation steps, so the team started from the same baseline.
- Backend and frontend integration: the frontend expected JSON in a different format from the backend response. We began defining each endpoint’s contract (what it sends and receives) before programming the interface.
- Documentation: we left the user manual and appendices until the end and had a last-minute rush. For the next project, we will document them one week in advance.