Advanced module

Capstone and Portfolio

Turn coursework into documented engineering evidence: problem definition, models, prototypes, tests, results, limitations, and recommendations.

Course outline only for now. Full chapter-level lessons are still in progress. Use this page for readiness, concepts, worked-example format, practice, review, and portfolio direction. Complete course contents are live today for Math, Physics, and Statics.

01

Readiness check

Before starting, confirm the prerequisite habits.

  • Write clear engineering claims.
  • Document assumptions.
  • Read plots and photos as evidence.
  • Explain limitations honestly.
0 or 1 weak itemContinue, but slow down at the worked example.
2 weak itemsReview the foundation page linked in the roadmap before solving practice problems.
3 or more weak itemsStep back to prerequisites; this module depends on them.
02

The core idea

Build a portfolio artifact that proves how you think, not just what you made.

A capstone is an evidence chain: every design claim must trace to an analysis, a test, or a reference; the deliverable is not the artifact but the documented argument that it works.

claim to evidence to limit
Works when: every claim about performance traces to a calculation, a test result, or a cited source.
Breaks down when: you assert the design meets requirements with no evidence chain linking claim to test.
Figure 1. Concept model for Capstone and Portfolio. The figure names inputs, computed variables, geometry, and result.
input/load result/constraint computed variable dimension/model geometry
03

The method

1Model

Make the physical situation visible.

2Relate

Translate the model into symbols.

3Solve

Calculate only after the model is clear.

4Check

Use units, scale, and limiting cases.

04

Worked example

Figure 2. Worked problem setup: A team built a small test rig. Define the evidence chain needed to claim that the design safely supports a 300 N load.
Figure 3. Calculation model. The result follows from the model, units, and reasonableness check.

A team built a small test rig. Define the evidence chain needed to claim that the design safely supports a 300 N load.

  1. Problem A team built a small test rig. Define the evidence chain needed to claim that the design safely supports a 300 N load.
  2. Given and find Claim: supports 300 N safely. Artifacts: CAD, hand calculations, FEA, prototype test, photos. Find: A portfolio evidence structure.
  3. Assumptions Idealized model, consistent units, and no hidden effects outside the stated scope.
  4. Step State the claim in measurable form.
  5. Step Link hand calculation, simulation, and physical test to the same load case.
  6. Step Document assumptions, margins, failure modes, and limitations.
  7. Step End with a recommendation for next revision.
  8. Conclusion traceable evidence chain. Carry this result into the design decision, not just into the answer box.
05

Misconceptions and diagnostics

MistakeSymptomDiagnostic questionCorrection
Claim without evidenceIt is strong enough, with no calculationWhat analysis or test backs this?Link every claim to a calculation or measurement.
Untraceable requirementsCannot show a requirement was metWhich test verifies this requirement?Maintain a requirement-to-verification trace.
Scope creepAdds features, drops verificationDoes each feature still have evidence?Hold scope to what you can verify.
06

Practice ladder

Level 1: direct skill

Redo the worked example with one changed input. Predict the trend before calculating.

Check yourself

The trend must match the governing relation: claim to evidence to limit.

Level 2: mixed concept

Draw the model from memory, label knowns and unknowns, then write the first equation without looking.

Check yourself

Your first equation should connect the model to portfolio claim.

Level 3: independent problem

Create a similar problem from a real object near you. State assumptions, solve it, and include a reasonableness check.

Check yourself

A valid solution has a sketch, given/find list, governing relation, units, and a conclusion.

Level 4: transfer task

Turn the result into a design decision: what would you change if the output missed its target by 25 percent?

Check yourself

Name the design variable with the strongest influence and justify it from the equation.

07

Working with AI, and proving it yourself

Useful AI role

Ask for a critique of assumptions, units, diagram labels, and missing checks after you have attempted the solution.

Do not outsource

Do not paste the problem and accept a final answer. Your evidence is the model, the checks, and the explanation.

08

Retrieval and spaced review

Closed-notes prompts: state a design claim, name the analysis or test that supports it, trace it back to a requirement, and state the limitation it does not yet cover.

TodayRedo the worked example from a blank page.
+1 daySolve Level 1 without notes.
+3 daysSolve Level 2 with changed numbers.
+7 daysConnect this module to another course.
+30 daysAdd a portfolio artifact.
09

Mapping and portfolio task

Course mapping

The capstone is where every prior course is cashed in: it forces analysis, materials, manufacturing, and testing skills to converge into one documented, defensible design.

First-pass focus: definitions, model setup, units, and worked examples. Save edge cases for the second pass.

Portfolio task

Create a one-page evidence-chain note linking one design claim to its analysis or test: sketch, assumptions, equations, result, reasonableness check, limitation, and recommendation.