Tip: Choose Save as PDF in the print dialog to download. Use A4 paper size.
Shade in the A or B circle for each question.
Draw a line connecting each item on the left to its match on the right.
| Left column | Right column | |
|---|---|---|
| 1Responsibility: Dev team collects load times | ANames who collects the data for a criterion, so the measuring task has a clear owner | |
| 2Responsibility: Client judges if the outputs are correct | BResponsibility is vague. It names no specific person or role, so no one clearly owns collecting the data or judging the criterion. | |
| 3Responsibility can split the work: one person collects the data and a different person judges it | CResponsibility: Tester records error counts; project manager judges against the criterion | |
| 4Responsibility should name a specific person or role for each criterion, not just 'everyone' | DCriterion 2 Responsibility: Lead developer measures and evaluates response time | |
| 5Responsibility: Everyone will check it somehow | ENames who evaluates the results and decides whether the criterion has been met | |
| 6Responsibility: Developer collects the data (no one named to judge it) | FOnly who collects the data is stated. It does not say who evaluates the data against the criterion. |
Complete each line of code by filling in the missing parts.
Shade in the letter of the line that contains an error.
responsibility — The part of an evaluation strategy that names who collects the data and who judges each criterion, so every task has a clear owner.collector = "Mia"
judge = "Sam"collector = "Mia"
judge = "Sam"
print("Data collected by", collector)owner = {"collect": "Mia", "judge": "Sam"}
print(owner["judge"])judge = ""
if judge == "":
print("No owner for this criterion!")def showowner(collector, judge):
print("Collects:", collector)
print("Judges:", judge)