JORDAN UNIVERSITY COLLEGE

A CONSTITUENT COLLEGE OF ST. AUGUSTINE UNIVERSITY IN TANZANIA

FACULTY OF ARTS AND SOCIAL SCIENCE

DEPARTMENT OF INFORMATION SCIENCE.

PROJECT TITLE

LEACTURE STUDENT ALERT SYSTEM

SUBMITTED BY

[ENTER YOUR FULL REGISTRATION NAME HERE]

[ENTER YOUR REGISTRATION NUMBER HERE]

SUPERVISOR

DR. CHURI

A PROJECT PROPOSAL SUBMITTED TO THE DEPARTMENT OF INFORMATION

SCIENCE FOR THE STUDY LEADING TO A PROJECT IN PARTIAL
FULFILLMENT OF THE REQUIREMENT FOR THE AWARD OF DEGREE OF
BACHELOR OF SCIENCE IN COMPUTER SCIENCE OF JORDAN UNIVERSITY
COLLEGE.

JANUARY, 2025
 Table of Contents

ABBREVIATIONS.........................................................................................................................ii

ABSTRACT...................................................................................................................................iii

CHAPTER ONE. INTRODUCTION..............................................................................................4

1.1. Introduction...........................................................................................................................4

1.2. Project Background..............................................................................................................4

1.3. Statement of the problem......................................................................................................4

1.4. Motivation.............................................................................................................................4

1.5. Objectives of the study.........................................................................................................5

1.5.1. Main Objective..................................................................................................................5

1.5.2. Specific objectives............................................................................................................5

1.6. Research Questions...............................................................................................................5

1.7. Significance of the project....................................................................................................5

1.8. Scope of the project..............................................................................................................5

CHAPTER II. LITERATURE REVIEW........................................................................................6

2.1. Review of current situation...................................................................................................6

2.2. Study of existing systems.....................................................................................................6

CHAPTER III. PROJECT DESIGN & METHODOLOGY...........................................................7

3.1. Methodology and General work procedures.........................................................................7

3.2. System Design......................................................................................................................8

3.3. Project Schedule.................................................................................................................11

3.4. Summary and Conclusion...................................................................................................13

REFERENCE................................................................................................................................14

i
 ABBREVIATIONS

ICT - Information and Communication Technology

IS - Information Systems

DBMS - Database Management System

SSL - Secure Sockets Layer

TLS - Transport Layer Security

SDK - Software Development Kit

HTML - HyperText Markup Language

CSS - Cascading Style Sheets

JS - JavaScript

PHP - Hypertext Preprocessor

JSON - JavaScript Object Notation

AJAX - Asynchronous JavaScript and XML

REST - Representational State Transfer

SOAP - Simple Object Access Protocol

SQL - Structured Query Language

IDE - Integrated Development Environment

OOP - Object-Oriented Programming

ii
 ABSTRACT

The Lecture and Student Alert System is designed to streamline communication between
lecturers and students in academic institutions. This system facilitates real-time notifications for
class schedules, cancellations, venue changes, and urgent announcements, ensuring efficient
information dissemination. By leveraging modern communication technologies, the system
eliminates delays and minimizes miscommunication. It provides an intuitive interface for
lecturers to broadcast alerts and for students to receive them promptly via web and mobile
platforms. This project aims to enhance academic coordination, improve attendance, and
optimize the overall learning experience.

iii
 CHAPTER ONE. INTRODUCTION

1.1. Introduction
The Lecture and Student Alert System is a modern solution aimed at improving communication
within academic institutions. It addresses challenges such as missed announcements, last-minute
schedule changes, and ineffective communication methods. This system enables lecturers to send
real-time alerts about lectures, changes, or other critical updates directly to students. By ensuring
timely and reliable information delivery, the system enhances student engagement, reduces
confusion, and promotes a more organized academic environment (Sergiienko, 2014).

1.2. Project Background

