Sources of objects

An object-oriented design is one in which each of the major modules corresponds to an entity either in the user's world or in an implementation of a solution to the user's problem. In seismic processing the program main entities are the data. These objects correspond to data stores. Many types of data may be needed such as Plane, Trace, Cube. Seismic operations are frequently represented in data flow diagrams. Each fragment consists of one process together with the input data, output data and control parameters. Frequently control parameters may become object candidate. For example the dimension of the data set is an object containing axes definition. Furthermore the splitting between the object handling data manipulations and the object handling data coordinates simplifies the interfaces to the operation of the objects. Some of the data flows may also become candidate objects. For example, reading or writting the file and the header file may be the role of input and output objects. In the same way, the conversion from float to byte is a such complex function that an object called ByteConverter is needed. Furthermore this relationship object between a float data set and a byte data set makes it easy to use each of the objects separately. If the relationship had been implemented with internal operations extra functionalities and internal private data would have been necessary.