Frank G. Goethals

Learn More
Enterprises are living things. They constantly need to be (re-)architected in order to achieve the necessary agility, alignment and integration. This paper gives a high-level overview of how companies can go about doing 'enterprise architecture' in the context of both the classic (isolated) enterprise and the Extended Enterprise. By discussing the goals(More)
In this paper we argue that there exist two basic forms of business-to-business integration (B2Bi), namely, extended enterprise integration and market B2Bi. The paper at hand clarifies the meaning of both concepts, shows that the difference between both is fundamental, and discusses the consequences of the difference in the realm of Web services(More)
In realizing Business-to-Business integration, much communication among persons with different backgrounds is needed. We affirm that Enterprise Architecture Descriptions are an important part of the necessary communication in information systems development and maintenance. This article is about categorizing the models that describe Business-to-Business(More)
Today many companies rely on third party applications and application services for (part of) their information systems. When applications from different parties are used together, an integration problem arises. Similarly, cross-organisational application integration requires the coordination of distributed processing across several autonomous applications.(More)
This paper advocates an approach to web service design and interaction that is based on web services simultaneously participating in shared business events. In contrast to one-to-one method invocations, such events are broadcast in parallel to all web services that participate in it. Moreover, the transactional business events are distinguished from(More)
Business-to-Business integration (B2Bi) is considered to be not merely an I Tissue , but also a business problem. This paper draws attention to the two communication gaps companies within an Extended Enterprise are confronted with when integrating their systems. To overcome these communication problems we propose the use of Enterprise Architecture(More)
This paper presents a layered software architecture reconciling model-driven, event-driven, and object-oriented software development. In its simplest from, 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(More)
This paper proposes the concept of business events as the cornerstone to web service description and coordination. First, a web service architecture is introduced as the result of an event based analysis & design phase. Then, it is advocated how the event concept can be used for semantically rich web service description. A distinction is made between two(More)