24,428 courses · 2,504 curriculum guides Sponsored by eAgentic Software Sponsored by eAgentic Software

EEE4450: Modeling and Simulation of Semiconductor Devices

EEE4450 — EEE4450
← Course Modules
3 credit hours 45 contact hours Prerequisites: FAMU/FSU: EEE 3300. WARNING: the description names numerical techniques the prerequisite does not - finite differences, iterative solution of coupled nonlinear equations, and convergence behaviour. Students arriving without a numerical methods course should expect to learn that material here, and programming fluency (MATLAB, Python or C) is assumed rather than taught. v1.0

Course Description

EEE 4450 Modeling and Simulation of Semiconductor Devices is the course that sits between device physics and the numerical methods needed to make that physics computable. The equations governing carrier transport in a semiconductor — Poisson’s equation coupled to the electron and hole continuity equations — have closed-form solutions only for idealised one-dimensional cases. Everything else is solved numerically, and this course teaches how.

The Statewide Course Numbering System description is precise: the course “covers various numerical techniques for the modeling and simulation of semiconductor devices, such as pn-junctions, metal-oxide semiconductor contacts, metal-oxide-semiconductor field-effect-transistors, and bipolar devices. Special emphasis is on the description and simulation of electron and hole transport in semiconductor devices.”

Florida A&M University carries the course at 3 credits. The FAMU–FSU College of Engineering bulletin lists it with a prerequisite of EEE 3300 and describes it in matching terms.

What kind of course this is. This is a computational course. Students spend their time discretising differential equations, implementing iterative solvers, and diagnosing why a solution failed to converge — work that resembles a numerical methods course more than a circuits course. The reward is a genuine understanding of what a TCAD tool is doing, which is what separates an engineer who can interpret a simulation from one who can only run it.

Learning Outcomes

Required Outcomes

Optional Outcomes

Major Topics

Required Topics

Optional Topics

Resources & Tools

Career Pathways

Special Information

⚠⚠ The description names numerical methods the prerequisite does not

The prerequisite is EEE 3300 Electronics I — a devices and circuits course. But the statewide description promises “various numerical techniques,” and the course delivers on that: finite differences, iterative solution of coupled non-linear systems, sparse linear algebra, and convergence analysis.

Nothing in the prerequisite chain guarantees a student has met any of this. That gap is where students fail, and it is worth naming explicitly:

Preparation that pays: if you have not taken numerical methods, spend time before the term on finite-difference approximation of a second derivative, on Newton’s method for a system of equations, and on how a sparse matrix is stored and solved. An afternoon on each will save weeks.

⚠ Course-code variation across Florida

Device simulation is offered narrowly in Florida at undergraduate level:

SCNS equivalency does not cross course numbers. Because the subject is offered narrowly, expect this course to articulate as a technical elective rather than as a named requirement, which is normally what a student wants from an elective. Carry the syllabus, and keep the solver code — it is more persuasive evidence than a course description.

Position in the curriculum

EEE 4450 is a senior-level elective in the devices track, following Electronics I. It complements the analytical device courses — EEE 4351 Solid-State Electronic Devices — by supplying what happens when the analytical assumptions fail, and it complements EEE 4330 Microelectronics Engineering by explaining how a process change is evaluated before it is run. A student taking the analytical devices course first will find this one considerably easier, and that ordering is worth arranging where the schedule permits.

Difficulty and time commitment

This is a demanding course, and the difficulty is concentrated in an unusual place: debugging. A device simulator that does not converge gives you very little information about why — the residual simply fails to decrease — and the cause may be a scaling error, a boundary condition, a mesh that is too coarse in the depletion region, an initial guess that is too far from the solution, or a sign error in the Jacobian. Diagnosing this systematically is the skill the course teaches, and it takes time.

Plan on ten to twelve hours a week, weighted heavily toward implementation, and start assignments immediately. A solver that does not converge cannot be fixed the night before it is due, because the diagnosis is inherently iterative.

