Cordora Trading and Services System Document Analysis
This Cordora Trading and Services System Document – Chapter 4 presents the data gathered, the results of the statistical analysis done and interpretation of findings to determine the perceived Usefulness and perceived Ease of Use of the developed “Cordora Trading and Services Management System”.
Experts’ Evaluation Report
We the proponents have conducted a survey to ten Experts in the company of Cordora Trading and Services like the owner, employees and IT experts to evaluate the System using the PSSUQ criteria.
Experts Result of Evaluation – Cordora Trading and Services System Document Analysis
| System Usefulness | Weighted Mean | Verbal Interpretation |
| Overall, I am satisfied with how easy it is to use this system. | 2.4 | Useful |
| It was simple to use this system. | 2.4 | Useful |
| I was able to complete the tasks and scenarios quickly using this system. | 2.8 | Useful |
| I felt comfortable using this system. | 2.6 | Useful |
| It was easy to learn to use this system. | 2.6 | Useful |
| I believe I could become productive quickly using this system. | 2.4 | Useful |
| Mean | 2.53 | Useful |
| Information Quality | Useful | |
| The system gave error messages that clearly told me how to fix problems. | 2.6 | Useful |
| Whenever I made a mistake using the system, I could recover easily and quickly. | 2.7 | Useful |
| The information (such as online help, on-screen messages, and other documentation) provided with this system was clear. | 2.8 | Useful |
| It was easy to find the information I needed. | 2.6 | Useful |
| The information was effective in helping me complete the tasks and scenarios. | 2.3 | Useful |
| The organization of information on the system screens was clear. | 2.7 | Useful |
| Mean | 2.61 | Useful |
| Interface Quality | Useful | |
| The interface of this system was pleasant. | 2.7 | Useful |
| I liked using the interface of this system. | 2.6 | Useful |
| This system has all the functions and capabilities I expect it to have. | 2.8 | Useful |
| Overall, I am satisfied with this system. | 2.5 | Useful |
| Mean | 2.65 | Useful |
Table 18. Shows the result of evaluation from the responders that is expert in the company of Cordora Trading and Services.
Table 19. Experts Overall Result of Evaluation
| Criteria for evaluation | Mean | Verbal Interpretation |
| System Usefulness | 2.53 | Useful |
| Information Quality | 2.61 | Useful |
| Interface Quality | 2.65 | Useful |
| Overall | 2.6 | Useful |
Table 19. Shows the overall result of evaluation from the responders that is expert in the company of Cordora Trading and Services
Based on the survey conducted to the experts, the systems’ usefulness is useful, and the Information Quality is useful and Interface Quality is useful. Overall, the End-users Evaluation results is useful with the systems’ functionality.
End-users’ Evaluation Report
The proponents conducted a survey to 20 random users for the system evaluation using the PSSUQ criteria.
Table 20. End-users’ Survey Result
| System Usefulness | Weighted Mean | Verbal Interpretation |
| Overall, I am satisfied with how easy it is to use this system. | 1.85 | 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. | 1.85 | Very Useful |
| I felt comfortable using this system. | 1.35 | 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.7 | Very Useful |
| Mean | 1.65 | Very Useful |
| Information Quality | Very Useful | |
| The system gave error messages that clearly told me how to fix problems. | 1.9 | Very Useful |
| Whenever I made a mistake using the system, I could recover easily and quickly. | 1.65 | Very Useful |
| The information (such as online help, on-screen messages, and other documentation) provided with this system was clear. | 1.55 | Very Useful |
| It was easy to find the information I needed. | 1.55 | Very Useful |
| The information was effective in helping me complete the tasks and scenarios. | 1.65 | Very Useful |
| The organization of information on the system screens was clear. | 1.4 | Very Useful |
| Mean | 4.52 | Very Useful |
| Interface Quality | 1.61 | Very Useful |
| The interface of this system was pleasant. | 1.55 | Very Useful |
| I liked using the interface of this system. | 1.95 | Very 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.5 | Very Useful |
| Mean | 1.7 | Very Useful |
Table 20. Shows the result of evaluation from the responders that is end-user for the field of Cordora Trading and Services.
Table 21. End-users’ Overall Survey Result
| Criteria for evaluation | Mean | Verbal Interpretation |
| System Usefulness | 1.65 | Very Useful |
| Information Quality | 1.61 | Very Useful |
| Interface Quality | 1.7 | Very Useful |
| Overall | 1.65 | Very Useful |
Table 21. Shows the overall result of evaluation from the responders that is end-user for the company of Cordora Trading and Services.
Based on the survey conducted to the end-users, the systems’ usefulness is very useful, and the Information Quality is very useful and Interface Quality is very useful Overall, the End-users Evaluation results is very useful with the systems’ functionality.
Related Article
- Cordora Trading and Services System Document – Chapter 1
- Cordora Trading and Services Project – Chapter 2
- Cordora Trading and Services System Document – Chapter 3
- Online Medicine Delivery System Documentation Chapter 4
- CHMSC Binalbagan IT Freshmen Admission System Thesis Chapter 4
- Automated Basketball Scheduling System Chapter 4 Documentation
- Library Borrowing System Documentation | Chapter IV – Existing System
- CRANE Thesis Chapter 4 | Presentation and Discussion of Result
Inquiries
If you have any questions or suggestions about Cordora Trading and Services System 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.
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 →