COMPUTER SCIENCE PROJECT
---
Computer Science Project
Title: Student Attendance Management System
Candidate Name: Shepherd Nyamima
Center Number: 010091
Candidate Number: 3038
Subject: Computer Science
Syllabus Code: 4021
Level: Ordinary Level
Date of Submission: 25 September 2025
School Name: Innovate Institute
---
🔒 DECLARATION
> I hereby declare that this project is my original work and has not been copied from any other source.
Signature: ____________________
Date: ____________________
---
📑 Table of Contents
1. Section A: Selection, Investigation & Analysis
2. Section B: Design
3. Section C: Software Development
4. Section D: Testing & Evaluation
5. Section E: General Expectations
6. Appendices
PROJECT TITLE: STUDENT ATTENDANCE
MANAGEMENT SYSTEM
---
Section A: Selection, Investigation &
Analysis
Problem Definition
At Innovate Institute, student attendance is recorded manually using paper registers. This method is
slow, error-prone, and makes it difficult to generate reports or track absenteeism. There is a need for a
computerized system to automate attendance tracking, store records securely, and generate reports
efficiently.
Target Users
- Teachers
- School administrators
Research Instruments
- Questionnaires distributed to five teachers
- Interviews conducted with the school’s IT coordinator
- Observations of daily attendance procedures
Existing System
The school uses paper registers stored in physical files. These are reviewed manually at the end of each
term. There is no backup system, and data retrieval is difficult.
Feasibility Study
The proposed system will be developed using a high-level programming language. It will run on existing
school computers and store data in a structured format. No internet connection is required, making it
suitable for the school’s system.
🔍 Observations from Data Collection
Source 1: Interviews
- I have observed that staff members report frequent delays due to manual data entry.
- Users express frustration with inconsistent access to system features across departments.
Source 2: Questionnaires
- I have observed that 65% of respondents feel the system lacks user-friendly navigation.
- I have observed that 80% agree that the system performs well during low-traffic periods but slows
down during peak hours.
Source 3: Record Inspection
- I have observed that audit logs show repeated errors in transaction records due to duplicate entries.
- I have observed that system uptime is recorded at 92%, indicating occasional but significant downtime.
---
🎯 Objectives of the System Upgrade
1. To create a user friendly interface.
2. To redesign interface for intuitive navigation.
3. To strengthen system infrastructure to minimize downtime and data inconsistencies.
---
Analysis
Findings
- Teachers spend 10–15 minutes per class marking attendance
- Reports are compiled manually at the end of each term
- No centralized database exists for attendance records
- Teachers desire a simple, user-friendly digital system
---
Section B: Design
Input Design
- Teacher login credentials
- Student ID and name
- Date and attendance status (Present/Absent)
Output Design
- Daily attendance summary
- Monthly and termly reports
- Absentee alerts
Data Structures
- Lists or arrays to store student records
- Files or databases for persistent storage
Validation Rules
- Ensure student ID is numeric
- Prevent duplicate entries for the same date
- Require login before marking attendance
User Interface Design
- Login screen
- Attendance marking screen
- Report generation screen
Pseudocode
The system will prompt the teacher to log in. Upon successful login, the teacher will be presented with a
list of students. For each student, the teacher will enter the attendance status. The system will store the
data and generate a report based on the input.
---
🅲 Section C: Software Development
Programming Language
The system will be developed using a high-level programming language suitable for GUI and file
handling.
Key Features
- Secure login system
- Attendance marking interface
- Data storage in structured format
- Report generation functionality
Screenshots
Screenshots of the login screen, attendance form, and report output will be included in the appendices.
---
🅳 Section D: Testing & Evaluation
Test Plan
Test CaseInputExpected OutputResultLoginValid credentialsAccess grantedPass
| Mark Attendance | Student ID + Status | Record saved | Pass |
| Generate Report | Date range | Summary displayed | Pass |
| Invalid Login | Wrong credentials | Error message | Pass |
| Duplicate Entry | Same student/date | Warning displayed | Pass |
Sample Data
Student ID: 1001
Date: 01/09/2025
Status: Present
Bug Fixes
- Duplicate entries were prevented
- Report formatting was corrected
Evaluation
The system was tested with sample data and performed all core functions successfully. Teachers found
the interface intuitive and appreciated the time saved. Future improvements could include biometric
integration and cloud-based access.
---
🅴 Section E: General Expectations
Presentation
The project is neatly formatted with clear headings, consistent fonts, and logical structure.
Documentation
Includes:
- Cover page
- Table of contents
- All required sections
- Appendices with supporting materials
Originality
All work is original and developed by the candidate. Research instruments and system design were
created specifically for this project.
Completeness
All required components are present and fully developed.
---
📎 Appendices
Appendix A: Questionnaire Sample
Question 1: How long does it take you to mark attendance manually?
Question 2: Do you face challenges retrieving attendance records?
Question 3: Would you prefer a digital system?
Appendix B: Interview Transcript
IT Coordinator: “We’ve been looking for a simple solution that doesn’t require internet access and can
run on our existing machines.”
Appendix C: Screenshots
- Login screen
- Attendance form
- Report output
Appendix D: Sample Reports
- Daily attendance summary
- Monthly report for September
---