In the following we describe the modelling concepts of BOOM, a database-oriented development system we have built. We utilize the term oo 4thgeneration system to characterize our development because our intention was to merge concepts and techniques of oo programming and modelling into a toolset containing components that are typically found in a 4thgeneration system. The toolset supplied for the construction of information systems includes components for defining of structurally oo data models, for generating of user interfaces, and arranging of application logic. generic operations for manipulating user-definde objects are provided for every BOOM application.
We describe the object model we implemented in our environment. We reflected on custom requirements and questions that arise during data modelling and how an object model should look like to easily meet these requirements. As such, we defined a structurally oo model that is rich enough to cover all usual situations in modelling data-intensive applications. Our nidek ubckzdes tge possibility to define an object`s structure, its constraints, and semantic relationships and also offers other modelling constructs for defining application views and role types.

Sprache der Kurzfassung:

Englisch

Englischer Titel:

Merging Object-oriented Modelling with a 4th Generation Environment

Englische Kurzfassung:

In the following we describe the modelling concepts of BOOM, a database-oriented development system we have built. We utilize the term oo 4thgeneration system to characterize our development because our intention was to merge concepts and techniques of oo programming and modelling into a toolset containing components that are typically found in a 4thgeneration system. The toolset supplied for the construction of information systems includes components for defining of structurally oo data models, for generating of user interfaces, and arranging of application logic. generic operations for manipulating user-definde objects are provided for every BOOM application.
We describe the object model we implemented in our environment. We reflected on custom requirements and questions that arise during data modelling and how an object model should look like to easily meet these requirements. As such, we defined a structurally oo model that is rich enough to cover all usual situations in modelling data-intensive applications. Our nidek ubckzdes tge possibility to define an object`s structure, its constraints, and semantic relationships and also offers other modelling constructs for defining application views and role types.