Requirements

Functional Requirements:

• Create courses with modules and multiple lesson types, allowing instructors to define title, description, category, and difficulty, with each course containing ordered modules and lessons of various types such as video, text, and quiz.
• Enroll students in courses and track their progress, creating a persistent record that monitors completed lessons and overall progress percentage for each course independently.
• Auto-grade quizzes that include multiple choice, true/false, and short answer questions, evaluating student answers against correct answers to compute a score.
• Issue completion certificates when all lessons are finished, generating a certificate with a unique ID, student name, course title, and completion date upon meeting passing criteria.

Non-Functional Requirements:

List the key non-functional requirements (eg thread safety, extensibility, maintainability, etc.)...

Core Objects & Relationships

Based on the requirements and use cases, identify the main objects of the system and analyze how they interact and relate to each other...

🎯 5 Core Domain Objects:

1. Students - Learners with enrollment and quiz capabilities
2. Teacher - Instructors who create and manage courses
3. Course - Learning containers with state-based lifecycle
4. Quiz - Assessment tools with grading strategies
5. Questions - Individual assessment items

🔄 Key Relationships:

• Composition: Course ↔ CourseState, QuizAttempt ↔ QuizState
• Aggregation: Course → Quiz, Quiz → Questions
• Association: Teacher → Course, Students → QuizAttempt

🎲 Design Pattern Integration:

• State Pattern: Manages course (Draft→Publish→Archive) and quiz (NotStarted→InProgress→Submitted→Graded) lifecycles
• Command Pattern: Provides undoable operations for quiz addition and enrollment
• Strategy Pattern: Enables flexible grading algorithms
• Facade Pattern: LMSManager as unified API

📈 Business Impact:

• Scalability: Services can be distributed independently
• Maintainability: Clear separation of concerns
• Extensibility: Easy to add new states, strategies, or commands
• Testability: Each component can be tested in isolation

APIs & Class Members

For each class, define the attributes (data) it will hold and the methods (functions) that operate on the attributes. Ensure they align with the object's responsibilities and adhere to the principle of encapsulation. Write your code in the code editor below.

Deep Dive

Explain design tradeoffs you considered. Check and explain whether your design adheres to SOLID principles. Explain how your design can handle changes in scale and whether it would be easy to extend with new functionalities. Identify areas for future improvement...