Effective communication is crucial in academic institutions to ensure smooth coordination
between lecturers and students. Traditional methods, such as notice boards and verbal
announcements, are often unreliable, leading to missed updates, reduced attendance, and
disruptions in academic activities. With the increasing adoption of digital technologies, there is a
growing need for a streamlined system to deliver real-time alerts. The "Lecture and Student Alert
System" is designed to address these gaps by providing an efficient platform for instant
communication, improving academic coordination, and ensuring a seamless flow of
information
(Optimizing IEEE 802.11i Resource and Security Essentials for Mobile and Stationary Devices, n.d.
.

1.3. Statement of the problem

Inefficient communication methods in academic institutions, such as notice boards and delayed
announcements, often lead to missed lectures, low attendance, and confusion among students.
These challenges disrupt academic schedules and hinder effective learning. There is a need for a
reliable, real-time alert system to address these issues and ensure timely information delivery.

1.4. Motivation
The need for efficient communication in academic institutions inspired this project. Challenges
such as missed updates, low attendance, and disorganized schedules highlight the importance of
a reliable alert system. By developing a platform for real-time communication, this project aims

4
to enhance academic coordination, improve student engagement, and promote seamless
information sharing, ultimately contributing to a better learning environment.

1.5. Objectives of the study

The objectives of this project are divided into main objective and specific objectives to ensure
focused and measurable outcomes.

1.5.1. Main Objective

To develop Lecture and student alert system

1.5.2. Specific objectives

i. To design a user-friendly interface for lecturers to send real-time alerts to students.
ii. To ensure reliable and secure data transmission for effective communication.
iii. To integrate the system with short message service for accessibility and convenience.

1.6. Research Questions

i. How can a digital alert system improve communication between lecturers and students in
academic institutions?
ii. What features are essential for an efficient and user-friendly lecture alert system?
iii. How can the system ensure timely and reliable delivery of notifications to students across
multiple platforms?

1.7. Significance of the project

Improved Communication. The system ensures real-time, direct communication between
lecturers and students, reducing misunderstandings and missed updates.

Enhanced Academic Coordination. By providing timely notifications, the system helps

streamline lecture schedules and academic activities, promoting better organization.

Increased Student Engagement. With instant access to class information, students are more
likely to stay informed, attend classes regularly, and participate actively in their education.

5
1.8. Scope of the project
The scope of the Lecture and Student Alert System includes the development of a web and
mobile based platform designed for academic institutions. The system will enable lecturers to
send real time alerts about class schedules, cancellations, and other important announcements.

CHAPTER II. LITERATURE REVIEW

2.1. Review of current situation

Currently, communication between lecturers and students in many academic institutions relies on
traditional methods such as notice boards, emails, and verbal announcements. These methods
often result in delayed information delivery, leading to missed lectures, schedule changes, and
confusion among students. Additionally, students may not always be aware of urgent updates
until it's too late, impacting attendance and academic performance. The reliance on physical
notice boards or scattered communication channels also creates inefficiencies, making it difficult
for students to stay informed consistently. This highlights the need for a more reliable, real-time
alert system to ensure timely, accurate, and efficient communication between lecturers and
students (Grassle et al., 2005).

2.2. Study of existing systems

Several existing systems aim to enhance communication between lecturers and students in
academic settings. Here are some notable existing solutions.

Hunter College Early Alert System. This system enables faculty to identify students facing
academic challenges, such as poor performance or low attendance. Faculty can log in, set an alert
for students, refer them to campus learning centers, and compose emails to them.

InformaCast Mass Notification System. Designed for higher education institutions, this system
delivers critical information across campus in seconds. It supports emergency alerts, schedule
changes, and other important communications, ensuring timely dissemination of information.

Campus Alerts Notification System. This platform allows campus administrators to send
emergency text messages to students and faculty/staff members in minutes. It is used for mass
notifications, severe weather alerts, campus lockdowns, and building evacuations.

6
OpenSIS Student Information System. A cloud-based platform that offers tools for student
data management, communication, and academic tracking. It supports administrators, teachers,
students, and parents in managing student information effectively.

CHAPTER III. PROJECT DESIGN & METHODOLOGY

3.1. Methodology and General work procedures

The Waterfall methodology is a traditional and linear approach to software development, where
each phase of the project flows sequentially from one to the next. This methodology is well-
suited for projects with clear and well-defined requirements, making it a good choice for the
development of the Lecture and Student Alert System. Here's how it can be applied.

1. Requirement Analysis. In this phase, all requirements for the system will be gathered
from the stakeholders (lecturers, students, and administrators). This includes
understanding the key features such as real-time alerts, notification types, system
security, and platform accessibility (Cha et al., 2019).

2. System Design. Based on the gathered requirements, the system’s architecture and
design will be planned. This includes both the user interface (UI) for students and
lecturers and the back-end architecture that will support the system’s functionalities
(Cha et al., 2019)
.

3. Implementation (Coding). In this phase, the actual development of the system begins.
The coding process will follow the design specifications, ensuring that the platform
supports sending and receiving alerts efficiently. Both the web and mobile versions of the
system will be developed at this stage (Booch et al., 1999).

4. Testing. Once the system is developed, it will undergo thorough testing to ensure that it
meets all the requirements. This includes functional testing (checking if alerts are sent
and received correctly), security testing, and performance testing to ensure the system
handles multiple users effectively (Valacich & George, n.d.).

7
 5. Deployment. After successful testing, the system will be deployed to the live
environment. This involves making it accessible to lecturers and students for everyday
use (Valacich & George, n.d.).

6. Maintenance. After deployment, the system enters the maintenance phase. This involves
addressing any issues that arise, performing regular updates, and ensuring the system
remains secure and efficient
(Essentials of Systems Analysis and Design, 5th Edition (Joseph Valacich
.

Why Waterfall is Ideal for This Project

1. Clear Requirements. The system’s objectives and features are clearly defined, making
Waterfall a natural choice as it works best when requirements are fixed.

2. Linear Progression. The project can proceed in a structured and step-by-step manner,
ensuring each phase is completed before moving on to the next.

3. Easier to Manage. With clear milestones and deadlines, Waterfall allows for better
project management, especially when delivering a specific set of features in a defined
timeline.

3.2. System Design

System design is a crucial phase where the architecture and components of the "Lecture and
Student Alert System" are planned in detail to ensure that it meets the functional and non-
functional requirements. This phase involves both high-level design (overall architecture) and
low-level design (detailed specifications of each component). Below is a breakdown of the
system design for the project (Sommerville, n.d.).

1. Architecture Design

 Client-Server Model. The system will follow a client-server architecture, where students
and lecturers will interact with the system through web and mobile clients (front-end),
while the server will handle data processing, storage, and communication (back-end)
(Filipova & Vilão, 2018)
.

8
 Web and Mobile Platforms. The system will be accessible via web browsers and mobile
apps to cater to different user preferences. Mobile applications will be developed for both
Android and iOS, while the web platform will provide a responsive design to ensure a
consistent user experience across devices (Filipova & Vilão, 2018)
.

 Real-time Communication. The system will incorporate real-time notifications using

technologies like WebSockets or push notifications to ensure that students and lecturers
receive alerts instantly (Filipova & Vilão, 2018)
.

 Database Design. A relational database (e.g., MySQL or PostgreSQL) will store data
such as user profiles, lecture schedules, alert messages, and system logs. A well-
structured schema will be designed to ensure efficient data retrieval and integrity
(Filipova & Vilão, 2018)
.

2. User Interface Design

 Lecturer Interface.

o Dashboard. A simple dashboard will allow lecturers to create, manage, and send
alerts to students.

o Alert Creation Form. A form for inputting alert details (e.g., lecture change,
cancellations, etc.), with options to specify recipients (all students or specific
groups).

o Alert History. An archive to track previously sent alerts, allowing lecturers to

review and manage communications.

 Student Interface.

o Dashboard. A personalized student dashboard will display received alerts,

upcoming lectures, and any changes to their schedules.

o Push Notifications. Students will receive push notifications or in-app alerts for
any updates regarding their lectures, including last-minute changes or
cancellations.

9
 Admin Interface. An admin panel will be designed for system administrators to manage
user accounts, monitor system performance, and configure general system settings (e.g.,
notification frequency or time zone).

3. Functional Design

 User Authentication. Both students and lecturers will have secure login processes, with
authentication methods such as email and password, or Single Sign-On (SSO) for
institutions with existing credentials.

 Alert System. Lecturers will be able to send different types of alerts (e.g., schedule
changes, cancellations, reminders) to individual students or groups. Alerts will be sent
through both push notifications and emails to ensure broad reach.

 Notification Scheduling. The system will support scheduling of alerts in advance,

allowing lecturers to plan notifications for specific dates and times, reducing last-minute
work.

 Calendar Integration. The system will integrate with existing student calendars (e.g.,
Google Calendar) to automatically update schedules with lecture times and alert
information.

4. Non-Functional Design

 Scalability. The system will be designed to scale, supporting the addition of more users,
alerts, and data without compromising performance. Cloud-based hosting solutions can
be considered for scalability.

 Security. User data will be protected using encryption protocols (SSL/TLS) and secure
authentication methods. Alerts and user data will be stored securely, following industry
best practices for database security.

 Performance. The system will be optimized to handle large volumes of alerts and users,
ensuring fast response times and minimal downtime.

 Usability. The design will prioritize a clean, intuitive interface for both students and
lecturers, making it easy to navigate and use.

10
 5. System Interaction and Flow

 Alert Flow.

1. The lecturer logs into the system and creates an alert (e.g., a class schedule
change).

2. The system stores the alert in the database and sends notifications to relevant
students.

3. Students receive the notification on their mobile app or web interface,

acknowledging the update.

4. The system logs all alert activity for reference.

 User Interaction Flow.

o A clear navigation flow will guide users through login, alert creation, notification
reception, and profile management, ensuring an easy and seamless experience.

6. Data Flow Diagram (DFD)

 The DFD will visually represent how data flows within the system, from the lecturer
creating alerts to students receiving notifications. This diagram will outline the
relationships between the database, user interfaces, and alert services.

3.3. Project Schedule

Detailed project schedule for the "Lecture and Student Alert System" from November 10, 2024,
to May 1, 2025.

SN TA TASK NAME MILESTONE DURATI STARTING ENDING STATUS

SK ON DATE DATE
ID (DAYS)
1 T1 Idea Initiation Finalized project 7 10/11/2024 16/11/2024 Pending
concept

11
2 T2 Supervisor Agreement on 5 17/11/2024 21/11/2024 Pending
Consultation project direction
3 T3 Proposal Writing Proposal draft 14 22/11/2024 5/12/2024 Pending
completed
4 T4 Proposal Defense Proposal 7 6/12/2024 12/12/2024 Pending
approved
5 T5 Requirement Requirement 14 13/12/2024 26/12/2024 Pending
Gathering & specification
Analysis completed
6 T6 System Design System 14 27/12/2024 9/01/2025 Pending
(Database and UI) architecture
completed
7 T7 Project Database schema 10 10/01/2025 19/01/2025 Pending
Implementation finalized
(Database Design)
8 T8 Project Frontend and 30 20/01/2025 18/02/2025 Pending
Implementation backend
(Coding - Frontend completed
& Backend)
9 T9 Project Testing Testing 14 19/02/2025 4/03/2025 Pending
completed
10 T10 System Refinement All bugs and 7 5/03/2025 11/03/2025 Pending
issues fixed
11 T11 Final Final project 10 12/03/2025 21/03/2025 Pending
Documentation report completed
12 T12 User Acceptance Acceptance 7 22/03/2025 28/03/2025 Pending
Testing testing
completed
13 T13 Presentation Final 10 29/03/2025 7/04/2025 Pending
Preparation presentation
ready

12
14 T14 Final Project Presentation 1 8/04/2025 8/04/2025 Pending
Presentation delivered
15 T15 Final Submission Project 7 9/04/2025 15/04/2025 Pending
successfully
submitted
16 T16 Project Review & Evaluation 7 16/04/2025 22/04/2025 Pending
Evaluation completed
17 T17 Final Report Final report 7 23/04/2025 29/04/2025 Pending
Submission approved
18 T18 Project Closure Project closure 2 30/04/2025 1/05/2025 Pending
complete

3.4. Summary and Conclusion

Summary

The Lecture and Student Alert System project is designed to address the communication
challenges faced by academic institutions, particularly in the timely dissemination of lecture
schedules, changes, cancellations, and other critical updates. The system aims to facilitate a
seamless exchange of information between lecturers and students, ensuring that students are
always informed of any changes to their academic schedules. It will leverage modern
technologies such as real-time notifications, mobile and web platforms, and secure data
management practices to provide an efficient and reliable communication tool.

Conclusion

The successful implementation of the Lecture and Student Alert System will significantly
improve the way information is communicated in academic institutions. By providing a real-
time, reliable, and user-friendly platform, the system will ensure that both students and lecturers
stay informed about critical updates, enhancing coordination and reducing confusion or missed
opportunities due to delayed or unclear information.

Through careful design and development, the system will meet the needs of academic
institutions, enabling better engagement, higher attendance rates, and a more organized academic

13
 environment. The integration of web and mobile platforms guarantees accessibility, while the
robust back-end design ensures the system’s reliability and performance.

In conclusion, the Lecture and Student Alert System has the potential to greatly enhance the
educational experience by eliminating the communication barriers that often hinder the learning
process. It provides an efficient solution for the effective management of academic schedules,
ensuring that both lecturers and students can focus on the core aspects of their education.

REFERENCE

Booch, Grady., Rumbaugh, James., & Jacobson, Ivar. (1999). The unified modeling language user guide.
Addison-Wesley.

Cha, S., Taylor, R. N., & Kang, K. (2019). Handbook of software engineering. In Handbook of
Software Engineering. Springer International Publishing. https://doi.org/10.1007/978-3-030-
00262-6

Essentials of Systems Analysis and Design, 5th Edition (Joseph Valacich, Joey George, Jeff A.
Hoffer) (z-lib.org). (n.d.).

Filipova, O., & Vilão, R. (2018). Software Development from A to Z. In Software Development from
A to Z. Apress. https://doi.org/10.1007/978-1-4842-3945-2

Grässle, Patrick., Baumann, Henriette., & Baumann, Philippe. (2005). UML 2.0 in action: a project-
based tutorial. PACKT.

Optimizing IEEE 802.11i Resource and Security Essentials for Mobile and Stationary Devices. (n.d.).
https://doi.org/10.1016/B978-0-12-802222-1/00007-9

14
Sergiienko, Andrii. (2014). WebRTC blueprints: develop your very own media applications and
services using WebRTC. Packt Pub.

Sommerville, I. (n.d.). Software engineering.

Valacich, J. S., & George, J. F. (n.d.). Modern systems analysis and design.

15