Complete model classes in an object-oriented database

The entire world trade is conducted with a few Container Types only. Logistic systems transport boxes fast and efficiently from one place to the other. (Or: Why do ERP Systems need thousands of classes or table formats to map business processes, if there are only 80 stable elements in the universe?)

Modeled on the global container logistic system, a business application system only represents the infrastructure for a data- or information logistics system. Different basic information patterns require a functionality, which connects data, upgrades data and provides the user with data at any time. Just like container content  does not matter, a business data model does not need to deal with information semantics. This will not have an effect until the user interface design. 

Highly abstract but - during runtime - easily upgradeable ClassiX® InstantView® RAD framework model classes guarantee for an exact business operation mapping while keeping the number of data types low (see different Business Patterns - always with the same classes).

 

Simple model structure
  • Few clearly-arranged master data types
  • Only 3 types of transactional data
  • Automatically generated monitor objects (static: OLAP, dynamic: BAM) for accounting, statistics and monitoring (aggregational data)

 

Comprehensive relations
  • Relations upgradeable by descriptive information (descriptive wrapper)
  • Overwriting referenced data possible (overwriting wrapper)
  • Any information can be conditioned (conditioned bags)
Strict object orientation
  • Upgrading conventional, basic data types by intelligent data types, such as calendar- and unit arithmetics, formulas, conditioned tables etc.
  • Business objects with polymorphic defined, abstract methods such as such as "AddAccount", "InsertIntoStructure", etc.
  • Transactional objects with polymorphic defined, abstract methods such as "Book", "Change State", etc.

 

Open upgrading
  • Many model classes implemented as upgradeable data container
  • All data fields only object references
  • Using the same classes with different names (dummy classes)