DoAssignment study guide

D2.1 · Analyse an ethical computing issue

Learn to analyse an ethical computing issue through clear examples and targeted practice.

Ontario Grade 12 Computer Science

Topics in Computer Science

ICS4U D2.1 study lesson: identify the issue, weigh impacts, and justify a response

In ICS3U, you encountered how computer systems and software affect the people who use them. This lesson builds on that foundation by focusing on one task: analysing an ethical computing issue. Analysis is more than saying that an action feels right or wrong. It means describing the choice, considering who may be affected, examining relevant values and likely consequences, and explaining why one response is more responsible than another. The examples are hypothetical; they are designed to practise reasoning, not to report real incidents or measurements.

What you will learn

  • Describe an ethical computing issue as a choice involving competing values or possible harms.
  • Identify affected people, relevant values, and likely consequences of possible actions.
  • Compare reasonable responses and justify a responsible choice using evidence and stated assumptions.

1. Start with the decision, not the verdict

An ethical computing issue arises when a computing-related decision may affect people or communities in ways that raise questions about what should be done. The decision might concern what information a service collects, how a digital tool is used, or whether a feature should be introduced. A technical system can work as intended and still raise an ethical concern: technical success alone does not settle whether its use is fair or responsible.
Begin by stating the decision as a clear question. Then separate known facts from assumptions. For example, “The app records location” is a fact only if the description or evidence establishes it. “Users may feel pressured to share it” is a possible effect that should be considered, not presented as proven. If key information is missing, name it and explain how it could change the analysis.
ICS3U knowledge helps you understand the basic purpose and use of software. You do not need to write code to analyse D2.1. The focus here is the human decision around computing, not designing an algorithm or claiming that a system has a particular technical property without evidence.
  • Frame the issue as a decision that someone can take or avoid.
  • Distinguish established facts, plausible consequences, and unanswered questions.
  • Do not treat a tool's technical capability as proof that every use of it is acceptable.

2. Map stakeholders, values, and consequences

Stakeholders are people or groups who may be affected by the decision. They can include direct users, people whose information is involved, people who rely on the service, and the organization making the decision. Ask who benefits, who bears risks, and whether some affected people have less choice or influence than others.
Values provide a way to examine the issue. Depending on the case, relevant values may include privacy, safety, fairness, access, honesty, or usefulness. Do not simply list every value. Explain how each one connects to the decision. For instance, collecting more information might make a service more useful while also creating a privacy concern. A good analysis acknowledges both sides rather than hiding a real trade-off.
Next, compare feasible responses. Consider likely benefits, possible harms, who experiences them, and how serious or avoidable they may be. Make your reasoning conditional where evidence is incomplete: “If the service stores location after a session, the privacy risk is greater than if it discards it immediately.” That is a reasoned comparison, not a claim that either design is in use.
Finally, state a recommendation and support it with the facts and values you have identified. A recommendation can include safeguards or a request for more information. Explain what could change your view. This makes the analysis transparent and open to revision rather than presenting a personal preference as an unquestionable answer.
  • Name affected groups and consider differences in their ability to choose or respond.
  • Connect each value to a specific benefit, risk, or trade-off.
  • Compare options, explain uncertainty, and justify a recommendation.

3. Practise a clear, balanced analysis

Use a short written structure: decision; known facts and uncertainties; stakeholders; relevant values; options and likely effects; recommendation with reasons. This is a reasoning aid, not a formula that guarantees the right answer. The quality of the analysis depends on whether the facts are relevant, the affected people are considered, and the conclusion follows from the reasoning.
When practising, avoid two extremes. One is a one-sided argument that mentions only benefits or only risks. The other is an unsupported conclusion such as “It is ethical because the company says so.” Instead, explain why an option is preferable in the circumstances and identify any safeguards or missing evidence that matter. The worked examples use hypothetical situations so that the reasoning, rather than external claims, can be examined.
  • Use a repeatable structure, but do not mistake the structure for the analysis itself.
  • Acknowledge competing considerations and make assumptions visible.
  • A strong recommendation gives reasons and notes relevant limits.

