Software capstone project in Honduras: deliverables and rules
Reviewed: September 26, 2026. Sources, review and corrections methodology
DIRECT ANSWER
A systems engineering capstone (proyecto de graduación) is usually a working system, most often an MVP, plus its documentation: requirements, design, database, testing, deployment and a user manual. Each university sets the modality and its requirements; for example, the UNITEC and CEUTEC Reglamento Académico lists the graduation project among its degree options, depending on each program's plan.
In systems engineering, computer science and related majors, the final project is not always a written thesis. Often it is a system that works plus a document that explains it. This guide covers what programs usually ask for, what Honduran universities publish about this modality and how to scope the project so you finish on time.
What the regulations in Honduras say
Each university defines its graduation modalities, and each program sets the specific requirements in its curriculum (plan de estudios). This is what we found in official documents (checked on September 26, 2026):
| University | What it publishes |
|---|---|
| UNITEC and CEUTEC | Its Reglamento Académico (academic regulations), in force since January 2024, lets students enroll in a graduation project, professional practice, an internado (internship) or social service, according to each program's plan. |
| UTH | Its Reglamento General de Normas Académicas (general academic rules, 2012; check whether it is still in force) requires a supervised professional practice and then lets students choose a research paper, thesis, monograph, project, general exam or another modality in the plan. |
| UNAH | Its Normas Académicas (academic rules, 2015) ask bachelor's students for a Seminario Taller de Investigación (research seminar and workshop) with a protocol or profile, plus social service or professional practice; the specific requirements are set in each program's curriculum. |
Before you design anything, ask your program coordinator for the project guide in writing: deliverables, document format, rubric and progress deadlines. Our page on Honduran universities gathers the official links for each institution.
What the deliverables usually include
| Deliverable | What it contains | Read more |
|---|---|---|
| Proposal (anteproyecto) | Problem, objectives, scope, technologies and schedule | Proposal checklist by faculty |
| Requirements | Functional and non-functional, with acceptance criteria | How to document a software project |
| Design | Use cases, architecture and UML diagrams | UML diagrams guide |
| Database | Entity-relationship model and data dictionary | MySQL vs PostgreSQL |
| Working system | An MVP with the core features | How to build an MVP |
| Version control | A repository with a readable history | Git and GitHub for students |
| Testing and deployment | Test cases, environment and installation | Documentation template (below) |
| Defense | Live demo and answers to the committee's questions | Thesis defense tips |
Not every program asks for all of this. A class project may stop at requirements, design and a prototype; a capstone usually also calls for testing, deployment and a user manual.
How to scope the project
The mistake that delays a capstone the most is trying to build a complete system. To finish on time:
- Pick one user and one problem. "A system for the clinic" is too broad; "book appointments and send reminders to a clinic's patients" is something you can finish.
- Choose three to five core features. Everything else goes under future work in your conclusions.
- Use technologies you already know. The committee looks at whether the system solves the problem and whether you can explain it, not at whether you picked the trendiest tool.
- Document as you build. Outdated requirements and diagrams show during the defense.
- Test with real users. Even a handful of them gives you feedback that backs up your conclusions.
Common mistakes
- Starting to code before your advisor approves the requirements.
- A data model that changes in the code but not in the document.
- Relying on a paid service or a personal key that stops working on defense day.
- Having no plan B for the demo: a short video of the system running saves you a scare.
- Presenting code you cannot explain. The authorship and the defense are yours.
Free template and support
If you want to start the document with the structure already in place, download the software documentation template: it covers requirements, use cases, data model, testing, deployment and a user manual.
If you need help closing out one part, Folium Labs supports software development, database design and technical documentation for university projects. We agree on scope and milestones in writing, and you are still the one who understands, presents and defends the project.
Primary and academic sources
These sources support the editorial review of this guide. Always verify the current rules of your own program.
- MDN Web Docs, Mozilla
- Web Content Accessibility Guidelines (WCAG), W3C
Need help with your project?
Our team can handle your thesis, research or technology project.
