PROJECT WRITE-UP-1

1
MAKERERE UNIVERSITY
PROJECT WRITE-UP ABOUT CAMPUS

SECURITY MANAGEMENT
GROUP 13
COLLEGE OF BUSINESS AND
MANAGEMENT SCIENCES,
SCHOOL OF STATISTICS AND PLANNING
STA1301: RECESS
MR. NAMUGERA FRANK, MISS
NAMUGENYI CHRISTABELLAH, MR.
BYAMUGISHA JIMREX, MR. FRANCIS
BBOSA AND MR. ASIIMWE JOHN BOSCO
JULY 16, 2024

2
CAMPUS SECURITY MANAGEMENT
COMPILED BY;
No Name Course Registration Student Signature
Number Number
1 Kakeeto Matthew William BSAS 23/U/08706/EVE 2300708706
2 Mukiza Cosmas BSAS 23/U/11875/EVE 2300711875
3 Muwonge Nicholas BSAS 23/U/12406/PS 2300712406
4 Mwendeze Desire Marion BSAS 23/U/12522/PS 2300712522
5 Nabukenya Glenda Lillian BSAS 23/U/12888/PS 2300712888
6 Nakimuli Apophia BSTA 23/U/1034 2300701034
7 Naluwembe Shakirah BSAS 23/U/14162/PS 2300714162
8 Nambalirwa Solome Theresa BSAS 23/U/14512/PS 2300714512
9 Settuba Mukiibi Clive BSAS 23/U/17562/PS 2300717295
10 Wacha Seth BSAS 23/U/18400/PS 2300718400

3
REFERENCES
Fahad Muganga, Uganda Radio Network (Oct 24, 2023). When will Makerere
University be safe.
https://ugandaradionetwork.net/story/when-will-makerere-university-be-safe
Makerere University (2024), newsletter. Facts and figures

https://www.mak.ac.ug/about/facts-figures
Makerere University (2024), newsletter. Campus security

https://www.mak.ac.ug/about/campus-security
Makerere University (2024), newsletter. Makerere University Regulations-Security

https://dos.mak.ac.ug/regulations/9-security
Makerere University (2021), newsletter. Campus Security

https://new.mak.ac.ug/web/about/campus-security
Makerere University (n.d.). Security policy

https://policies.mak.ac.ug/sites/default/files/policies/SECURITY%20POLICY.pdf
The Independent Uganda (March 27, 2023). Makerere University to limit entrance
and exit points to enhance campus security.
https://www.independent.co.ug/makerere-to-limit-entrance-and-exit-points-to-
enhance-campus-security/
4
Table of Contents
EXECUTIVE SUMMARY...................................................................................................................6
INTRODUCTION.................................................................................................................................6
NEEDS ASSESSMENT........................................................................................................................7
Problem statement.........................................................................................................................7
Solution Approach.........................................................................................................................7
Project Overview...........................................................................................................................8
Project objectives...........................................................................................................................8
Methodology.................................................................................................................................8
STATISTICAL REPORT......................................................................................................................8
BACKGROUND...............................................................................................................................8
OBJECTIVES...................................................................................................................................9
Major Objective.............................................................................................................................9
Other Objectives............................................................................................................................9
RESEARCH QUESTIONS...............................................................................................................9
METHODOLOGY..........................................................................................................................10
HYPOTHESES................................................................................................................................10
FINDINGS......................................................................................................................................14
CONCLUSIONS AND RECOMMENDATIONS...........................................................................15
Conclusions.................................................................................................................................15
Recommendations.......................................................................................................................16
DATABASE DESIGN........................................................................................................................16
Objective.........................................................................................................................................16
Data Analysis Techniques...............................................................................................................16
Database schema.............................................................................................................................16
DATABASE IMPLEMENTATION...................................................................................................20
TESTING AND DOCUMENTATION...............................................................................................21
Testing the program.........................................................................................................................21
Documentation................................................................................................................................23
Tables..........................................................................................................................................24
Forms...........................................................................................................................................25
Reports........................................................................................................................................25
User manual.....................................................................................................................................26
APPENDICES.....................................................................................................................................29
A: Survey questionnaire..................................................................................................................29
5
B. Detailed SQL scripts...................................................................................................................32

C. MINUTES...................................................................................................................................33
Minutes (02/07/2024)..................................................................................................................33
Minutes (03/07/2024)..................................................................................................................36
Minutes (04/07/2024)..................................................................................................................39
Minutes (08/07/2024)..................................................................................................................42
Minutes (09/07/2024)..................................................................................................................45
Minutes (11/07/2024)..................................................................................................................47
Minutes (12/07/2024)..................................................................................................................50
D. KOBO COLLECT EXCEL FILE...............................................................................................53
6
EXECUTIVE SUMMARY
This write-up provides a comprehensive analysis of the current security challenges
and measures at Makerere University and identifies the challenges faced by the campus
security management system. It also explains the database system generated to mitigate some
of the challenges faced by the security management system. The study evaluates existing
security measures such as CCTV surveillance, security patrols and access control systems,
and investigates their effectiveness in addressing security breaches. Makerere University
(n.d.) security policy. https://policies.mak.ac.ug/sites/default/files/policies/SECURITY
%20POLICY.pdf. Through a series of interviews and surveys involving students and staff,
the study identifies common security incidents, such as theft and vandalism, and assesses the
frequency and reporting of these incidents. Statistical analyses, including Chi-Square tests,
are utilized to test hypotheses related to the frequency of security incidents and the impact of
increased surveillance. The findings reveal significant security challenges at Makerere
University and underscore the need for improved surveillance, increased patrol frequency,
and better engagement with the campus community. Recommendations are provided to
enhance the overall security framework, ensuring a safer environment for all university
members.
INTRODUCTION
Campus security is a critical concern for educational institutions worldwide, and

