Skip to content

Lesson Issue: CSA 1.3 & 1.4 Expressions and Output, Assignment Statements and Input #100

@Ahaanv19

Description

@Ahaanv19

Overview

We are building new CSA lesson modules for Unit 1.3 (Mathematical Expressions, Operators, Precedence) and Unit 1.4 (Compound Assignment, Casting, and Remainder).
To make practice more interactive, we will:

  1. Create FRQ-style coding problems aligned to the College Board framework.
  2. Add gamified features (points, levels, and progress tracking).

Tasks

1. Full-Stack FRQ Questions

  • Content design:
    • 3–4 FRQs covering binary, unary, assignment, relational, and casting.
    • Include operator precedence challenges (e.g., tricky x += y * z).
    • Practice with integer vs. double division, remainder operator %.
  • Backend:
    • Autograder checks expressions for correctness.
    • Test cases handle edge cases (negative numbers, mixed types).
    • API endpoint returns pass/fail + explanation.
  • Frontend:
    • Code editor input (Monaco/Ace).
    • Submit → API → Feedback displayed in UI.

2. Gamified Features

  • Theme: “Code Quest: Operator Arena”
    • Each correct answer = earn coins.
    • Level up after clearing FRQ sets.
  • Mechanics:
    • Streak bonus for consecutive correct submissions.
    • Wrong answers → lose a “life” (but retry possible).
  • Visuals:
    • Small animations for correct / incorrect .
    • Progress tracker bar for 1.3 → 1.4 mastery.

3. Integration

  • Connect FRQs to game logic.
  • Store user progress in backend (scores + unlocked levels).
  • Lesson flow:
    • IntroPractice (FRQs)Game rewardsSummary screen.

Deliverables

  • Fully working lesson module (frontend + backend).
  • At least 3 FRQs for 1.3 and 3 FRQs for 1.4.
  • Gamified interface with scoring and progress tracking.

Stretch Goals

  • Timed challenges for operator speed drills.
  • Leaderboard for class competitions.
  • Teacher dashboard to assign custom FRQs.

Next Steps

  1. Draft FRQs for Unit 1.3 and 1.4.
  2. Decide on editor library for code input.
  3. Assign dev roles:
    • Content writers (FRQs).
    • Backend grading logic.
    • Gamified frontend UI.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions