KYAMBOGO UNIVERSITY

DEPARTMENT OF COMPUTER SCIENCE

SCHOOL OF COMPUTING AND INFORMATION SCIENCE
COURSE UNIT: SOFTWARE ENGINEERING
LECTURER: DR. BEATRICE AGUTI
TASK: GROUP ASSIGNMENT
DATE OF SUBMISSION: 4TH MAY 2025
GROUP 7 MEMBERS
FULL NAME REGISTRATION NUMBER SIGNATURE
MIREMBE DIVINE K 23/U/ITD/08084/PD
ATUHAIRE EDWIN 23/U/ITE/15040/PE
BUKENYA BENJAMIN 23/U/ITD/083/GV
WINENA JOANN JO 23/U/ITD/13522/PD
KINTU MOSES 23/U/ITE/06997/PE
NATUKUNDA KEVIN 23/U/ITD/10897/PD

A REPORT SUBMITTED TO THE DEPARTMENT OF COMPUTER SCIENCE IN PARTIAL

FULLFILLMENT OF BACHELORS DEGREE OF INFORMATION TECHNOLOGY AND
COMPUTING.

i
Table of Contents
1CHAPTER ONE: REQUIREMENT ELICITATION........................................................................ 1
1.1Introduction................................................................................................................................. 1
1.2Reasons why students may resist organizational change of the new system.............................. 1
1.3How the University Can Alleviate Student Resistance to Change.....2
1.4Importance of validating the Automated Biometric-enabled
student attendance management system.............................................................3
2CHAPTER TWO: REQUIREMENTS ENGINEERING AND ANALYSIS.....................................6
2.1Introduction................................................................................................................................. 6
2.2Statement of need........................................................................................................ 6
2.3Scope study..................................................................................................................................6
2.4Feasibility: Technical Feasibility...............................................................................................6
2.4.1Economic feasibility.............................................................................................................6
2.4.2Operational Feasibility......................................................................................................... 7
2.4.3Technical Environment Description.....................................................................................7
2.5Functional Requirements.......................................................................................... 7
2.5.1User Authentication & Access Control................................................................................ 7
2.5.2Course Enrollment & Scheduling.........................................................................................8
2.5.3Attendance Logging............................................................................................................. 8
2.5.4Communication & Notifications.......................................................................................... 8
2.5.5Reporting & Analytics..........................................................................................................8
2.6Non-Functional Requirements................................................................................ 8
2.6.1Performance Requirements.................................................................................................. 8
2.6.2Scalability Requirements......................................................................................................9
2.6.3Security Requirements......................................................................................................... 9
2.6.4Reliability Requirements......................................................................................................9
2.6.5Usability Requirements........................................................................................................ 9
2.7Usage Scenarios and Use Cases:..........................................................................9
3CHAPTER THREE: OO DESIGN AND MODELLING USING UML.........................................12
3.1Introduction............................................................................................................................... 12
3.2Use case scenario called Update Course Sessions.................................................................... 13
3.3Sequence Diagram.....................................................................................................................14

ii
1 CHAPTER ONE: REQUIREMENT ELICITATION
1.1 Introduction
The implementation of an Automated Biometric-enabled Student Attendance
management system introduces both technical and adoption challenges.
Student resistance may arise from privacy concerns and reluctance to change,
requiring strategies like transparency and phased rollout. Simultaneously, real-
time validation ensures instant attendance of the students and all the
necessary outcomes for the new system.

1.2 Reasons why students may resist organizational change of the new
system.
1. Lack of Understanding and Awareness of the new system:
Students may resist the new system if they don’t clearly understand how,
it works or how it affects them. Concerns may include privacy issues with
biometric data, fear of being wrongly marked absent due to technical
errors, and uncertainty about how the system impacts academic records.
Poor communication and lack of training can lead to mistrust and anxiety.
2. Reduced Personal Freedom: Biometric systems may be seen as
intrusive or overly controlling, especially if students feel they are being
monitored constantly since the system may note the exact time a
student arrives. This level of precision does not favor latecomers, who
may feel penalized even for slight delays. As a result, students may
perceive the system as rigid and unforgiving, creating anxiety or
discomfort, particularly for those who struggle with punctuality due to
valid personal or logistical reasons. The feeling of being constantly
monitored may also contribute to resistance, as students feel they are
losing control over their daily academic routines.
3. Concerns About Privacy and Security: Using biometric data like
fingerprints can raise fears about data misuse, unauthorized access, or
identity theft. Students may worry that their personal information could
be stored insecurely, shared without consent, or used beyond attendance
tracking.
4. Increased Accountability: Automated systems will reduce loopholes
that students might have previously used to manipulate attendance for
example students sometimes register on attendance lists for their fellows
who are absent leading to resistance from students who relied on such
practices.
5. Lack of Involvement of students in decision making: Students may
resist the new system if they feel excluded from the decision-making
process. When changes are introduced without their input or feedback,
they may see the system as unfair or unnecessary. This lack of
engagement can lead to mistrust, reduced cooperation, and a sense of
being controlled rather than supported

