# 3. Course Structure

User Type: **Super Administrator**
Source: *Mi Digital Academy - Education CRM Features Document*

---

## 3. Course Structure

### 3.1 Module-Wise Content Breakdown
**What it does:** Organizes a course's content into modules: the Super Administrator breaks the course into modules (major sections) and the units within each module (lessons, topics, activities), in the intended sequence. The module-wise breakdown is the course's internal structure — the map a learner follows — and it is the unit to which content, assignments, and progress attach.

**Sub-features:**
- Create modules within a course (the major sections), in sequence
- Create units within a module (lessons, topics, activities)
- Module/unit identity: name, description, and order
- Sequencing: the order of modules and units is maintained
- Content attachment: the course's content attaches to the units
- Breakdown view: the course's module structure with the content per unit
- Restructuring: reordering or reorganizing modules/units as the course evolves
- Audit logging of structure create/edit/reorder

**Super Administrator User Journey:**
1. For a course, Super Admin creates the modules: the major sections (e.g., Module 1: Foundations, Module 2: Core Skills, Module 3: Application).
2. Within each module, creates the units: the lessons, topics, and activities, in order.
3. Sets each module/unit's name, description, and order; the sequence is maintained.
4. Attaches the course's content to the units (a lesson's material under its unit); the unit is now the learning unit with its content.
5. Reviews the breakdown view: the course's module structure with the content per unit, so the map is complete and ordered.
6. For a restructure (a module split into two), reorganizes the modules/units and re-attaches the affected content; the change is recorded.
7. Confirms the structure is learner-navigable: a learner sees the modules and units in order, with their progress per unit.
8. The structure create, edit, and reorder events are audit-logged with the course and the timestamp.

**Rules & Edge Cases:**
- Modules and units belong to a course; the breakdown is the course's internal structure.
- The sequence is maintained; the order of modules and units is the learning order.
- Content attaches to units; the unit is the unit of content and progress.
- The breakdown view shows the structure with content per unit, so a gap (a unit with no content) is visible.
- A restructure reorganizes and re-attaches content, with the change recorded; existing learner progress is handled per the restructure's impact.
- Structure changes are audit-logged with the course and timestamp.

### 3.2 Sequential Learning Paths
**What it does:** Defines the sequential learning path through a course: the order in which a learner works through the modules and units, with the rules for progression (complete-in-order vs. free navigation). The Super Administrator configures the path so the course delivers its content in the intended sequence, with the right balance of structure and learner freedom.

**Sub-features:**
- Learning path: the sequence of modules/units a learner follows
- Progression rule: complete-in-order (locked until the prior unit is done) or free navigation
- Per-unit completion: a unit is marked complete when its requirements are met
- Path progress: a learner's position in the path (completed, current, upcoming)
- Path visibility: the learner sees the path and their progress along it
- Path configuration: the rule set per course (or per module)
- Audit logging of path configuration changes

**Super Administrator User Journey:**
1. For a course, Super Admin configures the learning path: the sequence of modules/units and the progression rule.
2. Sets the rule: complete-in-order for the foundational modules (a learner must finish Module 1 before Module 2) and free navigation for the reference modules.
3. Defines the per-unit completion requirement (watch the lesson, do the activity, pass the check), so a unit is complete when met.
4. Saves; the path is live: a learner sees the sequence and their progress (completed, current, upcoming).
5. A learner completes a unit's requirements; the unit marks complete and the next unlocks (under the complete-in-order rule).
6. For a reference module (free navigation), the learner can open any unit in it without completing the others.
7. Reviews the path configuration: the sequence, the rules per module, and the completion requirements are as intended.
8. The path configuration changes are audit-logged with the course, the rules, and the timestamp.

**Rules & Edge Cases:**
- The learning path is the course's sequence; the order is the intended learning order.
- The progression rule is per course or per module: complete-in-order locks until the prior unit is done; free navigation does not.
- A unit is complete when its requirements are met; completion is the gate for progression under the locked rule.
- The learner sees the path and their progress; the position (completed, current, upcoming) is always visible.
- A rule change affects new progression; a learner's completed units are not invalidated by a rule change.
- Path configuration changes are audit-logged with the course, rules, and timestamp.