Makerere University in Kampala, Uganda, is no exception. Established in 1922, Makerere
University is one of Africa's oldest and most prestigious institutions, hosting over 30,000
students, faculty, and staff. Makerere University (2024). Facts and figures.
https://www.mak.ac.ug/about/facts-figures . Despite its academic excellence, the university
faces significant security challenges typical of large campuses, including theft, unauthorized
access, and occasional incidents of violence. These challenges necessitate a robust and
adaptive security framework to safeguard the university community.
Over the years, Makerere University has implemented various security measures such as
CCTV surveillance, security patrols, and access control systems to address these challenges.
Makerere University (n.d.) Security policy.
https://policies.mak.ac.ug/sites/default/files/policies/SECURITY%20POLICY.pdf. However,
the frequency of security breaches indicates vulnerabilities in the existing measures,
highlighting the need for continuous evaluation and improvement. This study aims to provide
a detailed understanding of the current security measures in place, identify the most common
security breaches, and analyze the rate at which these incidents are reported.
Through this study, we aim to provide actionable insights and recommendations for
enhancing the security framework at Makerere University. By addressing the identified
security challenges and improving incident reporting and response mechanisms, the
university can create a safer environment for its community, thereby supporting its mission of
academic excellence and holistic development.
NEEDS ASSESSMENT
Problem statement
Security incidents on campus need to be documented and analyzed to improve safety
measures. Additionally, efficient scheduling of patrols and monitoring access to restricted
areas is crucial for preventing unauthorized access.
7
Solution Approach
To address these issues, we developed a comprehensive database system using
Microsoft Access 2016.
Project Overview
The Campus Security Management Database is designed to record insecurity
incidents, manage patrol schedules, track access to restricted areas, store emergency contact
information, and integrate with campus surveillance systems. The primary objective of this
project is to enhance campus security through effective security data management and
analysis.
Project objectives
 Record and report insecurity incidents.
 Manage and schedule insecurity patrols.
 Track and log access to restricted areas.
 Store and maintain emergency contact information.
 Integrate with campus surveillance systems for real-time monitoring.
Methodology
The study employs a survey approach, using Kobo collect to collect data through
interviews conducted at various locations within the campus. We then designed a database
system which tackles some of the challenges that were discovered from the survey.
STATISTICAL REPORT
UNDERSTANDING THE CURRENT SECURITY MEASURES AND THE
CHALLENGES FACED BY THE CURRENT SECURITY MANAGEMENT SYSTEM
AT CAMPUS.
BACKGROUND
The campus has experienced various security breaches over the years, ranging from
petty thefts to more severe incidents. Fahad Muganga, Uganda Radio Network (Oct 24,
2023). When will Makerere University be safe, https://ugandaradionetwork.net/story/when-
will-makerere-university-be-safe . The Independent Uganda (March 27, 2023). Makerere
University to limit entrance and exit points to enhance campus security.
https://www.independent.co.ug/makerere-to-limit-entrance-and-exit-points-to-enhance-
campus-security/ . These breaches highlight vulnerabilities in the existing security measures
and underscore the need for continuous improvement.
This study aims to evaluate the current security challenges at Makerere University, identify
the most common security breaches, and analyze the rate at which these incidents are
reported. By addressing these objectives, the study seeks to provide actionable insights and
recommendations for enhancing the security framework and ensuring a safer campus
environment for all members of the university community.
OBJECTIVES
Major Objective
 To understand the current security measures in place and the challenges faced by the
current security management system at campus.
Other Objectives
 To assess the current security challenges
 To find out the most common security breaches
8
 To assess the rate at which incidents are reported and to whom

 To find out the most reported to personnel when the insecurity incident occurs
RESEARCH QUESTIONS
 What are the current security challenges?
 What are the most common security breaches around campus?
 What is the rate at which incidents are reported and to whom?