Two pieces of practical advice that materially reduce the pain: build the solver incrementally — get the equilibrium Poisson solution working before adding continuity equations, and get one dimension working before considering two — and check against analytical limits at every stage, because a solver that converges to a wrong answer is harder to detect than one that fails outright.

Articulation and transfer

SCNS records EEE 4450 as guaranteed to transfer to an institution offering the same course. One Florida institution carries the number, so read that narrowly. The course is upper-division, carries 3 credits, and has no general-education or Gordon Rule designation.

FE exam relevance

The NCEES Fundamentals of Engineering (Electrical and Computer) exam covers semiconductor materials and devices but does not test numerical simulation. The device physics reinforced here supports the Electronics topic area indirectly. This is an elective taken for its own value and for graduate preparation rather than for FE coverage.

AI Integration

Device simulation is an area where machine learning is being adopted seriously as an engineering method, which makes this section a description of current research practice as much as a caution.

Where AI is genuinely used in the discipline. Three developments are real and worth knowing about. Surrogate modelling trains a neural network on TCAD results so that design-space exploration can be done in seconds rather than hours — now standard practice in device optimisation. Physics-informed neural networks encode the semiconductor equations directly in the loss function, an active research direction for solving these systems. And machine learning is widely used for compact model parameter extraction, replacing laborious manual curve fitting. A student entering device modelling will meet all three.

⚠ One caution that belongs with them: a surrogate model is only valid within the region of parameter space it was trained on, and it will extrapolate confidently and wrongly outside it. The physics-based solver remains the ground truth, which is precisely why this course teaches you to write one.

Where a general-purpose assistant helps in coursework. Explaining why the Scharfetter–Gummel scheme is needed, in different words from the textbook; generating boilerplate for sparse matrix assembly; explaining a linear algebra error message; suggesting a systematic order in which to test a non-converging solver; and helping structure and document code, which matters more here than in most courses because the programs are long enough to become unmanageable.

⚠ Where it fails, and why the failure is this course’s own subject. The characteristic error of an AI tool asked to produce device simulation code is to generate a discretisation that is mathematically reasonable and physically unusable — most commonly, central-differencing the current continuity equation instead of using Scharfetter–Gummel exponential fitting. That specific failure is the central numerical lesson of the course. The naive discretisation looks correct, compiles, runs, and produces oscillatory unphysical carrier densities as soon as the bias exceeds a few thermal voltages. It does not error; it just quietly stops meaning anything.

Two further failures recur. Models omit or mis-handle scaling, producing systems so ill-conditioned that they will not converge — and then attribute the non-convergence to something else. And they supply physical model parameters (mobility coefficients, recombination lifetimes) without stating the material, temperature or doping range they apply to, which is the same conditions-free failure that afflicts every device-physics question.

There is also a subtler trap specific to computational work: a generated solver that converges is not thereby correct. Convergence means the iteration found a solution to the discretised system you wrote down; whether that system represents the device is a separate question. Validating against analytical limits — the depletion approximation, the ideal diode equation, charge neutrality — is the only check that distinguishes the two, and it is a step a generated solution will not include.

The engineer’s responsibility. A simulation result is a claim about how a physical device will behave, and engineers make expensive decisions on such claims. The discipline is validation: against analytical limits, against measurement, and against the physics itself. The habit worth forming here is to ask of every simulated result: what does it reduce to in a case I can solve by hand, and does it? A plot that has never been checked against a known limit is not evidence.

Academic integrity. FAMU and FSU both maintain academic honour policies covering AI-generated work. In a course whose deliverable is code you wrote, submitting generated code as your own is straightforwardly a violation, and it is also self-defeating: the assessed understanding is the discretisation and the convergence strategy, which is exactly what you skip by not writing it. Generated simulation results are data fabrication. Ask your instructor what assistance is permitted, and disclose its use where the syllabus requires it.


Generated September 9, 2026 · Updated September 9, 2026