CA ICT & Anchor Standards Reference
What this is. A locally built index of California's CTE Model
Curriculum Standards, ICT sector (2013): the 11 cross-sector anchor standards plus
Pathway C (Software and Systems Development). What this is not. Original
paraphrases, not the CDE's text; only codes are reproduced as-is. Scope. This copy shows only what Working in Python carries.
Anchor Standards
#1.0 Academics
Successfully finishing an ICT pathway means meeting the academic standards tied to it, on the way to further education or a job.
#2.0 Communications
Working in ICT means using the sector's own vocabulary and communicating clearly, in writing, speech, and multimedia, at a career-ready level.
- #2.1 Communication follows a basic model: someone sends a message, someone else receives it.
- #2.2 Communication can break down, and recognizing what gets in the way of a message landing correctly is its own skill.
- #2.3 Reading both what's said and what's implied, then responding appropriately, is part of communicating well.
- #2.4 Clean spelling, grammar, and formatting show up in both written and electronic communication.
- #2.5 The same information often needs to reach different audiences, which means adapting the medium and format each time.
- #2.6 Using digital media and communication tools safely, legally, and responsibly is expected, not optional.
- #2.7 Writing clearly and communicating well, especially with people outside your own background, is its own working skill.
- #2.8 Serving a customer well starts from understanding what a customer-oriented approach actually looks like.
#3.0 Career Planning and Management
Making good career decisions means pulling together career information from many different kinds of sources.
- #3.1 Knowing your own interests, aptitudes, and skills is the starting point for any real career decision.
- #3.2 Traits like trustworthiness, respect, and responsibility carry real weight in how a career turns out.
- #3.3 Information and communication technologies themselves are tools people use to plan and decide on a career.
- #3.4 Different careers demand different levels of education, training, certification, or licensing, and that's worth researching directly.
- #3.5 A career plan has to account for shifting job trends, social needs, and the economy, not just personal preference.
- #3.6 Professional organizations, industry groups, and labor unions all play a role in how a working society functions.
- #3.7 Small businesses matter to both the California and the global economy.
- #3.8 Employers and colleges increasingly look at a candidate's digital footprint when evaluating them.
- #3.9 A career plan should reflect a person's actual interests, potential pathways, and options after high school.
#4.0 Technology
Both existing and brand-new technology get used in the ICT workplace to research and produce information, products, and services.
- #4.1 Electronic references are a normal source for gathering information and building products or services.
- #4.2 Technology-based communication tools can help unpack complicated systems and issues, when used responsibly.
- #4.3 More than one source often needs to be pulled together, weighed against each other, and reconciled -- and information and communication technologies are the tools for doing that.
- #4.4 Not all information found digitally is equally trustworthy, and spotting bias or intent in a source matters.
- #4.5 Technology keeps changing, and tracking how it has, does, and will affect a given pathway is worth doing directly.
- #4.6 Different information and communication technologies serve different populations, and choosing the right one is part of the task.
#5.0 Problem Solving and Critical Thinking
ICT problems get solved through research, ranging from quick lookups to sustained investigation, using critical and creative thinking.
- #5.1 Asking the right question, from more than one point of view, is often the first real step in solving a problem.
- #5.2 Work problems don't always have a predictable shape, and different kinds of reasoning fit different situations.
- #5.3 A complex work environment is a system, and understanding how its parts interact explains its outcomes.
- #5.4 Drawing a sound conclusion from analysis is what actually informs a good decision.
- #5.5 Tracking a problem to its source takes a structured, logical approach, not guesswork.
Chapter 5's Debugging section traces a symptom back to its structural cause rather than guessing: an indentation error reported at one line but caused by the line above, a decibels bug reported at line 5 but actually on line 4 (integer division). Headers only -- the chapter demonstrates this but doesn't name it as its own skill.
- #5.6 Knowing where to look for help solving a problem is itself a resource worth knowing.
- #5.7 Some problems get solved by working through them repeatedly, refining the approach each pass.
Chapter 7's has_e build-up (inline loop, then encapsulated, then a boolean return, then parameterized) and the incremental construction of uses_any mirror this standard's start-rough-and-refine framing -- the same pattern as AP's 3.9 Developing Algorithms, from the Anchor-standard side.
- #5.8 Algorithms are a tool for solving problems, not just an abstract concept.
- #5.9 A large problem becomes tractable once it's broken into smaller components.
Chapter 3's 'Why functions?' section explicitly frames functions as a way to divide a big program into smaller, debuggable, reusable pieces -- a direct match. Chapter 4's development plan is a literal, numbered decomposition procedure. Chapter 5's recursive decomposition (countdown, the Sierpinski exercise splitting a triangle of degree n into three of degree n-1) is a purer instance of the same idea.
- #5.10 Layers of abstraction let you work with a system without tracking every detail underneath it.
Calling repeat/print_twice without re-deriving what's inside them is a first, light instance of working through a layer of abstraction -- headers only, since the book doesn't use the word 'abstraction' this early and the connection is implicit. Chapter 4's interface/implementation split (two different circle implementations sharing one interface) makes the concept explicit for the first time. Chapter 6's leap of faith -- trusting a function's return value without re-examining its body -- is the clearest, most direct treatment of abstraction in the book so far.
- #5.11 Numbers can be represented in more than one base system, including binary and hexadecimal.
- #5.12 Boolean logic underlies both decision-making and searching in computing.
Chapter 5's boolean expressions and logical operators feed directly into its if statements -- boolean logic driving decision-making is the chapter's structure, not just present in it. Chapter 7's has_e/uses_any (booleans built from in/or) driving linear search, and Chapter 8's re.search result tested against None, are the searching half of the same standard -- the single best new match found in either chapter.
#6.0 Health and Safety
ICT work environments come with their own health and safety procedures, and their own specialized vocabulary.
- #6.1 Material Safety Data Sheets exist to be located and followed.
- #6.2 Workplace policies and regulations spell out what employers and employees are each responsible for.
- #6.3 Keeping tools, equipment, and supplies stored, clean, and in working order is itself a health and safety practice.
- #6.4 Lifting, bending, and moving equipment safely protects the person doing it.
- #6.5 Preventing and responding to workplace accidents includes understanding ergonomics.
- #6.6 A safe, healthy workplace has to be actively maintained, not just assumed.
- #6.7 OSHA laws and regulations apply to this workplace and are worth knowing.
- #6.8 Maintaining safety and health in the workplace is an ongoing responsibility, restated here as its own point.
- #6.9 E-waste carries health, environmental, and legal risk if it isn't disposed of properly.
- #6.10 Using natural resources like paper and ink deliberately, not wastefully, is a workplace habit.
- #6.11 Conserving energy while computing -- powering down equipment, using power-saving settings -- is a small but real practice.
#7.0 Responsibility and Flexibility
Working in the ICT sector means collaborating in ways that show personal and professional responsibility, flexibility, and respect.
- #7.1 Financial management choices ripple outward into the economy, the workforce, and the community.
- #7.2 Following through on your role -- whether it's personal, in your community, or at work -- takes real accountability.
- #7.3 Roles and responsibilities shift over time, and adapting to that is part of the job.
- #7.4 Managing time efficiently is what actually lets responsibilities get fulfilled.
- #7.5 High-quality work applies to how a product or presentation is designed, not just built.
- #7.6 Responsible financial management is a skill in its own right, not just a personal habit.
- #7.7 A professional work demeanor includes both behavior and appropriate attire for the field.
- #7.8 Issues with global reach touch the ICT sector too, and documenting that impact is worth doing.
#8.0 Ethics and Legal Responsibilities
Professional, ethical, legal behavior means responding thoughtfully to different perspectives and following applicable laws, regulations, and norms.
- #8.1 Quality assurance standards exist to be understood and actually put into practice.
- #8.2 Regulatory agencies at every level of government have their own laws and regulations covering this sector.
- #8.3 Ethical, legal practice in ICT means matching the workplace standards the sector has set.
- #8.4 Personal integrity, confidentiality, and ethical behavior matter directly to how a workplace functions.
- #8.5 An organization's culture and practices shape its whole working environment.
- #8.6 Copyright and intellectual property law apply to proprietary information, including how it gets cited.
- #8.7 Confidential information comes with its own rules about who it can be shared with.
- #8.8 Wider technology adoption has brought its own legal and ethical problems, including hacking, scams, and privacy breaches.
#9.0 Leadership and Teamwork
Working with peers means engaging with different perspectives, leadership styles, group dynamics, and resolving conflict productively.
- #9.1 Good leaders share a recognizable set of responsibilities, competencies, and behaviors.
- #9.2 Successful teams share traits: leadership, cooperation, collaboration, and sound decision-making.
- #9.3 Teamwork, leadership, and citizenship matter in school, community, and workplace settings alike.
- #9.4 Being part of a professional organization, or competing in career-development events, can genuinely sharpen academic preparation and open career doors.
- #9.5 Today's world is interconnected, and that calls for a genuinely global outlook.
- #9.6 Respecting individual and cultural differences is part of valuing diversity in the workplace.
- #9.7 Real ICT-sector problems get solved through active, interactive teamwork.
#10.0 Technical Knowledge and Skills
Every pathway in this sector draws on the same core toolkit of hands-on know-how, put into practice by following procedure carefully.
- #10.1 The ICT sector has its own terminology and practices worth being able to interpret and explain.
- #10.2 Every corner of the ICT sector comes with its own rules, regulations, and expectations to follow.
- #10.3 Projects and products in this sector have their own specific requirements and expectations to build toward.
- #10.4 Working with industry experts is a real way to gain specific technical knowledge and skill.
- #10.5 Both a single computer and a network are built from hardware and software parts that depend on each other.
- #10.6 Different kinds of information -- text, images, sound, video -- take up different amounts of data, and media formats vary in capacity.
- #10.7 Metric prefixes like kilo, mega, giga, and tera describe scale throughout computing.
- #10.8 Security in computing rests on concepts like authorization, access rights, and encryption.
- #10.9 Industry-standard software -- word processors, spreadsheets, databases, multimedia tools -- are common working tools.
- #10.10 Files get organized and managed within a hierarchical system.
- #10.11 Text, data, sound, video, and images can all move from one software program or system to another, and there's more than one route for doing it.
- #10.12 Different kinds of information call for different search strategies.
- #10.13 Retrieved information should be checked for accuracy, relevance, and completeness.
- #10.14 Online resources can meaningfully support collaboration, research, publishing, communication, and productivity -- or fail to.
#11.0 Demonstration and Application
The knowledge and skills named across this sector's anchor and pathway standards get demonstrated directly, in classrooms, labs, and real workplace settings.
- #11.1 Work-based learning experiences extend and apply what's learned in the classroom and lab.
- #11.2 Getting genuinely good at a technical pathway is what actually opens the door to certification, licensure, or further study.
- #11.3 Entrepreneurship, self-employment, and new ventures are all real options worth understanding.
- #11.4 Entrepreneurial practices and behaviors apply specifically within ICT-sector opportunities.
- #11.5 A portfolio is one way to show evidence of the skills and knowledge named in these standards.
Pathway C · Software and Systems Development Pathway
Students in this pathway prepare for computer-science-related careers: designing, building, deploying, and maintaining the software systems that keep modern organizations running, from e-commerce to healthcare records to entertainment.
#C1.0 Systems Development Process
Building software well means following a real systems-development process, not improvising.
- #C1.1 A systems-development life cycle moves through recognizable phases: analysis, design, programming, testing, deployment, maintenance, and improvement.
- #C1.2 Systems development can follow different models, including a traditional life-cycle approach or agile methods.
- #C1.3 Specifications and requirements for a piece of software, new or existing, get developed through a real process.
- #C1.4 Working on a development team means operating within that team's defined scope and boundaries.
- #C1.5 Versioning is how a project's milestones get tracked over time.
- #C1.6 Flowcharts and UML are tools for diagramming a process.
#C2.0 Requirements Analysis
Software and systems requirements need to be defined and analyzed before building starts.
- #C2.1 Development work serves different ends: automating a task, making people more productive, building a model to analyze something, or simply entertaining.
- #C2.2 Development work can have unintended consequences -- bugs, security holes, health or environmental risk, privacy problems -- that are worth watching for and preventing.
- #C2.3 A development strategy should target what a specific customer actually needs and wants.
- #C2.4 Understanding a customer's needs is a distinct analytical step in development.
- #C2.5 Requirements and possible solutions both need to be worked out and written down before they can be built.
#C3.0 Human-Computer Interfaces
The interface between a person and a piece of technology is itself something to design well.
- #C3.1 Every interface runs on the same basic cycle: input, processing, output.
- #C3.2 A good interface reflects real knowledge of how people think, move, and interact socially.
- #C3.3 Accessibility -- for users with disabilities and users who don't speak English -- has to be actively supported, not assumed.
#C4.0 Programming Languages
Software gets built in a programming language, and that language sits at some level of abstraction.
- #C4.1 Programming languages range from low-level, close to the hardware, to high-level and web-based.
- #C4.2 Programming languages and protocols interact -- client-side code, server-side code, and a query language reaching into a database are all pieces of the same system.
- #C4.3 Software gets built inside some kind of environment -- a simple content editor on one end, a full-featured IDE on the other.
- #C4.4 Data has types, and those types get encoded in specific ways.
Chapter 1 introduces int, float, and str as distinct types with different encodings, and the type() function to check them -- a direct match. Chapter 6's Checking types section (isinstance, a type-guarded factorial) extends it with a second, applied instance -- checking a type at runtime, not just naming types.
- #C4.5 Programming paradigms differ -- procedural, object-oriented, event-driven, multithreaded -- and each shapes how code gets structured.
- #C4.6 Every programming language has its own syntax, and using it correctly matters.
Chapter 1 introduces syntax errors (missing parentheses, illegal quote marks); Chapter 2's Debugging section explicitly names 'syntax error' as one of three error kinds. Both are about a language's own syntax rules, matching this standard directly.
- #C4.7 Data structures, arrays, objects, files, and databases are all ways of organizing a program's data.
Chapter 8's Writing files section (open, read mode vs 'w' mode, close) is a direct match for this standard's 'files' item.
- #C4.8 Object-oriented programming brings its own vocabulary: objects, properties, methods, inheritance.
- #C4.9 A working program leans on a shared toolkit of constructs -- branches and loops, reusable procedures and functions that take parameters, variables to hold state, ways to recover from errors, and sometimes a function that calls itself.
Chapter 2 introduces variables; Chapter 3 introduces functions, parameters, and the for loop, plus error handling via %%expect. Chapter 4 adds keyword arguments and more parameter work than chapters 2-3 combined. Chapter 5 adds branches (conditionals) and Chapter 6 adds recursion -- 'sometimes a function that calls itself' is this standard's own closing phrase, and Chapter 6's factorial/fibonacci are exactly that. Chapter 7 reinforces variables-holding-state (Updating variables) and a second error-recovery demo. Chapter 8 adds branch-on-condition file-reading loops and TypeError/IndexError recovery. By chapter 8 this standard's full construct list is covered.
- #C4.10 Different queueing, sorting, and searching algorithms trade off differently against each other.
Chapter 7's Search section explicitly names and builds the linear-search pattern -- the searching half of this standard. The trade-off half isn't reached; no second search algorithm exists yet to compare it against. Headers only.
- #C4.11 Development work needs documentation aimed at more than one audience -- comments for other programmers, manuals for users.
Chapter 2's Comments section is the 'comments for other programmers' half of this standard. Chapter 4's Docstrings section is a more formal instance of the same half -- a documented contract rather than a plain comment, so a distinct but related carrier, not a repeat. The 'manuals for users' half still isn't addressed anywhere.
#C5.0 Testing & Debugging
Software has to be tested, debugged, and improved, not just written.
- #C5.1 Reliable, effective, efficient software shares recognizable characteristics.
- #C5.2 A program sometimes has to change because its own specification changed, or because the technology around it moved on.
- #C5.3 Code can be optimized deliberately for better performance.
- #C5.4 Testing is a distinct step applied to both software and the broader project.
Chapter 7's Doctest section -- docstring-embedded tests, a dedicated pass/fail vocabulary, and a runner function built for the purpose -- is close to a literal match for testing as its own distinct development step.
- #C5.5 A finished result gets evaluated against what it was originally required to do.
- #C5.6 Debugging is part of quality assurance, not separate from it.
Every chapter's Debugging section -- same pattern as AP CRD-1.4/CRD-2.I, already the carrier for AP topic 1.4 in every chapter. Headers only throughout; no single chapter's Debugging section is more chapter-specific than any other's.
#C6.0 Media Integration
Development projects often pull together more than one kind of media.
- #C6.1 A print piece, a video, an audio track, and an interactive experience each have their own basic design vocabulary.
- #C6.2 Media gets encoded in different ways -- vector versus bitmap graphics, different bit depths -- and each choice trades off differently.
- #C6.3 Editing media takes the right tool for the format -- something for animating frame by frame, something for drawing or touching up an image, something for modeling in three dimensions.
- #C6.4 A multimedia project -- video, game, interactive site -- moves from storyboard through to finished production.
- #C6.5 Choosing a file format and compression level for media is its own analytical decision.
- #C6.6 Media has to actually be integrated into a finished project, using the right tools for the job.
- #C6.7 A finished project can include media built to a professional standard -- pictures, write-ups, sound, footage -- made or recorded directly rather than borrowed.
#C7.0 Web & Online Development
Web and online projects come with their own development process.
- #C7.1 Web hosting and related services need both server hardware and the right software.
- #C7.2 Getting content live online means registering a domain name and arranging both hosting and email for it.
- #C7.3 Search engine optimization, including keyword and metadata strategy, is how a site attracts visitors.
- #C7.4 E-commerce capability means handling a shopping cart and credit-card transactions, not just listing products.
- #C7.5 A website, an online business, or a personal e-portfolio is meant to actually go live, not just stay a plan.
- #C7.6 Delivering and retrieving online content quickly is its own optimization problem.
#C8.0 Databases
Databases are their own kind of software development.
- #C8.1 Databases play a critical role in how modern organizations actually function.
- #C8.2 Databases are built from basic structures: fields, records, tables, and views.
- #C8.3 Tables relate to each other in specific ways -- one-to-one, one-to-many, many-to-many -- established through primary keys, foreign keys, and indexes.
- #C8.4 Data modeling is how a database gets designed around real business needs.
- #C8.5 Queries are the tool for extracting and manipulating data, whether selecting it or acting on it.
- #C8.6 A well-normalized database follows an appropriate schema.
- #C8.7 Moving data between a database and other applications comes with real limitations and challenges.
- #C8.8 Turning data into things such as cross-tabulations, graphs, or charts is what actually makes it useful for deciding something.
#C9.0 Devices & Robotics
Software gets developed for more than just general-purpose computers, including robotics and other devices.
- #C9.1 Device-focused development shows up anywhere from personal computers to robots to smart appliances.
- #C9.2 Installing equipment and assembling hardware both call for the right tools and testing.
- #C9.3 Hardware is what actually captures input, processes it, and acts on it.
- #C9.4 Embedded programming involves digital logic, how data is represented at the machine level, and how memory is organized.
- #C9.5 A microcontroller can be programmed to run a device or a robot.
#C10.0 Intelligent Computing
Intelligent computing is its own area of software development.
- #C10.1 Models of intelligent behavior raise the question of what actually distinguishes a human from a machine.
- #C10.2 Intelligent computing covers areas like perception, proximity sensing, processing, and control.
- #C10.3 AI methods include things like neural networks, Bayesian inference, fuzzy logic, and finite state machines.
- #C10.4 Making AI behavior actually happen can lean on math-based modeling, reinforcement learning, or probability-based analysis, among other methods.