Watch the explanation. Practice the skill.

Builder capstone and technical defense

Show a small application’s behavior and defend its limits.

Visual lesson1:38

Captions appear here during playback.

Builder capstone and technical defense

Show a small application’s behavior and defend its limits.

Download transcriptOpen video file

Source-based teaching example · Fictional data · Reviewed 2026-10-03. Microsoft Mark · locally synthesized. On a small screen, use fullscreen for diagram details or read the transcript.

Read the descriptive transcript

0:00 · What you will learn

Show a small application’s behavior and defend its limits.

What appears on screen

Show a small application’s behavior and defend its limits.

0:06 · The idea

Connect the task, access rules, output checks and tests. Show how a new failure is detected and handled. A file named “test” is not proof that the important rule was tested.

What appears on screen

Connect the task, access rules, output checks and tests. Show how a new failure is detected and handled. A file named “test” is not proof that the important rule was tested.

0:21 · One useful term

Technical defense. Explaining your design and conclusions using work a reviewer can inspect.

What appears on screen

Explaining your design and conclusions using work a reviewer can inspect.

0:30 · A worked example

A surprise change alters an access label. The learner detects the regression, blocks release and restores the prior record. The incident becomes a new test case.

What appears on screen

A surprise change alters an access label. The learner detects the regression, blocks release and restores the prior record. The incident becomes a new test case.

0:44 · Your turn to think

Does a checked box prove an access rule works? Pause and decide before continuing.

What appears on screen

Does a checked box prove an access rule works? Pause the video if you need more time.

1:01 · Why this answer works

No. Show the test and its result. Keep the demo’s claims within its offline training conditions.

What appears on screen

No. Show the test and its result. Keep the demo’s claims within its offline training conditions.

1:10 · Check 1

Link requirements to actual tests.

What appears on screen

Link requirements to actual tests.

1:16 · Check 2

Demonstrate failure and recovery.

What appears on screen

Demonstrate failure and recovery.

1:21 · Check 3

Explain what remains unverified.

What appears on screen

Explain what remains unverified.

1:26 · 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.

What appears on screen

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

Watching explains the example. Complete the lesson practice to check what you can do. Explore all visual lessons →