METHODOLOGY
A survey was conducted to understand the current measures in place and challenges
faced by the current security management system at campus. Kobo Collect was used to
interview both students and staff of Makerere University. A total of 40 respondents
participated in the survey, with 20 students and 20 staff. The data collected was analyzed
using statistical software like IBM SPSS and Microsoft Excel 2016. Descriptive statistics,
tables, pie charts and graphs were also used.
HYPOTHESES
H0: Insecurity incidents occur at equal frequencies at Makerere University
H1: Insecurity incidents occur at varying frequencies at Makerere University
The Chi-Square test was conducted to assess whether there are significant differences in the
frequencies of security incidents at Makerere University. The observed data for Vandalism,
Theft, and Harassment were compared to the expected frequencies under the null hypothesis
of equal occurrence rates.
Results and interpretation
Based on the Chi-Square test results and the small p-value (0.00452 < 0.05) This p-
value indicates statistical significance, we reject the null hypothesis that all security incidents
occur with equal frequencies. Instead, we find evidence that different types of incidents,
specifically theft and vandalism occur with varying frequencies.
H0: Increased surveillance will not reduce the frequency of reported theft incidents on
campus.
H1: Increased surveillance will reduce the frequency of reported theft incidents on
campus.
The Chi-Square test was conducted to assess whether there is a significant relationship
between surveillance by use of cameras and frequency of reported theft incidents.
 The p-value (0.0497 < 0.05) suggests that there is a statistically significant association
between recommendations for more cameras and the frequency of reported theft
incidents. The chi-square statistic (3.85) indicates the magnitude of the association
between the variables. A higher value would suggest a stronger association.
Conclusion
9
Since the p-value is less than 0.05, we reject the null hypothesis (H0) and accept the
alternative hypothesis (H1). This supports the hypothesis that increased surveillance could
potentially reduce the frequency of reported theft incidents.
H0: There are no significant security challenges currently at Makerere University

H1: There are significant security challenges currently at Makerere University
The Chi-Square test was conducted to assess whether there are significant security
challenges currently at Makerere University. The observed data on reported security incidents
were compared to the expected frequencies under the null hypothesis of no significant
challenges.
The small p-value (0.0004777 < 0.05) indicating strong statistical evidence against the
null hypothesis therefore we reject the null hypothesis that there are no significant security
challenges at Makerere University. Instead, we find compelling evidence that there are indeed
significant security challenges currently on campus.
1.0 Results from the survey:

10
Analysis Variable Percentage Number of

respondents
Occupation
Student 50% 20
Staff 50% 20
Students’ experience of an insecurity
incident 74% 11
Theft 0% 0
Riots 13% 2
Harassment 0% 0
Mob justice 13% 2
Property Vandalism
Reporting of the insecurity incident
Yes 53.3% 8
No 46.7% 7
Reporting of the insecurity incident to
Student leader 12.5% 1
Police 62.5% 5
Warden/custodian 12.5% 1
Grounds men 12.5% 1
Was anything done about it
Yes 37.5% 3
No 62.5% 5
Reported insecurity incidents to staff
Theft 80% 16
Riots 0% 0
Harassment 5% 1
Mob justice 0% 0
Property vandalism 15% 3
Rate at which insecurity incidents are
reported 5% 1
Very low 30% 6
Low 30% 6
Moderate 30% 6
High 5% 1
Very high
Surveillance (CCTV) review
Daily 55% 11
Weekly 0% 0
Monthly 5% 1
Only when there is an insecurity incident 40% 8
Common case discovered from surveillance

Theft 84% 16
Riots 0% 0
Harassment 0% 0
Mob justice 0% 0
Property vandalism 16% 3
Patrol of key areas
Once a day 25% 5
Twice a day 10% 2
Thrice a day 65% 13
11
FINDINGS
From the above graph, it is evident that theft is the major insecurity concern in the
university, followed by cases of harassment and property vandalism.
To whom was the incident Number Percentage

reported
Grounds men 1 12.50%
Police 5 62.50%
Student Leader 1 12.50%
Warden/Custodian 1 12.50%
The table above shows that most of students (62.5%) that report an incident tend to
report it to the Police with the remaining evenly reporting cases to other authorities.
The pie chart above shows that theft (84%) is the most discovered insecurity incident when
surveillance is reviewed with it being the highest compared to other incidences.
12
From the above graph, most key areas are patrolled at least once a day and the most being
thrice.
CONCLUSIONS AND RECOMMENDATIONS
Conclusions
The survey highlights significant gaps in the current campus security management
system, particularly in incident reporting, follow-up, and patrolling.
Recommendations
 Enhance Surveillance Systems: Install additional cameras in strategic locations to
cover blind spots and high-risk areas and ensure that cameras are monitored in real-
time to allow for immediate response.
 Increase Patrol Frequency: Implement regular and frequent patrols, especially in
areas identified as high-risk, use technology to track patrol routes and ensure coverage
of all critical areas.
 Address Security Personnel Negligence: Conduct regular training sessions for
security personnel to improve vigilance and responsiveness.
 Community Engagement: Increase awareness among students and staff about the
importance of reporting incidents and foster a culture of safety where everyone takes
part in maintaining campus security.
DATABASE DESIGN
Objective
To develop a database system to address the identified needs and improve the efficiency of
the existing campus management system.
Data Analysis Techniques
We utilized queries, reports and forms to analyze the recorded data and draw insights.
Database schema
Tables
1. Incident report table
13
2. Patrol schedule table

