EGM3344 is the numerical methods course for engineers. The Statewide Course Numbering System titles it Introduction to Numerical Methods of Engineering and defines it as "methods for numerical solution of mathematical problems, with emphasis on engineering applications and on computer implementation. Curve fitting and functional approximation. Nonlinear algebraic equations. Systems of linear algebraic equations. Numerical differentiation and quadrature. Ordinary differential equations." The statewide prerequisite is engineering analysis of systems and ordinary differential equations.
⚠ Note the phrase "and on computer implementation". This is a programming course as much as a mathematics course. Students who can derive the Newton-Raphson iteration and cannot write it as working code do not pass, and that combination — knowing what the algorithm does and being able to make it run — is exactly what the course is for.
The subject is the bridge between the mathematics an engineer is taught and the mathematics an engineer meets. Closed-form solutions are the exception in practice: real structural, thermal, fluid and control problems produce equations with no analytical answer, and every piece of engineering software a graduate will use — finite element packages, circuit simulators, CFD, process simulators — is an implementation of the methods in this syllabus. ⚠ A student who finishes this course understands what those tools are doing, and more importantly understands how they fail.
Two Florida public universities carry it, and ⚠ at different credit values:
| Institution | Its title | Credits |
|---|---|---|
| University of Florida | Numerical Methods of Engineering Analysis | 3 |
| University of West Florida | Numerical Methods | 2 |
scipy.integrate.solve_ivp or MATLAB's ode45 — seeing that a production solver does adaptive stepping and error control is half the lesson.| Institution | Its title | Credits | Contact hours |
|---|---|---|---|
| University of Florida | Numerical Methods of Engineering Analysis | 3 | not published |
| University of West Florida | Numerical Methods | 2 | not published |
Both are State University System institutions, so statewide numbering guarantees transfer between them.
⚠⚠ Two credits against three, on a course whose content is as long as the statewide description makes clear. The transfer guarantee moves the credit you earned; it does not convert two credits into three. A student taking the two-credit version at the University of West Florida and transferring into a programme that budgets three is a credit short against the requirement, and an ABET-accredited engineering curriculum has no slack to absorb it — it surfaces at the graduation audit. Get it confirmed in writing before the term you need it.
⚠ The credit value also tells you something about coverage. Two credits cannot cover the statewide topic list at the same depth as three. Expect the shorter version to compress or omit the later material — partial differential equations, stiffness, boundary value problems — and read your own syllabus rather than this guide's topic list as the definitive scope.
⚠ The 45 contact hours at the top of this guide are derived for the three-credit version — the Florida convention for a 3-credit lecture course. Neither institution publishes an hour figure; the two-credit version will run around 30.
Numerical methods appears under a number of prefixes depending on which department teaches it and to whom: EGM3344 in engineering mechanics; CGN3405 as Applied Numerical Methods for Civil Engineering, which the University of Central Florida requires before structural analysis; and departmental equivalents in chemical, electrical and mechanical engineering. ⚠ They are not the same number and the statewide transfer guarantee does not run between them, so a receiving department will evaluate rather than accept automatically. Match on content and on the prerequisite, and carry your syllabus.
A junior-level course, taken after differential equations. It underpins later analysis courses and is a prerequisite in some programmes for structural analysis, heat transfer and control systems — ⚠ where its presence or absence changes what those courses can assume, most visibly in whether they reach the matrix formulation.
Numerical methods appears on the NCEES Fundamentals of Engineering examination within the mathematics content area, and the FE is the first step toward Professional Engineer licensure through the Florida Board of Professional Engineers.
Budget eight to twelve hours a week for the three-credit version. ⚠ The programming assignments are where the time goes, and they take longer than students estimate — not because the algorithms are hard but because numerical code fails quietly. A wrong sign in a Jacobian produces a method that converges to the wrong answer rather than crashing. Verify every implementation against a problem whose answer you already know before trusting it on one you do not; that discipline is the professional habit the course is really teaching.
⚠⚠ This course is an unusually direct case, because AI coding assistants will write every algorithm in the syllabus on request, and writing them is the assignment. That deserves a straight answer rather than a warning.
The honest position: a professional engineer does not implement Runge-Kutta from scratch — they call a library. The reason you are asked to write it is not that the code is needed; it is that implementing a method is how you learn what it does, where it breaks, and what its error behaves like. A student who has a model write the code has produced the artefact and skipped the learning, and the gap shows up immediately — in the examination, and later when a simulation returns a plausible wrong answer and they have no instinct for why.
Genuinely useful: explaining a derivation a second way; debugging code you wrote, which is legitimate and is what practitioners do; explaining why a method diverged; generating test cases with known analytical solutions to verify against; explaining library documentation; producing plots; and drafting report prose.
Where the tools fail, and the failures are specific to numerics:
⚠ The coincidence worth naming: this course exists to teach that a computed answer is not automatically a correct one — that every numerical result carries error, and that the engineer's job is to know how much. A confident, unverified, plausible-looking output is precisely the thing the course trains you to distrust, and that is true whether it came from MATLAB, from your own code, or from a chat window. Verify against a known solution. Check the residual. Refine the step and see whether the answer moves. Those checks take minutes and they are the entire professional standard.
Academic integrity: read your syllabus — this is one of the courses where policies are most explicit and most varied, and where the distinction between debugging your own code and generating it is usually spelled out.
Generated September 12, 2026 · Updated September 12, 2026