Federal acquisition artifacts for engineers
Write technical requirements that someone can actually test.
Reviewed: 2026-10-03
Source-based teaching example · Fictional data
Narration: Microsoft Mark · locally synthesized

00:00:00.000 — What you will learn

Write technical requirements that someone can actually test.

Visual description:
Write technical requirements that someone can actually test.

00:00:06.500 — The idea

Define the task, source evidence and expected failure behavior. Preserve the configuration and results. Technical planning does not itself make an award or spending decision.

Visual description:
Define the task, source evidence and expected failure behavior. Preserve the configuration and results. Technical planning does not itself make an award or spending decision.

00:00:21.250 — One useful term

Acceptance test. A defined check used to judge whether a stated requirement is met.

Visual description:
A defined check used to judge whether a stated requirement is met.

00:00:29.750 — A worked example

The fictional requirement says to use a named model and achieve high accuracy. The engineering comment instead specifies supported summaries, handling of conflicts and preserved test results.

Visual description:
The fictional requirement says to use a named model and achieve high accuracy. The engineering comment instead specifies supported summaries, handling of conflicts and preserved test results.

00:00:44.625 — Your turn to think

Does naming a model define how to judge the delivered work? Pause and decide before continuing.

Visual description:
Does naming a model define how to judge the delivered work?
Pause the video if you need more time.

00:01:01.583 — Why this answer works

No. Add task-specific checks. Refer brand and acquisition-authority questions to the responsible officials.

Visual description:
No. Add task-specific checks. Refer brand and acquisition-authority questions to the responsible officials.

00:01:12.375 — Check 1

Specify observable outcomes.

Visual description:
Specify observable outcomes.

00:01:17.625 — Check 2

Keep failed cases and configuration records.

Visual description:
Keep failed cases and configuration records.

00:01:23.625 — Check 3

Separate technical comments from award authority.

Visual description:
Separate technical comments from award authority.

00:01:29.458 — Now try a different case

Open the lesson and try its different practice case. Use every check in the full task. Watching alone does not mark the lesson complete.

Visual description:
Open the lesson
Try the new case
Check and revise
The full task and its requirements are in the linked lesson.