1
 6. Adaptation Challenges: Some students may struggle to adapt to the
new biometric attendance system due to limited digital literacy,
especially those not familiar with using technology regularly. Additionally,
students with disabilities or those from undeserved backgrounds may
face accessibility issues, such as difficulty using fingerprint scanners or
lack of access to required devices. These barriers can lead to frustration,
reduced system usage, or outright rejection of the system.
7. Resistance to Change: Resistance to change often stems from
students' familiarity with the manual paper-based attendance system,
which they have grown used to over time. This habit can make them
skeptical about the benefits of the new biometric system, leading to
reluctance or fear of dealing with unfamiliar technology. Additionally,
students in their final years may view the change as unnecessary or
disruptive, especially if they feel they have successfully managed with
the old system and see little personal benefit in adapting to a new one so
close to graduation.
8. Lack of clear communication or training: Lack of clear
communication or training can significantly contribute to student
resistance, as highlighted by the case mentioning that students are
"anxious about the expected changes." This anxiety often stems from
inadequate sensitization about the purpose and benefits of the new
biometric attendance system, leaving students uncertain about how it
works or how it impacts them. Without a proper onboarding plan or user
training, many may feel unprepared or overwhelmed by the transition.
Additionally, if students are unaware of whether their opinions or
concerns were considered during the planning phase, they may feel
excluded from the decision-making process, further reducing their
willingness to embrace the change.
9. Fear of Punitive Measures: Students may worry that the new system
will be used to enforce strict attendance policies, resulting in penalties
like being blacklisted, suspended, or barred from exams if their
attendance is below 75%. This can create fear and resentment, especially
among students with valid reasons for occasional absence

1.3 How the University Can Alleviate Student Resistance to

Change
1. Conduct Awareness and Sensitization Campaigns
The University should launch early and continuous awareness campaigns
to educate students about the new system what it does, how it works,
and why it is being implemented. Using seminars, workshops, orientation
sessions, and departmental meetings can help reduce misinformation
and anxiety.

2
2. Provide Clear Communication Channels
Regular updates and clear communication through emails, student
portals, and noticeboards should address student concerns. The
University should explain the purpose, benefits, and implications of the
system in simple terms. FAQs, brochures, and demo videos can help build
understanding.
3. Offer Training and User Support
The University must offer hands-on training and support for students,
especially those who may struggle with technology or have accessibility
needs. Helpdesks and digital literacy sessions can ensure no student
feels left behind or unable to use the system properly.
4. Ensure Transparency About Data Privacy and Security
Address privacy concerns by clearly explaining how biometric data will be
collected, stored, and protected. Assure students that the system
complies with data protection laws and that their data won’t be used for
any unauthorized purpose. Sharing the data policy publicly can help build
trust.
5. Include Students in the Change Process
To avoid perceptions of top-down imposition, the University should
involve student representatives in planning and implementation. This
could include consultation forums, feedback surveys, and pilot testing.
When students feel heard and involved, they are more likely to support
the initiative.
6. Start with a Pilot Phase
Implementing the system in phases starting with a pilot in one
department or class can help identify and solve problems before a full
rollout. Students can then experience the system firsthand, see its value,
and provide input for improvement.
7. Be Flexible and Accommodate Special Cases
The University should consider flexible policies for students with genuine
challenges (e.g., disability, illness, or technical issues). Manual overrides
or support mechanisms should be in place to ensure fair treatment and
avoid unintended penalties.
8. Reframe the System as a Support Tool, not a Punishment Tool
Emphasize that the system is meant to support student success by
identifying at-risk students early, improving engagement, and reducing
administrative burdens not just to punish latecomers or absentees.
Positive messaging can reduce resistance.
9. Address the Fear of Increased Surveillance
The University should clarify that the system tracks attendance only and
does not monitor behavior or invade personal privacy. Clearly stating the
boundaries of system usage can reduce feelings of constant surveillance.

