MATH 4810 Computational Modelling

School of Mathematics · TrustOpen

MATH 4810 · 3 Credits · Undergraduate Computational Modelling, Simulation, and Optimization

Build, implement, test, and defend computational models of real systems. Work through numerical methods for differential equations, Monte Carlo and discrete-event simulation, Markov chains, and linear programming with duality and sensitivity analysis — then integrate everything in a substantial simulation capstone.

Delivery Individualized study online · asynchronous Duration 18 weeks Workload 135 hours · 7–9 hrs/week Challenge Not available

Course description

From a real-world question to a defensible model

MATH 4810 develops advanced methods for constructing, implementing, analyzing, and validating computational models.

Students study numerical methods for ordinary and partial differential equations, Monte Carlo simulation, stochastic state-transition models, discrete-event simulation, linear programming, duality, and sensitivity analysis. Models are implemented in spreadsheet software and, optionally, in a scientific programming environment.

Applications are drawn from the physical sciences, social sciences, finance, medicine, operations, and business. The course emphasizes reproducible model architecture, numerical stability, uncertainty analysis, verification, validation, and communication.

Each topic is divided into conceptual analysis and numerical simulation, with Microsoft Excel used to construct and implement models. Optional Python, computer algebra, discrete-event simulation, and optimization tools are supported for students who wish to extend their work.

Who this course is for

  • Mathematics and applied mathematics students
  • Computing and data science students
  • Physical and life science students
  • Finance and business students
  • Students preparing for simulation or operations research

Prerequisites

Formal prerequisites: MATH 265, MATH 266, MATH 270, MATH 370, and MATH 376. There are no preclusions, and the course is not available for challenge credit.

Recommended preparation: single-variable calculus, linear algebra, real analysis, ordinary differential equations, probability, spreadsheet modelling, and basic optimization.

Technology requirements

Access to the learning management system, Microsoft Excel 2010 or later (or an institutionally approved equivalent), a scientific calculator, and accessible equation rendering. A Python notebook environment, computer algebra system, discrete-event simulation software, or mathematical optimization software is optional.

Learning outcomes

What you will be able to do

Upon successful completion of MATH 4810, students will be able to:

Model formulation

  • Distinguish observational, explanatory, deterministic, stochastic, static, and dynamic models.
  • Translate a real-world system into a computational model specification.
  • Design transparent spreadsheet or code-based model architectures.
  • Estimate and document model parameters.

Numerical and simulation methods

  • Analyze sources of truncation, discretization, roundoff, and sampling error.
  • Apply Euler, modified Euler, and Runge–Kutta methods to ordinary differential equations.
  • Use finite-difference methods for selected partial differential equations.
  • Assess consistency, stability, convergence, and step-size sensitivity.
  • Design Monte Carlo simulations and validate pseudorandom inputs.
  • Construct and analyze Markov-chain models.
  • Design elementary discrete-event simulations.

Optimization, validation, and communication

  • Formulate linear programming models.
  • Explain and apply the fundamental duality theorem.
  • Analyze shadow prices, reduced costs, binding constraints, and sensitivity ranges.
  • Verify model implementation and validate results.
  • Conduct sensitivity, uncertainty, and scenario analyses.
  • Compare analytical and numerical solutions.
  • Create reproducible computational workflows.
  • Communicate simulation assumptions, results, limitations, and recommendations clearly.

Recurring process

The computational modelling cycle

Every module returns to this cycle. It is the backbone of the laboratories, the assignments, and the capstone.

  1. Define the question and model purposeState what decision or understanding the model must support.
  2. Establish the system boundaryDecide what is inside the model and what is treated as external.
  3. Define variables, parameters, units, and assumptionsMake every quantity explicit and dimensionally consistent.
  4. Select the modelling approachDeterministic or stochastic, static or dynamic, analytical or numerical.
  5. Choose a numerical or simulation methodMatch the method to the structure, scale, and required accuracy.
  6. Implement the modelBuild a transparent spreadsheet or code architecture.
  7. Verify formulas, code, and model logicConfirm the implementation matches the intended specification.
  8. Test numerical stability and convergenceVary step size, grid, and replication count deliberately.
  9. Validate the model against evidence or known behaviourCompare with data, analytical solutions, or limiting cases.
  10. Conduct uncertainty and sensitivity analysisIdentify which inputs actually drive the outputs.
  11. Compare scenariosRun designed experiments rather than one-off trials.
  12. Interpret limitationsState what the model cannot tell you.
  13. Communicate findingsWrite for both technical and non-technical readers.
  14. Archive reproducible model filesLeave a trail another analyst could rerun.

