The expectations in this folder are reproduced from The Ontario Curriculum, Grades 10 to 12: Computer Studies (revised 2008), the Grade 11 university preparation course ICS3U — Introduction to Computer Science, published by the Ontario Ministry of Education.
The official sources
The verbatim text is from the Ministry’s published document (ICS3U appears on pages 39–46). © 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 expectationsA1.1,B4.3, … all appear exactly this way in the Ministry’s pages. When you citeB4.3in a design document 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 states that, apart from that course, the 2008 computer studies curriculum remains in effect and all Grades 11 and 12 computer studies courses continue to be based on it.
- The document prints no teacher prompts. Some Ontario curricula print “Teacher prompt:” text beneath an expectation; this one does not. What you see on each page is the whole of what the Ministry prints.
- Its typography is reproduced, not tidied. The document sets its
(e.g., …)examples in italics but its(i.e., …)clarifications in roman, and that distinction is kept here. So is the source’s American spelling of “Modeling” inB2.4, and its bracketed expansions such as “UML [Unified Modeling Language]“.
Each page keeps its code, and every concept, exercise, and task in this
course links back to the codes it addresses — including every stage of
The Community App. The codes are also tags, so every page tagged
#B4 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.