3
 10. Demonstrate Benefits with Real Examples
Showing how the system helps generate performance reports, improves
class participation tracking, or supports exam eligibility can make the
benefits tangible and relatable to students.

1.4 Importance of validating the Automated Biometric-enabled

student attendance management system
The Automated Biometric-enabled Student Attendance Management System
should be validated as a real-time system for the following reasons:

1. Continuous logging in:

The Automated Biometric-enabled Student Attendance Management
System allows for real-time logging of student attendance, which
eliminates the need for manual registers or waiting for administrative
updates. By utilizing biometric authentication (e.g., fingerprints or RFID),
students’ attendance is recorded the moment they arrive for a class. This
ensures that there are no delays in attendance tracking, and the system
provides immediate data for teachers and administrators to act on.
2. Accurate attendance tracking:
The real-time nature of the system ensures immediate reflection of students'
attendance status. By using biometric authentication, the system captures
students’ arrival times down to the second, avoiding errors like proxy
attendance or delays in recording absences. This level of accuracy helps
prevent discrepancies in the records and ensures the attendance data is up to
date for both instructors and students.
3. Timely monitoring of attendance patterns:
Since the system is real-time, it allows for immediate monitoring and analysis
of students' attendance trends. This enables lecturers and administrators to
track student participation and identify attendance issues as they arise, rather
than waiting for weekly or monthly updates. Prompt identification of students
who are consistently absent or late allows for quicker intervention and support
to improve academic engagement.
4. Instant reporting and feedback generation:
The system's real-time processing allows for an instant generation of reports.
Attendance reports can be produced immediately after a session ends,
ensuring that the most up-to-date information is available for administrative
and academic use. This is crucial for tracking student progress, generating
performance reports, and ensuring compliance with the University's attendance
policies, which require up-to-date attendance data for decision-making.
5. Reduction in administrative workload:

4
A real-time system reduces the time and effort required by administrative staff
to compile and process attendance data. With traditional manual systems, staff
must wait for all data to be entered and reviewed before creating reports. In
contrast, real-time updates provided by the biometric system streamline the
entire process, reducing administrative workload and allowing staff to focus on
other tasks, improving overall efficiency.
6. Improved accountability for the students and faculty:
Real-time tracking ensures accountability for both students and faculty.
Students can see their attendance status instantly and take necessary actions,
such as contacting lecturers when they are absent. Faculty members can also
monitor attendance in real time, ensuring they can address student absences
more effectively. This helps ensure that attendance policies are followed more
strictly, benefiting the overall academic integrity of the institution.
7. Enhanced system integration with other universities:
The real-time attendance data captured by the system can be integrated with
other university systems in real-time, such as the student portal or the
academic performance system. This allows students and faculty to receive live
updates on their attendance status, which can be used to make timely
decisions about academic progress, participation in courses, and eligibility for
exams. Immediate data exchange between systems enhances the functionality
and responsiveness of the University’s services.
8. Immediate identification of attendance issues
Real-time monitoring enables early detection of students who are chronically
absent or tardy. This allows instructors and administrators to quickly intervene
and offer support, such as sending reminders or engaging with the student to
understand the underlying issues. By addressing attendance problems as they
arise, the University can improve student retention, engagement, and overall
academic performance.
9. Proper communication with students
The real-time aspect of the system enhances communication between
students, lecturers, and administrators. If students are absent or have low
attendance, the system can automatically send alerts to the students via email
or SMS, notifying them of their attendance status. This reduces delays in
communication and ensures that students are aware of their standing before it
becomes a bigger issue, fostering better academic engagement.
10. Real time data accuracy and data tracking:
In a dynamic academic environment, having real-time data allows
administrators and faculty to make data-driven decisions quickly. Whether it’s
adjusting class schedules, providing additional support to students who are
struggling, or analyzing course engagement, real-time attendance data

5
provides accurate and up-to-the-minute insights, empowering decision-makers
to take timely action to improve educational outcomes.

2 CHAPTER TWO: REQUIREMENTS ENGINEERING AND

ANALYSIS
2.1 Introduction
This chapter introduces the development of the Automated Biometric-enabled
Students Attendance management system highlighting the statement of need,
feasibility techniques, requirements organized by the function and some of the
scenarios that will provide insights into the system.

2.2 Statement of need.

The current manual paper-based student attendance system is inefficient,

