Project Workshop

Turning a vague idea into a chain of problem, user, criteria, constraints, prototypes, tests and evidence.

Completion evidence: Project canvas, version log, test table, safety note and presentable output.

Choose a small real problem; state success as a number or behaviour, then test a paper prototype and a working version separately.

The order is recommended. Before a project page, complete evidence from foundation, practice and debugging lessons.

Turning a vague idea into a chain of problem, user, criteria, constraints, prototypes, tests and evidence. A correct example alone is therefore insufficient. Completion evidence should be project canvas, version log, test table, safety note and presentable output, tested with normal, boundary and invalid inputs.

In the first cycle, pair foundation and application among Doing Research, Solution Alternatives, Making a Demo Video, The Requirements List, The Bug Log. Predict the result, run or measure it, then explain any difference. Even when prediction and reality match, state which changed condition would break the result.

In the second cycle, complete this laboratory: Choose a small real problem; state success as a number or behaviour, then test a paper prototype and a working version separately. Do not close with one successful screenshot. Keep the input table, expected behaviour, actual behaviour, error or measurement and the correction in one file.

In the final cycle, connect Documenting a Project, Prototyping, Preparing a Presentation, Sketch and Flowchart, Test Scenarios. Let one lesson's output become another lesson's input; show where safe stopping is needed when data type, unit, wiring, timing or user expectation changes.

Repeat the same task one month later with less source support. Compare not only speed or appearance but test coverage, explainability, safety and whether another person can rebuild the work.

Use the foundation produced in Doing Research as an input to Bill of Materials and Cost. Then show in Test Scenarios how the same idea changes under the limits of a larger system. This bridge carries the goal of turning a vague idea into a chain of problem, user, criteria, constraints, prototypes, tests and evidence. beyond one isolated example.

Add three columns to the project canvas, version log, test table, safety note and presentable output file: knowledge carried from the previous lesson, condition changed in the new lesson and result observed in testing. Sharing a word does not establish a connection; one lesson’s output should genuinely become the next process’s input.

Test the connection through this laboratory: Choose a small real problem; state success as a number or behaviour, then test a paper prototype and a working version separately. After the first attempt, add an edge condition such as empty data, wrong type, disconnected input, extreme value or user error. Record whether the system remains understandable and safe beyond the normal example.

• Name the previous lesson output
• State the one changed condition
• Separate expected and actual result
• Define safe stopping or error feedback
• Make one change in the second version