Requirements

Determine the different ways the system will be used. This includes main functions the system needs to perform and who will use it.

1. Teachers can create the courses
2. Student can en-roll in the courses
3. Student can track their progress
4. Teacher can track the progress of each Student
5. Student can access to the Quizzes, Assignments etc.
6. Teacher can create those Quizzes, Assignments etc.
7. Teacher can evaluate the student

Define Core Objects

Based on the requirements and use cases, identify the main objects of the system...

These are the higher level classes responsible for full LMS flow:

1. User Management Class =>This will add RBAC to type of user, either teacher or student. It will give certain functionality to segregate the permissions.
2. Course Management Class => It will track the courses created by Admin and enrolled by Students.
3. Progress Tracker Class => It will check the progress of each student

Lower Level Classes:

1. User
2. Teacher
3. Student
4. Courses
5. Assignment
6. AssignmentType
7. Quizz
8. Certificate

Analyze Relationships

Determine how these objects will interact with each other to fulfill the use cases...

1. Teacher is a User
2. Student is a User
3. Teacher has Courses
4. User has Enrolled Courses
5. Courses has Quizz
6. Courses has Assignment
7. Courses has Grading
8. Courses has Certificates

Establish Hierarchy

Design inheritance trees where applicable to promote code reuse and polymorphism. This step involves identifying common attributes and behaviors that can be abstracted into parent classes...

Courses can be of different types:

ICourse =>

String instructor;

String course;

List assignment;

Quizz quizz;

getCourse, getInstructors, setInstructor

onlineCourse implements ICourse

offlineCourse implemets ICourse

. .

Assignments can be of different types: Mock, Graded, Non Graded, Practise, Outdoor etc.

Assignment =>

IAssignment:

String course;

List instructor;

Quizzes can be of different types: Timed, Not Timed, Timed MCQs, Not Timed MCQs etc.

Instructor=>

Mapcourses;

Map assignments;

addCourse(course);

removeCourse(course)

addAssignment(assignment);

removeAssignment(assignment);

Student =>

Listcourses;

Listassignments;

ProgressTracker =>

getProgress(student, assignment);

Design Patterns

Consider using design patterns (e.g., Factory, Singleton, Observer, Strategy) that fit the problem...

Define Class Members (write code)

Attributes: For each class, define the attributes (data) it will hold...

Methods: Define the methods (functions) that operate on the attributes. Ensure they align with the object's responsibilities and adhere to the principle of encapsulation.

Adhere to SOLID Guidelines

Check and explain whether your design adheres to solid principles (Ask interviewer what SOLID principle is if you can not recall it.)...

Consider Scalability and Flexibility

Explain how your design can handle changes in scale and whether it would be easily to extend with new functionalities...

Create/Explain your diagram(s)

Try creating a class, flow, state and/or sequence diagram using the diagramming tool. Mermaid flow diagrams can be used to represent system use cases. You can ask the interviewer bot to create a starter diagram if unfamiliar with the tool. Briefly explain your diagrams if necessary...

Future improvements

Critically examine your design for any flaws or areas for future improvement...