Worked example

A study app asks for location

A hypothetical study-planning app offers nearby study-space suggestions. Its designers propose requesting a user's location. Analyse whether the app should request it.
  1. Define the decision
    The choice is whether to request location for a feature that suggests nearby study spaces. The stated facts do not say whether location is stored or whether the feature can work without it, so those points remain unknown.
  2. Identify people and values
    Users may benefit from relevant suggestions. Users who do not want to share location may be concerned about privacy or may have less access to the feature. Usefulness and privacy are both relevant; neither automatically settles the decision.
  3. Compare responses
    One response is to request location as a requirement. Another is to make it optional and explain why it is requested. A third is to provide suggestions without location, though they may be less tailored. The best comparison depends on whether the feature truly needs location and what happens to the information.
  4. Recommend with conditions
    A reasonable recommendation is to make location optional, clearly explain its purpose, and offer a useful alternative. Before deciding how to handle information, the designers should establish whether it is stored and for how long. This recommendation supports user choice while recognizing that the missing details matter.
Answer: Make the request optional, explain its purpose, and provide an alternative. Confirm how location is handled before making stronger claims about privacy risk.
Check: The recommendation follows from the stated trade-off and clearly marks storage practices as unknown.

Worked example

A class considers an automated writing indicator

A hypothetical teacher is considering a software indicator that flags writing it classifies as possibly produced with automated assistance. The indicator may be wrong, and the class has not been told how the result would be used. Analyse whether the teacher should use it to make misconduct decisions.
  1. Separate the claim from the evidence
    The scenario says the indicator may be wrong and does not specify how it works or how reliable it is. It does not establish that a flagged piece of writing proves misconduct. Treating a flag as proof would go beyond the available information.
  2. Consider affected people and values
    Students may face consequences, while the teacher has a responsibility to assess work fairly. Relevant values include fairness, accuracy, and clear communication. Students may also need a meaningful chance to explain their work.
  3. Compare options
    The teacher could treat the indicator as decisive, use it only as a prompt for a careful conversation, or avoid using it until its limits and appropriate use are understood. Treating it as decisive creates a serious fairness concern because the scenario itself allows errors.
  4. Justify a response
    The teacher should not make a misconduct decision from the indicator alone. If considering it at all, the teacher should explain its limited role, review other relevant evidence, and give the student a chance to respond. The scenario does not establish the indicator's actual accuracy, so the analysis should not invent a rate.
Answer: Do not treat an indicator flag as proof. Any use should be limited, transparent, and accompanied by a fair review and an opportunity for the student to respond.
Check: The conclusion recognizes the stated possibility of error without inventing performance data.

Worked example

A community centre proposes a camera feature

A hypothetical community centre proposes a camera-based feature to help count attendance at events. The proposal does not explain whether images are kept or whether a manual counting option is available. Analyse whether the centre should introduce the feature as proposed.
  1. Clarify what is known
    The proposed purpose is counting attendance. The handling of images and availability of another method are unknown. Do not assume that images are stored, deleted, or used for another purpose; ask for those details.
  2. Map benefits and concerns
    The centre may find attendance estimates useful. People attending may have concerns about being recorded, and some may have limited choice about entering the space. Privacy, usefulness, and access are relevant considerations.
  3. Assess options
    The centre could introduce the feature without clarifying its operation, delay it while answering questions, or use a non-camera counting method if one meets the need. The first option leaves important effects unexplained. The alternatives require checking whether they can meet the centre's purpose.
  4. Give a conditional recommendation
    Do not introduce the feature as proposed until the centre explains whether images are kept, who can access them, and whether another method is practical. If a camera is still considered, the centre should explain its purpose to attendees and address the identified concerns. These are questions for analysis, not claims about a particular camera system.
Answer: Pause the proposal until the centre clarifies image handling and alternatives. Then compare the options against the attendance need and the effects on attendees.
Check: The recommendation is conditional because key facts are missing; it does not claim that images are necessarily retained.

Common mistakes and how to avoid them

