Transportation Design Development
Design geometry, sight distance, pavement sections and traffic operations per AASHTO/MUTCD.
Section progress
0% of the workflow complete
Highway & Traffic Engineering · Geometric design, traffic analysis, pavement, intersections and roadway safety to AASHTO and MUTCD.
Deliverable: Transportation design package
How to complete this section
Do this next: Read the Transportation Design Development lecture and the worked example so you know what "Transportation design package" has to contain.
Transportation Design Office — what this workspace teaches
Geometric design, traffic analysis, pavement, intersections and roadway safety to AASHTO and MUTCD.
- AASHTO Green Book design controls: design speed, functional class, design vehicle
- Traffic data: AADT, DHV, K and D factors, truck percentage, growth projection
- Horizontal alignment: curve radius, superelevation, side friction, transitions
- Vertical alignment: grades, crest and sag curves, K-values
- Sight distance: stopping, decision, passing and intersection sight distance
- Cross sections: lane and shoulder widths, side slopes, clear zone
- Pavement design: ESALs, subgrade support, layer thicknesses (flexible and rigid)
- Intersection design, roundabouts, turn lanes and capacity
- Traffic signals: warrants, phasing, cycle length, timing (MUTCD/HCM)
- Roadway drainage and safety: crash analysis, barriers, clear zone
End-of-term milestones
- Friday, November 20, 2026 — Poster printed and ready. 36 in × 48 in poster finalized and printed for the faculty and industry showcase — one to two weeks before December.
- Tuesday, November 24, 2026 — Final document package uploaded for scoring. Chapters 4–5, calculation package, drawings and appendices uploaded in the app for advisor scoring.
- Wednesday, November 25, 2026 — Poster presentation to faculty and industry. Printed 36 in × 48 in poster presented in person; industry reviewers score communication and impact.
- Wednesday, December 2, 2026 — Oral presentation and defense (scored). Scored oral presentation two to three days after the end of November.
Transportation Design Development
Design geometry, sight distance, pavement sections and traffic operations per AASHTO/MUTCD.
Section B
Engineering story
A real project situation that frames this module
It is week 6 of implementation and the transportation engineering team has reached transportation design development. Design geometry, sight distance, pavement sections and traffic operations per AASHTO/MUTCD. The DOT design reviewer asks one question: what establishes that apply the approved Capstone I methodology to transportation design development?
All inputs traceable to data, code or the approved proposal. Because document assumptions, governing standards and units for every decision, the error does not stay local: it is carried into the design of record that drawings, quantities and cost are generated from, and every downstream product inherits it before anyone notices.
Drivers, pedestrians, cyclists, transit riders and the agency that owns the facility carry the consequence. On this module specifically, the exposure runs through produce evidence an advisor can verify independently, and the cost of correction rises every week the roadway geometry, control plan and operational analysis moves closer to issue.
Decisions the engineer must make
- What record establishes apply the approved Capstone I methodology to transportation design development, and is that record in the project data inventory?
- Which adopted document governs this decision, and who confirmed it applies in this jurisdiction?
- What is the acceptance criterion for document assumptions, governing standards and units for every decision, and was it written before the result was known?
- Is the documented procedure valid for the conditions this project actually presents?
- If the check fails, does the team revise the roadway geometry, control plan and operational analysis or raise a change request against the locked baseline?
Photo 1. Peak-hour demand: the flow rate that drives capacity, delay and level-of-service analysis.
Wikimedia Commons, CC BY 2.0
Section C
Why this matters
Professional
Transportation Design Development is judged on whether an independent engineer can follow your reasoning to the same conclusion. Your transportation design package is the evidence that they can.
Technical
Apply the approved Capstone I methodology to transportation design development controls the numbers this module hands forward. Document assumptions, governing standards and units for every decision determines whether those numbers remain valid once conditions change.
Safety
The failure mode this module guards against is a geometric or control element that puts drivers in a conflict they cannot resolve. It reaches people through produce evidence an advisor can verify independently, which is why the safety check is recorded explicitly here rather than inferred from a passing strength or performance check.
Economic
The design of record that drawings, quantities and cost are generated from is priced from this work. Quantities, unit costs and schedule float all trace to apply the approved Capstone I methodology to transportation design development; a late correction here is paid for as a change order, not a redline.
Environmental
Environmentally, this module fixes vehicle delay emissions, pavement material demand and stormwater from added impervious area. 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
Everyone who walks, rides or drives the corridor every day inherit whatever this module decides — performance, accessibility, cost of ownership and resilience are set here, not at the ribbon-cutting.
Section D
Learning objectives
By the end of this module you will be able to:
- 1.Analyze apply the approved Capstone I methodology to transportation design development, using this project's own conditions rather than a textbook case.
- 2.Justify document assumptions, governing standards and units for every decision, using this project's own conditions rather than a textbook case.
- 3.Interpret produce evidence an advisor can verify independently, using this project's own conditions rather than a textbook case.
- 4.Produce transportation design package at a standard the DOT design reviewer would accept without a second revision cycle.
Section E
Instructional content
Full lecture notes with figures and governing equations
The engineering content of transportation design development
Design geometry, sight distance, pavement sections and traffic operations per AASHTO/MUTCD. That single sentence hides the substance of the module: apply the approved Capstone I methodology to transportation design development, and document assumptions, governing standards and units for every decision. Both must be established from project evidence before anything downstream is credible.
In transportation engineering, this work is the input to the roadway geometry, control plan and operational analysis. Produce evidence an advisor can verify independently — which is why this page asks you to record the source of every quantity, not just its value. The design of record that drawings, quantities and cost are generated from depends on it.
- Apply the approved Capstone I methodology to transportation design development.
- Document assumptions, governing standards and units for every decision.
- Produce evidence an advisor can verify independently.
Photo 1. The engineering content of transportation design development in practice — Peak-hour demand: the flow rate that drives capacity, delay and level-of-service analysis.
Wikimedia Commons, CC BY 2.0
Decision logic: the procedure that replaces a closed-form solution
Transportation Design Development is governed by a documented procedure rather than a single expression, so the decision logic is the deliverable: what you accept, what you reject, and on what evidence. Apply the approved Capstone I methodology to transportation design development.
Write the acceptance criterion before you look at the result. Document assumptions, governing standards and units for every decision — recording the criterion afterwards lets it be shaped to fit the number you happened to get.
Photo 2. Decision logic: the procedure that replaces a closed-form solution in practice — Peak-hour demand: the flow rate that drives capacity, delay and level-of-service analysis.
Wikimedia Commons, CC BY 2.0
Constraints, adopted standards and the safety case for transportation design development
No single code section governs this module, so the constraint set comes from the approved proposal, the owner's requirements and professional practice. Write those constraints down; an unwritten constraint is not enforceable at review.
The safety case is explicit here. The failure mode is a geometric or control element that puts drivers in a conflict they cannot resolve; the people exposed are drivers, pedestrians, cyclists, transit riders and the agency that owns the facility; the control that prevents it is produce evidence an advisor can verify independently together with an independent check by someone who did not perform the work.
- Controlling criterion for this module: apply the approved Capstone I methodology to transportation design development.
- Adopted reference: confirm with the jurisdiction before you rely on it.
- Failure mode guarded: a geometric or control element that puts drivers in a conflict they cannot resolve.
- Evidence produced: Transportation design package.
Photo 3. Constraints, adopted standards and the safety case for transportation design development in practice — Peak-hour demand: the flow rate that drives capacity, delay and level-of-service analysis.
Wikimedia Commons, CC BY 2.0
Where this method stops being valid
Every method has a domain of validity. State the range of geometry, loading, material behaviour or flow regime over which your approach holds, and state what you would do instead beyond it.
For this project, the boundary you are most likely to push is produce evidence an advisor can verify independently. 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 — Peak-hour demand: the flow rate that drives capacity, delay and level-of-service analysis.
Wikimedia Commons, CC BY 2.0
Section F
Engineering workflow
Steps
- 1. Assemble the inputs this module needs — apply the approved Capstone I methodology to transportation design development; document assumptions, governing standards and units for every decision — each with a unit and a source record.
- 2. Confirm which document governs, and record who verified that it applies here.
- 3. State the assumptions and the acceptance criterion for apply the approved Capstone I methodology to transportation design development.
- 4. Execute the documented procedure, recording each judgement and the evidence behind it.
- 5. Test the result against produce evidence an advisor can verify independently.
- 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 transportation design package and submit it to the DOT design reviewer for review.
Decision points
- Is every input behind apply the approved Capstone I methodology to transportation design development traceable? If not — stop and collect the record.
- Does the result satisfy document assumptions, governing standards and units for every decision? If not — revise the work, never the criterion.
- Would the correction change the design of record that drawings, quantities and cost are generated from? If yes — raise a change-control request before proceeding.
- Have you ruled out the most common error on this module — all inputs traceable to data, code or the approved proposal?
Quality checklist
- Documented: apply the approved Capstone I methodology to transportation design development
- Documented: document assumptions, governing standards and units for every decision
- Documented: produce evidence an advisor can verify independently
- Governing document cited
- Procedure steps recorded in order with evidence
- Acceptance criterion recorded before the result
- Independent check signed and dated
- Transportation design package attached and named per the course convention
Section H
Interactive visualization
Transportation Design Development — step-through
Advance one frame at a time. Each frame adds one engineering decision to the previous state.
Step 1 of 6
Start from the confirmed inputs: geometry, materials, loads or flows, each with a source.
Section I
Applicable codes and standards
Section J
Worked examples
Full engineering solution format
Section K
Common mistakes and how to avoid them
- All inputs traceable to data, code or the approved proposal
- Units consistent and dimensionally verified
- Governing code or standard cited with clause number
- Independent check performed and initialed
- Deliverable file attached and named to convention
- Treating apply the approved Capstone I methodology to transportation design development as a given instead of establishing it from a project record.
- Producing transportation design package without showing how document assumptions, governing standards and units for every decision was satisfied.
- Recording the outcome of this module without recording the judgement and evidence that produced it.
- Missing produce evidence an advisor can verify independently, which is exactly the path to a geometric or control element that puts drivers in a conflict they cannot resolve.
- Designing to the average condition when the governing condition is the controlling one.
- Freezing a design before the constructability and access review that would have changed it.
- 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).
- Ignoring constructability: a design that cannot be built safely is not a completed design.
Section L
Industry case study
Documented failure related to transportation design development
A constructed civil works project where this module's decision was made incorrectly or skipped.
Official findings
- Published investigation identified a breakdown between analysis assumption and constructed condition.
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
- Document the assumption, then have someone else check it before it becomes construction.
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 — transportation engineering section (record the section number from your handbook edition).
Exam topics
Handbook formulas
Weak results here feed your FE Civil Academy weak-area queue for targeted practice.
Question 1 of 2
Score: 0/2In transportation design development, which item must be established BEFORE the analysis is run?
Section N
Apply it to your project — Transportation Design Development
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 — Transportation Design Development
Your firm has been retained to deliver the transportation design development 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
Transportation design package
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
Transportation design package with advisor review and dual scoring.
Assessment: Faculty rubric score and administrator rubric score on this module's submission.
Rubric: Engineering design · Target: 70% of students at or above 'meets expectations'.
Transportation design package with advisor review and dual scoring.
Assessment: Faculty rubric score and administrator rubric score on this module's submission.
Rubric: Engineering design · Target: 70% of students at or above 'meets expectations'.
Section T
References and further study
Transportation Design Development — 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.