Classroom Management System

December 21,
2023

Attendance Tracking Module

CLASSROOM MANAGEMENT SYSTEM: A MODULE FOR ATTENDANCE TRACKING SYSTEM

 Jethro Malabar
Joshua Magdagasang
Justine Francisco
John Paul Colita
John Paul Burnea
Bonjovie Belbelone
Ben Ryan Rinconada
Jervin Sapid

A System Documentation Submitted to the Faculty of Computing, Data Sciences,

Engineering and Technology of the Davao Oriental State University
In Partial Fulfillment of the Requirements
for the course

ITP 133 – SYSTEMS INTEGRATION AND ARCHITECTURE

DECEMBER 2023
TABLE OF CONTENTS
TITLE PAGE
Title i
Table of Contents iii
List of Tables iv
List of Figures v
List of Appendices vi

CHAPTER I PROJECT DESCRIPTION

1.1 Project Overview
1.2 The Purpose of the Project
1.2.1 Background of the Project
1.2.2 Goals of the Project
1.3 The Scope of the Work
1.3.1 The Current Situation
1.3.2 The Context of the Work
1.4 Product Scenarios
1.5 Stakeholders
1.5.1 The Client
1.5.2 The Customer
1.5.3 The Users
1.5.4 Other Stakeholders
1.6 Mandated Constraints
1.6.1 Solution Constraints
1.6.2 Schedule Constraints
1.6.3 Budget Constraints
1.6.4 Implementation Environment of the Current System
1.7 Definition of Key Terms

CHAPTER II REQUIREMENTS
2.1. Product Use Cases
2.1.1 Use Case Diagrams
2.1.2 Product Use Case List
2.1.3 Use Case Descriptions
2.2. Functional Requirements
 2.3. Non-functional Requirements
2.3.1 Data Requirements
2.3.2 Performance Requirements
2.3.3 Dependability Requirements
2.3.4 Maintainability and Supportability Requirements
2.3.5 Security Requirements
2.3.6 Usability Requirements
2.3.7 Look and Feel Requirements
2.3.8 Operational and Environmental Requirements
2.3.9 Cultural and Political Requirements
2.3.10 Legal Requirements

CHAPTER III DESIGN AND METHODOLOGY

3.1 Software Methodology Model
3.2 System Design
3.3 Current Software Architecture
3.4 Proposed Software Architecture
3.4.1 Overview
3.4.2 Class Diagrams
3.4.3 Sequence Diagrams
3.4.4 State Transition Diagrams
3.4.5 Activity Diagrams
3.4.6 Data Dictionary
3.4.7 Access control and security
3.5. User Interface
3.6. Object Design

CHAPTER IV TEST PLANS

4.1. Features to be tested / not to be tested
4.2. Pass / Fail Criteria
 4.3. Test cases

CHAPTER V PROJECT ISSUES, SOLUTIONS, RISKS AND COSTS

5.1. Open Issues
5.2. Off-the-Shelf Solutions
5.3. Possible Risks
4.1. Possible Cost

References / Bibliography (Use APA format)

Appendices
Gantt Chart
Letters
User’s Manual
Curriculum Vitae
 1

LIST OF TABLES

Table 1: Class_session Data Dictionary

Table 2: Class_Attendance Data Dictionary

Table 3: Faculties Data Dictionary

Table 4: Students Data Dictionary

Table 5: Subjects Data Dictionary

 2

LIST OF FIGURES

Figure 1. Context Diagram for Attendance Tracking System/Module

Figure 2.1 QR Code Generation and Management
Figure 2.2 Attendance Tracking Using QR Code
Figure 2.3 Scanning and Validating QR Codes
Figure 3. Waterfall Model
Figure 4. Class Diagram
Figure 5. Sequence Diagram
Figure 6. State transition diagram (Top: Instructor’s Side; Bottom: Student’s Side)
Figure 7. Student’s activity diagram
Figure 8. Instructor’s activity diagram
Figure. 9. Student’s log in page
Figure. 10. Student’s welcome page
Figure. 11. Student’s QR scanning
Fig. 12. Faculty’s login page
Fig. 13. Faculty’s dashboard page
Fig. 14. Faculty’s class creation page

LIST OF APPENDICES
 3

Appendix 1: Gantt Chart

Appendix 2: Letters
Appendix 3: User’s Manual
Appendix 4: Curriculum Vitae
 4

CHAPTER I

PROJECT DESCRIPTION

Project Overview

This project introduces a revolutionary attendance tracking module utilizing QR codes within a

classroom management system (CMS). This user-friendly and efficient module aims to simplify and

automate attendance-taking, eliminating tedious manual tasks and ensuring accuracy while

empowering both instructors and students.

The Purpose of the Project

The purpose of this project includes the following:

 Eliminate time-consuming and error-prone manual attendance-taking methods.

 Streamline the attendance-taking process, enhancing classroom efficiency.

 Increase data accuracy and minimize discrepancies in attendance records.

 Provide a user-friendly experience for both instructors and students.

 Seamlessly integrate attendance data with the CMS for comprehensive student

monitoring and evaluation.

Background of the Project

In the modern classroom, the drawbacks of traditional attendance-taking techniques like physical

roll calls and sign-in sheets have become glaringly obvious, especially in large class sizes. These

traditional methods not only require a significant investment of teaching time but also have a high
 5

potential for human mistake and do not possess the necessary analytical skills required by the

demands of contemporary educational paradigms.

The motivation behind this project stems from a critical understanding of these shortcomings and a

pressing knowledge of the urgent need for an up-to-date, reliable, and technologically advanced

attendance tracking system. The idea of integrating a QR code-based module into a Classroom

Management System (CMS) is a strategic attempt to address the shortcomings inherent in

conventional approaches as educational institutions undergo a paradigm shift towards digital

transformation.

Among the current issues with manual attendance tracking systems include lengthy disruptions to

classes, possible errors in attendance logs, and a notable lack of quick insights into attendance

characteristics. These obstacles together affect the educational environment's overall operational

efficiency by restricting instructors' ability to make informed decisions based on attendance data.

The solution that is being presented is based on QR code technology and aims to address these

issues by providing a quick, accurate, and user-friendly method of tracking attendance. Through

the utilization of smartphones and the ease with which they can be scanned, the study aims to

optimize the process of taking attendance. This will reduce the amount of time that must be spent

on administrative work and allow teachers to spend more time on instructional activities.

In conclusion, this project introduces a QR code-based attendance tracking module in response to

the changing needs of educational institutions. This approach not only overcomes the drawbacks

associated with conventional techniques but also aligns with the overall goal of utilizing technology

to improve accuracy, efficiency, and data-driven decision-making in the context of modern

education.

