Finite element plasticity program architecture is the software organization needed to run plasticity analyses: input parsing, element loops, material-state storage, nonlinear solution control, stress recovery, and verification output.
Source Pattern
Finite-Elements-in-Plasticity-Theory-and-Practice describes modular FORTRAN routines linked into multiple plasticity programs. The important architecture lesson is not the language; it is the separation of responsibilities:
model and material input;
element stiffness, mass, and internal force routines;
integration-point stress update and state-variable storage;
global nonlinear or transient solution control;
postprocessing for displacements, reactions, stresses, and internal forces;
benchmark input cases for regression testing.
Why It Matters
Plasticity code fails when state ownership is unclear. Element routines need access to previous and trial state, material routines need a stable state-variable contract, and the global solver needs residuals and tangents that match the accepted material update.
Solver Development Checklist
Define state variables per integration point and section point.
Separate trial, iterative, and committed material states.
Make element routines independent of specific global solver choices where possible.
Emit enough output to compare displacements, reactions, element internal forces, stresses, and plastic variables.
Keep reference input cases small enough for TDD and regression runs.
김경종