DoAssignment study guide

D2.3 · Report on computer science research accurately

Learn to report on computer science research accurately through clear examples and targeted practice.

Ontario Grade 11 Computer Science

Topics in Computer Science

ICS3U study topic D2.3 · From source to faithful report

Computer science research can examine topics such as how people use software, how computer systems behave, or how a computing method performs. Reporting that research accurately means explaining what a source says without changing its meaning, overstating its results, or leaving out a qualification that matters. A report should help a reader tell the difference between the source’s information and your own explanation. This lesson uses a published technical standard as a source-handling example; a standard gives guidance and is not necessarily a report of one research study.

What you will learn

Explain what it means to report computer science research accurately.
Separate a source’s actual findings from your interpretation or opinion.
Use reliable sources and keep claims within the limits of the evidence.
Organize a short report so readers can check where its information came from.

1. Start with a question and a suitable source

A research report begins with a focused question. For example: “What does current U.S. digital-identity guidance say about password rules?” A focused question helps you choose relevant information instead of collecting interesting but unrelated facts.

Check what kind of source you have and who produced it. A research article reports a study; a technical standard or government publication may instead summarize guidance. Do not describe a standard as an experiment, or say that a study proved something if the source does not report that result. Check the title, author or organization, date, and the section that supports the claim.

For a computer science topic, look for sources that let you trace a claim to its origin: a research paper, a university or government publication, or a standards organization’s document. A search-result snippet or a post repeating someone else’s claim is not a substitute for checking the source itself. A trustworthy source can still be misread, so reliability does not remove the need to read carefully.

Write a question narrow enough to guide source selection.
Identify whether a source reports research, offers guidance, or does something else.
Verify a claim in the source, not just in a search-result preview.

2. Take notes that preserve meaning

Read the relevant passage and record the claim in your own words. Keep the source’s key conditions and limits. If a source says a recommendation applies in a particular setting, do not report it as a rule for every setting.

Keep three things separate in your notes: what the source states, your explanation of what it means, and your own judgment. Mark a direct quotation clearly and reproduce its wording accurately. For a paraphrase, change the wording but not the meaning, and still identify the source.

A useful check is to compare each sentence in your draft with the passage it relies on. Ask: Does the source actually support this sentence? Have I changed “may” into “will,” turned a recommendation into a requirement, or removed a condition? If so, revise the sentence.

Preserve conditions, limits, and the strength of the source’s wording.
Make clear which statements come from the source and which are your own.
Use a citation close enough to a claim that readers can identify its source.

3. Build a clear, checkable report

A short report can introduce its question, present relevant findings or guidance, explain why they matter to that question, and end with a conclusion that stays within the evidence. Use plain language, but do not simplify so much that the source’s meaning changes.

Cite the source with enough information for someone else to locate it. For a web publication, include the organization or author, title, publication or update date when available, and a stable URL. Follow the citation style your teacher requests. If the source points to a study, check that study before making a claim about its methods or results.

Before submitting, review the report sentence by sentence. Check names, dates, numbers, and technical terms against the source. Remove claims that have no support, or find a suitable source for them. A report is accurate not because it sounds confident, but because its claims can be checked and fairly represent the evidence.

Organize the report around the question.
Give readers enough citation information to find the source.
Check every factual claim and keep the conclusion proportional to the evidence.

4. Practice: source, claim, and conclusion

Use this routine when preparing a report: identify the question; locate and inspect a relevant source; note the exact supported claim and any qualification; write a careful paraphrase; add a citation; then compare your draft with the source again.

Consider NIST Special Publication 800-63B, a U.S. National Institute of Standards and Technology digital-identity guideline. In its password guidance, NIST says verifiers should not require memorized secrets to be changed periodically, but should force a change when there is evidence that the authenticator has been compromised. This is guidance in a technical publication, not a claim that NIST ran a classroom experiment or that every website follows the guidance.

A fair report might say: “NIST’s digital-identity guidance advises against routine periodic password changes, while recommending a change when there is evidence of compromise.” An unfair report would say: “Research proves passwords should never be changed.” That wording removes the condition, changes guidance into a universal claim, and says “proves” without support. The source’s own words and context determine what you can report.

Distinguish a source’s category from the kind of evidence it presents.
Keep meaningful conditions when summarizing guidance or findings.
A conclusion must not be broader than the source supports.

Worked example

Paraphrase guidance without changing its scope

A student is writing about password guidance. The relevant NIST passage advises against requiring periodic changes to memorized secrets, while calling for a change when there is evidence of compromise. Which summary preserves both points?

