In the Secant Architecture all of these services and events are available but without the need for an imposed object hierarchy. That is, no base classes are required. In general, a Business Object reflects a particular business entity, concept, or process. They are usually persistent and are part of a complex model that defines the business entity at hand. They are usually the principal objects involved in transactions.
Common table can contain all attributes from each class.
Once a base table is established for a concrete persistent class it cannot be changed in a subclass. Shared table with common elements, additional tables for subclasses. Inheritance support for aggregate types that are not first-class persistent objects. To do this requires the instance be constructed of two or more composite objects. The interface of the class would not reflect this however.