Goals of the Project

 Reduce attendance-taking time compared to traditional methods.

 Eliminate manual data entry errors, achieving high accuracy in attendance records.
 6

 Increase student engagement through a quick and easy scanning process.

 Empower instructors with real-time attendance data.

 Centralize attendance information within the existing CMS for comprehensive data

analysis.

The Scope of the Work

This attendance-tracking module will be used in classes who are currently using traditional

attendance-tracking methods such as roll calls or sign-in sheets or forms. Currently, most of the

classes or classrooms uses these traditional methods in order to keep tract of the attendance of

the students. This method often consumes a few minutes before the class can proceed to its

discussions or activities especially for classes who have larger population of students. Thus, this

module will be used in order to solve that problem. This module will mainly focus on tracking the

attendance of the students within a class in a faster and more efficient way.

Additionally, the project focuses on developing and integrating the QR code-based attendance

tracking module within the CMS. This will primarily involve:

Module design and functionality: Creating a user-friendly interface for both instructors and

students.

QR code generation and management: Implementing a secure system for generating unique QR

codes for each class or session.

Attendance recording and synchronization: Ensuring seamless recording of student attendance

upon scanning and data synchronization with the CMS.

CMS integration: Ensuring seamless integration of the module with a variety of existing CMS

platforms.

The Current Situation

 7

Upon analyzing and examining the current process or methods used by instructors or teacher in

attendance tracking, they commonly use manual attendance tracking which involves:

Roll Calls: These traditional processes are recognized for their time-consuming nature, often

disrupting the natural flow of classroom activities. Notably, roll calls are susceptible to being a

source of inefficiency, contributing to a less-than-optimal use of instructional time.

Sign-in Sheets: The deployment of sign-in sheets as an attendance-tracking mechanism

introduces an inherent vulnerability to errors and missing data. The reliance on manual input raises

significant concerns regarding the accuracy and completeness of the recorded attendance

information.

These antiquated attendance-taking methods pose a series of challenges, including:

Inefficient Use of Instructional Time: The conventional methods, particularly roll calls, are known

to consume valuable instructional time, diverting focus from the core educational objectives.

Error-Prone Data Due to Human Oversight: Manual processes, such as sign-in sheets, are

predisposed to inaccuracies arising from human errors, potentially compromising the integrity of

attendance records.

Inconvenience for Students, Especially in Large Classes: The inherent limitations of traditional

attendance methods become exacerbated in the context of larger class sizes, creating an

inconvenience for both students and instructors.

The Context of the Work

Below is the context diagram for the Attendance Tracking Module, visually illustrating the module's

interaction with the existing CMS, students, and instructors. This diagram will depict the various

data flows and information exchanges within the system.

 8

Figure 1. Context Diagram for Attendance Tracking System/Module

Product Scenarios

In the envisioned utilization of the QR code-based attendance tracking module, several scenarios

delineate its seamless integration into the educational milieu. Below are the following scenarios:

Scenario 1: An instructor initiates the attendance tracking process by generating a unique QR

code tailored to their class within the Course Management System (CMS).

Scenario 2: The instructor strategically displays the generated QR code in a prominent location

within the classroom, ensuring optimal visibility for attending students.

Scenario 3: As students enter the classroom, they adeptly employ their smartphones to scan the

displayed QR code, instantaneously recording their attendance via the intuitive QR code-based

system.

Scenario 4: The system systematically and automatically registers the attendance of each student,

swiftly updating the CMS database with the latest attendance information.
 9

Scenario 5: Subsequently, the instructor accesses comprehensive attendance reports and

conducts a meticulous analysis of student attendance patterns directly within the CMS interface.

This empowers educators with invaluable insights for informed decision-making and pedagogical

adjustments based on real-time attendance data.

Stakeholders

The Client: Educational institutions seeking to enhance their attendance tracking.

The Customer: Instructors and students who will directly benefit from the module's user-friendly features

and efficient functionality. In the case of mass-market product development, the customer encompasses

individuals, typically educators and students, who are likely to procure and utilize the product.

The Users: Potential users of the product include instructors responsible for attendance management and

students engaging with the attendance tracking module through smartphone scanning.

Other Stakeholders:

IT Personnel: IT professionals responsible for CMS integration and maintenance, ensuring the seamless

incorporation of the QR code-based attendance tracking module into existing technological infrastructures.

Administrators: Individuals overseeing attendance policies and data management, who play a pivotal role

in the strategic implementation and adherence to attendance-related protocols within the educational

institution.

Mandated Constraints:

Security: The module must adhere to strict data security standards to protect student privacy and

attendance information. Encryption, secure authentication protocols, and data access controls are

paramount.
 10

Accessibility: The module must be accessible to students with disabilities, including those with

visual or motor impairments. Alternative modes of attendance recording should be available if QR

code scanning presents challenges.

Scalability: The module should be scalable to accommodate various class sizes and institutions.

Efficient server infrastructure and flexible design are crucial.

Interoperability: Seamless integration with the CMS to avoid disrupting data flows and existing

workflows.

Solution Constraints:

Technology Choice: The chosen technology stack should be reliable, secure, and compatible with

the CMS. Open-source and industry-standard technologies are preferred for easier integration and

maintenance.

Privacy Concerns: Striking a balance between data collection and student privacy is crucial. Data

anonymization and clear communication about data usage policies are essential for building trust.

Schedule Constraints:

Project Timeline: A clear timeline with milestones for development, testing, and deployment must

be established. Meeting deadlines is crucial for minimizing disruption to academic schedules.

Pilot Testing: Conducting pilot testing with a select group of instructors and students before full

implementation allows for early identification and resolution of potential issues.

User Training: Adequate training materials and support must be provided for both instructors and

students to ensure smooth adoption and effective utilization of the module.

Budget Constraints:

Development Costs: Carefully outlining development costs for software, hardware, and personnel

is essential for securing funding and ensuring efficient resource allocation.

 11

Maintenance and Support: Budgeting for ongoing maintenance, updates, and technical support is

crucial for the long-term viability and sustainability of the module.

Cost-Benefit Analysis: Conducting a cost-benefit analysis to quantify the potential savings in

time, reduced errors, and improved data management can help secure funding and demonstrate

the module's value proposition.

Implementation Environment of the Current System:

CMS Platform: The module should be compatible with the CMS platform to be used by

educational institutions. Understanding the technical specifications and limitations of this platform is

crucial for seamless integration.

Network Infrastructure: Reliable and secure network infrastructure is essential for real-time

attendance recording and data synchronization.

Student Devices: The module should be accessible through a variety of student devices, including

smartphones, tablets, and laptops, to cater to diverse technological preferences.

Definition of Key Terms:

QR Code. A two-dimensional barcode encoding information readable by smartphones and other

devices. In this context, it uniquely identifies a class or session for attendance recording.

Classroom Management System (CMS). A software platform used by educational institutions to

manage various aspects of classroom administration, including student records, course materials,

and communication tools.

Attendance Tracking Module. The software component within the CMS designed specifically to

record and manage student attendance using QR codes.

Integration. The seamless connection between the attendance tracking module and the existing

CMS platform, enabling data exchange and centralized management.

 12

Stakeholder. Individuals or groups with vested interests in the project's success, including clients,

customers, and other relevant parties.

CHAPTER II

REQUIREMENTS

Product Use Cases

 13

In this section, we delve into the detailed and precise steps that the attendance tracking system

takes during its performance. Use cases are instrumental in not only defining the system's

boundaries but also in pinpointing functional requirements and initial objects.

Use Case: Attendance Tracking System

Actors:

 Faculty/Instructor

 Students

Preconditions:

 Faculty have already created an account.

 Students have been informed by faculty about login instructions including the URL of the

website.

 Both actors must have internet connection and devices to use.

Faculty Side Flow:

 Step 1: Faculty access website and enters login credentials.

 Step 2: Faculty is logged in successfully. Redirect to faculty main dashboard.

 Step 3: Faculty select attendance page to use the module for attendance. Redirects to

attendance dashboard.

 Step 4: Faculty selects, and view generate session page.

 Step 5: Faculty enters subject code.

 Step 6: Faculty select conduct session. System automatically generated QR code for that

session.

 Step 7: Faculty select and set session status to active.

 Step 8: Faculty gives the generated QR code to class for students to scan.

Student Side Flow:

 14

 Step 1: Student access website and enter log in credentials.

 Step 2: Student is logged in successfully. Redirect to student portal homepage.

 Step 3: Student select QR scanner.

 Step 4: Student Scans the QR code given by the faculty.

 Step 5: Student will be notified the attendance is recorded.

Postconditions:

 Attendance data for the class session is updated in the system specifically on faculty’s

side attendance page.

 Faculty can view updated attendance record for the class on attendance page.

 After class attendance faculty could delete the session created.

Use Case Diagram

 15

Figure 2.1 QR Code Generation and Management

 16

Figure 2.2 Attendance Tracking Using QR Code

 17

Figure 2.3 Scanning and Validating QR Codes

Product Use Case List

1. Attendance Tracking with QR Codes: This use case involves the process of tracking student

and teacher attendance using QR codes, including the steps to generate and display QR

codes, scan them, and record attendance.

2. QR Code Generation and Management: This use case focuses on the generation and

management of QR codes, including creating new QR codes, updating existing ones, and

deleting unnecessary ones.

3. Scanning and Validating QR Codes: This use case involves the process of scanning QR

codes, validating their integrity, and updating attendance records accordingly.

Use Case Descriptions

Use Case Name QR Code Generation and Management

Actors  Faculty

 Have internet connection.

Preconditions  Faculty already have an account

Step 1: Faculty will enter the Inova Class website URL. Successfully
Descriptions browsed the website and login page.
Step 2: Enter login credentials. Successfully logged in. Redirect
Normal Step 3: Select attendance page to use the module for attendance.
Redirects to attendance dashboard.
 18

Flow Step 4: Selects, and view generate session page.

Step 5: Enters subject code.
Step 6: Select conduct session. System automatically generates QR code
for that session.
Step 7: Faculty gives the generated QR code to class for students to
scan.

 Students can successfully scan the QR code.

Postconditions  Faculty could delete the session created if the time
intended for the specified class session has ended.

Step 1: Faculty may enter different subject code and conduct

Alternative Flows and Exceptions session.
Step 2: Delete session.
Step 3: Enter the subject code.
Step 4: Conduct session.
 19

Use Case Name Attendance Tracking Using QR Code

Actors  Faculty
 Students
 Have internet connection.
Preconditions  Faculty already have an account.
 Faculty is already logged in on Inova Class website and have
conducted a session.
 Student Already have an account.
Step 1: Faculty will give/show the session generated QR code to
Descriptions students.
Step 2: Students enter Inova Class student portal. Successfully
Normal Flow browsed the website and redirected to Login page.
Step 3: Enter Login credentials. Successfully logged in. Redirected to
student portal homepage.
Step 4: Use QR scanner. Navigate the QR scanner at the bottom-center of
the student portal. Successfully opened the scanner.
Step 5: Students can now scan the given QR code by the faculty.

 Students successfully scan the QR code.

Postconditions  Faculty could delete the session created if the time intended
for the specified class session has ended.
 Prompt should appear on the student portal for successfully
attending that session.

Step 1: Students input wrong login credentials.

Alternative Flows and Exceptions Step 2: Student must strictly follow the instructions for logging in.
Step 3: Student input correct login credentials. Successfully logged in.
Step 4: Use QR scanner.
 20

Use Case Name Scanning and Validating QR Code

Actors  Faculty
 Students
 Have internet connection.
Preconditions  Faculty already have an account.
 The faculty is already logged in on Inova Class website and
already in attendance module using the generate session
page.
 Student Already have an account and knows the URL of
the student portal website. Also know where to find the
QR scanner.

Descriptions Faculty Side:

Step 1: Faculty enter subject code and select conduct session.
Normal Flow Student Enter login credentials. Successfully logged in.

Step 2: Generate session QR code. QR code successfully and

automatically generated after conduct session. Students opened
QR Code.
Step 3: Gives/shows session generated QR code to students.
Students scan the given QR code. Students successfully scanned
the QR code.
Step 4: Student portal prompts a message indicating that the
student successfully attended the session. Faculty view
attendance page for verifying.

 Student id and other details appear on the attendance

Postconditions page on faculty side.
 Faculty could delete the session created if the time
intended for the specified class session has ended.

Alternative Flows and Exceptions

 21

Functional Requirements

QR Code Generation: The system must allow instructors to generate unique QR codes for each

class in the CMS. QR codes must be securely generated, ensuring uniqueness and authenticity.

QR Code Display: The system must enable instructors to display the generated QR code within

the classroom environment. Display mechanisms should be compatible with common projection

systems.

QR Code Scanning: The attendance tracking app must facilitate QR code scanning for students.

The system must validate and record scanned data in real-time.

Attendance Recording: The system must automatically update attendance records in the CMS

upon successful scanning. Data synchronization must be seamless and immediate.

Access to Attendance Reports: Instructors should have access to comprehensive attendance

reports within the CMS. Reports should be easily generated and navigable.

Non-functional Requirements

Security: Data transmitted during QR code scanning must be encrypted to ensure privacy and