Calling a technology ethical or unethical without describing the decision.
Correction: State the choice being considered and explain how it affects people.
Listing stakeholders but discussing only the organization using the system.
Correction: Consider direct users and other people affected, including those with less choice or influence.
Treating an assumption as an established fact.
Correction: Label uncertainty and explain what information would help resolve it.
Giving a recommendation without addressing a competing value.
Correction: Compare relevant benefits and risks, then explain why your reasons support the recommendation.

Lesson summary

  • D2.1 asks you to analyse an ethical computing issue, not merely label it.
  • Define the decision; distinguish facts from unknowns; identify stakeholders and values; compare consequences; justify a response.
  • A balanced recommendation can include safeguards and state what further information could change the analysis.

Check your understanding

Question 1

A proposal says a service may collect information, but does not say whether it keeps it. Which statement is best supported?
  1. The service definitely stores the information permanently.
  2. The service definitely deletes the information immediately.
  3. Whether the information is kept is unknown and should be clarified.
  4. The service is automatically fair because the purpose is useful.
Show answer and explanation
Whether the information is kept is unknown and should be clarified.
The scenario leaves retention unspecified. A sound analysis identifies that uncertainty rather than inventing an answer.

Question 2

A tool may incorrectly flag a student's work. What is the strongest ethical concern about using its flag as the only basis for a penalty?
  1. It could lead to an unfair decision if the flag is wrong.
  2. It guarantees that every student receives the same result.
  3. It proves the student intended to break a rule.
  4. It removes the need to explain the decision.
Show answer and explanation
It could lead to an unfair decision if the flag is wrong.
The stated possibility of error means relying only on the flag could harm a student unfairly. The scenario does not establish intent or certainty.

Question 3

Which recommendation shows the clearest ethical analysis?
  1. Use the feature because new technology is always better.
  2. Reject it because any use of computing is harmful.
  3. Choose an option, explain who benefits and may be harmed, and identify important unknowns.
  4. Avoid naming affected people so the answer stays neutral.
Show answer and explanation
Choose an option, explain who benefits and may be harmed, and identify important unknowns.
An analysis connects a recommendation to affected people, consequences, and uncertainties. The other choices rely on unsupported generalizations or omit the reasoning.

Key terms

Ethical computing issue
A computing-related decision that raises questions about its effects on people or communities and what should be done.
Stakeholder
A person or group that may be affected by a decision.
Value
A consideration, such as privacy or fairness, used to judge possible actions and their effects.
Assumption
A claim taken as true for the analysis without being established by the available information.

Continue through ICS4U

View the complete ICS4U Ontario Grade 12 Computer Science curriculum and lessons

Tutor support for D2.1 · Analyse an ethical computing issue

Working on D2.1 · Analyse an ethical computing issue in ICS4U? Bring the question and your own attempt. In a live session, you can trace a small example and find the first step where the output differs from what you expected. Ask about the first step that does not make sense, then try a similar question yourself.

Explore coding tutoring · Request an eligible free 30-minute introduction. Your request is matched by subject and language; a tutor must accept before a time is confirmed.

برای مبحث D2.1 · تحلیل مسئله اخلاقی رایانش در درس ICS4U، سؤال و تلاش خود را همراه بیاورید. در جلسه می‌توانید یک مثال کوچک را دنبال کنید و نخستین گامی را که خروجی با انتظار شما فرق دارد پیدا کنید. راهنمای معلم برنامه‌نویسی را ببینید یا جلسهٔ معارفهٔ رایگان ۳۰ دقیقه‌ای درخواست کنید. زمان جلسه پس از پذیرش معلم قطعی می‌شود.

About this lesson and its review

Published by DoAssignment. This reviewed lesson follows Ontario Grade 12 Computer Science (ICS4U), expectation D2.1. It is a study resource, not an official curriculum publication.

Before publication, content is checked for structure, mathematical or chemical notation, calculations, course boundaries, and readability. Errors can still occur, so corrections are welcomed.

Official curriculum reference

Report a correction or ask a question