3. Access control table
4. Emergency contacts table
5. Surveillance integration table
6. Alert table
7. Login details table
Forms
1. Incident report form
2. Patrol schedule form
3. Access control form
4. Cameras form
5. Emergency contacts form
Reports
1. Access control report
2. Patrol schedule efficiency report
3. Incident summary report
4. Alert report
5. Cameras report
6. Surveillance report
Detailed tables within the database system
Insecurity incident reporting table Patrol scheduling table
Field name Data type Field name Data type
Auto
Incident_form_No number Patrol_ID Auto number
Student_ID_No Short text Patrol_Officer Short text
Staff_ID_No Short text Type_of_Patrol Short text
Visitor_ID_No Short text Patrol_Start_time Date/Time
Type_of_incident Short text Patrol_End_time Date/Time
Scene_of_incident Short text Day_of_Patrol Short text
Date_of_incident Date/Time Patrol_Status Short text
Incident_reported_by Short text Location_of_Patrol Short text
Last_Completed_Patro
Description_of_incident Long text l Date/Time
Next_Scheduled_Patro
Incident_reported_to Short text l Date/Time
Witnesses_at_the_scene Short text Patrol_supervisor Short text
Action_taken Short text
Response_time Date/Time
Severity_of_incident Short text
Status Short text
Camera_ID Short text Login details table
Photo Attachment Field name Data type
Time_of_incident Date/Time Username Short text
Response_date Date/Time Password Short text
14
Emergency contacts table Alert table

Field name Data type Field name Data type
Auto
Emergency_Form_No number Alert_ID Auto number
Student_ID_No Short text Camera_ID Short text
Staff_ID_No Short text Alert_type Short text
Visitor_ID_No Short text Alert_time Date/Time
Name_of_emergency contact Short text
Relationship_with_emergency contact Short text
Phone_number_of_emergency contact Short text Cameras table
Email_address_of emergency contact Hyperlink Field name Data types
Location_address_of emergency
contact Short text Camera_id Short text
Personal_contact Short text Location Short text
Personal_email_address Hyperlink IP_address Short text
Personal_location_address Short text Status Short text
Access control table

Field name Data type
Auto
Access form ID number Surveillance videos table
User_ID Short text Field name Data type
User_ID_No Short text Video_ID Short text
Location_accessed Short text Camera_ID Short text
Access_Date Date/Time Start_time Date/Time
Access_entry_Time Date/Time End_time Date/Time
Access_exit_Time Date/Time File path Short text
Telephone_number Short text Resolution Short text
Signature Short text Storage_location Short text
Project algorithm
15
ENTITY RELTIONSHIP DIAGRAM
DATABASE IMPLEMENTATION
 We used Microsoft Access database 2016 program.
 Split database into front end and back end. Front end where the user would be
entering data and back end where the data entered is stored and viewed collectively
 Executed the database schema to produce the database structure
 Inserted initial data for testing purposes
 Developed interface for data entry and management e.g. data entry forms
 Performed unit testing to ensure it was working properly
 Deployed database
 Set up access control to manage user permissions for security personnel
TESTING AND DOCUMENTATION

Testing the program
Steps taken
1. Entering dummy data
2. Finding loop holes e.g. incorrect data types
3. Rectifying loop holes e.g. using correct data types
4. Making improvements to the program e.g. improving the user interface
5. Releasing the program to the public
Findings
Random data was entered into the program to check for loop holes and the would-be interface
challenges when operating the program.
 We found out that the students, staff and visitors’ report had one table in which their
data was stored i.e. the “insecurity incident reporting table”
 There were some data types changed from various tables as shown below:
16
Insecurity incident reporting table

Field edited Original data type Secondary data type
Date of incident Date/Time Short text
Patrol Scheduling Table

Patrol start time Date/Time Short text
Patrol end time Date/Time Short text
Emergency contacts table

Student ID No Number Short text
Staff ID No Number Short text
Visitor ID No Number Short text
NB: Some fields were changed because the data was entered there where data type entries
had to be rectified.
Below are the tables where data was stored together with the corresponding entry forms
TABLE ENTRY FORM
Access control Access control sheet
Alert Alert form
Cameras Cameras form
Emergency contacts Emergency contacts form
Insecurity incident reporting Insecurity incident reporting
table form
Login details Login
Patrol scheduling Patrol scheduling form
Surveillance videos Surveillance videos form
Main menu
Welcome
Security personnel's menu
NB: Below are forms accessed by only security personnel
1. Alert camera settings
2. Cameras
3. Login
4. Security personnel menu
5. Surveillance videos
Documentation
The Campus Security Management System aims to enhance the safety and security of
the campus by efficiently managing incident reporting, patrol scheduling, access control,
emergency contacts, and surveillance integration. Our approach involves developing a
Microsoft Access-based system to organize and track all relevant security data.
To tackle this project, we divided the work into key components:
 Incident Reporting: Creating a structured database for reporting security incidents.
 Patrol Scheduling: Designing a schedule tracker for security personnel.
17
 Access Control: Maintaining a log of authorized personnel and access points.

 Emergency Contacts: Compiling a list of critical contacts for emergency situations.
 Surveillance Integration: Linking surveillance data with incident reports for
