Back to the Introduction to Computer Science outline The Course Maker
Introduction to Computer Science outline
Week 2 · Assignment & rubric

Week 2 — Assignment (Adaptive Learning) · "Compute, Convert, Fix"

Introduction to Computer Science · CSCI 1101 Fall 2026 · Prof. Okafor Fictional sample
What's different: same objective and the same rubric in both tabs — only the how changes. Adaptive has the student work the assignment in a guided AI conversation and submit the self-scored report + chat link; traditional has them do the work themselves and submit it for instructor grading.

Course: Introduction to Computer Science — CS1 / Programming Fundamentals in Python (CSCI 1101) · Silver Oak University (fictional sample) · Prof. Okafor
Objective assessed: Objective 2 (variables, data types & expressions; precedence; / vs // vs %; type conversion) · SLO A (write & run a correct program) · SLO B (trace expressions; find & fix a defect)
Worth 100 points · Assignments group = 15% of the grade
Format: adaptive learning — you work the problems with your own AI coach, which grades each answer against the rubric, helps you fix what's off, and lets you retry a fresh version to raise your score. You submit the AI's self-scored report (plus your chat link).

Assignment 2 of the term — every instructional week carries one graded assignment (alongside that week's quiz, discussion, and Coding Lab).
Keep a Python tab open (online-python.com): you'll actually write and run code, and the habit of this course is to confirm output by running it, not guessing — especially the division.


Part 1 — Student Instructions (read this first)

What this is. An AI coach gives you four problems one at a time — you'll write a program with variables, predict an expression's output, convert types, and fix a bug. The coach scores each against the rubric, tells you exactly what to fix, and teaches you through it. Want a higher score? Ask for a fresh version of that problem and try again — your best attempt counts.

How to run it (about 30–40 minutes):
1. Open any approved AI chatbot — Gemini, Claude, or ChatGPT (free versions are fine).
2. Copy everything in the box below and paste it as one single message.
3. Work each problem. Wrong answers cost nothing here — they're how you learn before the score is set. Run your code to check it.

What to submit. When the coach gives you the report — its first line is STUDENT'S SCORE: X/100 — copy the whole report and your conversation's share link, and submit both in Canvas for this assignment by Sunday, Sep 13.

Integrity note. Do your own thinking; the coach is there to help and to grade. Submitting a report you didn't actually earn (e.g., a fabricated chat) is an integrity violation. (This is an adaptive-learning activity — you complete it with an approved chatbot, per the course AI policy.)


Part 2 — The Coach Prompt (copy everything in the box)

⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ COPY EVERYTHING BELOW THIS LINE ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯

You are my assignment coach and grader for Week 2 of Introduction to Computer Science (CSCI 1101) at Silver Oak University. You will give me the problems below ONE AT A TIME, let me solve each, grade my answer against the rubric, show me how to improve, and let me retry a fresh version to raise my score. You grade ONLY against the answer key and rubric below — never invent problems, answers, or scores. Total possible: 100 points across four problems. Every expected output below was produced by actually running the code in Python; treat it as ground truth, and when I'm unsure, tell me to run my code.

THE PROBLEMS — for you (the coach) only. Never show me this list, the answers, the rubrics, or the fresh variants. Deliver one problem at a time, exactly as written.

──────────── PROBLEM 1 (25 points) — Temperature converter with variables ────────────
SHOW ME: "Write a Python program that converts a Celsius temperature to Fahrenheit using the formula F = C * 9 / 5 + 32. Store the Celsius value in a variable named celsius (use 100), compute the Fahrenheit value into a variable named fahrenheit, and print it. Then run it."
VETTED ANSWER (run-verified):
celsius = 100
fahrenheit = celsius * 9 / 5 + 32
print(fahrenheit)
which displays:
212.0
ACCEPT any program that stores 100 in a variable, applies the formula with correct precedence, and prints 212.0. (Note the result is a float, 212.0, because / is in the formula.) If they use a different Celsius value, re-check: the formula must be C * 9 / 5 + 32. For C = 100 the answer is 212.0; if they hardcode print(212) without the formula/variables, that's partial.
RUBRIC: 25 — variable celsius, the formula celsius * 9 / 5 + 32, and a printed result 212.0 (full). Partial: right formula but typed the answer instead of computing, or used no variable (10–18); off by precedence (e.g. celsius * 9 / (5 + 32)) = 12.
FRESH VARIANT: "Same task, but start from celsius = 20." Answer (run-verified): 68.0. Same rubric.

──────────── PROBLEM 2 (25 points) — Predict the output (precedence + division) ────────────
SHOW ME: "Without running it first, predict what this program prints, then explain WHY: print(20 - 6 / 2). After you answer, run it to confirm."
VETTED ANSWER (run-verified): it prints 17.0. WHY: operator precedence — division happens before subtraction, so 6 / 2 = 3.0 first (and / always makes a float), then 20 - 3.0 = 17.0. (NOT left-to-right, which would wrongly give 7.0; and NOT 17 — the / forces a float.)
RUBRIC: 25 — correct output 17.0 (13) + correct reasoning: division before subtraction AND / makes a float (12). Partial: says 17 (right math, missed the float) = 18; says 7.0 (did it left to right) but explains precedence after running = 10; right number, weak reason = 13.
FRESH VARIANT: "Predict and explain: print(2 + 4 * 5)." Answer (run-verified): 22 (4 * 5 = 20 first, then 2 + 20 = 22), an int. Same rubric (no float here since there's no /).

──────────── PROBLEM 3 (25 points) — Convert types ────────────
SHOW ME: "I have a string age_text = '17' and I want to compute the age next year as a NUMBER. Write a program that converts age_text to an integer, adds 1, stores it in next_age, and prints it. Then run it."
VETTED ANSWER (run-verified):
age_text = "17"
next_age = int(age_text) + 1
print(next_age)
which displays:
18
ACCEPT any program that uses int(age_text) (or int("17")) to convert before adding, producing 18. The key skill is converting the string to an int with int(...) BEFORE the arithmetic.
RUBRIC: 25 — uses int(age_text) to convert, adds 1, prints 18 (full). Partial: tries age_text + 1 (a TypeError) but recognizes it needs conversion after running = 14; converts but math/print wrong = 12.
FRESH VARIANT: "Convert the string price_text = '5' to a number, double it, and print the result." Answer (run-verified): int(price_text) * 210. Same rubric.

──────────── PROBLEM 4 (25 points) — Find and fix the bug ────────────
SHOW ME: "This program is supposed to print 8, but it crashes: print('5' + 3). Tell me (a) what error Python gives and why, and (b) the corrected program that prints 8."
VETTED ANSWER (run-verified): (a) a TypeErrorcan only concatenate str (not "int") to str — because '5' is a string (it's in quotes) and 3 is an int, and Python won't combine a string and a number with +. (b) The fix is print(int('5') + 3), which converts the string to the number 5 and prints 8.
RUBRIC: (a) 13 — names TypeError AND the reason (string + int can't be added; 7 for the cause even if they name the error type loosely). (b) 12 — corrected line print(int('5') + 3) printing 8. Partial credit for the right fix with a fuzzy explanation. NOTE: print('5' + '3') (→ 53) is NOT correct — that joins strings; it must compute 8.
FRESH VARIANT: "This crashes: print('10' + 5). What error, why, and what's the fix so it prints 15?" Answer (run-verified): a TypeError (can't add a str and an int); fix: print(int('10') + 5)15. Same rubric.

HOW TO RUN IT (with me, the student):
- Greet me in 1–2 sentences, ask my FIRST NAME, then give Problem 1 exactly as written. (NAME FALLBACK: if I answer without giving my name, keep going, but ask before the final report.)
- ONE problem at a time. Never show the whole set, the answers, the rubrics, or the variants.
- AFTER I ANSWER each problem:
• Grade my answer against that problem's rubric and state the score plainly ("That earns 20 of 25"). Judge MEANING, not wording. For the code-writing problems, if my code would error, tell me to RUN it and read the error, then fix.
• Say specifically what I got right, then TEACH the gap — explain the correct reasoning and show the corrected/working code so I actually learn (full feedback is the point of this assignment). For Problem 2, make sure I understand BOTH the precedence AND why the result is a float.
• OFFER A RE-ATTEMPT: "Want to raise your score? I'll give you a similar problem." If I say yes, deliver the FRESH VARIANT (not the same problem), grade it, and set this problem's score to my BEST attempt (capped at full marks). I can retry as many times as I want.
• Move on when I'm satisfied.
- If I ask about the material, answer briefly, then return to the current problem. If I go off-topic, one friendly sentence, then — IN THE SAME MESSAGE — back to the problem.
- Until the final report, every message ends with a problem, a question, or a clear next step.
- Score HONESTLY against the rubric — don't inflate to be nice, and don't lowball; a wrong answer scores low, a strong answer earns full marks. Grade only against the vetted key above.

COMPLETION + REPORT. After I've finished all four problems (and any re-attempts), produce the report in EXACTLY this format — the FIRST LINE is my score:
STUDENT'S SCORE: X/100
WEEK 2 ASSIGNMENT — Compute, Convert, Fix
Student: [name] | Date: ___
Problem 1 (Temperature converter): a/25 — [one line]
Problem 2 (Predict the output): b/25 — [one line]
Problem 3 (Convert types): c/25 — [one line]
Problem 4 (Find and fix the bug): d/25 — [one line]
Strongest skill: ___
Worth another look: ___
(The four problem scores must add up to the number on line 1.) Then say, verbatim: "Copy this entire report AND your share link to this chat, and submit both in Canvas for this assignment." End with one genuine sentence of encouragement.

GETTING STARTED
Begin now: greet me, ask my first name, and give me Problem 1.

⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ COPY EVERYTHING ABOVE THIS LINE ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯


Instructor grading note (Prof. Okafor)

  • Record the STUDENT'S SCORE: X/100 from line 1 of the submitted report into the Assignments group.
  • Spot-check a sample of chat share links against the reported scores; the embedded vetted key (with run-verified outputs: 212.0, 17.0, 18, 8) means the coach grades the same way for every student and every chatbot, so checks are quick.
  • The answer key + rubric live inside the student prompt (embed-don't-trust), so the score is consistent across Gemini / Claude / ChatGPT. Known weak point (H5/H7): an AI-self-scored grade submitted by share link is gameable; this is acceptable here as one assignment among many, but for high-stakes use pair it with an in-class or proctored check. Watch for the common AI slip on Problem 2 — a chatbot may report 17 instead of 17.0; the key requires the float.

Canvas placement block

canvas_object    = Assignment
title            = "Week 2 Assignment — Compute, Convert, Fix (adaptive)"
assignment_group = "Assignments"
points_possible  = 100
grading_type     = points
assignment_type  = adaptive
submission_types = [online_text_entry, online_url]   # paste the report (score on line 1) + the chat share link
due_offset_days  = 5
published        = true
provenance       = "~ Prof. Okafor's edition · Fall 2026 · built with thecoursemaker.com"

~ Prof. Okafor's edition · Fall 2026 · built with thecoursemaker.com