Identify the source type
NIST SP 800-63B is a technical guideline. Describe its statement as guidance, not as the result of an experiment.
Keep the condition
The passage has two parts: it discourages requiring routine periodic changes, and it identifies evidence of compromise as a reason to change a secret. Leaving out the second part would make the summary incomplete.
Write a bounded summary
A faithful paraphrase keeps both parts and attributes the recommendation to NIST. It does not claim that all services follow the guidance.

Answer: NIST’s digital-identity guidance advises against requiring routine periodic password changes and recommends a change when there is evidence of compromise.

Check: The summary preserves the source’s two-part guidance and does not present it as a universal rule or experimental result.

Worked example

Reject an unsupported expansion

A draft says, “NIST proved that passwords should never be changed.” The source passage gives the guidance described in Example 1. What is inaccurate, and how can the sentence be revised?

Compare the claim with the source
“Proved” suggests a demonstrated research result, but the cited passage is guidance. “Never” also conflicts with the passage’s condition that a change is called for when there is evidence of compromise.
Narrow the wording
Name NIST as the source, describe the statement as guidance, and retain the condition. This makes the revised sentence checkable against the publication.

Answer: Revision: “NIST guidance advises against requiring routine periodic password changes, but calls for a change when there is evidence of compromise.”

Check: The revision removes the unsupported claim of proof and the inaccurate word “never.”

Worked example

Make a report claim checkable

A student has written, “A government publication recommends a password practice.” The student used NIST SP 800-63B but gave no title, organization, or link. What should be improved so a reader can verify the report?

Identify missing source details
“A government publication” is too vague to locate. The report should name the issuing organization and the publication, and provide a link or other location information.
Attach the source to its claim
Put the citation near the statement it supports. Use the publication’s actual title and a stable URL; follow the citation format assigned by the teacher.
Check the claim itself
A complete citation does not make an inaccurate summary accurate. Recheck that the sentence reflects the relevant passage and preserves its qualification.

Answer: Name the National Institute of Standards and Technology (NIST), identify Special Publication 800-63B by title, and provide its official publication link near the claim. Then confirm that the claim accurately represents the cited passage.

Check: A reader should be able to locate the source and identify which claim it supports.

Common mistakes and how to avoid them

Calling any technical publication a research study.

Correction: Identify what the source actually is, such as a study, guideline, or technical report, and describe its statements accordingly.

Turning qualified wording into an absolute claim.

Correction: Keep conditions and limits that affect meaning; avoid words such as “always,” “never,” or “proves” unless the source supports them.

Paraphrasing without identifying the source.

Correction: Cite paraphrased information as well as direct quotations so readers can check the original.

Adding a conclusion that goes beyond the cited evidence.

Correction: Narrow the conclusion to what the source supports or find another suitable source.

Lesson summary

D2.3 asks you to report computer science research accurately: represent sources fairly and make claims checkable.
Choose sources relevant to a focused question, and identify whether they report research or provide another kind of information.
Preserve a source’s meaning, conditions, and limits when quoting or paraphrasing.
Cite claims clearly and compare your draft with the source before submitting.

Check your understanding

Question 1

A source says a recommendation applies under a stated condition. Which report is most accurate?

State the recommendation and retain the condition.
Remove the condition to make the sentence shorter.
Say the source proves the recommendation applies everywhere.
Present the recommendation as your own finding without a citation.

Show answer and explanation

State the recommendation and retain the condition.

Retaining the condition preserves the source’s scope. The other options change its meaning or hide where the claim came from.

Question 2

You are using a technical guideline, not a study. What should you call its statement?

An experimental result
Guidance or a recommendation, as appropriate
A proven fact for every computer user
Your own research finding

Show answer and explanation

Guidance or a recommendation, as appropriate

Name the kind of source accurately. A guideline should not be described as an experiment or as your own finding.

Question 3

What is the best final check for a factual sentence in a research report?

Check that it sounds certain.
Compare it with the cited source and confirm the source supports it.
Remove its citation if the wording is in your own words.
Add a stronger conclusion to make the report persuasive.

Show answer and explanation

Compare it with the cited source and confirm the source supports it.

Comparing the sentence with its source checks both accuracy and support. Paraphrased claims still need attribution.

Key terms

Research report: A written account that presents information from sources in a clear, checkable way.
Source: The publication or other information origin used to support a report’s claims.
Paraphrase: A restatement in your own words that preserves the source’s meaning and is still attributed to that source.
Citation: Information identifying a source so a reader can locate and check it.
Qualification: A condition or limit that affects how broadly a claim applies.

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 D2.3. 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