Tools and Equipment Monitoring System Results

This Tools and Equipment Monitoring System Results discussed the presentation of results and analysis of data gathered by the proponents.

This study aimed to determine how it affects and meets the users and expert’s needs by using the Tools and Equipment Monitoring System.

This chapter showed the results of the evaluation of the developed system conducted by the proponents.

User’s Evaluation Results of Tools and Equipment Document Thesis Project

The proponents conducted a random evaluation in both administrative office and employees using PSSUQ (Post-Study System Usability Questionnaire) with 15 total of respondents, the results are followed:

Table 18 Users Evaluation Result

No.	Criteria	Average	Verbal Interpretation
System Usefulness
1	User satisfaction how easy to use the system.	1.46	Very Useful
2	Simplicity of the system.	2.0	Very Useful
3	Able to complete the task and scenarios quickly using the system.	1.86	Very Useful
4	Comfortability of the system.	2.13	Very Useful
5	The system is easy to use and learn.	1.66	Very Useful
6	Become productive quickly using this system.	2	Very Useful
Mean		1.85	Very Useful
Information Quality
7	The system gave error messages that clearly told me how to fix problems.	1.8	Very Useful
8	The system is easy to recover when something went wrong.	1.93	Very Useful
9	The notification is clear.	2.13	Very Useful
10	The information needed is easy to find.	1.73	Very Useful
11	The information was effective in helping me complete the tasks and scenarios.	1.73	Very Useful
12	The organization of information on the system screens was clear.	1.8	Very Useful
Mean		1.85	Very Useful
Interface Quality
13	The interface of this system was pleasant.	2.2	Very Useful
14	Liked using the interface of this system.	1.86	Very Useful
15	This system has all the functions and capabilities.	2.10	Very Useful
16	Over all satisfied with this system.	1.18	Very Useful
Mean		1.83	Very Useful

Criteria for Evaluation	Mean	Verbal Interpretation
System Usefulness	1.85	Very Useful
Information Quality	1.85	Very Useful
Interface Quality	1.83	Very Useful
Overall	1.84	Very Useful

Table 18 is the User Evaluation Result. It was calculated and resulted in 1.84 which interpret as “Very Useful”.

Experts Evaluation Result

The proponents asked three IT experts to evaluate the system using PSSUQ (Post-Study System Usability Questionnaire) with 5 total of respondents, the results are followed:

Table 19 is the Expert Evaluation Result

No.	Criteria	Average	Verbal Interpretation
System Usefulness
1	User satisfaction how easy to use the system.	1.60	Very Useful
2	Simplicity of the system.	1.60	Very Useful
3	Able to complete the task and scenarios quickly using the system.	2.20	Very Useful
4	Comfortability of the system.	2.40	Very Useful
5	The system is easy to use learn and Use.	1.60	Very Useful
6	Become productive quickly using this system.	1.40	Very Useful
Mean		1.80	Very Useful
Information Quality
7	The system gave error messages that clearly told me how to fix problems.	2.00	Very Useful
8	The system is easy to recover when something went wrong.	2.40	Very Useful
9	The notification is clear.	1.40	Very Useful
10	The information needed is easy to find.	2.00	Very Useful
11	The information was effective in helping me complete the tasks and scenarios.	1.60	Very Useful
12	The organization of information on the system screens was clear.	1.60	Very Useful
Mean		1.83	Very Useful
Interface Quality
13	The interface of this system was pleasant.	1.60	Very Useful
14	Liked using the interface of this system.	2.40	Very Useful
15	This system has all the functions and capabilities.	1.60	Very Useful
16	Over all satisfied with this system.	1.40	Very Useful
Mean		1.75	Very Useful

Criteria for Evaluation	Mean	Verbal Interpretation
System Usefulness	1.80	Very Useful
Information Quality	1.83	Very Useful
Interface Quality	1.75	Very Useful
Overall	1.79	Very Useful

Table 19 is the Expert Evaluation Result. It was calculated and resulted in 1.79 which interpret as “Very Useful”.

Related Capstone Resources

Inquiries

if you have any questions or suggestions about Tools and Equipment Document Thesis Project , please let me know by dropping your comment below.

BSIT capstone essentials

General guidance for BSIT capstone projects that applies across all specializations.

Start Chapter 3 (methodology) first. Forces you to think about the whole system.
Do documentation and coding in parallel. Never save documentation for the end.
Meet weekly with the team. Track blockers, adjust the timeline.
Back up everything daily. Two locations minimum.
Get adviser feedback per major milestone. Not just at the end.
Rehearse the defense presentation multiple times. Time yourself.

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 long should a BSIT capstone project take?

4-6 months is typical. Longer timelines encourage scope creep. Shorter timelines risk incomplete testing. Plan for parallel development + documentation to avoid last-minute rush.

What should I focus on first when starting a capstone?

Start with Chapter 3 (system design and methodology) — the diagrams and database schema force you to think about the whole system. Chapter 1 and 2 become easier once you know exactly what you are building.

Should I code first or document first?

Do both in parallel. Design in Chapter 3 first, then start coding while writing Chapter 1 and 2. Do not save documentation for the end. Panels can tell when documentation was rushed.

What common capstone mistakes should I avoid?

Do not over-scope. Do not copy from other capstones without attribution. Do not skip user testing. Do not defer documentation. Do not forget to back up your code and documents daily.

How do I balance capstone with regular coursework?

Block dedicated capstone time in your weekly schedule (10-15 hours minimum). Do not treat capstone as extra credit — it’s your thesis. Communicate schedule conflicts to your team early.

Joken E. Villanueva

Founder & Lead Developer at PIES IT Solution

Founder of PIES Information Technology Solutions, a software company building production-grade applications for institutions across the Philippines. Over 8 years of hands-on full-stack development experience, currently leading the development of ClinicAI, an AI-powered clinic management platform.

Expertise: PHP, MySQL, JavaScript, AI Integration, SaaS Architecture, VB.NET, Database Design, Capstone Documentation, Java · View all posts by Joken E. Villanueva →

Tools and Equipment Monitoring System Results