Assessment
Assignment briefs
Full details for each of the five applied assignments, including purpose, task, deliverables, rubric, and submission.
§ Overview
The five assignments are staged across the first six modules of the course. Each is worth 10 percent of the final grade. Together they carry 50 percent, with the remaining 50 percent allocated to the integrative capstone (45%) and its presentation (5%).
Each assignment consolidates one module's skills and prepares you for the capstone by exercising a subset of the fourteen-step modelling lifecycle. The pattern is the same in each: define the question, build the model, produce evidence, report the results. What changes is the class of model and the class of evidence.
Assignment 1
Model architecture and parameterization. Module 1.
Assignment 2
ODE numerical simulation and error analysis. Module 2.
Assignment 3
Finite-difference PDE model. Module 3.
Assignment 4
Monte Carlo simulation. Module 4.
Assignment 5
Markov, discrete-event, or optimization model. Module 5 or 6.
The staged pattern
Assignments 1 through 4 each address one module and one class of model. Assignment 5 offers a choice between the two modelling families of Modules 5 and 6. The capstone draws on all of them.
A1 Assignment 1 · Model Architecture and Parameterization
Weight
Of the final course grade.
Module
Module 1 · Computational Modelling Foundations.
Time
Approximately eight hours.
Purpose
Assignment 1 consolidates the skills of Module 1: model classification, three-layer spreadsheet architecture, parameter estimation, and the distinction between verification, validation, and reproducibility. It also introduces the assignment format used throughout the course — a model file, a written report, and a reproducibility package — that the later assignments extend.
Task
- Choose a small system and write a one-paragraph purpose statement. State the decision the model supports.
- Classify the model along the three axes: observational or explanatory, deterministic or stochastic, static or dynamic. Justify each choice.
- Write the model specification. System boundary, variables, parameters, units, assumptions, and claim-support scope.
- Build the three-layer spreadsheet. Inputs, calculations, and outputs in clearly separated regions with a documentation sheet.
- Estimate one parameter from data or from reasoned assumptions. Report the estimate with an uncertainty.
- Verify the implementation using at least three tests from Unit 1.2.
- Validate against at least one held-out observation or known behaviour. State the disconfirming evidence in advance.
- Assemble the reproducibility package. Model file, data, readme, and documentation.
Suggested scenarios
Cooling of a beverage
Newton's law of cooling. Estimate the cooling rate. Verify against the analytical solution.
Compound interest projection
Model a savings account. Estimate the effective return. Validate against actual balances.
Population growth
Exponential or logistic growth. Estimate the rate. Validate one period forward.
Spread of a rumour
Diffusion of information in a closed group. Verify conservation of group size.
Deliverables
| Deliverable | Weight | What it should contain |
|---|---|---|
| Model specification | 20% | Purpose, boundary, classification, variables, parameters, units, assumptions, claim-support scope. |
| Spreadsheet model | 30% | Three-layer architecture, separated inputs, calculations, and outputs. Documentation sheet. |
| Parameter estimation report | 15% | Estimation method, data source, point estimate with uncertainty, residual check. |
| Verification and validation report | 20% | At least three verification tests. One validation exercise with pre-stated criteria. |
| Reproducibility package | 15% | Model file, data, readme. Tested by an independent rerun. |
| Total | 100% |
Pitfalls to avoid
- Reporting a parameter estimate with no uncertainty.
- Verification tests that would pass for any model.
- Validating on the data used to calibrate.
- Hard-coded constants buried inside formulas.
A2 Assignment 2 · ODE Simulation and Error Analysis
Weight
Of the final course grade.
Module
Module 2 · Numerical Methods for ODEs.
Time
Approximately ten hours.
Purpose
Assignment 2 consolidates the numerical ODE methods of Module 2. It asks you to implement a small library of one-step solvers, demonstrate their convergence orders numerically, apply them to a nonlinear model without a closed-form solution, and diagnose a stiff case.
Task
-
Implement four solvers. Euler, modified Euler,
midpoint, and fourth-order Runge–Kutta, each as a reusable
function of
(t, y, f, h). - Verify against an analytical solution. Choose a problem with a known closed-form solution. Compare each method's output against the reference at a moderate step size.
- Conduct a convergence study. Run each method at four step sizes and estimate the observed order from the ratios of successive errors. Produce a log-log plot.
- Apply to a nonlinear model. Simulate a system with no closed-form solution — a pendulum, a predator–prey system, or an epidemic. Estimate the error by step doubling.
- Diagnose a stiff case. Construct or choose a stiff initial-value problem. Demonstrate the stability limit of an explicit method and discuss the practical consequences.
Suggested models
Nonlinear pendulum
No closed form at large amplitude. Suitable for the step-doubling error estimate.
Lotka–Volterra
Predator–prey system with a conserved invariant. Useful for a conservation check.
Damped oscillator
Closed-form solution available. Useful as a verification reference.
SIR epidemic
Conserves total population. Combines a conservation check with a nonlinear application.
Deliverables
| Deliverable | Weight | What it should contain |
|---|---|---|
| Solver implementations | 20% | Four methods correct, documented, and reusable for a general first-order system. |
| Analytical verification | 15% | Comparison against a closed-form solution, with an error table. |
| Convergence study | 25% | Observed order for each method at four step sizes. Log-log plot. Comparison to theory. |
| Nonlinear application | 20% | Simulation with step-doubling error estimate and a claim-support statement. |
| Stiffness diagnosis | 20% | Demonstration of the stability limit. Practical consequences discussed. |
| Total | 100% |
Pitfalls to avoid
- Using
k₁in thek₃stage of RK4. - Estimating order from only two step sizes.
- Comparing observed order to a single ratio rather than the slope of a log-log plot.
- Extrapolating a stable step size into the stiff regime.
A3 Assignment 3 · Deterministic PDE Model
Weight
Of the final course grade.
Module
Module 3 · Numerical PDE Models.
Time
Approximately ten hours.
Purpose
Assignment 3 consolidates the finite-difference methods of Module 3. It asks you to construct a grid, implement the FTCS scheme for the heat equation, verify against an analytical solution, demonstrate the CFL stability restriction, and report the results with full documentation.
Task
- Choose a PDE problem. State the PDE, the domain, the initial condition, and the boundary conditions.
-
Design the grid. Choose
Δx,Δt, and the diffusion numberr. Compute the stability margin. - Implement the FTCS scheme. Three-layer spreadsheet or code. Document the boundary handling explicitly.
- Verify against the analytical solution for a case where one exists. Compute the error at several times.
- Conduct a convergence study. Refine the grid at three levels. Confirm the observed order matches the theory.
-
Demonstrate stability. Run at
r = 0.4andr = 0.6. Plot and interpret the difference. - Write the report. Include the claim-support statement and the limitations.
Suggested problems
Heat equation, sine initial condition
Analytical solution available. Simplest verification case.
Rod with one insulated end
Homogeneous Neumann boundary at one end. Requires numerical BC handling.
Diffusion with a Gaussian initial condition
Tests the grid's ability to resolve a narrow feature.
Wave equation with reflecting ends
Different stability condition from the heat equation.
Deliverables
| Deliverable | Weight | What it should contain |
|---|---|---|
| Problem specification | 10% | PDE, domain, initial condition, boundary conditions, physical interpretation. |
| Grid and stencil design | 15% | Grid dimensions, spacing, diffusion number, chosen step size, justification. |
| FTCS implementation | 20% | Working model with the update rule and boundary handling documented. |
| Verification and convergence | 25% | Comparison against analytical solution. Observed order at three refinements. |
| Stability demonstration | 15% | Numerical evidence of the CFL condition. Instability at r > 0.5 shown. |
| Technical report | 15% | Specification, implementation, verification, stability, limitations. |
| Total | 100% |
Pitfalls to avoid
- Off-by-one in grid dimensions. A domain divided into
Nintervals hasN+1points. - Applying the interior stencil at boundary points.
- Assuming stability without checking
r. - Claiming convergence without matching the theoretical order.
A4 Assignment 4 · Stochastic Simulation Experiment
Weight
Of the final course grade.
Module
Module 4 · Monte Carlo and Stochastic Simulation.
Time
Approximately ten hours.
Purpose
Assignment 4 consolidates Module 4. It asks you to design and run a Monte Carlo experiment, quantify sampling error, and apply a variance-reduction technique. It is the first assignment in which the answer is a distribution rather than a single number, and it emphasises reporting uncertainty alongside the estimate.
Task
-
Choose a quantity of interest and express it as
an expectation
E[g(X)]. Justify the choice ofg. - Implement the naive Monte Carlo estimator. Generate samples with a recorded seed. Report the estimate, the standard error, and a 95% confidence interval.
-
Run a convergence study. Compute the standard
error at four sample sizes. Produce a log-log plot with slope
near
−1/2. - Diagnose convergence with a running-mean plot.
- Apply one variance-reduction technique. Antithetic variates, control variates, or importance sampling. Report the variance-reduction factor.
- Compare the estimates and discuss the tradeoff between the naive and the reduced estimator.
Suggested problems
Estimate an integral
e.g. ∫₀¹ e^(−x²) dx. Analytical benchmark available.
Estimate a tail probability
P(Z > 3). Naive sampling rarely hits the tail; importance sampling helps.
Estimate π by simulation
Hit-or-miss in the unit square. Simple and amenable to antithetic variates.
Value at Risk
95% VaR of a two-asset portfolio. A risk-management application.
Deliverables
| Deliverable | Weight | What it should contain |
|---|---|---|
| Estimator design | 15% | Quantity as an expectation. Choice of g. Justification. |
| Naive implementation | 20% | Estimate, standard error, 95% confidence interval. Recorded seed. |
| Convergence study | 20% | SE at four sample sizes. Log-log plot with slope near −1/2. |
| Variance reduction | 25% | One technique applied. Variance-reduction factor reported. Comparison with naive. |
| Error discussion | 10% | Sampling error vs. structural error clearly distinguished. |
| Technical report | 10% | Design, results, variance reduction, limitations. |
| Total | 100% |
Pitfalls to avoid
- Reporting a point estimate without a confidence interval.
- Applying antithetic variates to a non-monotone function.
- Confusing the
1/√Nrate with a claim about accuracy. - Choosing a poor proposal for importance sampling.
- Forgetting to record the seed.
A5 Assignment 5 · Markov, Discrete-Event, or Optimization Model
Weight
Of the final course grade.
Module
Choose one track.
Time
Approximately twelve hours.
Purpose
Assignment 5 offers a choice between two modelling families. You may build either:
- Track A — Markov or discrete-event model (Module 5). A state-transition model or a queueing simulation, with full output analysis.
- Track B — Linear program with duality and sensitivity (Module 6). An optimization model with dual analysis and a sensitivity report.
The choice is yours. Neither track is easier or harder; they exercise different skills. Choose the track that best fits your interests and your capstone direction.
Track A — Markov or discrete-event model
Choose one of the following sub-tasks:
- Markov chain. Specify a Markov chain with 3–4 states, compute the stationary distribution, simulate the chain, and compare the empirical frequencies against the theoretical distribution.
- Discrete-event simulation. Build a discrete-event queueing simulation with an event calendar. Apply warm-up removal, run independent replications, and report performance measures with confidence intervals.
Track B — Linear program with duality and sensitivity
Formulate and solve a linear program of moderate size. Construct its dual, verify strong duality, interpret the shadow prices in decision-relevant terms, and produce a sensitivity report with ranges and at least one scenario analysis that exceeds the sensitivity range.
Deliverables
Track A
| Deliverable | Weight |
|---|---|
| System specification (four-concept vocabulary or Markov specification) | 15% |
| Model implementation (event calendar or transition matrix + simulation) | 25% |
| Verification (conservation, analytical comparison, or theory) | 15% |
| Output analysis (warm-up, replication, or empirical frequencies) | 20% |
| Results with confidence intervals and interpretation | 15% |
| Technical report | 10% |
| Total | 100% |
Track B
| Deliverable | Weight |
|---|---|
| LP formulation (decision variables, objective, constraints, units) | 15% |
| Spreadsheet model and solution (with feasibility verification) | 20% |
| Dual construction and shadow price interpretation | 20% |
| Sensitivity report (ranges, 100 percent rule, scenario analysis) | 25% |
| Recommendation with claim-support statement | 10% |
| Technical report | 10% |
| Total | 100% |
Choosing your track
If your capstone is likely to involve simulation, choose Track A. If it is likely to involve optimization, choose Track B. Both are fully assessed and neither is weighted more heavily than the other.
Pitfalls to avoid
- Scheduling events in the past (DES).
- Not removing warm-up (DES).
- Using the same seed for all replications (DES).
- Reversed inequality directions (LP).
- Reporting shadow prices without their sensitivity ranges (LP).
- Extrapolating shadow prices beyond their range (LP).
§ Common format requirements
The following requirements apply to every assignment. Failure to meet them may cost marks even when the model itself is correct.
| Requirement | Detail |
|---|---|
| Submission format | Single ZIP archive named MATH4810-aN-studentID.zip. |
| Archive contents | The model file, the data used, the written report (PDF), and the documentation required by the brief. |
| Report format | PDF. Typed, with headings and captions for all figures and tables. |
| Report length | Typical: 4–8 pages plus figures and appendices. Assignment 5 may be slightly longer. |
| Model files | Submitted in their native format (XLSX, PY, IPYNB). Must run and reproduce the reported results. |
| Seeds | Any stochastic assignment must record the random seed used. |
| Units | Every quantity must have units stated. Tables of variables and parameters must include a units column. |
| Citation style | IEEE style. Every cited source must be verified. |
| AI disclosure | If any AI tool was used, disclose it in an appendix (see below). |
§ Deadlines and penalties
| Assignment | Module | Suggested week |
|---|---|---|
| Assignment 1 | Module 1 | Week 2 |
| Assignment 2 | Module 2 | Week 4 |
| Assignment 3 | Module 3 | Week 6 |
| Assignment 4 | Module 4 | Week 9 |
| Assignment 5 | Module 5 or 6 | Week 11 or 13 |
Deadlines are confirmed in the LMS. Students should treat the suggested weeks as a planning aid and confirm the exact dates in the course schedule.
Late submission policy
Late assignments are subject to a 5 percent penalty per day, to a maximum of 25 percent. Extensions must be requested from the course tutor before the deadline. Requests made after the deadline are considered only in exceptional circumstances.
§ Integrity and AI disclosure
Every assignment is subject to the course's academic-integrity and responsible-AI-use policies. The two most important requirements for assignments are:
- The work you submit must be your own in a meaningful sense. If you cannot explain the model, reproduce the results, or justify the choices, the work is not yours.
- Any use of AI must be disclosed. Include a short appendix in every assignment stating whether an AI tool was used, which tool, and what it was used for.
The following are permitted with disclosure:
- Asking an AI tool to explain a concept or provide an example.
- Using an AI tool to check grammar or suggest rephrasing.
- Using an AI tool to help debug code you have written.
The following are not permitted:
- Submitting work produced primarily by an AI tool.
- Citing sources you have not verified.
- Submitting model files you cannot explain.
- Undisclosed use of AI.
An honest-use test
Before submitting, ask: could I reproduce this work without the AI tool, and could I explain it to a classmate? If either answer is no, the work is not yours in the sense the course requires.
§ Common pitfalls across all assignments
Watch for these
- Reporting a point estimate without uncertainty. Every parameter estimate and every stochastic result requires an uncertainty statement.
- Verification tests that would pass for any model. A test is only useful if it can fail.
- Validation on calibration data. Validation requires held-out evidence.
- Acceptance criteria set after seeing the result. State the criteria in advance, in writing, before running the test.
- Hard-coded constants in formulas. Every parameter lives in the input layer.
- Units missing or inconsistent. Every coefficient and every output has units.
- Model files that do not run. Test the submission by opening the file from the ZIP and running it.
- Seeds not recorded. A stochastic model without a recorded seed is not reproducible.
- Claims that exceed the evidence. The claim-support statement should follow from the verification and validation evidence, not precede it.
- No discussion of limitations. Every assignment requires you to state what the model does not do.
The standard to aim for
Each assignment should be a small example of the modelling practice the course teaches: a clearly stated question, a transparently built model, verification and validation evidence that another analyst could review, and an honest statement of what the model says and what it does not.