comprehensive monitoring.
The Microsoft Access-based system consists of multiple tables, forms, and reports,
each dedicated to a specific aspect of campus security. Below is a detailed breakdown of the
database structure and functionality:
Tables
1. Incident Report Table:
Purpose: Stores detailed information about each reported incident in campus.
2. Patrol Schedule Table:
Purpose: Tracks the schedules of security personnel and the areas they patrol around all
campus areas and premises.
3. Access Control Table:
Purpose: Logs entry and exit times of authorized personnel at various access points for easy
tracking in case of any reported incident.
4. Emergency Contacts Table:
Purpose: Lists important contacts for use during emergency situations.
5. Surveillance Integration Table:
Purpose: Links surveillance footage references to corresponding incidents.
6. Alert Table:
Purpose: To notify users when specific events or activities occur for example motion
detection, and sound detection.
7. Login details table:
Purpose: To enable the user access the security system.
Forms
The system also consists of different forms for enabling different data entries and menus.
These are listed below and their purposes.
1. Incident Report Form: Facilitates easy data entry for incident reporting.
2. Patrol Schedule Form: Allows for scheduling and updating patrol shifts
3. Access control form: Enables logging of access control entries. For example, the
different people in charge of accessing the various access points and the time they
access these points for easy follow up of any incidents.
4. Cameras form: This allows the security personnel to record the cameras information
like the camera id, location and status.
5. Emergency Contacts Form: Provides quick access to emergency contact
information.
6. Alert setting form: Allows personnel edit alert settings of cameras e.g. motion
detection.
18
7. Surveillance form: Allows personnel record surveillance footage captured by

cameras.
8. Log in form: Allows security personnel access their menu.
Reports
1. Access Control Report: Summarizes entries and exits for a particular access point.
2. Patrol Schedule Efficiency Report: Produces a detailed overview of patrol schedule
3. Incident Report Summary: Generates a detailed overview of incidents reported.
4. Cameras report: This gives information about the cameras that are in campus and where
they are located.
5. Surveillance report: Compiles observations and recorded activities from the cameras
over time. It includes details on incidents captured, times and dates of recordings and
camera resolutions.
User manual
This contains the instructions for using the database.
1. Load the database into main memory
2. Click “open database” from the welcome screen.
3. Main menu displays with options such as;

 Welcome: Takes you back to the welcome page
 Student menu: Views student menu
 Staff menu: Views staff menu
 Visitor menu: Views visitors’ menu
 Security personnel menu: Views security personnel menu
 Exit: Exits the application database
4. On clicking the student/staff/visitor menu, a

uniform submenu pop up displays options such
as;
 Report insecurity incident: Open insecurity
incident reporting form to report a case
 Add emergency contact: Opens emergency
contacts form to add emergency details
 Add access record: Opens access record form
to add records for places they accessed
 Main menu: Opens the main menu
19
 Exit: Exits the application database
6. On clicking the security personnel menu, a login popup appears for username and
password entering for only authorized personnel.
 The security personnel enter the details to continue;
Username: Security_101
Password: CSM@123
 If wrong details are entered an error message appears
 If correct details are entered, they are redirected to the security personnel submenu
7. The security personnel submenu displays

the following options
 Schedule patrol: Opens schedule
patrol form
 Add alert details: Opens camera alert
details form
 Add cameras: Opens camera form
 Add surveillance footage: Opens
surveillance form
 Views patrol schedule: Views patrol
schedule table in back end
 Views insecurity incident record:
Views incident records report
20
 Main menu: Back to Main menu

 Exit: Exits program
21
APPENDICES
A: Survey questionnaire
TOPIC: TO UNDERSTAND THE CURRENT MEASURES IN PLACE AND THE
CHALLENGES FACED BY THE SECURITY SYSTEM AT CAMPUS.
Introduction
Good morning/afternoon. My name is……………………., a student from the school of
Statistics and
planning at Makerere University. We are doing an assessment on the security system of the
campus for our recess term project. The main aim is to understand the current security
measures, rate at which cases are reported and find out the security challenges. i request you
to share your honest views on the topic we will be discussing. Your participation in this
interview is voluntary and you are free to stop if you feel uncomfortable at any point. I would
like, however, to assure you that the information you provide shall be kept confidential and
will only be used for the purpose of this study.
What’s your occupation?
1. Students
2. Staff
If student, go to section A, and if staff go to SECTION B.
SECTION A; Students’ case
1. Student’s Number:
……………………………………………………………………………
2. Have you ever experienced any security incident?
1. Yes
2. No
If no, thank you for your time
3. What incident was it?
1. Theft
2. Riots
3. Harassment
4. Mob justice
5. Property vandalism
6. Others (Specify)
4.Did you report the incident?
1. Yes
2. No
If yes to question4;
i.) To whom was it reported?
Student leader
1. Police
2. Warden/custodian
3. grounds men
ii.) Was anything done about it?
5.What measures should be taken to ensure safety?
…………………………………………………………………………………………………
…………………………………………………………………………………………………
…………………………………………………………………………………………………
………………….
22
SECTION B; Staff section.