Curriculum

Seven modules, fourteen units

Each unit pairs conceptual analysis with numerical simulation. Modules 1 through 6 carry a staged assignment; Module 7 supports the integrative capstone.

Assessment

Five staged assignments and an integrative capstone

Assignments build cumulatively across the modules. The capstone carries the greatest weight because it demonstrates integrated modelling competence end to end.

10%

Five staged assignments

One applied modelling assignment per module across Modules 1–5, each worth 10 percent.

45%

Simulation capstone

A substantial computational model, verified, validated, analyzed, and reported.

5%

Capstone presentation

An accessible presentation of the model, its results, and its limitations.

Assessment plan
Assessment Weight
Assignment 1: Model Architecture and Parameterization10%
Assignment 2: ODE Numerical Simulation10%
Assignment 3: PDE Finite-Difference Model10%
Assignment 4: Monte Carlo Simulation10%
Assignment 5: Markov, Discrete-Event, or Optimization Model10%
Simulation Capstone45%
Capstone Presentation5%
Total100%

Credit requirements

Students must achieve at least 50 percent overall, submit all five assignments, achieve at least 50 percent on the simulation capstone, submit functioning model files, submit the capstone presentation, and meet academic-integrity requirements.

  • Assignment 1 Computational model design and audit Details →
  • Assignment 2 ODE simulation and error analysis Details →
  • Assignment 3 Deterministic PDE model Details →
  • Assignment 4 Stochastic simulation experiment Details →
  • Assignment 5 State-transition or queueing simulation Details →

Culminating work

The simulation capstone

Students construct, verify, validate, analyze, and communicate a substantial computational model of their choosing, subject to approval.

Suggested application areas

  • Health-service queues
  • Inventory systems
  • Financial risk
  • Energy storage
  • Population or epidemic dynamics
  • Diffusion or heat transfer
  • Transportation flows
  • Supply chains
  • Reliability systems
  • Resource allocation
  • Environmental uncertainty
  • Emergency-service operations

Required deliverables

  • Project proposal
  • Problem and stakeholder statement
  • Model-purpose statement
  • Variables, parameters, units, and assumptions
  • Conceptual model diagram
  • Mathematical formulation
  • Numerical or simulation method
  • Model implementation
  • Verification evidence
  • Validation evidence
  • Numerical error analysis
  • Sensitivity and uncertainty analysis
  • Scenario experiments
  • Results and visualizations
  • Limitations and ethical considerations
  • Reproducible spreadsheet or code files
  • Technical report
  • Plain-language executive summary
  • Accessible presentation

Capstone rubric

Weighting of capstone criteria
Criterion Weight
Problem definition and conceptual model8%
Mathematical formulation12%
Method selection10%
Implementation quality15%
Verification and numerical testing12%
Validation10%
Sensitivity and uncertainty analysis10%
Results and interpretation8%
Reproducibility and documentation8%
Communication and accessibility7%
Total100%

Learning design

How each lesson is built

Every lesson follows the same structure so that theory, implementation, and judgement stay connected.

Lesson anatomy

  1. Modelling context

    Why this method exists and where it is used.

  2. Learning objectives

    What you should be able to do afterwards.

  3. Prerequisite review

    The mathematics you need before starting.

  4. Mathematical formulation

    The model or method stated precisely.

  5. Numerical or simulation method

    How the formulation becomes an algorithm.

  6. Spreadsheet or code architecture

    How the implementation is laid out.

  7. Worked implementation

    A complete, runnable example.

  8. Verification check

    Evidence that the implementation is correct.

  9. Interpretation

    What the output means in context.

  10. Stability or uncertainty discussion

    Where the result could break down.

  11. Common implementation errors

    Mistakes to watch for.

  12. Independent modelling task

    Your turn to build and test.

  13. Reflection prompt

    Consolidate what changed in your thinking.

  14. Lesson summary

    The key takeaways in brief.

Important misconceptions to address

