Water Resources Overview
Establish the scope, design storm basis, and regulatory framework governing the water resources chapter.
Section progress
0% of the workflow complete
Water Resources · Watershed hydrology, stormwater, channels, culverts, networks and hydraulic structures.
Deliverable: Water resources design basis memo with design storm frequencies and regulatory framework.
Minimum tables, figures and equations for Water Resources Overview
Tables — at least 7
- 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 — inlet, pipe, culvert and outlet sizing with slope, capacity and headwater depth
- 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
- Table — pre- versus post-development peak flows by design storm
Figures — at least 5
- 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
- Figure — hydraulic grade line and energy grade line profile
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 — outlet scour velocity and riprap sizing check
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 Water Resources Overview lecture and the worked example so you know what "Water resources design basis memo with design storm frequencies and regulatory framework." 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.
Hydraulic Design Office — what this workspace teaches
Watershed hydrology, stormwater, channels, culverts, networks and hydraulic structures.
- Watershed delineation, land use, curve number and imperviousness
- Rainfall: IDF curves, design storms, return periods
- Rational Method and NRCS/SCS runoff methods with validity limits
- Hydrograph development and flood routing (HEC-HMS concepts)
- Open channel flow: Manning's equation, normal and critical depth, froude number
- Culvert hydraulics: inlet vs. outlet control, headwater, performance curves
- Storm sewer network design and hydraulic grade line
- Detention basin sizing, stage-storage-discharge and outlet structures
- Weirs, orifices and energy dissipation structures
- Stormwater BMPs, water quality volume and EPA guidance
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.
Water Resources Overview
Establish the scope, design storm basis, and regulatory framework governing the water resources chapter.
Section B
Engineering story
A real project situation that frames this module
Week 4: water resources overview is the item standing between the team and a reviewable hydrologic and hydraulic model with the sized conveyance. Establish the scope, design storm basis, and regulatory framework governing the water resources chapter. Review stalls on a single line: the team cannot show the record behind drainage design scope.
Using a single design storm frequency for both minor and major systems. Because regulatory framework, 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.
Downstream property owners, emergency responders and the utility carry the consequence. On this module specifically, the exposure runs through design storm frequency selection by facility type (2-yr, 10-yr, 25-yr, 100-yr), and the cost of correction rises every week the hydrologic and hydraulic model with the sized conveyance moves closer to issue.
Decisions the engineer must make
- What record establishes drainage design scope, and is that record in the project data inventory?
- Does EPA NPDES/SWMM (Current), MS4 Permit, govern here — and is that the edition adopted by the jurisdiction?
- What is the acceptance criterion for regulatory framework, 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 hydrologic and hydraulic model with the sized conveyance or raise a change request against the locked baseline?
Photo 1. Pump station: where system head curve, pump curve and operating point meet real hardware.
Capstone Studio instructional photograph
Section C
Why this matters
Professional
A licensed engineer defending water resources overview cites EPA NPDES/SWMM (Current), MS4 Permit, and shows the record behind each input. Your water resources design basis memo with design storm frequencies and regulatory framework. is reviewed the same way — traceability is assessed before arithmetic.
Technical
Drainage design scope controls the numbers this module hands forward. Regulatory framework determines whether those numbers remain valid once conditions change.
Safety
The failure mode this module guards against is a conveyance or storage element overtopped by the design event. It reaches people through coordination with transportation (roadway drainage) and geotechnical (infiltration) chapters, 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 drainage design scope; a late correction here is paid for as a change order, not a redline.
Environmental
Environmentally, this module fixes receiving-water quality, channel erosion and altered baseflow. 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
Households and businesses in the floodplain the design is meant to protect 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.Interpret drainage design scope, using this project's own conditions rather than a textbook case.
- 2.Apply regulatory framework, using this project's own conditions rather than a textbook case.
- 3.Compare design storm frequency selection by facility type (2-yr, 10-yr, 25-yr, 100-yr), using this project's own conditions rather than a textbook case.
- 4.Analyze level of protection concept and residual risk beyond the design storm, using this project's own conditions rather than a textbook case.
- 5.Apply EPA NPDES/SWMM (Current), MS4 Permit, and cite the section that governs your acceptance decision.
- 6.Reproduce the worked example for a collector roadway inlet system uses a 10-yr design storm while the overall floodplain must be checked against… and defend the interpretation of the result.
- 7.Produce water resources design basis memo with design storm frequencies and regulatory framework. at a standard the floodplain administrator would accept without a second revision cycle.
Section E
Instructional content
Full lecture notes with figures and governing equations
Reading water resources overview as a practising engineer
Establish the scope, design storm basis, and regulatory framework governing the water resources chapter. That single sentence hides the substance of the module: drainage design scope, and regulatory framework. Both must be established from project evidence before anything downstream is credible.
In water resources engineering, this work is the input to the hydrologic and hydraulic model with the sized conveyance. Design storm frequency selection by facility type (2-yr, 10-yr, 25-yr, 100-yr) — 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.
- Drainage design scope: minor system (pipes/inlets) vs. major system (overland flow paths)
- Regulatory framework: local drainage criteria manual, NPDES MS4 permit, FEMA floodplain requirements
- Design storm frequency selection by facility type (2-yr, 10-yr, 25-yr, 100-yr)
- Level of protection concept and residual risk beyond the design storm
- Coordination with transportation (roadway drainage) and geotechnical (infiltration) chapters
Photo 1. Reading water resources overview as a practising engineer in practice — Inlet capture during rainfall: gutter spread and inlet capacity decide whether the lane floods.
Capstone Studio instructional photograph
Decision logic: the procedure that replaces a closed-form solution
Water Resources Overview 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. Drainage design scope.
Write the acceptance criterion before you look at the result. Regulatory framework — 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 — Inlet capture during rainfall: gutter spread and inlet capacity decide whether the lane floods.
Capstone Studio instructional photograph
Constraints, adopted standards and the safety case for water resources overview
EPA NPDES/SWMM (Current), MS4 Permit, governs this module: Municipal separate storm sewer system requirements FEMA (Current), Flood Insurance Study Guidelines, adds the second constraint: Floodplain mapping standards
The safety case is explicit here. The failure mode is a conveyance or storage element overtopped by the design event; the people exposed are downstream property owners, emergency responders and the utility; the control that prevents it is coordination with transportation (roadway drainage) and geotechnical (infiltration) chapters together with an independent check by someone who did not perform the work.
- Controlling criterion for this module: drainage design scope.
- Adopted reference: EPA NPDES/SWMM (Current) — cite MS4 Permit by number.
- Failure mode guarded: a conveyance or storage element overtopped by the design event.
- Evidence produced: Water resources design basis memo with design storm frequencies and regulatory framework..
Photo 3. Constraints, adopted standards and the safety case for water resources overview in practice — Inlet capture during rainfall: gutter spread and inlet capacity decide whether the lane floods.
Capstone Studio instructional photograph
Where this method stops being valid
The worked example — a collector roadway inlet system uses a 10-yr design storm while the overall floodplain must be checked against the 100-yr… — holds only while its assumptions hold. Selecting only one design storm frequency for the whole project would either under-protect against rare floods or over-build the everyday drainage system. 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 coordination with transportation (roadway drainage) and geotechnical (infiltration) chapters. 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 — Inlet capture during rainfall: gutter spread and inlet capacity decide whether the lane floods.
Capstone Studio instructional photograph
Section F
Engineering workflow
Steps
- 1. Assemble the inputs this module needs — drainage design scope; regulatory framework — each with a unit and a source record.
- 2. Confirm EPA NPDES/SWMM (Current) is the adopted edition and locate MS4 Permit.
- 3. State the assumptions and the acceptance criterion for drainage design scope.
- 4. Execute the documented procedure, recording each judgement and the evidence behind it.
- 5. Test the result against design storm frequency selection by facility type (2-yr, 10-yr, 25-yr, 100-yr).
- 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 water resources design basis memo with design storm frequencies and regulatory framework. and submit it to the floodplain administrator for review.
Decision points
- Is every input behind drainage design scope traceable? If not — stop and collect the record.
- Does the result satisfy regulatory framework? 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 — using a single design storm frequency for both minor and major systems?
Quality checklist
- Documented: drainage design scope
- Documented: regulatory framework
- Documented: design storm frequency selection by facility type (2-yr, 10-yr, 25-yr, 100-yr)
- EPA NPDES/SWMM MS4 Permit cited by section number
- Procedure steps recorded in order with evidence
- Acceptance criterion recorded before the result
- Independent check signed and dated
- Water resources design basis memo with design storm frequencies and regulatory framework. attached and named per the course convention
Section H
Interactive visualization
Water Resources Overview — step-through
Advance one frame at a time. Each frame adds one engineering decision to the previous state.
Step 1 of 6
Confirm project drainage area limits
Section I
Applicable codes and standards
EPA NPDES/SWMM
Current · MS4 Permit
Adopted design/analysis reference governing this module.
Relevance: Municipal separate storm sewer system requirements
Reference the section number and edition in your calculation package. Do not reproduce code text.
FEMA
Current · Flood Insurance Study Guidelines
Adopted design/analysis reference governing this module.
Relevance: Floodplain mapping standards
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
- Using a single design storm frequency for both minor and major systems
- Failing to confirm the local drainage criteria manual overrides a national default
- Starting hydrology work before confirming which flood maps govern
- Treating drainage design scope as a given instead of establishing it from a project record.
- Producing water resources design basis memo with design storm frequencies and regulatory framework. without showing how regulatory framework was satisfied.
- Recording the outcome of this module without recording the judgement and evidence that produced it.
- Missing coordination with transportation (roadway drainage) and geotechnical (infiltration) chapters, which is exactly the path to a conveyance or storage element overtopped by the design event.
- 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.
- Referencing figures, tables, or sources that never appear in the reference list.
- Carrying an assumption forward after the governing condition changed, without re-checking the result.
- Reporting numbers without units, or mixing US customary and SI inside a single calculation chain.
Section L
Industry case study
Documented failure related to water resources overview
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 — water resources 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 water resources overview, which item must be established BEFORE the analysis is run?
Section N
Apply it to your project — Water Resources Overview
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 — Water Resources Overview
Your firm has been retained to deliver the water resources overview 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, SHP
No files uploaded yet.
Section R
Deliverable and advisor review
Water resources design basis memo with design storm frequencies and regulatory framework.
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
Water resources design basis memo with design storm frequencies and regulatory framework. 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'.
Water resources design basis memo with design storm frequencies and regulatory framework. 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
EPA NPDES/SWMM (Current)
Adopted reference — cite section numbers, do not reproduce text.
FEMA (Current)
Adopted reference — cite section numbers, do not reproduce text.
Water Resources Overview — 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.