This IT Freshmen Admission System Thesis presents and discusses Presentation, Analysis, and Discussion, the results of the data gathered by the proponents from the survey participated in by the end users.
The survey aims to determine how well the system meets user’s needs. The chapter shows the overall evaluation results for the developed of CHMSC Binalbagan IT Freshmen Admission System.
Users Evaluation Results
The table below presents the results of CHMSC Bin- IT Admission System evaluation ratings and interpretation of users in CHMSC using PSSUQ Questionnaire with 10 respondents from CHMSC bin students.
Table 16 User’s Evaluation Result
| No. | Criteria | Average | Verbal Interpretation |
| Overall, I am satisfied with how easy it is to use this system | 1.5 | Very useful | |
| It was simple to use this system. | 1.8 | Very useful | |
| I was able to complete the tasks and scenarios quickly using this system. | 2.2 | useful | |
| I felt comfortable using this system. | 1.9 | Very useful | |
| It was easy to learn to use this system. | 2.2 | useful | |
| I believe I could become productive quickly using this system. | 1.8 | Very useful | |
| The system gave error messages that clearly told me how to fix problems. | 1.8 | Very useful | |
| Whenever I made a mistake using the system, I could recover easily and quickly. | 1.6 | Very useful | |
| The information (such as online help, on-screen messages, and other documentation) provided with this system was clear. | 2 | Very useful | |
| It was easy to find the information I needed. | 1.9 | Very useful | |
| The information was effective in helping me complete the tasks and scenarios. | 1.8 | Very useful | |
| The organization of information on the system screens was clear. | 1.4 | Very useful | |
| The interface of this system was pleasant. | 1.5 | Very useful | |
| I liked using the interface of this system. | 1.7 | Very useful | |
| This system has all the functions and capabilities I expect it to have. | 2.2 | useful | |
| Overall, I am satisfied with this system. | 2.4 | useful | |
| Total average mean | 1.8 | Very useful |
Table 15 shows the overall mean of the user’s evaluation using PSSUQ Software Evaluation Criteria was 1.8 and this was interpreted a very useful.
Experts Evaluation Result
Table 17 expert evaluation result
| No. | Criteria | Average | Verbal Interpretation |
| Overall, I am satisfied with how easy it is to use this system | 1.6 | Very useful | |
| It was simple to use this system. | 1.6 | Very useful | |
| I was able to complete the tasks and scenarios quickly using this system. | 2.2 | useful | |
| I felt comfortable using this system. | 1.4 | Very useful | |
| It was easy to learn to use this system. | 1.6 | Very useful | |
| I believe I could become productive quickly using this system. | 1.4 | Very useful | |
| The system gave error messages that clearly told me how to fix problems. | 2 | Very useful | |
| Whenever I made a mistake using the system, I could recover easily and quickly. | 2.2 | useful | |
| The information (such as online help, on-screen messages, and other documentation) provided with this system was clear. | 1.4 | Very useful | |
| It was easy to find the information I needed. | 2 | Very useful | |
| The information was effective in helping me complete the tasks and scenarios. | 1.6 | Very useful | |
| The organization of information on the system screens was clear. | 1.4 | Very useful | |
| The interface of this system was pleasant. | 1.6 | Very useful | |
| I liked using the interface of this system. | 2.2 | useful | |
| This system has all the functions and capabilities I expect it to have. | 1.8 | Very useful | |
| Overall, I am satisfied with this system. | 1.4 | Very useful | |
| Total average mean | 1.7 | Very useful |
Table 16 showed the sub-mean result of the evaluation of the functional characteristics of the developed system. It was calculated and resulted in 1.7 which interpreted as “very useful” Therefore, IT Teacher rates the system’s functionality developed by the proponents a very useful.
Related Capstone Resources
- CHMSC Binalbagan IT Freshmen Admission System Thesis Chapter 1
- CHMSC Binalbagan IT Freshmen Admission System Thesis Chapter 2
- CHMSC Binalbagan IT Freshmen Admission System Thesis Chapter 3
- CHMSC Binalbagan IT Freshmen Admission System Document Chapter V
- Enrollment System Thesis Chapter 4 Existing System
- Classroom Management System Thesis Documentation Chapter 4
- Computerized Sales And Inventory System Thesis Chapter 4
- Sales And Inventory System Thesis Documentation Chapter 4
- Boarding House Finder Thesis Documentation Chapter 4
Inquiries
if you have any questions or suggestions about Freshmen Admission System Thesis Project , please let’s me know by dropping your comment below.
Capstone chapter writing checklist
Structuring a BSIT capstone chapter correctly saves rework and eases the defense. Follow this checklist for consistent quality across all 5 chapters.
- Draft the outline first. Every section header first, then fill in the content.
- Write the methodology before the introduction. Chapter 3 (methodology) forces you to think through the system; Chapter 1 becomes easier after.
- Include diagrams early. UML diagrams in Chapter 3 clarify what you’re building.
- Cite sources as you write. Do not defer citations. Use Zotero or Mendeley to track sources.
- Get adviser feedback per chapter. Do not write all 5 chapters then ask for review.
- Number figures and tables. Figure 3.1, Table 4.2, etc. Panels reference these numbers.
- Follow the school template exactly. Font, margins, spacing — do not deviate.
Common capstone mistakes to avoid
- Copying without attribution. Panels use Turnitin. Cite everything you did not write yourself.
- Over-scoping the project. A well-executed simple system beats a poorly-executed ambitious one.
- Deferring documentation. Documentation quality is a big part of the grade.
- Skipping user testing. Panels ask about user feedback. Have real data.
- Ignoring adviser feedback. Advisers know what the panel will ask.
Recommended free tools for capstone projects
- draw.io / diagrams.net. UML diagrams for Chapter 3.
- Google Docs. Collaboration + version history + adviser comments.
- Zotero or Mendeley. Reference management + auto-formatted citations.
- GitHub. Version control for the source code (also earns E-E-A-T signal on your CV).
- Grammarly. Language + tone check on the documentation.
- Turnitin. Plagiarism check before submission (some schools provide access).
- ChatGPT or Claude. For outline scaffolding — not for writing the actual content.
Where to get more capstone resources
- Capstone project ideas. Browse itsourcecode.com/topics/fyp/ for 140+ tested capstone concepts.
- Working source code. itsourcecode.com/topics/free-projects/ has 1,000+ downloadable projects.
- UML diagrams. itsourcecode.com/uml/ has 300+ free UML examples for Chapter 3.
- ER diagrams. itsourcecode.com/topics/uml/erd/ for database schemas.
Official references
Frequently asked questions
How many pages should a BSIT capstone chapter be?
Chapter 1 (Introduction) is typically 8-12 pages. Chapter 2 (RRL) is 15-25 pages. Chapter 3 (Methodology and System Design) is 15-30 pages depending on diagram count. Chapter 4 (Results) is 10-20 pages. Chapter 5 (Conclusions) is 5-10 pages. Total: 60-100 pages for the whole capstone.
What order should I write the chapters in?
Recommended order: Chapter 3 first (system design and methodology — most concrete), then Chapter 1 (introduction with the problem statement), then Chapter 2 (RRL to justify Chapter 1), then Chapter 4 (results — after implementation), then Chapter 5 (conclusions). This avoids rewrites and speeds up defense readiness.
What formatting style should I use for the capstone documentation?
Most Philippine BSIT programs require IEEE or APA 7th edition. Confirm with your adviser first. Use Times New Roman 12pt, double-spaced, 1-inch margins, and page numbers. Reference all sources properly and use consistent citation style throughout.
How many references do I need per chapter?
Chapter 1: 5-10 references. Chapter 2 (RRL): 20-40 references. Chapter 3: 10-15 references. Chapter 4-5: minimal, mostly self-referential. Recent sources (last 5 years) are strongly preferred over older ones.
What tools help write the capstone chapters?
Zotero or Mendeley for reference management, Grammarly for language check, Turnitin for plagiarism scan, Google Docs for collaboration with adviser, LaTeX (Overleaf) for advanced formatting, and ChatGPT or Claude for outline scaffolding (not for writing the actual content).
Adrian Mercurio
Full-Stack Developer at PIES IT Solution
Specializes in building complete capstone projects with full documentation. Strong background in PHP/MySQL development and database design. Has personally built and tested over 30 capstone-ready projects with ER diagrams, DFDs, and chapter-by-chapter thesis documentation.
Expertise: PHP, Laravel, Database Design, Capstone Projects, C#, C, C++, Python, AI Projects · View all posts by Adrian Mercurio →