prone to errors, difficult to manage, and time-consuming. It lacks real-time
updates, is labor-intensive, and is easily manipulated (e.g., students signing in
for others). There is also no easy way to generate attendance reports or
monitor students' engagement over time. There’s a clear institutional need to
modernize the attendance process to ensure accuracy, security, and
automation.

2.3 Scope study.

The study focuses on the design of an Automated Biometric-enabled Student
Attendance Management System that utilizes biometric technologies such as
fingerprint or RFID for authenticating students during attendance registration.
The system will be developed to facilitate functionalities such as course
enrollment integration, real-time attendance tracking, and automated
generation of attendance reports. It also includes features for communicating
with students via email and SMS, particularly to notify those whose attendance
falls below 75%. The study encompasses user roles such as students, lecturers,
administrators, and the Dean of Students, and aims to ensure the system is

6
integrated with existing digital platforms like the Student Portal and the Time-
Tabling System to enable synchronized tracking of class sessions.

2.4 Feasibility: Technical Feasibility

The proposed system is technically feasible due to the existing infrastructure

already in place at the university. Lecture halls are equipped with biometric
access control systems, making it easier to integrate fingerprint or RFID
authentication without the need for extensive hardware installation.
Additionally, the university already uses digital platforms such as the Student
Portal and Time-Tabling System, which can be connected to the new attendance
system for seamless data sharing. Reliable internet access and server
capabilities at the university also support the implementation of a web-based
real-time system.

Economic feasibility
From a financial standpoint, the system is economically viable. Since the
university already possesses core biometric infrastructure, major investment
costs are significantly reduced. Biometric devices and RFID systems are now
relatively affordable and widely supported, minimizing both installation and
maintenance expenses. In the long run, the system will save money by
eliminating costs associated with manual paper-based attendance tracking
(e.g., paper, printing, storage) and reducing the administrative workload.
Furthermore, improved monitoring can help the university reduce academic
fraud and absenteeism, increasing the value of the investment.

Operational Feasibility
The new system aligns well with the university's operational needs and goals. It
directly addresses the inefficiencies of the current manual attendance system
by automating and digitizing attendance records, making data easier to access,
more accurate, and timely. Students, lecturers, and administrators are primary
users, and they are already familiar with digital platforms, reducing resistance
and the learning curve. Administrative staff and the Dean have shown support
for improving attendance management, which strengthens the likelihood of
smooth system adoption and usage.

Technical Environment Description

The technical environment for the Automated Biometric-enabled Student
Attendance Management System is built on a combination of existing on-
premises infrastructure and university-managed network systems. The current
infrastructure already includes access control systems with biometric hardware
(fingerprint/RFID scanners) installed in each lecture theatre, which significantly
simplifies integration with the new system. The university also maintains an
internal student portal and time-tabling system, which will be integrated to
synchronize course enrolment and session schedules. Networking across
campus is supported by a stable LAN/Wi-Fi environment with internet access,
facilitating real-time data synchronization and cloud backups.
7
The system will follow modular client-server architecture. At the front end,
students and lecturers will interact with the system via web and mobile
interfaces. These interfaces communicate with a centralized application server
via RESTful APIs. The application server manages core functions such as
authentication, attendance logging, notifications, and report generation. A
biometric module integrated into the Access Control System interfaces directly
with the backend, using APIs to send authenticated attendance events to the
central database. The backend also interacts with external systems like the
student portal and timetable service to fetch enrolment data and verify session
eligibility.

2.5 Functional Requirements

2.6
User Authentication & Access Control
The system will incorporate a secure user authentication and access control
framework, enabling students to verify their identities using biometric methods
such as fingerprint or RFID scans matched against pre-registered profiles. It will
support role-based access, ensuring that students, lecturers, administrators,
and deans can only access features relevant to their roles. Additionally,
lecturers and administrators will log in securely using usernames and
passwords, further safeguarding the system against unauthorized access.

Course Enrollment & Scheduling

The system will enable students to log in and enroll in their officially registered
courses, ensuring that only valid course selections are accepted. It will
integrate with the existing Student Portal and Time-Tabling System to
automatically retrieve course and timetable information. Before recording
attendance, the system will validate each student's enrollment to ensure they
are eligible to attend the specific session, thereby maintaining accurate
attendance records.

Attendance Logging
The system will automatically log student attendance in real time when a
fingerprint or RFID scan is performed at the lecture hall entrance, accurately
linking each record to the corresponding course session. It will display a list of
eligible students for every class to assist lecturers in monitoring attendance.
Additionally, lecturers will have the ability to manually view, verify, or update
attendance records for any given session, ensuring flexibility and accuracy in
managing attendance data.