1.What is your role?
…………………………………………………………………………………………………
………………………………………………………….
2.What are the most common security incidents reported?
1. Theft
2. Riots
3. Harassment
4. Mob justice
5. Property vandalism
3.At what rate are security incidents reported?
1. Very low
2. Low
3. Moderate
4. High
5. Very high
4.How often is the surveillance reviewed?
1. Daily
2. Weekly
3. Monthly
5.What is the most common case discovered from the surveillance?
6.How often are the key areas patrolled?
1. Once a day
2. Twice a day
3. Thrice a day
7.What are the challenges faced in the security system?
…………………………………………………………………………………………………
…………………………………………………………………………………………………
8.What measures should be taken to better the security system?
…………………………………………………………………………………………………
Thank you for your time!
23
C. MINUTES
Minutes (02/07/2024)
TEAM MEETING
Date: July 2, 2024
Time: 9:00a.m.
Meeting called to order by: Kakeeto Matthew William
Location: CTF 4.2
IN ATTENDANCE
 Kakeeto Matthew William (Chairperson & Group leader)
 Mukiza Cosmas
 Muwonge Nicholas
 Mwendeze Desire Marion
 Nabukenya Glenda Lillian
 Nakimuli Apophia
 Naluwembe Shakirah
 Nambalirwa Solome Theresa
 Settuba Mukiibi Clive
 Wacha Seth
AGENDA: MAIN ITEMS

 Opening prayer
 Attendance taking
 Introduction
 Assigning of subgroups
 Topic and etc.
 Generation of questionnaire
 Lunch break
 Generation of kobo collect excel file
 Next meeting
 Closing prayer
OPENING PRAYER
Mr. Kakeeto Matthew led the opening prayer. He thanked God for the group and
prayed for strength and wisdom for all group members.
ATTENDANCE TAKING
24
Miss Nabukenya Glenda took attendance of all group members present by making
them all sign against their names on a roll call sheet.
INTRODUCTION
Mr. Kakeeto Matthew debriefed the group members on how and when we’d be
discussing during the two weeks. Miss Naluwembe Shakirah argued that the time assigned
for physical discussions was too little and majority of the group members seconded her. Mr.
Kakeeto then changed then changed the timetable such that physical discussions would be
held almost every day excluding weekends for the next two weeks.
He then gave a brief summary of what the group’s project entailed and encouraged the group
members to give their own ideas of how they understood the question assigned to the group.
ASSIGNING OF SUB-GROUPS
The group leader assigned work in pairs as shown below;
1. Miss Nambalirwa Solome and Miss Mwendeze Desire - Needs assessment team-
department
2. Mr. Mukiibi Clive and Mr. Muwonge Nicholas - Statistical reporting team-department
3. Mr. Wacha Seth and Mr. Kakeeto Matthew - Database and C++ design team-
department
4. Miss Nabukenya Glenda and Miss Naluwembe Shakirah - Report and Presentation
team-department
5. Mr. Mukiza Cosmas and Miss Nakimuli Apophia - Implementation, documentation
and data analysis team-department
TOPIC AND E.T.C.

The group members led by Miss Nakimuli Apophia and Mr. Mukiza Cosmas
generated a topic of study, research questions, objectives and hypotheses of the study.
GENERATION OF QUESTIONNAIRE
The group leader then led the group members in the discussion of which questions to
include in the questionnaire.
LUNCH BREAK
The group members took a 2-hour break to have lunch.
GENERATION OF KOBO COLLECT EXCEL FILE
After the lunch break, the group members reconvened and Miss Nambalirwa Solome
and Miss Mwendeze Desire used the questionnaire to generate a kobo collect excel file that
the group members were to use during the interviews for the survey.
The group leader then told the group members to carry out interviews using kobo collect for
the remainder of the day.
NEXT MEETING
Next meeting will be held on July 3, 2024.
Motion to adjourn was made at 4:00 p.m. and was passed unanimously.
CLOSING PRAYER
25
Miss Mwendeze Desire led the group members through the closing prayer and she
thanked God for the progress made so far.
CHAIRPERSON SECRETARY
_________________ _____________________
Minutes (03/07/2024)
TEAM MEETING
Date: July 3, 2024
Time: 10:00 a.m.
Location: CTF 4.2
IN ATTENDANCE
 Mukiza Cosmas
 Wacha Seth
AGENDA: MAIN ITEMS

 Opening prayer
 Data analysis
 Lunch break
 Simple statistical report
 Next meeting
 Closing prayer
OPENING PRAYER
26
Miss Nambalirwa Solome led the opening prayer. She thanked God for the group and
prayed that our project collects the highest marks.
ATTENDANCE TAKING
Miss Naluwembe Shakirah took attendance of all group members present by making
DATA ANALYSIS
Mr. Muwonge Nicholas led the discussion for analysing the data collected. An excel
sheet of the data collected was downloaded from Kobo collect, the group members analysed
it and discovered key insights and patterns that were directly related to the research questions.
The group members also discussed which descriptive statistics and visual aspects to use in the
statistical report.
LUNCH BREAK
The group members then took a 2-hour break to have a lunch break.
STATISTICAL REPORT
After the lunch break, Mr. Mukiibi Clive and Mr. Muwonge Nicholas started
generated the simple statistical report.
NEXT MEETING
CLOSING PRAYER
Mr. Wacha Seth led the group members through the closing prayer and he thanked
God for wisdom and teamwork.
_________________ _____________________
Minutes (04/07/2024)
TEAM MEETING
Date: July 4, 2024
Time: 8:00 a.m.
Location: CTF 4.2

