Publication | Closed Access
Nonlinear Finite-Element Analysis Software Architecture Using Object Composition
858
Citations
24
References
2009
Year
Geometric ModelingFinite Element MethodNumerical AnalysisMethod EngineeringEngineeringIsogeometric AnalysisComputer EngineeringSystems EngineeringComputer-aided DesignModeling And SimulationStructural OptimizationComputational MechanicsStructural MechanicsNonlinear EquationsSolid ModelingUnstructured Mesh GenerationDesign PatternsClass Inheritance
Object composition provides a flexible finite‑element software architecture by encapsulating core algorithms in separate classes that interact through design patterns. The architecture implements interchangeable components—root‑finding, time integration, constraint handling, linear solvers, and DOF numberers—using the Strategy, Bridge, Factory, Adapter, and Iterator patterns to decouple model objects from numerical solvers. Sequence diagrams confirm that this design enables interoperable assembly and solution of nonlinear finite‑element equations, proving that object composition with design patterns is a general method for developing and refactoring such software.
Object composition offers significant advantages over class inheritance to develop a flexible software architecture for finite-element analysis. Using this approach, separate classes encapsulate fundamental finite-element algorithms and interoperate to form and solve the governing nonlinear equations. Communication between objects in the analysis composition is established using software design patterns. Root-finding algorithms, time integration methods, constraint handlers, linear equation solvers, and degree of freedom numberers are implemented as interchangeable components using the Strategy pattern. The Bridge and Factory Method patterns allow objects of the finite-element model to vary independently from objects that implement the numerical solution procedures. The Adapter and Iterator patterns permit equations to be assembled entirely through abstract interfaces that do not expose either the storage of objects in the analysis model or the computational details of the time integration method. Sequence diagrams document the interoperability of the analysis classes for solving nonlinear finite-element equations, demonstrating that object composition with design patterns provides a general approach to developing and refactoring nonlinear finite-element software.
| Year | Citations | |
|---|---|---|
Page 1
Page 1