Communication & Notifications

The system will include a robust communication and notification module that
automatically sends weekly SMS or email alerts to students whose attendance
falls below 75%, helping to ensure timely awareness and intervention.
Lecturers will also have the ability to send targeted notifications to students
8
who are absent from their sessions. Furthermore, administrators will be able to
customize notification templates, allowing for consistent and context-specific
communication across different departments.

Reporting & Analytics

The system will feature robust reporting and analytics capabilities, enabling the
generation of weekly, monthly, and semester-based attendance reports for
each department or school. It will allow administrators to create blacklists of
students whose attendance falls below predefined thresholds, such as 50% or
75%. To support administrative tasks and documentation, reports can be
exported in user-friendly formats like PDF and Excel. Additionally, the system
will provide insightful analytics to display attendance trends and performance
by class, course, or individual student, aiding in decision-making and student
support interventions

2.7 Non-Functional Requirements

Performance Requirements
The system is expected to deliver high performance by enabling real-time
attendance logging, ensuring each biometric scan is processed within 2
seconds. It must also handle concurrent usage efficiently, supporting at least
200 students simultaneously across multiple lecture theatres without
degradation in speed or system responsiveness.

Scalability Requirements
The system shall be scalable to accommodate additional faculties or
departments in the future.

Security Requirements
The system will ensure robust security by encrypting biometric data before
storing it in the database to protect sensitive information. It will use HTTPS for
secure communication, safeguarding data during transmission. Additionally,
role-based permissions will be implemented to prevent unauthorized access,
ensuring that only authorized personnel can access student data and other
sensitive system resources.

Reliability Requirements
The system will be designed for high reliability, ensuring a 99.9% uptime
guarantee to minimize disruptions. It will also implement regular backups to
safeguard data against potential loss, ensuring continuous operation and
secure storage of attendance records.

Usability Requirements
The system will feature an intuitive user interface that is accessible through
both web browsers and mobile devices, ensuring ease of use for all users. To
9
support first-time users, training materials or help guides will be provided,
helping them navigate the system effectively and ensuring a smooth
onboarding experience.
Actors:
1. Student – Registers attendance, enroll for courses, views attendance,
receives notifications.
2. Lecturer – Views student lists, marks or edits attendance, sends absence
alerts.
3. Administrator – Manages system configuration, views overall reports,
blacklists students.
4. Dean of Students – Generates departmental reports, monitors student
engagement.
5. Notification system- provides Email/SMS services

2.8 Usage Scenarios and Use Cases:

Student Registers Attendance
• Scenario: Upon entering a lecture theatre, the student scans their
fingerprint/RFID to mark attendance.
• Use Case: Register Attendance
• <<include>>: Authenticate Identity
• <<extend>>: Notify Student (Low Attendance)
Student Enrolls for Course
• Scenario: The student logs in to select course sessions for the semester
via the portal.
• Use Case: Enrolls in Course
• <<include>>: Login
• <<extend>>: Update Course Sessions
Lecturer Views Class Attendance
• Scenario: Lecturer logs in to view the attendance record for a given
session and sends reminders.
• Use Case: View Class Attendance
• <<include>>: Login
• <<extend>>: Send Absence Alerts
Administrator Generates Reports
• Scenario: Administrator logs in to generate and export weekly/monthly
attendance reports.

10
 • Use Case: Generate Attendance Reports
• <<include>>: Login
• <<include>>: Access Attendance Database
Dean Views and Blacklists Students
• Scenario: The Dean checks attendance levels and blacklists students
below 50–75%.
• Use Case: Blacklist Student
• <<include>>: Generate Reports
• <<extend>>: Notify Blacklisted Students

11
12
3 CHAPTER THREE: OO DESIGN AND MODELLING USING
UML
3.1 Introduction
In this chapter, the diagrams shown here help the programmer to depict and
visualize real life imagination of how the system would if all requirements were
meant
I. The following is a class UML diagram showing the existence of the
relationship between the different classes with their functions and
executions in the system.

13
3.2 Use case scenario called Update Course Sessions

With generalizations of the student’s name and Reg.number must be

complete for course enrollment as per the system.

14
3.3 Sequence Diagram
Depicting two use case scenarios login and generating student
attendance. The system allows all users to login and generate student
attendance records.

15