Instructor Dashboard for E-Learning Systems using
Machine Learning
Design Document
Version 1.0
Group Id: S2402AE256
Supervisor Name: Mehboob Ali
Revision History
Date Version Description Author
(dd/mm/yyyy)
07/07/2024 1.0 Instructor Dashboard for E- BC210200101
Learning Systems using
Machine Learning BC210200009
Table of Contents
1. Introduction of Design Document
2. Entity Relationship Diagram (ERD)
3. Sequence Diagrams
4. Architecture Design Diagram
5. Class Diagram
6. Database Design
7. Interface Design
8. Test Cases
1. Introduction of Design Document
This design document outlines the structure and planning for the development of the
"Instructor Dashboard for E-Learning Systems using Machine Learning" project. The
document covers various design aspects including database schemas, architecture design,
sequence diagrams, class diagrams, interface designs, and test cases. The purpose of this
phase is to create a clear and detailed plan that guides the development process, ensuring that
all components of the system are well-defined and aligned with the project requirements.
This helps in identifying potential issues early, streamlining the development process, and
facilitating communication among stakeholders.
2. Entity Relationship Diagram (ERD)
The ERD visually represents the data structure of the system, showing how different entities
such as students, instructors, admins, courses, subjects, class rosters, and various
management functions (profile management, marks entry, marks editing, certificate
generation, fee management) are related. This diagram is created using Microsoft Visio
3. Sequence Diagrams
Sequence diagrams illustrate the sequence of operations for each use case, showing the
interaction between different components of the system. These diagrams help in
understanding the flow of tasks and are created using Rational Rose.
4. Architecture Design Diagram
<Provide a Tiered Architecture of the system>
5. Class Diagram
<Provide Class Diagram of the system>
6. Database Design
<Provide Database Design Diagram of the system>
7. Interface Design
<Provide here the screenshots (GUI) of the system (Provide 3 or 4 main
GUIs/interfaces, to show the most important features of the application as you are
visualizing your application to be, in actual development phase. You can update
these GUIs in Final Report and Final Presentation, in case they are changed after
the actual development.>
8. Test Cases
<Provide test cases for each use case scenario>