prevent unauthorized access. Authentication mechanisms must be robust, protecting against

unauthorized QR code generation.

Accessibility: The attendance tracking app must be accessible to students with disabilities,

providing alternative methods for attendance recording. QR codes must have sufficient contrast

and readability for users with visual impairments.

Scalability: The system should accommodate varying class sizes and institutional scales.Server

infrastructure must be scalable to handle increased loads during peak times.

 22

Interoperability: The attendance tracking module must seamlessly integrate with a variety of

existing CMS platforms. Compatibility with different CMS versions and configurations should be

ensured.

Data Requirements:

Performance Requirements:

1. The system must exhibit fast and efficient performance, minimizing latency during QR code

scanning and validation processes.

2. It should have the capability to handle a large number of concurrent users engaging in scanning

and validating QR codes simultaneously, ensuring optimal responsiveness.

Dependability Requirements:

1. The system must demonstrate high reliability, ensuring consistent availability of attendance

tracking and management functions using QR codes.

2. Fault-tolerance mechanisms should be in place to handle unexpected issues, ensuring

continuous operation even in the event of system failures.

Maintainability and Supportability Requirements:

1. The system must be designed for easy maintenance, with clear and comprehensive

documentation provided to facilitate ongoing support.

2. A robust change management process should be established to streamline updates,

enhancements, and troubleshooting procedures.

Security Requirements:
 23

1. The system must comply with stringent data protection and privacy requirements, implementing

access controls to safeguard attendance data associated with QR codes.

2. Integrity checks and encryption mechanisms must be in place to prevent unauthorized access or

tampering of QR code-related information.

Usability Requirements:

1. The system must feature a user-friendly interface, ensuring ease of use for individuals involved

in scanning and validating QR codes.

2. Clear and concise instructions should be provided to guide users through the attendance

tracking process, minimizing the learning curve.

Look and Feel Requirements:

1. The system's design must be professional, adhering to a visually appealing aesthetic consistent

with the school's branding and guidelines.

2. The interface should be intuitive, promoting a positive user experience and aligning with the

overall visual identity of the educational institution.

Operational and Environmental Requirements:

1. The system must be adaptable to various environmental conditions, supporting different devices

for QR code scanning and validation.

2. Compatibility with diverse network configurations is essential to ensure seamless operation

across different environments within the educational institution.

Cultural and Political Requirements:

1. The system must be culturally sensitive, respecting and accommodating diverse cultural

practices within the educational setting.

 24

2. It should comply with relevant laws and regulations governing cultural practices and political

considerations in the region where it is implemented.

Legal Requirements:

1. The system must fully comply with all applicable laws and regulations, including but not limited to

data protection and privacy requirements associated with the use of QR codes.

2. Legal considerations related to the collection, storage, and processing of attendance data

through QR codes must be rigorously adhered to, ensuring full legal compliance.

CHAPTER III

DESIGN AND METHODOLOGY

 25

Software Methodology Model

Figure 3. Waterfall Model

The Waterfall Model is considered suitable for the development of the attendance tracking module/system

due to its alignment with the project's well-defined and stable requirements. With clear sequential phases,

such as design, implementation, and testing, the Waterfall Model accommodates the structured nature of

developing a QR code-based attendance system. Its document-driven approach ensures comprehensive

documentation, aiding in tracking progress and facilitating future maintenance. Given the module's

predictable requirements and the critical need for adherence to academic schedules in educational

institutions, the Waterfall Model provides a reliable and systematic framework, emphasizing risk

management, reduced ambiguity, and a predictable timeline. While the Waterfall Model may not be

universally applicable, its suitability for this project lies in its ability to provide a disciplined and well-

organized approach to software development.

 26

System Design

Components:

1. QR Code Generation and Distribution:

 Each instructor/faculty generate unique QR Code for each class.

 QR codes can be generated and distributed through a dedicated portal or integrated with

existing student information systems.

2. QR Code Scanning

 Students scan the QR Code generated by the teacher using their devices.

3. Data Management and Processing

 Scanned QR code data is transmitted for processing.

 Server verifies student IDs, and timestamps attendances.

 Attendance data is stored securely in a database for future reporting and analysis.

4. Notifications and Reporting:

 Real-time attendance updates can be sent to teachers or administrators through

dashboards or notification systems.

 Detailed attendance reports can be generated for individual students, classes, or by

year, providing insights into attendance trends and potential issues.

Current Software Architecture

Canvas Attendance Architecture:

Data Model: Canvas likely stores attendance data in a relational database, such as MySQL or

PostgreSQL. This data model likely includes tables for users, courses, attendance

events, sessions, and enrollments.

 27

Attendance Events: Canvas captures attendance through various methods, such as:

 Activity completion: Tracking completion of assignments, quizzes, or other activities.

 Attendance module: Students can manually mark attendance within a dedicated module.

 Integrations: Canvas can integrate with external attendance systems (e.g., Zoom) for real-

time tracking.

 Events Processing: Once captured, attendance events are processed to calculate overall

attendance percentages, identify late arrivals, and generate reports.

 Reporting: Canvas provides various reports on attendance, such as individual student

attendance for a course, overall course attendance, and instructor attendance reports.

 API Access: Canvas provides an API for developers to access and manipulate attendance

data, potentially for custom integrations or reporting tools.

Proposed Software Architecture

Frontend (User Interface):

Instructor Interface:
 Dashboard: A user-friendly dashboard for instructors to manage classes, generate QR
codes, and view attendance reports.
 QR Code Generator: A tool to generate unique QR codes for each class or session within
the CMS.
 Attendance Reports: Real-time and historical attendance reports for instructors to analyze
attendance patterns.
Student Interface:
 QR Code Scanner: An intuitive interface for students to scan QR codes using their
smartphones.
 Confirmation: Instant feedback to students upon successful attendance registration.
 Accessibility: Alternative modes for attendance recording for students with disabilities.

Backend:
Authentication and Authorization:
 Secure login for instructors and students.
 Role-based access control to ensure proper authorization.
QR Code Management:
 28

 Generation: Secure generation of unique QR codes tied to specific classes.

 Validation: Verification of scanned QR codes to prevent fraudulent attendance.
Attendance Recording:
 Real-time recording of attendance data upon successful QR code scanning.
 Synchronization: Seamless integration with the CMS to update attendance records.
Database:
 Storage of attendance data in a secure and scalable database.
 Encryption: Implement encryption for sensitive data to adhere to security standards.
CMS Integration:
 API (Application Programming Interface): Develop APIs for integration with different CMS
platforms.
 Data Exchange: Ensure smooth data flow between the attendance module and the CMS.

Mobile Application (Optional):

Instructor App:
 QR Code Generation: Capability for instructors to generate QR codes on-the-go.
 Notification: Receive real-time notifications on attendance updates.
