A Semester Computer Science Elective for Grades 7–10
Planning an 18-week computer science elective for Grades 7–10? This bundle supplies 10 units and 30 lessons with lesson plans, slides, printable worksheets and projects, enough to cover a full semester of topics when you add practice and project time. Students move from algorithms and binary through Python, networks and encryption to AI and filter bubbles, and you start the elective with the materials already in place.
See the semester bundle →For an 18-week semester CS elective, the Computer Science Activities Bundle ($119.99) offers 10 units and 30 lessons for Grades 7–10. One suggested pace is under two weeks per unit, with project and practice time added. Topics include computational thinking, Python, AI and prompt engineering, cybersecurity, data privacy, cryptography, networks, binary and recommendation algorithms. It is an instant digital download and includes no software or coding platform.
The resources
Computer Science Activities Bundle, Grades 7–10
Start with the first resource; the others are optional add-ons. Open any cover for the full contents and price.
Computer Science Activities Bundle | Artificial Intelligence, Python Programming, Cybersecurity & Digital Literacy | Middle School Grades 7–10
AI Literacy & Cybersecurity Activities | Artificial Intelligence, Prompt Engineering & Online Safety | Grades 7–10
Digital Citizenship Activities | Cyberbullying, AI, Social Media & Media Literacy Lessons | Grades 7–10
Programming with Python – Computer Science Unit (Grades 6–9)
Teach-Life-Balance: The Complete Time-Saving Course for Teachers (incl. Planner, Guides & Templates)
The real problem
Filling eighteen weeks without padding
A semester elective is long enough to need real structure and short enough that every week counts. Students choose electives, so they arrive curious, but that interest fades quickly if the class turns into a string of unrelated puzzles. The course needs an arc: concepts first, then building, then thinking about how technology affects people. Electives also attract a wide range. Some students have built games at home; others have never typed a line of code. Planning for both in the same room is harder than in a core class with tracked sections. Then there is the calendar. Eighteen weeks shrink once you subtract testing days, assemblies and the last week before break. Teachers often find that a planned unit gets squeezed out and the semester ends abruptly. What makes an elective work is a defined set of units in a logical order, each short enough to finish, with project time built in at points where students can show what they learned.
Why it fits
How the bundle maps onto a semester
Ten units across eighteen weeks leaves room for projects without running out of material early.
- Ten units across eighteen weeks works out to a unit roughly every week and a half to two weeks.
- Differentiated instruction supports electives that mix first-time coders with students who code at home.
- Project-based learning gives you natural checkpoints at mid-semester and at the end of the term.
- Units on AI ethics and filter bubbles give the final weeks a reflective close instead of more drills.
- Discussion activities absorb the short, interrupted weeks around testing and holidays.
- Lesson plans and slides for all thirty lessons keep you from building content during the term.
Getting started
A suggested semester arc
One possible order across 18 weeks. The bundle does not include a semester calendar; this is a planning suggestion.
- Weeks 1–4: how computers thinkStart with computational thinking and algorithms, then binary and data representation. Students build vocabulary and confidence before writing any code. This block needs no devices.
- Weeks 5–8: Python and a projectTeach the Python unit using whatever devices and Python setup your school has, then give a week for students to extend the work into a small project.
- Weeks 9–11: networks and securityMove to how the internet works, then cybersecurity. Students see how data travels and why protecting it matters, which leads naturally into the next block.
- Weeks 12–14: privacy and encryptionTeach data privacy and online safety, then cryptography. Encryption activities make abstract privacy ideas concrete and work well on paper. The two units reinforce each other well.
- Weeks 15–18: AI and final projectClose with artificial intelligence, AI literacy and prompting, and recommendation algorithms. Reserve the last week for a final project or presentation. Leave room for presentations.
What to buy
What a semester elective needs
For a full semester, buy the Computer Science Activities Bundle at $119.99; buying ten single units at $24.99 each would cost more. If your elective has a stronger ethics or media angle, adding Digital Citizenship Activities ($69.99) gives you 4 more units and 12 lessons on cyberbullying, influencers, AI responsibility and consumer ethics. If you teach the elective twice a year and planning is what wears you down, Teach-Life-Balance ($89.90) is a separate course on time-saving routines.
Honest limits
Before you build the syllabus
The 18-week arc on this page is a suggestion; the bundle itself contains units and lessons, not a dated calendar. Thirty lessons will need project and practice days around them to fill a daily semester. No software, coding platform or devices are included, so the Python block depends on your school's equipment. Check the content against your district or state requirements before submitting a course description. Sharing with another elective teacher needs a short message to Teach Lessons first. Exchange within 7 days for store credit of equal value if it does not fit.
Good to know
Frequently asked questions
Can I list standards alignment in my elective proposal?
Not based on this product. It claims no alignment with CSTA, state or district standards and has no endorsement. It is written for Grades 7–10. For a course proposal, compare the ten topics to your local framework and describe the coverage in your own words.
Is 30 lessons enough for 18 weeks?
It is enough content, but not enough individual class periods on its own. Plan to stretch each unit with practice, discussion and project time. Roughly two weeks per unit, with some shorter, fills a semester without padding. Keep a small buffer at the end for interruptions.
What order should the units go in?
Concepts before code works well: algorithms and binary first, Python next, then networks, security, privacy and encryption, and AI-related units last. The arc above is one suggestion; reorder around your lab schedule. Keeping Python in the first half of the semester also lets students apply it in later projects.
How do I handle experienced coders?
Use the differentiated instruction in the bundle and give experienced students extended project goals. They can also take on harder variations of the Python tasks while beginners work through the basics. Pairing an experienced coder with a beginner during project work can help both, as long as the beginner still does the typing and the thinking.
What if my semester is shorter than 18 weeks?
Drop one or two units, such as networks or recommendation algorithms, or combine privacy and cybersecurity into one block. Short three-lesson units make trimming straightforward. Keep the AI units, since they tend to interest students most and give the elective a strong ending. A shorter semester also suits a slightly smaller final project rather than dropping it completely.
Can I teach it again next semester?
Yes, the license covers your own teaching, including repeat sections. Keep notes on timing after the first run so the second semester is easier to pace. The second run usually goes faster because you know where each class will need more or less time, and you can adjust the project scope to the calendar of that particular term.
Your elective, planned before day one
Ten units give the semester a clear arc from algorithms to AI.
See the semester bundle →