### 3.3 Hands-On Assignments and Projects
**What it does:** Integrates hands-on assignments and projects into the course structure: practical work a learner completes to apply what they learn. The Super Administrator assigns the assignments and projects within the course, defines their requirements, and tracks their completion, so the course builds applied skill, not just passive consumption.

**Sub-features:**
- Assignments: the hands-on tasks within the course (per unit or module)
- Projects: the larger practical works (a capstone, a portfolio piece)
- Requirement definition: what the assignment/project requires for completion
- Assignment within the structure: placed at the point where the skills are ready
- Completion tracking: a learner's assignment/project work tracked
- Assessment of the work: the work assessed against the requirements (self, peer, or instructor per the course)
- Audit logging of assignment/project changes

**Super Administrator User Journey:**
1. For a course, Super Admin assigns the hands-on assignments: the tasks per unit/module where the learner applies the skill just learned.
2. Defines each assignment's requirement (what it takes to complete it) and places it at the point where the skill is ready.
3. Integrates the projects: the larger practical works (a capstone at the end, a portfolio piece mid-course), with their requirements.
4. Saves; the assignments and projects appear in the course structure at their points, and learners see them as part of the path.
5. A learner completes an assignment; the work is tracked and assessed against the requirement (per the course's assessment mode).
6. For the capstone project, the learner submits the work; it is assessed, and the completion reflects the project done.
7. Reviews the assignment/project set: the requirements are clear, the placement is right (skills ready before the task), and the coverage is adequate (the course builds applied skill).
8. The assignment/project changes are audit-logged with the course, the items, and the timestamp.

**Rules & Edge Cases:**
- Assignments and projects are integrated into the structure; they are part of the learning path, not an add-on.
- Placement is skill-appropriate: a task is assigned where the required skill is ready, not before.
- The requirement is defined per item; completion is assessed against it.
- The assessment mode (self, peer, or instructor) is per the course's setting; it is explicit.
- A learner's work is tracked; the completion record reflects the assignments and projects done.
- Assignment/project changes are audit-logged with the course, items, and timestamp.

### 3.4 Downloadable Resources, Templates, and Certificate upon Completion
**What it does:** Provides the course's supporting downloadable materials (resources and templates the learner uses) and the completion certificate: the Super Administrator attaches the downloadable resources and templates to the course and configures the certificate issued on completion, so the learner has the practical materials and a credential for finishing.

**Sub-features:**
- Downloadable resources: the supporting materials (documents, datasets, references) attached to the course
- Templates: the reusable templates a learner uses for assignments/projects
- Attachment to the structure: resources/templates placed at the relevant units
- Download permission: governed by the platform's download policy (see Content Settings)
- Completion certificate: the certificate issued when a learner completes the course
- Certificate content: the course name, the learner, the outcome, and the date
- Certificate issuance on completion (automatic) with a record
- Audit logging of resource/template attachment and certificate configuration

**Super Administrator User Journey:**
1. For a course, Super Admin attaches the downloadable resources: the supporting materials a learner needs (reference documents, datasets), placed at the relevant units.
2. Attaches the templates: the reusable templates for the assignments/projects (a report template, a project scaffold), so a learner starts from the right structure.
3. Confirms the download permission: the resources are downloadable per the platform's download policy (the entitlement and cap apply).
4. Configures the completion certificate: the certificate issued when a learner completes the course, with the course name, the learner, the outcome, and the date.
5. Saves; the resources and templates are available in the course (downloadable per policy), and the certificate is set for issuance.
6. A learner downloads a template, completes the assignment with it, and works through the course.
7. On completion, the platform issues the certificate automatically; the learner can view/download it, and the issuance is recorded.
8. The resource/template attachment and certificate configuration are audit-logged with the course and the timestamp.

**Rules & Edge Cases:**
- Downloadable resources and templates are attached to the structure; they are placed where the learner needs them.
- Downloading is governed by the platform's download policy (entitlement, cap, retention); the course attachment does not override the policy.
- The completion certificate is issued automatically on completion; it is not a manual grant.
- The certificate shows the course, the learner, the outcome, and the date; it is the completion credential.
- A certificate issuance is recorded; re-issue and revocation follow the certification rules (per policy).
- Resource/template attachment and certificate configuration are audit-logged with the course and timestamp.