Using design patterns in object-oriented finite element programming

Saved in:
Bibliographic Details
Title: Using design patterns in object-oriented finite element programming
Authors: Heng, B.C.P.1, Mackie, R.I. r.i.mackie@dundee.ac.uk
Source: Computers & Structures. Aug2009, Vol. 87 Issue 15/16, p952-961. 10p.
Subjects: Object-oriented programming, Finite element method data processing, Pattern recognition systems, User interfaces, Decomposition method, Modular programming
Abstract: Abstract: This paper proposes the use of design patterns to capture best practices in object-oriented finite element programming. Five basic design patterns are presented. In Model-Analysis separation, analysis-related classes are separated from those related to finite element modelling. Model-UI separation separates responsibilities related to the user interface from model classes. Modular Element uses object composition to reduce duplication in element type classes while avoiding the problems associated with class inheritance. Composite Element lets clients handle substructures and elements uniformly. Decomposing the analysis subsystem as in Modular Analyzer increases reuse and flexibility. Alternative solutions to each pattern are also reviewed. [Copyright &y& Elsevier]
Copyright of Computers & Structures is the property of Pergamon Press - An Imprint of Elsevier Science and its content may not be copied or emailed to multiple sites without the copyright holder's express written permission. Additionally, content may not be used with any artificial intelligence tools or machine learning technologies. However, users may print, download, or email articles for individual use. This abstract may be abridged. No warranty is given about the accuracy of the copy. Users should refer to the original published version of the material for the full abstract. (Copyright applies to all Abstracts.)
Database: Engineering Source
Description
Abstract:Abstract: This paper proposes the use of design patterns to capture best practices in object-oriented finite element programming. Five basic design patterns are presented. In Model-Analysis separation, analysis-related classes are separated from those related to finite element modelling. Model-UI separation separates responsibilities related to the user interface from model classes. Modular Element uses object composition to reduce duplication in element type classes while avoiding the problems associated with class inheritance. Composite Element lets clients handle substructures and elements uniformly. Decomposing the analysis subsystem as in Modular Analyzer increases reuse and flexibility. Alternative solutions to each pattern are also reviewed. [Copyright &y& Elsevier]
ISSN:00457949
DOI:10.1016/j.compstruc.2008.04.016