AP Computer Science Principles Unit 5: Impact of Computing Notes

Introduction

Computing innovations reshape opportunities, risks, participation, and power through specific technical and social mechanisms.

Strong impact reasoning distinguishes direct function from plausible effect, identifies affected stakeholders, uses evidence at the correct level, and preserves uncertainty. Access, bias, crowdsourcing, rights, privacy, and security are design concerns rather than afterthoughts.

Current exam guidance: Aligned to the Fall 2023 AP CSP framework used in 2026–27. The May 14, 2027 digital exam includes 70 multiple-choice questions in 120 minutes plus two Create-related written-response questions in 60 minutes. The Create components are due April 30, 2027 at 11:59 p.m. ET; current College Board directions always control submission policy.

5.1

Beneficial and Harmful Effects

How can the same computing innovation produce benefits and harms at the same time?

Short answer

Effects emerge through design, deployment, users, access, incentives, and context, so one feature can help one stakeholder while burdening another.

Know firstProgram function and purpose · Claim and evidence

Trace an effect through a mechanism

Begin with direct function: what the innovation demonstrably does. A municipal wait-time display receives location updates and shows an estimated arrival interval. A rider changing departure time is a plausible effect, but it requires observation. “The display eliminates delays” is an unsupported guarantee because the display does not control vehicles or traffic.

Benefits and harms can coexist. Connected riders may face less uncertainty, while people without a compatible device receive no display. Inaccurate updates may create new confusion, and collecting location data may introduce privacy or security concerns. A strong analysis names a stakeholder, the technical mechanism connecting design to effect, evidence that would test the claim, uncertainty, and a mitigation with its own limit.

Impact analysis trace

Classify claims by the evidence they require

innovation: wait-time display

claim A: displays an estimated arrival interval
claim B: some riders may adjust departure time
claim C: eliminates all delays

classify A → direct function
classify B → plausible effect; evidence needed
classify C → unsupported guarantee

Execution stateStep 1 of 4

claim: displays estimate
basis: observable program behavior
classification: direct function

Open complete trace table

Complete trace states
Step	claim	basis	classification	audit	stakeholders	evidenceNeeded
1	displays estimate	observable program behavior	direct function	—	—	—
2	riders adjust departure	human response not measured	plausible effect	—	—	—
3	eliminates all delays	program does not control traffic	unsupported guarantee	—	—	—
4	—	—	—	access and accuracy	connected and unconnected riders	usage and error data

Output

function|plausible|unsupported

Displaying an estimate is direct behavior, a rider response is plausible but needs evidence, and eliminating all delays is unsupported because the system does not control delay causes.

Build an impact chain

State the direct technical function.
Name a specific affected stakeholder.
Explain the mechanism from feature to effect.
Identify evidence, uncertainty, and one bounded mitigation.

Keep these three ideas

Function is not the same as social effect.
Effects require a stakeholder and mechanism.
Benefits, harms, and uncertainty can coexist.

Impact of Computing