27
IN ATTENDANCE
 Mukiza Cosmas
 Wacha Seth
AGENDA: MAIN ITEMS

 Opening prayer
 Review of statistical report
 Project discussion
 Lunch break
 Further research
 Database project
 Next meeting
 Closing prayer
OPENING PRAYER
Mr. Mukiza Cosmas led the opening prayer. He thanked God for the group and prayed
for strength and wisdom for all group members.
ATTENDANCE TAKING
REVIEW OF STATISTICAL REPORT

Mr. Muwonge Nicholas and Mr. Mukiibi Clive took the group members present
through the simple statistical report they had generated. A few members noticed a few areas
in need of improvement and they were worked on immediately, the final report was then
shared on the shared WhatsApp group for further review.
PROJECT DISCUSSION
The group members discussed what kind of project they wanted and majority agreed
to have a database project over a C++ project. Miss Nambalirwa Solome suggested that the
system should also be accessed by the users and the members agreed.
The members also discussed the different field names to be included in the database.
LUNCH BREAK
28
The group members took a 2-hour break to eat lunch.

FURTHER RESEARCH
After the lunch break, Mr. Kakeeto Matthew did more research on database using
YouTube and he found a video that showed ways of making visually pleasing user interfaces
on Microsoft Access database. He then assigned each group member with watching the video
and generating similar forms as those shown in the video during the weekend.
DATABASE PROJECT
Mr. Kakeeto Matthew and Mr. Wacha Seth made plans to meet over the weekend and
generate the final database project.
NEXT MEETING
CLOSING PRAYER
Mr. Muwonge Nicholas led the group members through the closing prayer and she
thanked God for the progress made so far.
_________________ _____________________
Minutes (08/07/2024)
TEAM MEETING
Date: July 8, 2024
Time: 9:00 a.m.
Location: CTF 4.2
IN ATTENDANCE
 Mukiza Cosmas
29
 Wacha Seth
AGENDA: MAIN ITEMS

 Opening prayer
 Presentation of database forms
 Review of database
 Next meeting
 Closing prayer
OPENING PRAYER
Miss Nakimuli Apophia led the opening prayer. She thanked God for the progress so
far and prayed for strength and wisdom for all group members.
ATTENDANCE TAKING
PRESENTATION OF DATABASE FORMS

Each group member presented and the database form they came up with over the weekend.
LUNCH BREAK
The members took a 2-hour break to have lunch.
REVIEW OF DATABASE SYSTEM
After the break, Mr. Kakeeto Matthew and Mr. Wacha Seth then took all the group
members through the database system they generated, its user manual and documentation.
The group members then entered dummy data into the system to test it and check for errors,
the errors discovered were then taken note of. The team then promised to present the final
database in the next meeting.
NEXT MEETING
CLOSING PRAYER
Mr. Mukiibi Clive led the group members through the closing prayer. He thanked
God for the discussion and prayed for protection of all the group members.
_________________ _____________________
30
Minutes (09/07/2024)
TEAM MEETING
Date: July 9, 2024
Time: 9:00 a.m.
Location: CTF 4.2
IN ATTENDANCE
 Mukiza Cosmas
 Wacha Seth
AGENDA: MAIN ITEMS

 Opening prayer
 Vote of thanks
 Review of final database system
 SQL testing
 Next meeting
 Closing prayer
OPENING PRAYER
Miss Naluwembe Shakirah led the opening prayer. She thanked God for the steady
progress so far.
ATTENDANCE TAKING
VOTE OF THANKS
31
The group leader, Mr. Kakeeto Matthew gave a vote of thanks to the group members.
He thanked them for showing up for every physical discussion. He also thanked them for
working hard within their pairs and also as a group. He encouraged the members to keep up
the team spirit so as to attain the highest marks as a group.
REVIEW OF FINAL DATABASE SYSTEM
Testing of the final database was done by all the group members. Dummy data was
entered into the database to check for errors and the errors discovered were worked on
immediately. Mr. Wacha Seth also changed the back ground of the user interface of the
system with the guidance of the group members so as to make it more visually pleasing.
SQL TESTING
Mr. Mukiza Cosmas entered dummy data so that it could be tested using SQL.
NEXT MEETING
CLOSING PRAYER
Miss Mwendeze Desire led the group members through the closing prayer and she
thanked God for His guidance and the team spirit exhibited by all the group members.
_________________ _____________________
Minutes (11/07/2024)
TEAM MEETING
Date: July 11, 2024
Time: 10:00 a.m.
Location: CTF 4.2
IN ATTENDANCE
 Mukiza Cosmas
32

 Wacha Seth
AGENDA: MAIN ITEMS

 Opening prayer
 Review project write-up
 Generation of presentation
 Next meeting
 Closing prayer
