Design Evaluation
Reports and interprets the design evaluation findings from the verified design/analysis, distinguishing results from engineering conclusions.
Section progress
0% of the workflow complete
Analysis & Interpretation · Statistically validate results, compare against literature and interpret them as an engineer.
Deliverable: Design Evaluation section with numbered tables/figures, statistical summary, and explicit engineering interpretation.
Minimum tables, figures and equations for Design Evaluation
Tables — at least 6
- Table — trial sections or sizes considered, with the capacity of each and the selection decision
- Table — final selected geometry for every element: dimensions, thickness, grade, spacing, elevation
- Table — slab, beam, column and shear wall schedule with governing demand
- Table — ultimate limit state check summary: demand, capacity, ratio, pass or fail, governing clause
- Table — serviceability check summary: deflection, crack width, settlement, freeboard or velocity against its limit
- Table — factors of safety achieved against the factor required, per failure mode
Figures — at least 4
- Figure — free body diagram of each isolated element, fully labelled with loads, reactions, dimensions and axes
- Figure — shear and moment (or pressure and velocity) diagrams for each force-carrying element
- Figure — dimensioned section or plan of each designed element
- Figure — capacity versus demand plot, interaction diagram, or rating curve as applicable
Equations — at least 8
- Equation — equilibrium equations written out for each free body (sum of forces and sum of moments, or continuity and energy)
- Equation — the internal force relations V(x) and M(x), or the momentum/thrust relation, used to compute each element's demand
- Equation — the resulting demand at the critical section of each element, with numeric substitution
- Equation — the capacity expression for each element type, shown with full numeric substitution and units
- Equation — the sizing criterion that sets the final dimension (for example required area, depth or diameter)
- Equation — each limit state check written as demand over capacity with numbers substituted
- Equation — the factor of safety calculation for each failure mode checked
- Equation — punching shear, drift and deflection checks with limits
Number every table and figure (Table 4.x, Figure 4.x), caption it, and refer to it by number in your text. Number displayed equations and show the substitution with units. These counts are minimums — add whatever else your design needs.
Engineering documentation standard — required in every Chapter 4 subsection
These rules are graded on every subsection. Work that misses them is capped on technical accuracy, exhibits, codes and communication, whatever the quality of the prose.
Code and standard references
- Every requirement, factor, coefficient, limit and allowable you apply cites the governing document AND the exact section, article or sub-article number — e.g. ACI 318-19 §22.5.5.1, AISC 360-22 Chapter J, Section J3.6, AASHTO LRFD 10th Ed. Article 3.6.1.2.2, ASCE 7-22 §12.8.1, ASTM D2487, state DOT manual section, local stormwater manual chapter.
- Give the edition or year of every document the first time it appears, then use a consistent short form.
- Where a code equation is used, quote the equation number (e.g. Eq. 22.5.5.1) next to your displayed equation.
- Where you depart from a code provision, state the clause you are departing from and the engineering justification.
- List every code, standard and manual actually used in a Codes and Standards table at the start of the subsection.
Citations for statements
- Every statement of fact, value taken from elsewhere, material property, soil parameter, rainfall depth, unit cost or published method carries an in-text citation (APA) to its source.
- Field and lab data cite the report, boring log, gauge, survey file or test number and its date.
- Manufacturer data cites the product literature and revision date; software results cite the program, version and model file name.
- Uncited assertions are treated as assumptions and must appear in the assumptions table with a justification.
- Every in-text citation resolves to a full entry in the reference list.
Step-by-step calculations
- Structure every calculation the same way: (1) objective, (2) governing code clause, (3) equation in symbolic form with the equation number, (4) definition of each symbol, (5) numerical substitution, (6) result with units, (7) comparison against the limit and the pass/fail statement.
- Show the substitution line — never jump from the formula to the answer.
- Number displayed equations sequentially (Eq. 4.1, 4.2, …) and refer to them by number in the text.
- State the load or flow combination governing each calculation by name.
- Carry consistent significant figures and round only at the reported result; state the rounding convention once.
- Present repetitive element checks in a calculation table with one row per element and the same column order throughout.
Free body diagrams and figures
- Draw a separate free body diagram for each isolated element — no combined sketches standing in for several members.
- Dimension every FBD: span, depth, thickness, cover, eccentricity, embedment, slope, pipe diameter, wall height — with the dimension lines and values shown.
- Label every force, pressure, reaction and moment with its symbol, magnitude and units, and show the sign convention and coordinate axes.
- Show supports and boundary conditions explicitly (pin, roller, fixed, elastic, buoyant, hydrostatic).
- Accompany each FBD with its shear, moment, thrust, pressure or hydraulic grade diagram at the same scale reference.
- Number and caption every figure (Figure 4.x) and refer to it by number in the narrative; add a scale or north arrow to plans.
Units and notation
- Every number in text, tables, figures and equations carries its unit — no bare numbers.
- Use one unit system throughout (US customary or SI); if both appear, give the converted value in parentheses consistently.
- Check dimensional homogeneity of each equation and say so — the units of both sides must match.
- Provide a nomenclature table defining every symbol with its unit.
Checking and verification
- Every calculation is checked by an independent route — hand check against software, alternative method, order-of-magnitude estimate, or a published worked example — and the check is shown, not just claimed.
- Report demand-to-capacity ratios and factors of safety against the required values, with the source clause for each required value.
- Include a verification/checking table: item, method of check, expected, obtained, difference, accept or revise.
- Sanity-check every result (magnitude, direction, plausibility) and state the conclusion.
- Record who checked the work and on what date; flag anything still unverified as an open item.
- State limitations and the range over which the result is valid.
How to complete this section
Do this next: Read the Design Evaluation lecture and the worked example so you know what "Design Evaluation section with numbered tables/figures, statistical summary, and explicit engineering interpretation." has to contain.
Not sure how to start or how much depth is expected? Read the fully written model example for this deliverable first — it shows the structure, tables and level of justification your advisor grades against.
Results & Analytics Lab — what this workspace teaches
Statistically validate results, compare against literature and interpret them as an engineer.
- Descriptive statistics and appropriate summary measures
- Hypothesis testing, p-values and practical vs. statistical significance
- Regression, R², residual analysis and model adequacy
- Confidence intervals and error bars
- Uncertainty propagation through engineering calculations
- Verification vs. validation of engineering results
- Comparing results against published literature
- Designing figures and tables that carry the argument
- Engineering interpretation: what the numbers mean for the decision
- Stating limitations and framing recommendations
End-of-term milestones
- Tuesday, November 17, 2026 — Poster printed and ready. 36 in × 48 in poster finalized and printed one week before the November 24 showcase.
- Wednesday, November 18, 2026 — Final document package uploaded for scoring. Chapters 4–5, calculation package, drawings and appendices uploaded in the app for advisor scoring.
- Wednesday, November 18, 2026 — Poster presentation to faculty and industry. Wednesday poster session — printed 36 in × 48 in poster presented in person; industry reviewers score communication and impact.
- Wednesday, November 25, 2026 — Oral presentation and defense (scored). Scored oral presentation and defense held on Wednesday, November 25.
Design Evaluation
Reports and interprets the design evaluation findings from the verified design/analysis, distinguishing results from engineering conclusions.
Section B
Engineering story
A real project situation that frames this module
The team opens week 10 believing design evaluation is a formality, because the proposal treated it in a single sentence. Reports and interprets the design evaluation findings from the verified design/analysis, distinguishing results from engineering conclusions. The first review question is not about arithmetic — it is where the basis for results are the verified numeric/graphical output came from.
Presenting a results table with no comparison to an acceptance criterion. Because every table/figure is numbered, captioned, and referenced in the narrative text, the error does not stay local: it is carried into the interpretation that converts output into an engineering recommendation, and every downstream product inherits it before anyone notices.
The owner, the reviewing agency and the engineer of record carry the consequence. On this module specifically, the exposure runs through comparison against the acceptance criterion, code limit, or published benchmark stated explicitly, and the cost of correction rises every week the project record moves closer to issue.
Decisions the engineer must make
- What record establishes results are the verified numeric/graphical output, and is that record in the project data inventory?
- Does ASME V&V 20-2009 (2009), §4 — Reporting results with uncertainty, govern here — and is that the edition adopted by the jurisdiction?
- What is the acceptance criterion for every table/figure is numbered, captioned, and referenced in the narrative text, and was it written before the result was known?
- Is Percent difference from benchmark: Δ% = (Result − Benchmark) / Benchmark × 100% valid over the parameter range this project actually occupies?
- If the check fails, does the team revise the project record or raise a change request against the locked baseline?
Photo 1. Field review: the conversation in which a scope, a constraint or a decision is actually settled.
Capstone Studio instructional photograph
Section C
Why this matters
Professional
A licensed engineer defending design evaluation cites ASME V&V 20-2009 (2009), §4 — Reporting results with uncertainty, and shows the record behind each input. Your design evaluation section with numbered tables/figures, statistical summary, and explicit engineering interpretation. is reviewed the same way — traceability is assessed before arithmetic.
Technical
Results are the verified numeric/graphical output is what makes Percent difference from benchmark: Δ% = (Result − Benchmark) / Benchmark × 100% usable on this project rather than a formula copied from a reference. Get it wrong and every quantity derived from it is wrong by the same factor.
Safety
The failure mode this module guards against is a decision made without a traceable basis. It reaches people through uncertainty and limitations stated alongside the headline result, which is why the safety check is recorded explicitly here rather than inferred from a passing strength or performance check.
Economic
The interpretation that converts output into an engineering recommendation is priced from this work. Quantities, unit costs and schedule float all trace to results are the verified numeric/graphical output; a late correction here is paid for as a change order, not a redline.
Environmental
Environmentally, this module fixes material use, land disturbance and the waste stream generated by rework. Choosing conservatively without justification is not free — the excess shows up as material, energy and land that the project consumes for no measurable gain.
Community
A results section must state the engineering conclusion the data supports, not merely display the data and let the reader infer it. The residents and agencies who inherit the completed work live with that outcome long after the semester ends.
Section D
Learning objectives
By the end of this module you will be able to:
- 1.Evaluate results are the verified numeric/graphical output, using this project's own conditions rather than a textbook case.
- 2.Apply every table/figure is numbered, captioned, and referenced in the narrative text, using this project's own conditions rather than a textbook case.
- 3.Analyze comparison against the acceptance criterion, code limit, or published benchmark stated explicitly, using this project's own conditions rather than a textbook case.
- 4.Explain statistical treatment of results (mean, COV, R², RMSE) reported with sample size, using this project's own conditions rather than a textbook case.
- 5.Compute the governing quantity from Percent difference from benchmark: Δ% = (Result − Benchmark) / Benchmark × 100%, with a unit audit on every term.
- 6.Apply ASME V&V 20-2009 (2009), §4 — Reporting results with uncertainty, and cite the section that governs your acceptance decision.
- 7.Reproduce the worked example for a results table for design evaluation reports a governing value alongside its acceptance limit and percent margin and defend the interpretation of the result.
- 8.Produce design evaluation section with numbered tables/figures, statistical summary, and explicit engineering interpretation. at a standard the advisor of record would accept without a second revision cycle.
Section E
Instructional content
Full lecture notes with figures and governing equations
Design Evaluation — what the work actually is
Reports and interprets the design evaluation findings from the verified design/analysis, distinguishing results from engineering conclusions. That single sentence hides the substance of the module: results are the verified numeric/graphical output, and every table/figure is numbered, captioned, and referenced in the narrative text. Both must be established from project evidence before anything downstream is credible.
In civil engineering practice, this work is the input to the project record. Comparison against the acceptance criterion, code limit, or published benchmark stated explicitly — which is why this page asks you to record the source of every quantity, not just its value. The interpretation that converts output into an engineering recommendation depends on it.
- Results are the verified numeric/graphical output; conclusions are the engineering judgment drawn from them — the two must not be conflated
- Every table/figure is numbered, captioned, and referenced in the narrative text
- Comparison against the acceptance criterion, code limit, or published benchmark stated explicitly
- Statistical treatment of results (mean, COV, R², RMSE) reported with sample size
- Uncertainty and limitations stated alongside the headline result
Photo 1. Design Evaluation — what the work actually is in practice — Field review: the conversation in which a scope, a constraint or a decision is actually settled.
Capstone Studio instructional photograph
Governing relationships and how they are applied here
The relationships below govern design evaluation. Percent difference from benchmark: Δ% = (Result − Benchmark) / Benchmark × 100% — each is valid only inside the parameter range this project occupies, so state that range before substituting.
Every table/figure is numbered, captioned, and referenced in the narrative text sets the values you place into these expressions. Any code-prescribed factor must match ASME V&V 20-2009 (2009); a factor lifted from a different edition silently changes the answer.
Percent difference from benchmark: Δ% = (Result − Benchmark) / Benchmark × 100%
Photo 2. Governing relationships and how they are applied here in practice — Field review: the conversation in which a scope, a constraint or a decision is actually settled.
Capstone Studio instructional photograph
Constraints, adopted standards and the safety case for design evaluation
ASME V&V 20-2009 (2009), §4 — Reporting results with uncertainty, governs this module: Governs reporting of verified/validated results with stated uncertainty ASCE 7-22 (2022), Referenced limit-state comparisons, adds the second constraint: Used as the benchmark against which structural results are compared
The safety case is explicit here. The failure mode is a decision made without a traceable basis; the people exposed are the owner, the reviewing agency and the engineer of record; the control that prevents it is uncertainty and limitations stated alongside the headline result together with an independent check by someone who did not perform the work.
- Controlling criterion for this module: results are the verified numeric/graphical output.
- Adopted reference: ASME V&V 20-2009 (2009) — cite §4 — Reporting results with uncertainty by number.
- Failure mode guarded: a decision made without a traceable basis.
- Evidence produced: Design Evaluation section with numbered tables/figures, statistical summary, and explicit engineering interpretation..
Photo 3. Constraints, adopted standards and the safety case for design evaluation in practice — Field review: the conversation in which a scope, a constraint or a decision is actually settled.
Capstone Studio instructional photograph
Where this method stops being valid
The worked example — a results table for design evaluation reports a governing value alongside its acceptance limit and percent margin — holds only while its assumptions hold. A 13% margin below the acceptance limit is reported with the governing load/condition identified, giving the reviewer a defensible basis for the pass conclusion. Outside that envelope the arithmetic still returns a number, and the number is wrong in a way no unit check will catch.
For this project, the boundary you are most likely to push is uncertainty and limitations stated alongside the headline result. If you cross it, say so in writing, bound the error, and carry the limitation into your results chapter. A disclosed limitation is professional practice; a silent extrapolation is not.
Photo 4. Where this method stops being valid in practice — Field review: the conversation in which a scope, a constraint or a decision is actually settled.
Capstone Studio instructional photograph
Section F
Engineering workflow
Steps
- 1. Assemble the inputs this module needs — results are the verified numeric/graphical output; every table/figure is numbered, captioned, and referenced in the narrative… — each with a unit and a source record.
- 2. Confirm ASME V&V 20-2009 (2009) is the adopted edition and locate §4 — Reporting results with uncertainty.
- 3. State the assumptions and the acceptance criterion for results are the verified numeric/graphical output.
- 4. Evaluate Percent difference from benchmark: Δ% = (Result − Benchmark) / Benchmark × 100% term by term, carrying one extra significant figure.
- 5. Test the result against comparison against the acceptance criterion, code limit, or published benchmark stated explicitly.
- 6. Audit units and run an order-of-magnitude check by hand before the number leaves your desk.
- 7. Obtain an independent check from a teammate who did not perform the work, and record their name and date.
- 8. Assemble design evaluation section with numbered tables/figures, statistical summary, and explicit engineering interpretation. and submit it to the advisor of record for review.
Decision points
- Is every input behind results are the verified numeric/graphical output traceable? If not — stop and collect the record.
- Does the result satisfy every table/figure is numbered, captioned, and referenced in the narrative text? If not — revise the work, never the criterion.
- Would the correction change the interpretation that converts output into an engineering recommendation? If yes — raise a change-control request before proceeding.
- Have you ruled out the most common error on this module — presenting a results table with no comparison to an acceptance criterion?
Quality checklist
- Documented: results are the verified numeric/graphical output
- Documented: every table/figure is numbered, captioned, and referenced in the narrative text
- Documented: comparison against the acceptance criterion, code limit, or published benchmark stated explicitly
- ASME V&V 20-2009 §4 — Reporting results with uncertainty cited by section number
- Units audited on every expression
- Acceptance criterion recorded before the result
- Independent check signed and dated
- Design Evaluation section with numbered tables/figures, statistical summary, and explicit engineering interpretation. attached and named per the course convention
Section H
Interactive visualization
Design Evaluation — step-through
Advance one frame at a time. Each frame adds one engineering decision to the previous state.
Step 1 of 6
Organize verified results into tables and figures.
Section I
Applicable codes and standards
ASME V&V 20-2009
2009 · §4 — Reporting results with uncertainty
Adopted design/analysis reference governing this module.
Relevance: Governs reporting of verified/validated results with stated uncertainty
Reference the section number and edition in your calculation package. Do not reproduce code text.
ASCE 7-22
2022 · Referenced limit-state comparisons
Adopted design/analysis reference governing this module.
Relevance: Used as the benchmark against which structural results are compared
Reference the section number and edition in your calculation package. Do not reproduce code text.
Section J
Worked examples
Full engineering solution format
Section K
Common mistakes and how to avoid them
- Presenting a results table with no comparison to an acceptance criterion.
- Conflating 'the result was 0.87' with 'therefore the design is acceptable' without stating the limit.
- Omitting uncertainty or limitations from the headline finding.
- Treating results are the verified numeric/graphical output as a given instead of establishing it from a project record.
- Producing design evaluation section with numbered tables/figures, statistical summary, and explicit engineering interpretation. without showing how every table/figure is numbered, captioned, and referenced in the narrative text was satisfied.
- Substituting into Percent difference from benchmark: Δ% = (Result − Benchmark) / Benchmark × 100% outside the range where it is valid, and reporting the number anyway.
- Missing uncertainty and limitations stated alongside the headline result, which is exactly the path to a decision made without a traceable basis.
- Presenting output tables as results without stating what decision they support.
- Omitting the sensitivity of the recommendation to the least certain input.
- Using inputs that no field record, laboratory report, or published source supports.
- Stopping at output and skipping verification — an unverified number is not an engineering result.
- Confusing results (what the analysis produced) with conclusions (what the engineer decided).
Section L
Industry case study
Space Shuttle Challenger O-ring failure (1986)
NASA STS-51-L launch
Official findings
- The Rogers Commission found that engineers had results showing reduced O-ring resiliency at low temperature, but the results were not carried through to an explicit go/no-go recommendation.
Field observations
- The controlling assumption was documented nowhere in the design record.
- No independent check existed at the stage where the error entered the work.
Engineering interpretation
- Interpretation below is student analysis for instructional purposes, not an official finding.
- Map the failure to a step in your own workflow and state where your process would have caught it.
Lessons learned
- A results section must state the engineering conclusion the data supports, not merely display the data and let the reader infer it.
Source: Summarize the published investigation; cite it in your reference list. Do not reproduce copyrighted report text.
Section M
FE Civil exam connection
Handbook FE Reference Handbook — civil engineering practice section (record the section number from your handbook edition).
Exam topics
Handbook formulas
- Percent difference
- R², RMSE
- NPV
Weak results here feed your FE Civil Academy weak-area queue for targeted practice.
Question 1 of 2
Score: 0/2In design evaluation, which item must be established BEFORE the analysis is run?
Section N
Apply it to your project — Design Evaluation
Complete this using your own capstone project data. Every field is saved to your project record and routed to your advisor with this module's submission.
Inputs and sources
Every value needs a traceable source.
| Quantity | Value | Unit | Source / record |
|---|
Assumptions and consequences
| Assumption | Basis | Consequence if wrong |
|---|
Self-check before submission
Section O
Design challenge
Consulting challenge — Design Evaluation
Your firm has been retained to deliver the design evaluation scope for a municipal client on a compressed schedule. Produce the technical position your firm would defend at a public meeting.
Client request: The client wants a defensible recommendation, the basis of design, and an honest statement of what remains unresolved.
Constraints
- Adopted local code edition governs; no exceptions without written variance.
- Budget and schedule are fixed; scope changes require change control.
- Public safety and accessibility requirements are non-negotiable.
Deliverables
- One-page basis of design
- Supporting calculation extract
- Risk and limitation statement
Evaluation
- Technical correctness
- Standard compliance
- Clarity of engineering judgment
- Honest treatment of uncertainty
Section P
Documentation workspace
Write the report section for this module in the academic editor
Section Q
File uploads
Accepted: PDF, DOCX, XLSX, CSV, PNG, JPG, ZIP
No files uploaded yet.
Section R
Deliverable and advisor review
Design Evaluation section with numbered tables/figures, statistical summary, and explicit engineering interpretation.
Submissions route to your assigned faculty advisor and are scored independently by faculty and administrator rubrics.
Reflection
What was the hardest engineering judgment in this module, and how did you resolve it?
Section S
ABET outcome mapping
Design Evaluation section with numbered tables/figures, statistical summary, and explicit engineering interpretation. with advisor review and dual scoring.
Assessment: Faculty rubric score and administrator rubric score on this module's submission.
Rubric: Results interpretation · Target: 70% of students at or above 'meets expectations'.
Design Evaluation section with numbered tables/figures, statistical summary, and explicit engineering interpretation. with advisor review and dual scoring.
Assessment: Faculty rubric score and administrator rubric score on this module's submission.
Rubric: Results interpretation · Target: 70% of students at or above 'meets expectations'.
Section T
References and further study
ASME V&V 20-2009 (2009)
Adopted reference — cite section numbers, do not reproduce text.
ASCE 7-22 (2022)
Adopted reference — cite section numbers, do not reproduce text.
Design Evaluation — instructor design procedure
Course template for the calculation package format expected in the final report appendix.
NCEES FE Reference Handbook
Locate the equations used here and note the handbook section for exam recall.
Advisor meeting agenda item
Bring the unresolved decision from this module to your next weekly advisor meeting.