đź“š ICS4U S1

About These Expectations

The expectations in this folder are reproduced from The Ontario Curriculum, Grades 10 to 12: Computer Studies (revised 2008), the Grade 12 university preparation course ICS4U — Computer Science, published by the Ontario Ministry of Education.

The official sources

Computer Science, Grade 12, University Preparation (ICS4U) — Ontario Curriculum and Resources

The verbatim text is from the Ministry’s published document (ICS4U appears on pages 55–61). © Queen’s Printer for Ontario, 2008. Reproduced for educational use.

These codes are the Ministry's own

This document prints its codes. The strand letters, the overall expectations A1, A2, …, and the specific expectations A1.1, C2.3, … all appear exactly this way in the Ministry’s pages. When you cite C2.3 in a design document, a code review, or a course outline, you are using the Ministry’s own address for that expectation, not a local convention.

Three notes about this course’s status and this reproduction:

  • This curriculum is current. A newer Grade 10 computer studies course exists — Digital Technology and Innovations in the Changing World (ICD2O, 2023) — but it replaced only the Grade 10 material. The Ministry’s own ICS4U course page states that the 2008 computer studies curriculum remains in effect and that Grades 11 and 12 courses continue to be based on it.
  • The document prints no teacher prompts. What you see on each page is the whole of what the Ministry prints beneath that expectation.
  • Its typography and its slips are reproduced, not tidied. The document sets (e.g., …) examples in italics but (i.e., …) clarifications in roman, and that distinction is kept. So are three things a proofreader would have changed: D1.1 prints “(e.g. ergonomic standards)” with no comma after “e.g.” — the only such instance in the course; C1.1 prints “UML [Unified Modeling Language]” with the American spelling; and the hyphens in phrases like “character-to-integer” in A1.2 are the document’s own, not artifacts of a line break.

Each page keeps its code, and every concept, exercise, and stage of The Software Project links back to the codes it addresses. The codes are also tags, so every page tagged #C2 can be gathered in one place.

Why the codes matter more than they look

A code is a shared address. When a student asks “why are we doing this?”, the answer is a link. When a department writes a course outline, or a teacher takes over a class partway through, the codes are what make one person’s planning legible to another.