Gunnar Thies

Governance in Web-oriented Architectures

Web-oriented Architectures provide a way of designing an IT system by using a variety of Web Procedures, i.e., procedures (or services) called over the Web. The idea of (typically atomic) components that are black boxes, have interfaces, and can be assembled into a larger process is fundamental and has existed since the early days of distributed systems. Two particular types of modern distributed systems are Service-oriented Architectures and Resource-oriented Architectures, which are built upon specific technology stacks and define their own concepts. Web-oriented Architecture (WOA) is using the best of both worlds plus some specifics such as Web APIs, in order to build an interconnected IT system in the easiest way possible. In this paper we first sharpen our understanding of the concept behind aWOA, the topology of a WOA and possible integration scenarios within an enterprise. More importantly, we point out how governance and control of a WOA can be achieved, by using a controlling software element called the Web Architecture Controller (WAC) which specifies the Web-centric core elements of a WOA.

Identification, Specification, and Development of Web-Oriented Architectures

Web-oriented Architectures (WOAs) provide a way of designing an IT system by using a variety of Web Procedures, i.e., procedures (or services) called over the Web. The idea of (typically atomic) components that are black boxes, have interfaces, and can be assembled into a larger process is fundamental and has existed since the early days of distributed systems. Two particular types of modern distributed systems are Service-oriented Architectures and Resource-oriented Architectures, which are built on specific technology stacks and define their own concepts. A WOA uses the best of both worlds plus specifics like Web APIs to build an interconnected IT system in the easiest way possible. In this article, the authors introduce the concept behind a WOA, the topology of a WOA, and possible integration scenarios within an enterprise. More importantly, the authors discuss what a methodology for building a WOA can look like and how control can be achieved, by using a logical software element called the Web Architecture Controller, which specifies the Web-centric core elements of a WOA. Lastly, the cost of implementing and running such a system is briefly addressed.

ISETTA: Service Orientation in the “Bologna Process” of a Large University

With the signing of the “Bologna Declaration” in June 1999 by 29 representatives of the European education ministries, a decision was made to introduce comparable educational structures among European universities based on a. Bachelor-Master system until the year 2010. The process itself, collectively known as the “Bologna process,”1 is now well-underway and has created both administrative as well as technical challenges. The ISETTA project at the University of Muenster in Germany aims at the development of an Integrated Student, Exam, Test, and Teaching Application that properly reflects the changes of the university’s internal activities caused by the Bologna process. In this paper, we report on the specific requirements of the project, the approach that has been taken and the current status of ISETTA.