2005
DOI: 10.1016/j.finel.2004.06.003
|View full text |Cite
|
Sign up to set email alerts
|

On the implementation of object-oriented philosophy for the design of a finite element code dedicated to multibody systems

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
4
1

Citation Types

0
10
0

Year Published

2007
2007
2021
2021

Publication Types

Select...
7

Relationship

0
7

Authors

Journals

citations
Cited by 8 publications
(10 citation statements)
references
References 30 publications
0
10
0
Order By: Relevance
“…It is exemplified, in the Figure 6, for the assets and the Balance Sheet. The inheritance concept is used to define object hierarchies and abstract objects allow the writing of generic algorithms and the easy extension of the existing code and this capability of the O-O applications to interpret the same request differently depending on the object being processed is called polymorphism (Kromer et al 2005). After the definition of the scenarios and the identification of the classes, attributes, operations and its relationships, it was obtained the architecture requested by the O-O approach.…”
Section: From the Financial Reporting To An Object-oriented Architecturementioning
confidence: 99%
“…It is exemplified, in the Figure 6, for the assets and the Balance Sheet. The inheritance concept is used to define object hierarchies and abstract objects allow the writing of generic algorithms and the easy extension of the existing code and this capability of the O-O applications to interpret the same request differently depending on the object being processed is called polymorphism (Kromer et al 2005). After the definition of the scenarios and the identification of the classes, attributes, operations and its relationships, it was obtained the architecture requested by the O-O approach.…”
Section: From the Financial Reporting To An Object-oriented Architecturementioning
confidence: 99%
“…The lack of flexibility is magnified with increase in the number of subroutines. This lack of flexibility gives rise to the following shortcomings [1,2]:…”
Section: Introductionmentioning
confidence: 99%
“…The philosophy behind the object-oriented programming (OOP) is based on the fact that the subroutines can be associated with data structures they operate on [1]. This self-contained entity is called class, and objects are instances of a class [3].…”
Section: Introductionmentioning
confidence: 99%
“…Advantages of the OOP are demonstrated for two different types of partial differential equations. Kromera et al [24] describe a design implementation of a FEM multibody flexible mechanisms code using object-oriented architecture. An OOP class systems for finite element modeling and analysis was suggested by Mackie [30].…”
Section: Introductionmentioning
confidence: 99%