Sitonce
Country: US
Show exams for United States Hong Kong
Sign in

Praxis Computer Science 5652 Syllabus and Topics

Updated 6 min read
Key takeaway

The ETS 5652 Study Companion lists five approximate categories: Impacts of Computing (15%), Algorithms and Computational Thinking (25%), Programming (30%), Data (15%), and Computing Systems and Networks (15%).

  • The distribution guides coverage, not exact form counts.
  • Check detailed outcomes in the current companion.
On this page16 sections
  1. Five categories define a broad content map
  2. Impacts of Computing
  3. Algorithms and Computational Thinking
  4. Programming
  5. Data
  6. Computing Systems and Networks
  7. Study outcomes as actions
  8. Quick reference
  9. Impacts includes intellectual property and ethics
  10. Standards are context, not a second exam map
  11. Map outcome verbs to practice
  12. Impacts of computing: assess trade-offs
  13. Algorithms: decompose and abstract
  14. Relate concepts to the blueprint language
  15. Include impacts as technical reasoning
  16. Turn standards language into evidence of mastery

Five categories define a broad content map

The ETS companion lists Impacts of Computing at approximately 15%, Algorithms and Computational Thinking at 25%, Programming at 30%, Data at 15%, and Computing Systems and Networks at 15%. Approximate counts include scored and unscored questions and can vary by form.

Use the distribution to plan coverage, not to forecast exact question counts. Programming has the largest approximate share, but omitting ethics, data or networks still leaves real gaps.

Impacts of Computing

This category includes computing as creativity and problem solving, communication, innovation, barriers to access, digital divide issues, beneficial and harmful effects, intellectual property, ethics, privacy and security. Candidates should compare trade-offs and connect a practice to its consequences.

A school choosing cloud storage may gain collaboration and access across devices while taking on dependence on connectivity, account controls and the provider's data practices. Compare those trade-offs in the school's context.

Algorithms and Computational Thinking

The outline covers problem decomposition, algorithmic problem-solving, design and analysis, and concepts such as abstraction, data structures and algorithm efficiency. Be ready to trace a procedure, compare steps and interpret a stated complexity bound.

The assumptions matter. Binary search needs ordered data and repeated access to a middle point; a sequential scan does not require ordering. Sorting before searching has a cost, so the number of future searches can change which approach is useful.

Programming

The programming category includes code comprehension, variables and types, expressions, conditionals, loops, functions, data structures, testing, debugging, documentation and development practices. The companion uses pseudocode and sample code; follow its notation and any language identified in the prompt.

Trace initialization, condition, body, update and termination. For arrays, check indexing; for functions, track arguments and returned values; for conditionals, test exact boundary cases. The goal is not to memorize one language's syntax if the item states different rules.

Data

Data outcomes include organizing, representing, collecting, analyzing and interpreting data, as well as considering limitations and privacy. A value can be stored in a number, string, table or encoded bit pattern, and the chosen representation affects operations and meaning.

A chart can make trends visible, but scale, aggregation and missing data can change the impression. Ask what was measured, how it was collected, which records are absent and whether the conclusion fits the sample.

Computing Systems and Networks

The companion covers hardware, software, operating systems, networks, internet concepts and security. Understand how components and protocols support communication and what a service does at a broad level.

A DNS issue, transport connection issue and application response are different stages of a network request. Do not assume one failed page load proves the cause or that every web protocol uses the same transport.

Study outcomes as actions

For each outcome, write a small observable task: trace code with a boundary, compare two algorithms, explain a digital-access barrier, convert a bit pattern under a stated convention or identify a network layer. This makes a broad outline easier to monitor.

The test is described as consistent with national computer science education studies and standards, but not aligned to one particular curriculum. The current code-specific companion remains the scope anchor for preparation.

Quick reference

CategoryApproximate questionsApproximate percent
Impacts of Computing1515%
Algorithms and Computational Thinking2525%
Programming3030%
Data1515%
Computing Systems and Networks1515%

Impacts includes intellectual property and ethics

Candidates should understand ways to protect intellectual property, such as copyright, open-source licensing and Creative Commons approaches, and consider trade-offs. Ethical practice, privacy and security are also within the category.

A classroom resource may be openly licensed with conditions. Check attribution and reuse terms rather than assuming online material is free to copy.

Standards are context, not a second exam map

ETS says the test is consistent with recommendations from national computer science education studies but not aligned to one specific curriculum. The companion remains the test scope source.

CSTA and the K-12 framework help educators understand broader learning progressions. Do not treat every standard statement as a tested item.

Map outcome verbs to practice

Use “recognize” for accurate identification, “apply” for a new scenario, “analyze” for evidence and trade-offs, and “design” for a procedure or representation.

A well-matched activity shows the ability required by the outcome rather than merely repeating a definition.

Impacts of computing: assess trade-offs

The companion includes beneficial and harmful effects of computing innovations. Consider social, economic and cultural consequences, and the groups affected.

A recommendation should address mitigation: accessibility design, transparent data use, security controls, human review or a non-digital alternative where appropriate.

Algorithms: decompose and abstract

Computational thinking can simplify a problem by identifying relevant information, dividing work into manageable parts and expressing steps clearly. Abstraction removes details that do not affect the goal.

For a library search, a record can be represented by an ID and title; the cover image may be irrelevant to lookup. Choose an abstraction that preserves what the task needs.

Relate concepts to the blueprint language

The ETS categories describe broad areas, while the detailed outline identifies specific knowledge and skills. Translate each listed skill into something observable. “Analyze an algorithm” might mean trace an input, compare growth as input size changes, or select a method for a stated constraint. “Understand networks” might mean distinguish addressing, transport and application services.

This translation prevents vague review goals such as “study programming.” A better goal is “trace a loop with a boundary condition and explain the output” because it can be checked with a fresh problem.

Include impacts as technical reasoning

The impacts category asks candidates to consider how computing affects people, institutions and society. These questions can involve privacy, security, accessibility, intellectual property, workforce effects or unequal access. They call for a reasoned connection between a technology and a consequence, not merely an opinion that technology is good or bad.

For example, collecting location data may improve a service while increasing exposure if access controls are weak. A careful answer identifies the benefit, the data risk and a proportionate safeguard. Avoid assuming one policy resolves every tradeoff.

Turn standards language into evidence of mastery

For each outline statement, define what a correct explanation or solution would look like. If the skill is to evaluate a program, evidence might include tracing its output, identifying an input that violates an assumption, and proposing a corrected condition. If it is to discuss societal impact, evidence might include naming a stakeholder, a concrete benefit, a risk and a relevant safeguard.

This approach makes broad domains studyable without reducing them to vocabulary lists. Keep one solved example and one counterexample for each major skill to show where a rule works and where it does not.

Common questions

What are the five categories?

Impacts, algorithms, programming, data, and computing systems and networks.

Which category has the largest share?

Programming, at approximately 30%.

Are category counts fixed?

No. The companion describes approximate counts that can vary by form.