Teaching code attribution activity in Grade 7 unit cover (OAS 7.AP.PD.02)

Teaching Incorporate & Credit in Grade 7: Oklahoma Standard 7.AP.PD.02

Teaching Incorporate & Credit in Grade 7: Oklahoma Standard 7.AP.PD.02

Teaching code attribution activity in grade 7 does not have to be complicated. Picture a software developer using libraries and existing code to build features faster while crediting original sources. That kind of thinking is exactly what Oklahoma's grade 7 computer science standard 7.AP.PD.02 asks students to practice — and it is very teachable with the right materials. This post walks through what the standard means, the misconceptions students bring to it, and discussion starters you can use tomorrow, whether you teach in a classroom or at your kitchen table.

What Does Standard 7.AP.PD.02 Actually Ask?

Incorporate existing code, media, and libraries into original programs of increasing complexity and give attribution. — Oklahoma Academic Standards for Computer Science (February 2023)

In plain language: Oklahoma's standard asks seventh graders to incorporate existing code, media, and libraries into original programs of increasing complexity and give attribution.

In student-friendly terms, the learning target is: "I can incorporate existing code, media, and libraries into original programs of increasing complexity and give attribution."

What Students Should Be Able to Do

  • I can distinguish original work from incorporated existing code, media, or libraries.
  • I can incorporate existing code, media, or libraries into an original program.
  • I can give clear, accurate attribution for incorporated resources.
  • I can explain why attribution matters, both ethically and practically.

Along the way, students pick up the working vocabulary of the topic: attribution, library, original, license, source, copyright, credit, incorporate, dependency, plagiarism, ethical, complexity.

Code Attribution Activity: Misconceptions to Watch For

These are the wrong turns students reliably take with this standard — knowing them ahead of time is half the lesson plan. Each correction strategy below comes straight from the unit's teacher guide (the paragraph and activity references point into the unit itself).

1. "Using a library means writing all of that functionality yourself from scratch."

Use paragraph 2's key point — a library provides pre-written code so you don't have to build that functionality entirely on your own.

2. "Giving attribution makes your own original work look less impressive or valuable."

Reference paragraph 5 — giving credit doesn't take anything away from your own work; it simply and accurately acknowledges what came from elsewhere.

3. "All media found online is automatically free to use however you want."

Point to paragraph 3 — media typically comes with its own specific license explaining exactly how it's allowed to be used.

4. "Attribution matters less as a program becomes more complex."

Clarify from paragraph 8 — attribution becomes more important, not less, as a more complex program likely incorporates more distinct existing resources.

Discussion Starters You Can Use Tomorrow

  • Why do you think attribution is taken seriously in both school and professional settings?
  • What's an example of a license that requires attribution versus one that requires payment?
  • Why might keeping organized attribution records from the start of a project be easier than reconstructing them later?

Bringing It Home

This topic is a natural one for families. One ten-minute activity to try: Together, look at the credits or 'about' section of an app or game you both use, and talk about what kinds of resources (art, music, code libraries) it might be crediting.

Where This Leads

Students who can incorporate existing code, media, and libraries into original programs of increasing complexity and give attribution are building skills used every day in software development, game development, open source maintenance, tech legal/compliance, and computer science education.

See the Unit in Action

Get the Complete 7.AP.PD.02 Unit

I built a complete, no-prep unit for this standard — Incorporating Existing Code with Attribution — covering 3-4 days of instruction across 36 pages:

  • Teacher guide — day-by-day pacing, misconceptions to watch for, discussion questions, differentiation for support / ELL / extension, and a 4-point rubric
  • Student learning target page — a kid-friendly "I can" statement with success criteria
  • Full content lesson with 3 embedded "Check Your Understanding" checkpoints
  • 12-question assessment (6 multiple choice, 4 true/false, 2 short answer) with a complete answer key, explanations, and exemplar responses
  • Group activity — "Attribution Detective Challenge" (45-50 minutes)
  • Individual activity — "My Incorporated Resources and Credits Page" (40-50 minutes)
  • Crossword and word search built from all 12 vocabulary terms (with answer keys)
  • Family connection letter — a plain-language page for parents, with dinner-table questions and a 10-minute home activity
  • Certificate of achievement — ready to sign and send home
  • Attribution Scenario and Reference Materials (separate printable, 1 page)

Get Incorporate & Credit on Teachers Pay Teachers →

Every Sooner Standards resource is built directly from the official Oklahoma Academic Standards for Computer Science (February 2023) — standard text verified, never paraphrased from memory.

Similar Posts

Leave a Reply