Student App:
 QR Code Scanner: Integrated QR code scanner for students.
Security:
Encryption:
 Encrypt sensitive data stored in the database.
Overview

Class Diagram
 29

Figure 4. Class Diagram

Our class diagram encapsulates the core entities - 'Instructor,' 'Student,' 'Student-Profile,' 'Class

Session' and 'Attendance record.' The 'Instructor' initiates a 'Class Session,' leading to QR code

generation. 'Students' interact with the system through the web app, scanning the QR code to mark

their attendance. The relationships are designed intuitively, offering a clear visual of how the

system entities collaborate.

Sequence Diagram

Figure 5. Sequence Diagram

 30

Step into the sequence diagram, a visual storytelling of our QR Code Scanning System. It unfolds

with the 'Instructor' commencing a new 'Class Session,' triggering QR code creation. 'Students'

then log in, scan the QR code, and voilà—the system validates their attendance as 'present.' This

dynamic illustration captures the elegant dance of interactions within the system.

State Transition Diagram

Figure 6. State transition diagram (Top: Instructor’s Side; Bottom: Student’s Side)

Behold the state transition diagram, illustrating the system's various states. Starting from 'No

Ongoing Cass,' it gracefully transitions to 'New Class being Active' as the 'Instructor' launches a
 31

'Class Session.' As 'Students' engage, scanning the QR code,' marking their attendance as

'present.' It's a visual journey through the system's dynamic states.

Activity Diagram

Figure 7. Student’s activity diagram

 32

Figure 8. Instructor’s activity diagram

The instructor, after logging into the system, starts a new class session, generates a unique QR

code associated with the session, displays the QR code for student scanning, monitors real-time

attendance validation as students scan the code, and, optionally, concludes the class session to

end the attendance tracking process.

The student initiates the process by logging into the web app, navigates to the ongoing class

session, scans the QR code using the web app on their phone, undergoes QR code verification,

and, upon validation, has their attendance marked as 'present' in real-time.

 33

Data Dictionary

Class_session

Field Name Data Type Field Length Constraint Description

id varchar 30 Primary Key A unique identifier for each class

sessions.

Faculty_id varchar 30 Foreign key The unique identifier for the faculty.

Subject_code varchar 10 Foreign key The unique identifier for each

Subject

created_at timestamp Not Null Time when the class session is

created

updated_at timestamp Time when the class session is

updated

status enum (0,1) Not Null Status of the current class session

Table 1: Class_session Data Dictionary

Class_Attendance

Field Name Data Type Field Length Constraint Description

id varchar 30 Primary Key A unique identifier for each class attendance

record.

faculty_id varchar 30 Foreign key The unique identifier for the faculty.

subject_code varchar 10 Foreign key The unique identifier for the Subject

attended_at timestamp Not null Time when the student has attended

updated_at timestamp Time when student attendance is updated

Table 2: Class_Attendance Data Dictionary

 34

Faculties

Field Name Data Type Field Length Constraint Description

Faculty_id varchar 30 Primary key The unique identifier for the faculty.

user_id varchar 30 Not Null The faculty's unique user id.

course varchar 30 Not Null Course where the faculty is assigned

Table 3. Faculties Data Dictionary

Students

Field Name Data Type Field Length Constraint Description

Student_id varchar 11 Primary Key Student’s unique identifier.

user_id varchar 30 Not null Student’s user id.

street varchar 255 Student’s user street location.

barangay varchar 255 Student’s user barangay location.

municipality varchar 255 Student’s user municipality location.

province varchar 255 Student’s user province location.

course varchar 11 Not null Student’s course.

Table 4. Students Data Dictionary

Subjects

Field Name Data Type Field Length Constraint Description

Subject_code varchar 10 Primary key The subject’s unique identifier.

description varchar 255 Not Null The subject’s description.

unit int 1 Not Null The subject’s unit.

 35

type enum Not Null The subject’s type.

created_at timestamp Not Null The subject’s creation time.

Updated_at timestamp The subject’s update time.

Table 5. Subjects Data Dictionary

Access control and security

In our proposed attendance tracking system, robust access control and security measures are

built-in throughout the design, ensuring data integrity and protecting against unauthorized access,

breaches, and misuse. Here are some key details:

User Authentication:

Role-based access control (RBAC): Users are assigned roles with specific permissions, limiting

access to sensitive data and functionalities based on their needs and responsibilities.

Session management: Automatic session timeouts and inactivity detection prevent unauthorized

access from compromised devices.

Data Security:

Data encryption: All sensitive data, including attendance records and personal information, are

encrypted at rest and in transit using law-standard algorithms.

Secure storage: We utilize secure databases with access controls to prevent unauthorized access

and track user activity.

Regular backups and disaster recovery: Data is regularly backed up to secure locations and a

comprehensive disaster recovery plan ensures system restoration in case of unforeseen events.

Security Monitoring and Alerts:

 36

Real-time anomaly detection: The system continuously monitors for suspicious activity, such as

unauthorized login attempts, unusual access patterns, or data breaches.

Logging and auditing: All user activity and system events are logged, providing a detailed record

for forensic analysis and compliance purposes.

Compliance:

Data privacy regulations: Our system adheres to relevant data privacy regulations and guidelines

to ensure user data is protected and handled responsibly.

Security audits and penetration testing: Regular security audits and penetration testing identify

vulnerabilities and ensure the system remains secure against evolving threats.

By implementing these comprehensive access control and security measures, our proposed

attendance tracking system ensures the integrity and protection of your sensitive data, promoting

trust and compliance while safeguarding your organization from potential threats.

Remember, security is an ongoing process, and we are committed to continuously improving and

updating our security measures to stay ahead of evolving threats and ensure the long-term

protection of your data.

User Interface
 37

Student’s Interface

Fig. 9. Student’s log in page Fig. 10. Student’s welcome page Fig. 11. Student’s QR scanning page

Faculty’s Interface

Fig. 12. Faculty’s login page

 38

Fig. 13. Faculty’s dashboard page

Fig. 14. Faculty’s class creation page

 39

CHAPTER IV

TEST PLANS

Scope and Objectives

This chapter outlines the test plan for the Attendance Tracking Module, a component integrated

within the Classroom Management System (CMS). This plan specifies features included and

excluded from the testing process, establishes pass/fail criteria for each element, and presents

sample test cases for comprehensive evaluation.

Features to be Tested

Teacher-Driven QR Code Management:

 Generation and management of unique QR code.

 Deactivation/update functionality for teacher QR codes.

 User interface (UI) design for efficient and intuitive QR code management.

Student Attendance Scanning:

 Compatibility of teacher QR code scanning with diverse student devices and authorized apps.

 Fast and accurate scan recognition and data processing upon student attendance recording.

 Real-time attendance updates within the CMS upon successful QR code scans.

 Handling of duplicate scans from different students during attendance.

Data Integration and Security:

 Seamless data exchange between scanned QR codes and the CMS database.

 Secure storage and access controls to protect against unauthorized data manipulation.

 Data analysis and reporting functionalities for attendance data captured through QR codes.

Features Not Tested

 40

 Existing manual attendance recording methods within the CMS, as the Attendance Tracking

Module aims to replace them.

 Features outside the current implementation scope, such as future integrations with other

systems beyond the CMS.

4.4 Pass/Fail Criteria

Teacher-Driven QR Code Management:

Pass: Teachers can easily generate and manage unique QR codes for each class/session and

deactivate/update them without issues. UI design facilitates efficient and intuitive QR code

management.

Fail: Difficulties in generating, managing, creating bulk QR codes, or deactivating/updating them.

Inefficient or unintuitive UI design.

Student Attendance Scanning:

Pass: Seamless scanning of assigned teacher QR codes with compatible devices and authorized

apps, fast and reliable scan recognition, real-time attendance updates, and effective handling of

duplicate scans.

Fail: Incompatibility with some devices or apps, scanning errors, delayed or inaccurate attendance

updates, or inability to handle duplicate scans correctly.

Data Integration and Security:

Pass: Seamless data exchange, secure storage and access controls, accurate data analysis, and

insightful reports based on QR code data.

Fail: Data transmission failures, vulnerabilities in access controls, data inconsistencies, or

inaccurate/misleading reports.

Sample Test Cases

 41

Test Case ID: ATM-0001

Objective: To comprehensively test the overall functionality of the module, including QR code

generation, scanning, data integration, accuracy, and reliability.

Test Steps

1. QR Code Management:

 Teachers generate unique QR codes for a representative group of classes/sessions

 Test QR code generation for a classroom

 Verify the interface for deactivating or updating teacher QR codes.

2. Attendance Scanning:

 Students attempt scanning assigned teacher QR codes using diverse compatible devices and

authorized apps.

 Simulate scenarios with simultaneous scanning or duplicate scan attempts from different

students.

3. Data Integration and Security:

 Verify real-time attendance updates within the CMS based on scanned QR codes.

 Compare scanned data against student records and confirm consistency.

 Run reports and analytics on QR code-based attendance data to verify accuracy and

completeness.

 Test security measures to ensure unauthorized access and data manipulation attempts are

unsuccessful.

Expected Results:

 Successful generation and management of unique QR codes for each class/session.

 42

 Seamless scanning of assigned teacher QR codes with compatible devices and authorized

apps.

 Accurate and immediate attendance updates within the CMS upon successful scans.

 No discrepancies or inconsistencies in attendance data captured through QR code scans.

 Effective handling of duplicate scans and prevention of potential attendance fraud.

 Secure data storage and access controls within the system.

Conditions:

 Ensure the Attendance Tracking Module is fully implemented and integrated within the CMS.

 Populate the test environment with sample student data and attendance records for realistic

execution

CHAPTER V

PROJECT ISSUES, SOLUTIONS, RISKS, and COSTS

This chapter, will delve into the various aspects of the Attendance Tracking Module, a crucial

component integrated into the Classroom Management System (CMS). The module's primary

function is to track student attendance through a QR code-scanning system, ensuring accurate and

timely records for teachers and administrators. This chapter will discuss the open issues, off-the-

shelf solutions, possible risks, and potential costs associated with the development and

implementation of the Attendance Tracking Module. By analyzing these factors, the project team
 43

aims to provide a comprehensive understanding of the challenges and opportunities that lie ahead

in this project.

Open Issues

The Attendance Tracking Module faces several open issues that need to be addressed to ensure

its successful integration within the CMS. These issues include:

Integration with CMS: The integration of the Attendance Tracking Module with the Classroom

Management System (CMS) raises concerns about seamless data exchange and compatibility. Any

discrepancies in data transfer between the two systems could lead to inaccuracies in attendance

records and affect the overall functionality of the module.

Handling Duplicate Scans: Addressing the potential for duplicate scans is crucial to maintain the

accuracy of attendance records. Implementing measures to prevent or manage instances where

multiple students scan the same QR code simultaneously is essential for the reliability of the

system.

Data Security and Access Controls: Ensuring secure storage and strict access controls for

attendance records is imperative. Unauthorized data manipulation or access could compromise the

integrity of the system and lead to inaccuracies in attendance tracking.

Off-the-Shelf Solutions

To tackle the open issues, the project team will explore various off-the-shelf solutions, such as QR

code scanning apps, existing attendance tracking systems, and best practices for handling

duplicate scans:

QR Code Scanning Apps: Examining existing QR code scanning applications and platforms is

essential to identify a solution that seamlessly integrates with the CMS. Compatibility and ease of

integration are key factors to consider during the evaluation process.

 44

Attendance Tracking Systems: Investigating available attendance tracking systems provides

insights into potential integration options and best practices. Analyzing the features and

compatibility of these systems can guide the development of the Attendance Tracking Module

within the CMS.

Duplicate Scan Handling Best Practices: Researching industry best practices for handling

duplicate scans in attendance tracking systems is necessary to implement effective measures

within the module. Learning from established solutions can help mitigate the risks associated with

duplicate scan occurrences.

Possible Risks

The Attendance Tracking Module is subject to several possible risks. These includes:

Integration Risks: Difficulties in integrating the Attendance Tracking Module with the CMS pose a

risk of data inconsistencies or loss. The likelihood of encountering integration challenges should be

carefully assessed to proactively address any potential issues.

Security Risks: Weak access controls and data security measures present a significant risk of

unauthorized data manipulation or access. Mitigating these risks through robust security

implementations is essential to safeguard the integrity of the attendance tracking system.

Usability Risks: The potential for an inefficient or unintuitive user interface for teachers and

students poses a usability risk. Addressing user experience concerns is vital to prevent confusion

or frustration, ultimately ensuring the effective adoption of the Attendance Tracking Module.
 45

Possible Costs

The development and implementation of the Attendance Tracking Module come with certain costs,

including the evaluation of off-the-shelf solutions, the implementation of security measures and

duplicate scan handling strategies, and the addressing of any integration or security-related issues:

Evaluation and Integration Costs: The cost of evaluating and integrating off-the-shelf solutions,

including QR code scanning apps and attendance tracking systems, should be considered. This

encompasses the resources required for compatibility assessments and integration efforts.

Security and Duplicate Scan Handling Costs: Implementing additional security measures and

