Automated Basketball Scheduling and Monitoring System – Methodology
This article discusses the methodology of the Automated Basketball Scheduling and Monitoring system as well as the step-by-step processes happening in a basketball tournament.
Below is the list of Outline of Automated Basketball Scheduling Chapter 3 | Methodology
- Methodology
- System Development Life Cycle(SDLC)
- Use Case Model
- Activity Diagrams
- Context Diagram
- Dataflow Diagrams
- Entity Relationship Diagram
- Architectural Diagram
- Hardware and Software Requirements
SYSTEM DEVELOPMENT LIFE CYCLE (SDLC)
SDLC – System Development Life Cycle defines the process of developing a proposed system. It consists of different stages or methodologies which will be a guide in processing the development of a system.
In addition to this, the SDLC as the structure and the development of the system will be done by the team within the software organization.
The life cycle of the system development will describe the developing and maintaining processes of the proponent system and also the replacement of the specific system.
Automated Basketball Scheduling and Monitoring System RAPID APPLICATION DEVELOPMENT
The RAD (RAPID APPLICATION DEVELOPMENT) methodology is the basis for the process of the Automated Basketball Scheduling System. This also helps the researcher on how to start the processing up to finishing it.
The system chose to use this as the method of development because of its concept that can help in the step-by-step processes of the study.
This development diagram allows the proponents to review its steps in development through the prototype applied. All in all, this Automated basketball scheduling system methodology will help the process of building it to be a well-polished and functional system.
Analysis and Quick Design
In this phase, the process is about interviewing the problems in handling basketball tournament activities to gather information for the design of the system. This phase also discusses the analysis in designing possible features and functionalities in this phase.
Demonstrate
In the demonstrate phase, the information gathered is evaluated. This phase values the information and then formulates a solution that will answer the needs of the user, by this activity you will be able to initiate the finalization of the features of the proposed study.
Refine
In the refine phase, the process starts with the refining of the system’s information in all aspects before building it. Researchers should make sure that every step of the development of the study was correct to avoid unnecessary events while building it.
Build
In this phase, the system is already in the state of building the designed study. The researchers used PHP for the building of the web-based system for managing the basketball tournament and MySQL platform for the development of the database.
Testing and Implementation
In this phase, the system already has the full finished project that will be evaluated. This will also be the time that the end-users manipulate the system and know how this system helps the target users.
The researchers use some questions to the users regarding the effectiveness and efficiency of the system.
Use Case Diagrams
This general use case figure shows the main functions of the basketball tournament which is the basis for the system’s work and its guide to the step-by-step process as it will be breakdown into specific use cases.
Activity Diagram
Context Diagram
Data Flow Diagram
Entity Relationship Diagram
Architectural Diagram
Hardware and Software Used for Developing The System
Hardware Specification for System Development:
The hardware specification that was used in developing the system are:
- Processor: Intel® Celeron® CPU N3060 @ 1.60GHz 1.60
- System Type: 64-bit operating system, x64-based processor
- Memory (RAM): 4.00 GB
Software Specification for System Development:
The software specification that was used in developing the system are:
- Windows 10 Pro
- Sublime Text 3
- XAMPP v3.2.2
- Chrome/Edge
Hardware Specification for System Requirements:
Here’s the hardware specification that the system requires:
- Processor: Intel® Celeron® CPU N3060 @ 1.60GHz 1.60
- System Type: 64-bit operating system, x64-based processor
- Memory (RAM): 4.00 GB
Software Specification for System Requirements:
Here’s the hardware specification that the system requires:
- Windows 10 Pro
- Chrome or Edge
Related Capstone Resources
- Automated Basketball Scheduling And Monitoring System Chapter 1
- Automated Basketball Scheduling And Monitoring System Chapter 2
- Automated Basketball Scheduling System Chapter 4 Documentation
- Tools And Equipment Monitoring System Methodology
- Chapter 3 Methodology Attendance Monitoring System 2019 Doc
- Pharmacy Management System Thesis Chapter 3 Methodology
Inquiries
If you have any questions or suggestions about Documentation – Chapter 3, 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 →