A Layered Architecture Sustaining Model-Driven and Event-Driven Software Development
This paper presents a layered software architecture reconciling model-driven, event-driven, and object-oriented software development. In its simplest form, the architecture consists of two layers: an enterprise layer consisting of a relatively stable business model and an information system layer, containing the more volatile user functionality. The paper explains how the concept of events is used in the enterprise layer as a means to make business objects more independent of each other. This results in an event handling sublayer, allowing to define groups of events and handling consistency and transaction management aspects. This type of architecture results in information systems with a high-level modular structure, where changes are easier to perform as higher layers will not influence the inherently more stable lower layers.
KeywordsBusiness Object Business Rule Method Invocation Output Service Information System Architecture
Unable to display preview. Download preview PDF.
- 2.Maes, R., Dedene, G.: Reframing the Zachman Information System Architecture Framework, Tinbergen Institute, discussion paper TI 9–32/2 (1996)Google Scholar
- 4.Goebl, W.: Improving Productivity in Building Data-Oriented Information Systems —Why Object Frameworks are not Enough. In: Proc. of the 1998 Int. Conf. On Object- Oriented Information Systems, Paris, September 9-11. Springer, Heidelberg (1998)Google Scholar
- 5.Cook, S., Daniels, J.: Designing Object Systems: Object-Oriented Modeling with Syntropy. Prentice-Hall, Englewood Cliffs (1994)Google Scholar
- 7.Meyer, B.: Object-Oriented Software Construction, 2nd edn. Prentice Hall, Englewood Cliffs (1998)Google Scholar