measures to handle duplicate scans incurs associated costs. This includes the development and

integration of security protocols and duplicate scan prevention mechanisms.

Integration and Risk Mitigation Costs: Anticipating and addressing any integration or security-

related issues that may arise during development is essential. Allocating resources to mitigate

potential risks and ensure a seamless integration process is a fundamental aspect of the overall

project cost estimation.

By addressing these issues, exploring available solutions, identifying potential risks, and

considering the associated costs, the project team can gain a better understanding of the

challenges and opportunities associated with the development and implementation of the

Attendance Tracking Module within the Classroom Management System. This analysis will

ultimately guide the project's decision-making process and ensure the successful integration of the

module into the CMS.

 46

References
[1]

Inc., B. (2023). Retrieved from Blackboard Inc.: https://www.blackboard.com/

[2] Incorporated, D. W. (2023). Retrieved from QRcode.com: https://www.qrcode.com/en/

[3] LLC., G. (2023). Retrieved from Google Classroom: https://classroom.google.com/

[4] Hernandez, C., Aslankoohi, E., Frolikov, P., Li, H., Kurniawan, S., & Rolandi, M. (2023).
Implementing QR codes in academia to improve sample tracking, data accessibility, and
traceability in multicampus interdisciplinary collaborations. PloS one, 18(4), e0282783.
https://doi.org/10.1371/journal.pone.0282783

[5] Mohammed, Mustafa & Zidan, Khamis. (2023). Enhancing attendance tracking using
animated QR codes: a case study. Indonesian Journal of Electrical Engineering and Computer
Science. 31. 1716. 10.11591/ijeecs.v31.i3.pp1716-1723.

[6] Teamwork. (2020). Project Stakeholders – Who Are They & Why Are They Important?
Www.teamwork.com. https://www.teamwork.com/project-management-guide/project-
stakeholders/

[7] Waterfall Model - Software Engineering. (2018, March 18). GeeksforGeeks.

https://www.geeksforgeeks.org/waterfall-model/

[8] What is integration? - Definition from WhatIs.com. (n.d.). SearchCustomerExperience.

https://www.techtarget.com/searchcustomerexperience/definition/integration
 47

APPENDICES
Appendix 1. Gantt Chart
 48

Appendix 2. Letters

Classroom Management System

Attendance Tracking

DATE OF REQUEST SERVICE REQUESTED FOR ORGANIZATION

𝐅𝐚𝐜𝐮𝐥𝐭𝐲 𝐨𝐟 𝐂𝐨𝐦𝐩𝐮𝐭𝐢𝐧𝐠, 𝐃𝐚𝐭𝐚 𝐒𝐜𝐢𝐞𝐧𝐜𝐞𝐬, 𝐄𝐧𝐠𝐢𝐧𝐞𝐞𝐫𝐢𝐧𝐠 𝐚𝐧𝐝
𝐓𝐞𝐜𝐡𝐧𝐨𝐥𝐨𝐠𝐲 (𝐅𝐂𝐃𝐒𝐄𝐓)
October 27, 2023

SUBMITTED BY (key user contact) EXECUTIVE SPONSOR (funding authority)

Name Justine Francisco Name Cindy A. Lasco

Title Project Manager Title Program Head

Office Office

Phone Phone

TYPE OF SERVICE REQUESTED:

Information Strategy Planning Existing Application Enhancement

Business Process Analysis and Redesign Existing Application Maintenance

✓
(problem fix)

New Application Development Not Sure

