VIRTUAL CLASSROOM REMINDER APP

Design Document

Version 1.0

Group Id: F240203283

Supervisor Name : Noureen Hameed

 Revision History

Date Version Description Author

(dd/mm/yyyy)
19/11/2024 1.0 The project's goal is to BC230209821
develop a user-friendly web
application that will help
both teachers and students
handle reminders for
assignments, tests, and
events in the classroom. In
order to increase
productivity and time
management in a virtual
classroom setting, it focuses
on scheduling, watching,
and alerting users about
upcoming assignments.
 Table of Contents

1. Introduction of document

2. Scope (of the project)

3. Functional Requirements Non Functional requirements

4. Use Case Diagarm

5. Work Plan

6. Entity Relationship Diagram (ERD)

7. Database Design

8. Interface Design

1. Introduction of Document
This document explains the plan for creating the Virtual Classroom Reminder App, a web

application that helps teachers and students manage and receive reminders for classroom

activities such as assignments, exams, and events. The document outlines the features of

the app, how it will be structured, and how the development will be carried out. It includes

important sections like the functional and non-functional requirements, how the database

will be organized, what the app’s interface will look like, and the timeline for completing

the project. The purpose of this document is to make sure everyone involved in the project

understands the goals and how the app will be built.

What is Included in This Document

Scope of the Project: Explains what the app will do and what it won’t do.

Functional and Non-Functional Requirements: Details the features of the app and how it

should perform.

Use Case Diagram: A simple diagram that shows how users (teachers and students) will

interact with the app.

Work Plan: A timeline showing what tasks need to be done and when.

Entity Relationship Diagram (ERD): A diagram that shows how the app’s data will be

organized and connected.

Database Design: Describes how the data will be stored in the app.

Interface Design: Shows what the app will look like and how users will interact with it.

Purpose and Benefits of this Phase in a Software Development

Project

Purpose:

This phase is about planning and organizing the project before development starts. It

makes sure everyone understands what the app will do, how it will work, and how it will be

built. This planning helps make sure we’re all on the same page and sets clear goals for the

project.

Benefits:

Clear Understanding: Everyone knows exactly what the app will do and how it will work.

Less Confusion: With a clear plan, the development process will be more organized and

efficient, avoiding mistakes and misunderstandings.

Better Quality: By defining the app’s requirements upfront, we can make sure it meets

users’ needs and works well.

Avoiding Problems: Identifying potential issues early on helps avoid delays and unexpected

problems later in the project.

2. Scope of the project

- Create a Web App that helps teachers and students set and manage reminders for

classroom activities like assignments, exams, and events.

- Set Up User Registration and Login so teachers and students can create accounts,

securely log in, and access their own dashboard.

- Build a User Dashboard where users can see their reminders, which will be sorted into

"Upcoming," "Completed," and "Overdue" categories to keep things organized.

- Develop Reminder Management Features allowing users to create, edit, and delete

reminders with details like title, description, due date, and category (Assignment, Exam,

Event). Teachers can assign reminders to specific students or groups, while students can

create personal reminders.

- Create a Notification System that sends reminders through email or app alerts to notify

users about upcoming deadlines (like 1 day or 1 hour before).

- Add Search and Filter Options so users can easily search for reminders by title or sort

them by category or due date.

- Make the App Mobile-Friendly so it works smoothly on phones and tablets, making it

easy for users to access on any device.

- Test and Fix Any Issues to make sure the app works well, is easy to use, and runs properly

on different web browsers and devices.

3. Functional Requirements & Non Functional requirements

Functional Requirements:

User Registration & Authentication:

Users (students and teachers) should be able to register with basic information (name,

email, password).

A login system with email and password-based authentication.

Dashboard for Users:

After login, the user is directed to a dashboard where upcoming reminders are displayed.

The dashboard should show reminders categorized as "Upcoming", "Completed", and

"Overdue".

Reminder Management:

Users should be able to create a reminder by providing details such as title, description,

due date, and category (Assignment, Exam, Event).

Teachers should be able to create reminders and assign them to specific students or groups

of students.

Students should be able to create personal reminders (e.g., study time or project

deadlines).

Notification System:

The system should send notifications (email or in-app alerts) to users based on reminder

deadlines (e.g., 1 day before, 1 hour before).

Reminder Editing & Deletion:

Users should be able to edit or delete existing reminders.

Search & Filter:

Users should have the ability to search for specific reminders by title or filter reminders by

category or due date.

Mobile-Responsive UI:

The web app should be responsive and work smoothly on mobile devices.

Non-Functional Requirements:

Usability:

The UI should be simple and intuitive to allow users to create and manage reminders easily.

The system should be accessible to users with minimal technical knowledge.

Maintainability:

The system should be built with clean and modular code to allow for future updates and

feature enhancements.

Cross-Browser Compatibility:

The web app should function correctly across modern browsers (Chrome, Firefox, Safari,

Edge).
4. Use Case Diagarm
5. Work Plan
6. Entity Relationship Diagram (ERD)
7. Database Design
 8. Interface Design

LOGIN PAGE
SIGNUP PAGE
DASHBOARD SAMPLE (maybe)
Sample 2