Object-oriented programming abstraction

A useful principle of object-oriented specification (and design) is that the structure of a software system should be based on a well-chosen model of the world with which it deals that approach makes the design easier to update with business changes. Each real-world object (whether physical or more abstract orders, meetings, menus) has its counterpart inside the system. A first step in building an object-oriented program from scratch is therefore to make a business model and then declare it to be the first draft of a type model of the software. The objects and their relationships are used as the type model of the system. 

All object-oriented programming languages provide a feature called access modifier that facilitates separations between the interfaces and the implementations of an object. The way to achieve this result is to define member variables of the object as private or protected and define methods that provide services to the object s client as public. Only the public elements of an object can be accessed by its clients, and these are all that its clients care to know. In Java and C, we can go even further by creating interfaces that have only method signatures. The implementations of these methods are provided by the classes that implement these interfaces. Although there is no interface in C + +, you can, however, create an abstract class by declaring one or more of the class s methods as pure virtual. Abstract class is also supported by Java and C. Interfaces and abstract classes are useful software constructs for defining abstractions in a software system. 

Abstract data types have been established in computer science for many years (2). Indeed they are at the heart of the object-oriented programming paradigm. However, their use in scientific programming has been limited -probably because, prior to FORTRAN 90, FORTRAN provided no direct... 

Abstract This contribution deals with the modeling of coupled thermal (T), hydraulic (H) and mechanical (M) processes in subsurface structures or barrier systems. We assume a system of three phases a deformable fractured porous medium fully or partially saturated with liquid and a gas which remains at atmospheric pressure. Consideration of the thermal flow problem leads to an extensively coupled problem consisting of an elliptic and parabolic-hyperbolic set of partial differential equations. The resulting initial boundary value problems are outlined. Their finite element representation and the required solving algorithms and control options for the coupled processes are implemented using object-oriented programming in the finite element code RockFlow/RockMech. 

Ada 95 introduced direct support for object-oriented programming encapsulation (as just noted), objects (entities that have state and operations), classes (abstractions of objects), inheritance, polymorphism, and dynamic binding. 

Structural part. Here, all the available operators are characterised. In addition to the primitive HBBs (see physical part), we consider two other types of operators abstract building blocks (ABBs) and predefined EXUs/ASUs. These two types can be associated with abstraction hierarchy and architectural hierarchy respectively. Abstraction hierarchy is similar to class hierarchy in the object-oriented programming sense the operators are classified in a lattice, in which the ABBs are used at several levels of abstraction to represent... 

---