OPENING PRAYER
Mr. Mukiza Cosmas led the opening prayer. He thanked God for the group members
and prayed for guidance during the discussion.
ATTENDANCE TAKING
REVIEW OF PROJECT WRITE-UP

Miss Nabukenya Glenda took the group members through the project write-up. The
group members identified areas that needed improvement and she took note of them. She
then promised to present the updated version during the next meeting.
GENERATION OF PRESENTATION
Miss Naluwembe Shakirah and Miss Mwendeze Desire led the discussion for the
group’s power-point presentation. The team generated a precise and easy to follow
presentation of the entire project.
NEXT MEETING
CLOSING PRAYER
Miss Nakimuli Apophia led the group members through the closing prayer and she thanked
God for teamwork portrayed by the group members.
_________________ _____________________
Minutes (12/07/2024)
TEAM MEETING
33
Date: July 12, 2024
Time: 10:00 a.m.
Location: CTF 4.2
IN ATTENDANCE
 Mukiza Cosmas
 Wacha Seth
AGENDA: MAIN ITEMS

 Opening prayer
 Review power-point presentation
 Presentation practice
 Next meeting
 Closing prayer
OPENING PRAYER
Miss Naluwembe Shakirah led the opening prayer. She thanked God for the group
members and prayed for wisdom and guidance during the discussion.
ATTENDANCE TAKING
REVIEW OF POWER-POINT PRESENTATION

Miss Naluwembe Shakirah shared the final power-point presentation on the
WhatsApp group for all members to review and share ideas on how to improve it. A few
34
members noticed some important information missing and she made sure to include it
immediately.
PRESENTATION PRACTICE
Miss Naluwembe Shakirah led the presentation practice. All the group members
practiced leading the presentation individually so as ensure that each member is able to
efficiently present.
NEXT MEETING
CLOSING PRAYER
Mr. Muwonge Nicholas led the group members through the closing prayer and he
thanked God for the progress and teamwork portrayed by the group members.
_________________ _____________________
35
D. KOBO COLLECT EXCEL FILE

PROJECT WRITE-UP-1

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

PROJECT WRITE-UP-1

Uploaded by

Copyright:

Available Formats

1

PROJECT WRITE-UP ABOUT CAMPUS

JULY 16, 2024

CAMPUS SECURITY MANAGEMENT

2 Mukiza Cosmas BSAS 23/U/11875/EVE 2300711875

3 Muwonge Nicholas BSAS 23/U/12406/PS 2300712406

4 Mwendeze Desire Marion BSAS 23/U/12522/PS 2300712522

5 Nabukenya Glenda Lillian BSAS 23/U/12888/PS 2300712888

6 Nakimuli Apophia BSTA 23/U/1034 2300701034

7 Naluwembe Shakirah BSAS 23/U/14162/PS 2300714162

8 Nambalirwa Solome Theresa BSAS 23/U/14512/PS 2300714512

9 Settuba Mukiibi Clive BSAS 23/U/17562/PS 2300717295

10 Wacha Seth BSAS 23/U/18400/PS 2300718400

Makerere University (2024), newsletter. Facts and figures

Makerere University (2024), newsletter. Campus security

Makerere University (2024), newsletter. Makerere University Regulations-Security

Makerere University (2021), newsletter. Campus Security

Makerere University (n.d.). Security policy

B. Detailed SQL scripts...................................................................................................................32

Campus security is a critical concern for educational institutions worldwide, and

 To assess the rate at which incidents are reported and to whom

Results and interpretation

H0: There are no significant security challenges currently at Makerere University

Results and interpretation

1.0 Results from the survey:

Analysis Variable Percentage Number of

Common case discovered from surveillance

To whom was the incident Number Percentage

2. Patrol schedule table

Emergency contacts table Alert table

Access control table

ENTITY RELTIONSHIP DIAGRAM

TESTING AND DOCUMENTATION

Insecurity incident reporting table

Patrol Scheduling Table

Emergency contacts table

 Access Control: Maintaining a log of authorized personnel and access points.

7. Surveillance form: Allows personnel record surveillance footage captured by

3. Main menu displays with options such as;

4. On clicking the student/staff/visitor menu, a

 Exit: Exits the application database

7. The security personnel submenu displays

 Main menu: Back to Main menu

SECTION B; Staff section.

Date: July 2, 2024

Meeting called to order by: Kakeeto Matthew William

Location: CTF 4.2

AGENDA: MAIN ITEMS

TOPIC AND E.T.C.

Date: July 3, 2024

Time: 10:00 a.m.

Meeting called to order by: Kakeeto Matthew William

Location: CTF 4.2

AGENDA: MAIN ITEMS

Date: July 4, 2024

Time: 8:00 a.m.

Meeting called to order by: Kakeeto Matthew William

Location: CTF 4.2

AGENDA: MAIN ITEMS

REVIEW OF STATISTICAL REPORT

The group members took a 2-hour break to eat lunch.

Date: July 8, 2024

Time: 9:00 a.m.

Meeting called to order by: Kakeeto Matthew William