Other (please specify ________________________________________________________

BRIEF STATEMENT OF PROBLEM, OPPORTUNITY, OR DIRECTIVE (attach additional documentation as necessary)

Traditional methods of monitoring student attendance take a lot of time, are inaccurate, and don't
provide you with up-to-date information. It is difficult for teachers to maintain accurate records and
 49

respond immediately to attendance issues when taking attendance by typing it into a computer or using
paper-based approaches. This not only wastes important instructional time but also makes it
challenging to use attendance data to raise academic standards. An excellent option to enhance and
simplify the attendance tracking procedure is to incorporate an advanced Attendance Tracking feature
into a classroom management system (CMS). Schools may eliminate manual entry and guarantee
accurate real-time attendance records by utilizing technology. This creates new opportunities for
improved student learning overall through more effective teacher-student communication,
individualized education practices, and data-driven decision-making. The CMS must be equipped with
a robust and approachable Attendance Tracking system. To automate the attendance tracking process,
this system should make use of cutting-edge technology like smart devices. It should provide teachers
and administrators with up-to-the-minute information about attendance across all academic activities
and classes. Not only are the issues with conventional attendance tracking methods to be resolved, but
attendance data is also to be made into a tactical tool for improving educational practice. To offer a
comprehensive approach to classroom administration, the system should be scalable, configurable,
and connect seamlessly with other CMS capabilities.

BRIEF STATEMENT OF EXPECTED SOLUTION

The expected solution involves the integration of an advanced Attendance Tracking module within the
Classroom Management System (CMS). The system aims to automate attendance recording, offering a
real-time, user-friendly interface for educators and students. It prioritizes privacy, implements robust
security measures, and seamlessly integrates with the academic calendar. The solution generates
comprehensive reports and analytics to empower educators with valuable insights, facilitating
personalized instruction and informed decision-making. Scalable, customizable, and integrated with
other CMS features, this solution seeks to transform attendance data into a strategic asset for proactive
and effective classroom management.

ACTION (IT Office Use Only)

Feasibility assessment approved Assigned to ______________________

Feasibility assessment waived Approved Budget $ ___________________

Start Date ________ Deadline _____________

Request delayed Backlogged until date: ______________

Request rejected Reason: ______________________________

Authorized Signatures:
______________________________ Cindy A. Lasco _

Project Executive Sponsor

 50

Appendix 3. User’s Manual

Faculty Side

Login Page: this is the entry point of the website and all you need to do is to input the credentials of the
faculties (email, password).
 51

Dashboard: In this part all you have to do is to click the attendance part
 52

Attendance Dashboard: In this part you may see we have a Attendance and Generate Session on our
dashboard. If you click the Generate Session you may choose a subject code that you handled and
generate session while at the Attendance part It will dispay the sudent that attended on that session.

Student Side

Student Portal: Students are required to input their credentials to sign in.
 53

Student Portal Dashboard: At this part all you have to do is to click the scanner to scan the qr code.
 54

CURRICULUM VITAE

BEN RYAN ANDAMON RINCONADA

Camia, Kinablangan, Baganga,
Davao Oriental

Cell no.: 09955497678

[email protected]

PERSONAL BACKGROUND
NICKNAME: “ben”
BIRTHDATE: June 09, 2003
BIRTHPLACE: Kinablangan
AGE: 20
NATIONALITY: Filipino
RELIGION: Roman Catholic
CIVIL STATUS: Single
FATHER’S NAME: Enresto P. Rinconada
MOTHER’S NAME Elma C. Andamon

EDUCATIONAL BACKGROUND
TERTIARY EDUCATION: Davao Oriental State University
2021 - Ongoing

SECONDARY EDUCATION: Dr. Beato C. Macayra National High School

2015 – 2021
PRIMARY EDUCATION: Kinablangan Elementary
School
 55

2009 - 2015

CURRICULUM VITAE

JOSHUA E. MAGDAGASANG
Adjesum Vlg, Brgy. Dahican, City
of Mati, Davao Oriental Cell no.:
09958658626
[email protected]

PERSONAL BACKGROUND
NICKNAME: “Josh”
BIRTHDATE: June 14, 2003
BIRTHPLACE: City of Mati
AGE: 20
NATIONALITY: Filipino
RELIGION: Faith Tabernacle
CIVIL STATUS: Single
FATHER’S NAME: Ronaldo M. Magdagasang
MOTHER’S NAME Marilyn E. Magdagasang

EDUCATIONAL BACKGROUND
TERTIARY EDUCATION: Davao Oriental State University
2021- ongoing
SECONDARY EDUCATION Davao Oriental Regional Science High
School2015- 2021
PRIMARY EDUCATION Rabat-
Rocamora Mati
Central
Elementary
School, Special
Education
Center
 56

2009 - 2015
CURRICULUM VITAE

JUSTINE CAMILO FRANCISCO

P-3 Upper Tagawisan, Brgy. Badas,
City of Mati, Davao Oriental

Cell no.: 09150522603

[email protected]

PERSONAL BACKGROUND
NICKNAME: “Gino”
BIRTHDATE: December 28, 2002
BIRTHPLACE: Metro Manila
AGE: 20
NATIONALITY: Filipino
RELIGION: Roman Catholic
CIVIL STATUS: Single
FATHER’S NAME: Rolan O. Francisco
MOTHER’S NAME Lesilda V. Camilo
EDUCATIONAL BACKGROUND
TERTIARY EDUCATION: Davao Oriental State University
2021 - Ongoing

SECONDARY EDUCATION: Mati National Comprehensive High School

2015 – 2021
PRIMARY EDUCATION: Juana Bolivar Peña
Florida Elementary
School

2009 - 2015
 57

CURRICULUM VITAE

JERVIN C. SAPID
Brgy. La Filipina, Tagum City,
Davao Del Norte

Cell no.: 09382119466

[email protected]

PERSONAL BACKGROUND

NICKNAME: “Jev”
BIRTHDATE: October 19, 2001
BIRTHPLACE: City of Tagum
AGE: 22
NATIONALITY: Filipino
RELIGION: Roman Catholic
CIVIL STATUS: Single
FATHER’S NAME: Ruben M. Sapid
MOTHER’S NAME Meryjene C. Sapid

EDUCATIONAL BACKGROUND
SENIOR HIGH SCHOOL: Tagum City Senior High School
Science, Technology, Engineering, and
Mathematics April 2020
JUNIOR HIGH SCHOOL: Tagum City Junior High School
April 2018
ELEMENTARY: La Filipina
Elementary
School March
 58

2014
CURRICULUM VITAE

Bonjovie A. Belbelone
Brgy. Sainz, City of Mati, Davao Oriental
Davao Oriental Cell no. : 09457847682
[email protected]

PERSONAL BACKGROUND
NICKNAME: "Bon"
Birthdate: December 8, 2000
Birthplace: Mati City
Age: 23
NATIONALITY: Filipino
RELIGION: Roman Catholic
CIVIL STATUS: Single
FATHER'S NAME: Rolando H. Belbelone
MOTHER'S NAME: Lucita P. Abunda
EDUCATIONAL BACKGROUND
TERTIARY EDUCATION: Davao Oriental State University
2021- ongoing
SECONDARY EDUCATION: Mati National Comprehensive
Highschool
2015-2021
PRIMARY EDUCATION: Biasong Pantukan elementary
school
2009-2015
 59

CURRICULUM VITAE

John Paul M. Burnea

Bilawan - 1, Brgy. Central, Mati City, Davao Oriental
Cell no. : 09674066080
[email protected]

PERSONAL BACKGROUND
NICKNAME: "Burn"
Birthdate: February 17, 2003
Birthplace: Rizal Ext. Mati City
Age: 20
NATIONALITY: Filipino
RELIGION: Roman Catholic
CIVIL STATUS: Single
FATHER'S NAME: Romulo A. Burnea
MOTHER'S NAME: Corazon M. Burnea
EDUCATIONAL BACKGROUND
Tertiary Education: Davao Oriental State University
2021 - Ongoing
Secondary Education: Mati National Comprehensive Highschool
2015 - 2021
Primary Education: Rabat-Rocamora Mati Central Elementary School
2009 - 2015
 60

CURRICULUM VITAE

JETHRO L. MALABAR
Brgy. Tamisan, City of Mati, Davao
Oriental Cell no.: 09533661605
[email protected]

PERSONAL BACKGROUND
NICKNAME:
BIRTHDATE: May 02, 2002
BIRTHPLACE: City of Mati
AGE: 21
NATIONALITY: Filipino
RELIGION: Baptist
CIVIL STATUS: Single
FATHER’S NAME: Joel D. Malabar
MOTHER’S NAME Mila L. Malabar

EDUCATIONAL BACKGROUND
TERTIARY EDUCATION: Davao Oriental State University
2021- ongoing
SENIOR HIGH SCHOOL: Davao Oriental Regional Science High
School Science, Technology,
Engineering, Mathematics
June 2021
JUNIOR HIGH SCHOOL: Davao Oriental Regional Science High
School
April 2019
ELEMENTARY: Bobon
Elementary
School
March 2015
 61

CURRICULUM VITAE

JOHN PAUL COLITA

Brgy. Matiao, Davao Oriental
Cell no.: 09773978599
[email protected]

PERSONAL BACKGROUND
NICKNAME:
BIRTHDATE: October 19, 2002
BIRTHPLACE: City of Mati
AGE: 21
NATIONALITY: Filipino
RELIGION: Roman Catholic
CIVIL STATUS: Single
FATHER’S NAME: Guillermo Colita
MOTHER’S NAME Melchora Cuadrasal

EDUCATIONAL BACKGROUND
TERTIARY EDUCATION: Davao Oriental State University
2021- ongoing
SENIOR HIGH SCHOOL: AICS-Montalban
June 2021
JUNIOR HIGH SCHOOL: KVNHS
April 2019
ELEMENTARY: KVES
March 2015