Medicine Delivery System Documentation
This Medicine Delivery System Documentation presents the data gathered Presentation, Analysis and Discussion of Reports, the results of the statistical analysis done and interpretation of findings to determine the perceived Usefulness and perceived Ease of Use of the developed “Online Medicine Delivery System with SMS Notification”.
Users Evaluation Report
The proponents have conducted a survey from different users specifically the online riders and shoppers to evaluate the System using the PSSUQ criteria.
Table 20: User’s Result of Evaluation
| System Usefulness | Mean | Verbal Interpretation |
| Overall, I am satisfied with how easy it is to use this system. | 4.133 | Very satisfactory |
| It was simple to use this system. | 4.267 | Very satisfactory |
| I was able to complete the tasks and scenarios quickly using this system. | 4.133 | Very satisfactory |
| I felt comfortable using this system. | 4.067 | Very satisfactory |
| It was easy to learn to use this system. | 4.467 | Very satisfactory |
| I believe I could become productive quickly using this system. | 4.133 | Very satisfactory |
| Mean | 4.2 | Very satisfactory |
| Information Quality | ||
| The system gave error messages that clearly told me how to fix problems. | 4.533 | Very satisfactory |
| Whenever I made a mistake using the system, I could recover easily and quickly. | 4.2 | Very satisfactory |
| The information (such as online help, on-screen messages, and other documentation) provided with this system was clear. | 4 | Very satisfactory |
| It was easy to find the information I needed. | 4.133 | Very satisfactory |
| The information was effective in helping me complete the tasks and scenarios. | 4 | Very satisfactory |
| The organization of information on the system screens was clear. | 4.333 | Very satisfactory |
| Mean | 4.2 | Very satisfactory |
| Interface Quality | ||
| The interface of this system was pleasant. | 4.333 | Very satisfactory |
| I liked using the interface of this system. | 4.4 | Very satisfactory |
| This system has all the functions and capabilities I expect it to have. | 4.4 | Very satisfactory |
| Overall, I am satisfied with this system. | 4.6 | Very satisfactory |
| Mean | 4.433 | Very satisfactory |
Table 20: Shows the result of evaluation from the users.
Table 21: User’s Overall Result of Evaluation
| Criteria for evaluation | Mean | Verbal Interpretation |
| System Usefulness | 4.2 | Very Satisfactory |
| Information Quality | 4.2 | Very Satisfactory |
| Interface Quality | 4.433 | Very Satisfactory |
| Overall | 4.278 | Very Satisfactory |
Table 21: Shows the overall result of evaluation from the users.
Based on the survey conducted from the users, the systems’ usefulness, Information Quality and Interface Quality are all very satisfactory. Overall, the End-users Evaluation results is very satisfactory with the systems’ functionality.
Expert’s Evaluation Report
The proponents conducted a survey to 5 random I.T experts for the system evaluation using the PSSUQ criteria.
Table 22: Expert’s Survey Result
| System Usefulness | Mean | Verbal Interpretation |
| Overall, I am satisfied with how easy it is to use this system. | 3.8 | Satisfactory |
| It was simple to use this system. | 4.2 | Very satisfactory |
| I was able to complete the tasks and scenarios quickly using this system. | 3.2 | Satisfactory |
| I felt comfortable using this system. | 3.8 | Satisfactory |
| It was easy to learn to use this system. | 4 | Very satisfactory |
| I believe I could become productive quickly using this system. | 4.2 | Very Satisfactory |
| Mean | 3.8667 | Satisfactory |
| Information Quality | ||
| The system gave error messages that clearly told me how to fix problems. | 4.2 | Very Satisfactory |
| Whenever I made a mistake using the system, I could recover easily and quickly. | 3.8 | Satisfactory |
| The information (such as online help, on-screen messages, and other documentation) provided with this system was clear. | 3.4 | Satisfactory |
| It was easy to find the information I needed. | 4 | Very Satisfactory |
| The information was effective in helping me complete the tasks and scenarios. | 3.8 | Satisfactory |
| The organization of information on the system screens was clear. | 4 | Very Satisfactory |
| Mean | 3.8667 | Satisfactory |
| Interface Quality | ||
| The interface of this system was pleasant. | 4.4 | Very Satisfactory |
| I liked using the interface of this system. | 4.2 | Very Satisfactory |
| This system has all the functions and capabilities I expect it to have. | 3.4 | Satisfactory |
| Overall, I am satisfied with this system. | 4 | Very Satisfactory |
| Mean | 4 | Very Satisfactory |
Table 22: Shows the result of evaluation from the validators the I.T experts.
Table 23: Expert’s Overall Survey Result
| Criteria for evaluation | Mean | Verbal Interpretation |
| System Usefulness | 3.8667 | Satisfactory |
| Information Quality | 3.8667 | Satisfactory |
| Interface Quality | 4.0 | Very Satisfactory |
| Overall | 3.9111 | Satisfactory |
Table 23: Shows the overall result of evaluation from validators the I.T experts.
Based on the survey conducted from the experts, the systems’ usefulness and Information Quality was rated satisfactorily while Interface Quality are all very satisfactory. Overall, the End-users Evaluation results is satisfactory with the systems’ functionality.
Related Capstone Resources
- Online University Management System Project Report Documentation
- Hotel Management System Project Report Documentation PDF
- Inventory Management System Project Report Documentation PDF
- Payroll Management System Project Documentation PDF Report
- Employee Management System Project Report Documentation PDF
- Pharmacy Management System Project Abstract PDF Documentation
Inquiries
if you have any questions or suggestions about Online Delivery System Thesis Project , please let’s 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.
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 →