This thesis chapter 4 documentation of Automated Basketball Scheduling and Result Monitoring System is created to explain its evaluation result and enlighten you the content of the system.
This article on thesis chapter 4 documentation of Automated Basketball Scheduling and Monitoring System presents the given by the responders.
These data were based on parameters of questionnaires used and to evaluate the result of the analysis. To evaluate the usability and function of the system the responders used PSSUQ format.
Since this chapter 4 documentation also explains the results of the evaluation and the system helps or meet their goal.
The gathered evaluated results will be the basis to measure the users’ satisfaction about the system.
Here is the important content of this Thesis Chapter 4 Documentation
- Experts’ Evaluation Report
In this thesis chapter 4 documentation, proponents have conducted a survey to five Experts in Basketball Scheduling like Referees, Coaches, Sport Coordinator to evaluate the System using the PSSUQ criteria.
This table shows the result of evaluation from the responders that is expert in the field of scheduling or in handling Basketball Tournament. - Experts’ Overall Evaluation Result
The conducted survey result for the experts has parameters and total summation to give the experts’ evaluation.
This table shows the overall result of evaluation from the responders that is expert in the field of scheduling or in handling Basketball Tournament.The result of the conducted evaluation to the specific individuals which were experts in the field of basketball scheduling were based on the criteria used in the PSSUQ (Post-Study System Usability Questionnaire) standard, the SYSUSE (System Usefulness), the INFOQUAL (Information Quality) and the INTERQUAL (Interface Quality).
The SYSUSE means that the system allows the users to achieve or to complete a set of task and achieve the main work of managing or scheduling of basketball and it was rated as “Very Useful” for the experts.
The INFOQUAL means that the information inputs to the system were usefully corresponds to the work flow of the task that is needed. During the testing, the experts rates the system as “Very Useful” in terms of handling information.
While the INTERQUAL values the interaction between the system and the user if the interface is easy to handle and understandable specially to those that were new to using technologies and they were satisfied with the systems’ interface and they rated it “Very Useful” too.
Overall, the experts rated the developed system 1.4733 which is interpreted as “Very Useful” which means that they were satisfied with the operations used and work of the system.
- End-users’ Evaluation Report
In this thesis chapter 4 documentation, proponents conducted a survey to 10 random users for the system evaluation using the PSSUQ criteria.
Shows the result of evaluation from the responders that is end-user for the field of scheduling or in handling Basketball Tournament.
- End-users’ Overall Survey Result
The conducted survey result for the experts has parameters and total summation to give the experts’ evaluation.
This table shows the overall result of evaluation from the responders that is end-user for the field of scheduling or in handling Basketball Tournament.The result of the conducted evaluation to the targeted end users of the developed system for the use of scheduling Basketball tournament were based on the criteria used in the PSSUQ (Post-Study System Usability Questionnaire) standard, the SYSUSE (System Usefulness), the INFOQUAL (Information Quality) and the INTERQUAL (Interface Quality).
The SYSUSE means that the system allows the users to achieve or to complete a set of task and achieve the main work of managing or scheduling of basketball and the end-users rated it as “Very Useful” in terms of doing the bracketing of schedules and assigning of venues and time ranges.
The INFOQUAL means that the information inputs to the system were usefully corresponds to the work flow of the task that is needed. During the testing the end-users were satisfied with the system because the system operates as what is needed and useful in their field that they rated the developed system as “Very Useful”.
While the INTERQUAL values the interaction between the system and the user if the interface is easy to handle and understandable specially to some of them that were new to using technologies but then they were satisfied with the systems’ interface and they rated it “Very Useful” too.
The overall performance of the system satisfies the end-user and the evaluation result was “Very Useful” for the end-users.
Related Capstone Resources
- Automated Basketball Scheduling And Monitoring System Chapter 1
- Automated Basketball Scheduling And Monitoring System Chapter 2
- Automated Basketball Scheduling And Monitoring System Methodology
- Classroom Management System Thesis Documentation Chapter 4
- Sales And Inventory System Thesis Documentation Chapter 4
- Existing System Chapter 4 Doc Attendance Monitoring System
Inquiries
If you have any questions or suggestions about Chapter 4 Documentation, please inform me by 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).
Mary Grace G. Patulada
Programmer & Technical Writer at PIES IT Solution
Mary Grace G. Patulada (pen name ‘Nym’) is a programmer and writer at PIES IT Solution with a BSIT background from Carlos Hilado Memorial State College, Binalbagan Campus. Authored 370+ UML diagram tutorials and capstone documentation guides at itsourcecode.com. Specializes in UML (class, use case, activity, sequence, component, deployment), DFD, and ER diagrams for BSIT capstone projects.
Expertise: UML Diagrams · DFD · ER Diagrams · Use Case Diagrams · Activity Diagrams · Capstone Documentation · PHP
· View all posts by Mary Grace G. Patulada →