DoAssignment study guide

D3.1 · Research computer science careers and trends

Learn to research computer science careers and trends through clear examples and targeted practice.

Ontario Grade 11 Computer Science

Topics in Computer Science

ICS3U study topic D3.1 | Turning questions into evidence-based findings

Computer science research is not limited to writing programs. In D3.1, the task is to research computer science careers and trends: ask a focused question, find and assess information, and explain what the evidence supports. A career question might ask what tasks a particular role involves. A trend question might ask how a technology or work practice is changing. A careful researcher does not assume that a popular headline applies everywhere or that a job title means the same thing at every workplace. This lesson uses source-based research, not code. The examples show how to make and check research decisions; they do not claim that any career statistic or technology trend is current.

What you will learn

Describe a practical process for researching a computer science career or trend.
Use reliable sources and check when information was published or updated.
Separate evidence from opinion and avoid treating one source as proof of a broad claim.
Present a concise finding that answers a research question and identifies its evidence.

1. Start with a focused question

A research question tells you what information to look for. “What is computer science?” is too wide to investigate efficiently. A narrower career question could be: “What tasks does a software developer perform, and what skills do two credible sources say are useful?” A trend question could be: “What change does a named source describe in the use of a particular technology, and what evidence does it provide?” These are starting questions, not assumptions that a change has occurred.

Before searching, identify the key terms in the question. For a career, terms might include a job title, typical tasks, skills, and work setting. For a trend, include the technology or practice, the kind of change being discussed, and a time period if the source provides one. Use more than one phrasing when searching: employers, educators, professional organizations, and public agencies may use different words for related work.

Set a manageable scope. Decide whether you are investigating one role, comparing two roles, or examining one stated trend. A focused scope makes it easier to tell whether each source actually helps answer the question. Do not expand a small research task into a claim about every computer science workplace.

Turn a broad interest into a question that can be answered with evidence.
Choose search terms that match the question, then check that sources address it.
Keep conclusions within the question's scope.

2. Find and evaluate sources

Start with sources that have a clear responsibility for the information they publish. Examples include a government employment or occupational information service, a professional association describing its field, a college or university explaining a program or role, and an employer describing its own vacancies. Each source answers different questions. An employer's posting can provide an example of skills requested by that employer; it cannot by itself establish that every employer requires those skills.

Use identifiable sources that a reader can revisit. For Canadian occupational information, consult the Government of Canada's Job Bank at jobbank.gc.ca and look for its career or occupation information. For descriptions of computing fields, consult the Association for Computing Machinery at acm.org. For program descriptions, use the institution's own website. These sources are starting points, not automatic guarantees that every page is relevant, complete, or up to date. Record the page title, publisher, URL, and date you accessed it.

Evaluate a source by asking: Who published it? What is its purpose? What evidence or experience does it give? When was it published or updated? Does it describe a particular country, employer, or group? Is the information a measured finding, an explanation, an advertisement, or an individual's opinion? For a trend, check what is being compared and over what period. A prediction is not the same as a measured change.

Compare sources before drawing a conclusion. If sources use different job titles or describe different tasks, report the difference instead of forcing them into a single definition. If a source does not provide evidence for a claim, say so. Avoid turning a small sample, one vacancy, or an unsupported headline into a statement about an entire career or industry.

Check publisher, purpose, evidence, date, and scope.
A source can be useful for one question but unsuitable for another.
Distinguish descriptions, opinions, predictions, and evidence of change.

3. Organize evidence and report a careful finding

Make notes in your own words and connect each note to its source. A simple evidence record can include the research question, source details, the relevant finding, and a note about limitations. Keeping evidence separate from your interpretation helps prevent an opinion from being presented as a source's conclusion.

For example, a source may describe tasks, while a second source may list skills requested in a particular setting. You can report both, but make clear which source supports which statement. If the sources agree on a point, say that the sources you checked agree; do not claim universal agreement. If they differ, identify how their scope or wording differs.

A concise report can follow this pattern: answer the research question; give the supporting information and name its source; note an important limitation; and identify what further information would help. For a trend, include the source's timeframe and the kind of evidence it uses. If the information is a prediction, label it as a prediction. If you cannot establish that a trend is occurring from the available sources, report that limitation rather than inventing certainty.

In class, follow your teacher's directions for citation style. Whatever style is used, include enough information for another person to locate the source. A URL alone may be difficult to identify later, so pair it with the publisher and page title, and record the access date when required.

Keep notes traceable to their sources.
State what the evidence supports and what it does not establish.
Report differences, limits, and uncertainty honestly.

4. Apply the process to career and trend questions

Career research and trend research use the same careful habits, but ask for different evidence. Career research may examine tasks, work settings, or skills described by a source. Trend research asks whether a change is described, how the source supports that description, and what timeframe and group the claim concerns. A job posting can illustrate what one organization asks for; it is not a reliable stand-in for all roles. A forecast can describe an expectation; it does not prove what later happened.

A useful final check is to read each sentence of your draft and ask, “Which source supports this?” If no source supports a factual claim, remove it, qualify it as your own question or interpretation, or continue researching. This habit makes a short report more trustworthy than one filled with unsupported detail.

Career research describes roles using sources suited to that purpose.
Trend research checks evidence, time period, and scope before describing change.
A research conclusion should be no broader than its evidence.

Worked example

Example 1: Narrow a career question

A student is curious about software development and wants a research question that can be answered with sources. They find a government occupation page and an employer's job posting. How should they frame and limit the investigation?

Focus the question
Ask about specific information rather than whether the career is simply good or bad. For instance: “What tasks does a software developer perform, and what skills are identified by the government occupation source and this employer?”
Match each source to its use
Use the government page for the occupational description it actually provides. Use the posting as an example of what one employer says it wants. The posting can support a statement about that posting, not a claim about every software developer job.
Write a bounded finding
After reading the pages, the student should summarize only the tasks and skills they can verify there, identify which source supports each point, and note that one employer's posting has limited scope. No particular task or skill should be asserted until it has been checked in the sources.

Answer: A suitable question is: “What tasks does a software developer perform, and what skills are identified by the government occupation source and this employer?” Keep the government description and the single employer example distinct.

Check: The conclusion remains limited to the two sources and does not invent current job requirements.

Worked example

Example 2: Check a claim about a trend

A headline says that a technology is changing computer science work. A student wants to include the claim in a short report. What should they verify before describing it as a trend?

Identify the claim
Rewrite the headline as a question: What change is claimed, for whom, and over what time period? A headline may leave these details unclear.
Find the underlying evidence
Locate the report or source behind the headline. Check who published it, when it was updated, what group or setting it covers, and whether it presents observations, a forecast, or an opinion.
Compare and qualify
Look for another relevant source and compare the claims and scope. If evidence only supports a prediction or a change in one setting, describe it that way. If the sources do not establish a trend, do not present the headline as proof that a broad trend exists.

Answer: The student should verify the claim's evidence, publisher, timeframe, and scope, then state only what those sources establish. A headline by itself is insufficient evidence for a broad trend.

Check: The reasoning distinguishes a prediction or limited example from evidence of a wider change.

Worked example

Example 3: Handle sources that differ

Two sources describe a computing role differently. One gives a broad occupational description; another describes the work at a particular organization. The student is asked to report what the role involves. How can they avoid making the sources seem to contradict each other without evidence?

Compare purpose and scope
Check whether both sources discuss the same job title, country, workplace, and kind of information. A broad occupational description and a description of one organization's work may have different purposes.
Connect each statement to its source
Write notes that identify which source supports each task or description. Avoid combining details in a way that makes them appear to be one source's claim.
Report the difference fairly
Explain that the sources describe the role at different levels or in different settings, if that is what checking them shows. If the reason for a difference is unclear, say that it is unclear and seek another suitable source rather than guessing.

Answer: Describe each source's account with its scope attached. Do not claim that one description is universal or that the sources conflict until their coverage and wording have been compared.

Check: The report preserves source context and does not resolve an unexplained difference by guessing.

Common mistakes and how to avoid them

Treating the first search result or a headline as proof.

Correction: Open the source, identify its publisher and evidence, check its date and scope, and compare it with another relevant source.

Using one job posting to describe every workplace.

Correction: Present it as an example from that employer and use a broader source for a broader occupational description.

Calling a forecast a measured trend.

Correction: Label predictions as predictions and describe the evidence and timeframe the source actually provides.

Combining source statements without showing which source supports each one.

Correction: Keep notes tied to source details and make your report's attribution clear.

Lesson summary

D3.1 research begins with a focused question about a computer science career or trend.
Choose sources suited to the question and check publisher, purpose, evidence, date, and scope.
Compare sources and distinguish measured information, descriptions, opinions, and predictions.
Write conclusions that are traceable to sources and no broader than the evidence.

Check your understanding

Question 1

A student uses one employer's posting to claim that every person in a role needs the same listed skills. What is the main problem?

The posting can only support a statement about that employer's posting, not every workplace.
A job posting can never be used in career research.
A source's publisher and purpose do not need to be checked.
The claim is reliable as long as the job title is familiar.

Show answer and explanation

The posting can only support a statement about that employer's posting, not every workplace.

One posting is evidence about one employer's stated requirements. The student should limit the claim or consult sources with broader scope.

Question 2

A source describes a possible future change but gives no measured information that it has happened. How should a student report it?

As a proven trend across the entire field.
As a prediction or possibility described by that source, with its limits made clear.
As a current fact because the source published it.
As evidence that no change can occur.

Show answer and explanation

As a prediction or possibility described by that source, with its limits made clear.

A prediction is not the same as evidence of an observed change. The student should identify what the source says and avoid overstating it.

Question 3

Two sources describe a career differently. What is the best first step?

Choose whichever description sounds more appealing.
Combine both descriptions and remove source details.
Compare each source's purpose, date, wording, and scope.
Assume one source must be false.

Show answer and explanation

Compare each source's purpose, date, wording, and scope.

Differences may reflect different settings, purposes, or coverage. Compare those features before deciding what the evidence supports.

Key terms

Career research: Gathering and assessing information about a role, such as its tasks or the skills a source identifies.
Trend: A described pattern of change over time; a claim about one should be checked against its evidence and timeframe.
Scope: The group, place, time period, or subject that a source or conclusion covers.
Evidence: Information a source provides to support a claim, which must be considered in context.

Continue through ICS3U

View the complete ICS3U Ontario Grade 11 Computer Science curriculum and lessons

About this lesson and its review

Published by DoAssignment. This reviewed lesson follows Ontario Grade 11 Computer Science (ICS3U), expectation D3.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