A smaller time step is not automatically sufficient to guarantee a correct result.
Step-size reduction controls one source of error. It does not fix a wrong equation, an incorrect boundary condition, or a misspecified model.
Numerical convergence does not establish model validity.
A converged solution can be a converged solution to the wrong problem.
Verification and validation are different activities.
Verification asks whether the implementation matches the specification. Validation asks whether the model represents the real system well enough for its purpose.
Pseudorandom values are algorithmically generated.
They are deterministic sequences that pass statistical tests; reproducibility depends on controlling the seed.
More simulation replications reduce sampling error but cannot correct structural model error.
Precision is not accuracy. A biased model converges confidently to the wrong answer.
A graphical fit does not by itself establish model adequacy.
Visual agreement can coexist with systematic error, especially over short observation windows.
Discrete-event simulation requires an explicit event and clock mechanism.
Without a defined event calendar and clock-advance rule, the simulation is not a discrete-event simulation.
A steady-state Markov result may not describe short-run behaviour.
Transient dynamics can dominate over the horizon that actually matters to a decision.
Solver output does not guarantee that the model represents the intended decision problem.
An optimal solution to a mis-specified linear program is still a mis-specified answer.
Shadow prices are valid only within specified sensitivity ranges.
Beyond the allowable increase or decrease, the dual values change and the reported interpretation no longer holds.
Spreadsheet transparency does not guarantee formula correctness.
A visible formula can still reference the wrong cell, use the wrong units, or copy incorrectly down a column.
A simulation model should support decision-making without concealing uncertainty.
Reporting a single number without its uncertainty undermines the purpose of the model.

Accessibility and responsible computing

Designed to be usable, and used responsibly

Course production and student work both carry obligations around accessibility, transparency, and the ethical use of models.

Accessibility commitments

  • Semantic HTML and keyboard-accessible navigation
  • Accessible equation notation
  • Accessible spreadsheet templates
  • Text descriptions of simulation charts
  • Captions and transcripts
  • High colour contrast
  • No reliance on colour alone
  • Static alternatives to interactive dashboards
  • Screen-reader-compatible assessments
  • Downloadable model files
  • Plain-language descriptions of algorithms
  • Explicit input and output labels
  • Reproducible software instructions
  • Mobile-responsive content pages

Responsible computing topics

  • Data privacy
  • Bias in inputs and assumptions
  • Numerical uncertainty
  • Stakeholder impacts
  • Reproducibility
  • Transparent reporting
  • Responsible use of optimization
  • Responsible use of generative AI

Reproducibility standard

Model files submitted for this course must be runnable by another person. That means documented inputs, labelled outputs, stated units, recorded seeds and step sizes, and no hidden manual steps.

Questions

Frequently asked

Do I need to know how to program?

No. The course is built around spreadsheet implementation, and Microsoft Excel 2010 or later (or an institutionally approved equivalent) is the required technology. A Python notebook environment, computer algebra system, discrete-event simulation software, or optimization package is optional for students who want to extend their work.

How much mathematics background do I need?

The formal prerequisites are MATH 265, MATH 266, MATH 270, MATH 370, and MATH 376. In practice you should be comfortable with single-variable calculus, linear algebra, real analysis, ordinary differential equations, and probability.

How is the course delivered?

Individualized study online, asynchronously, over approximately 18 weeks. The estimated total workload is 135 hours, or roughly 7 to 9 hours per week.

Can I challenge the course for credit?

No. Challenge credit is not available for MATH 4810, and there are no preclusions.

What software will I actually use?

Required: the learning management system, Microsoft Excel 2010 or later (or an approved equivalent), a scientific calculator, and accessible equation rendering.

Optional: a Python notebook environment, a computer algebra system, discrete-event simulation software, and mathematical optimization software.

What is the capstone, exactly?

A substantial computational model of your own choosing, subject to approval. You define the problem, formulate the model, select and implement a method, verify and validate it, run sensitivity and uncertainty analyses, and communicate the results in a technical report, a plain-language executive summary, and an accessible presentation.

How do I pass the course?

Achieve at least 50 percent overall, submit all five assignments, achieve at least 50 percent on the capstone, submit functioning model files, deliver the capstone presentation, and meet academic-integrity requirements.

Ready to start building models that hold up?

Begin with the orientation to review course structure, technology setup, assessment expectations, and the modelling cycle that runs through every module.

👤