NEW

Please note the tabs on top of this page. New material appears there!

Also note that all individual meetings take place in my office in D221, not in the seminar room. When reserving your meeting time, do make sure you WRITE it to the appointment calendar DIRECTLY so I can see it, NOT using any sophisticated negotiations (that the appointmentbook is not capable of handling). The meetings should be reserved between 9-16, or then negotiated in person.

Introduction

In service-oriented computing (SOC), models are mostly used in connection of model driven engineering processes (MDE). In MDE, an abstract model of the software or the service is first created, either at a platform-independent level (PIM), or even, at a computational-independent level (CIM). A platform independent model would roughly correspond a portable program, while a computational-independent model would leave the exact computing algorithm to be freely selected afterwards, by just catching requirements on the system behaviour (corresponding to the information state it represents). After the model creation, pre-prepared transformations are used for generating a less abstract model, such as runnable program for a certain platform (CORBA, Linux) or a less abstract model that will be further refined. The reverse process is also preferred: from a changed target model an automated "reverse engineering" to the more abstract models should be easy to achieve. The benefits of these downward processes with specialising or upward processes with abstractions include portability of solutions to new envionments, interoperability of solutions generated from a joint model for different platforms, and model-driven engineering tool interoperability (by sharing the more abstract model level).

In SOC, models commonly appear in terms of service descriptions and business process descriptions. This kind of model use in operational time service composition have been studied on courses of Service ecosystems, Service oriented software engineering, Model driven engineering and Business process automation. More commonly, the SOC style model use can be noted in Web Services technologies stack.

In this seminar we study architectures where different types of models are used as the key element in the management/governance of system or service behaviour at operational time. Examples of operational time model-driven management include reflective systems, complex adaptive systems,  multi-agent systems and context-aware systems. Especially, we focus on the model-driven governance of inter-enterprise collaborations, decision-making in enterprise interoperability context, and automated management of collaborations and service ecosystems.

This seminar has two tracks, a learning seminar track for students who are just learning the basics of the use of models, and a research seminar track for students already involved with the CINCO group by passing the above mentioned courses. For the learning seminar track, topics with recommended background material are made available in the beginning of the seminar. For the research seminar track, please mention your position when applying for the seminar. In the research seminar track, you may  suggest a topic either at application time, or by mid-August at latest. The research seminar track members have an opportunity to work on a shared research survey article by invitation.

The seminar schedule will be approximately as follows:

• Introduction sessions: getting to know each other, splitting to tracks, introductory lecture on the topic area, advise on paper writing and presentation preparation
• Working sessions: peer meetings where each member has regularly an opportunity to report the progress and discuss problems with peer seminar group members
• Deadlines: 1) topic selection wk 2; 2) work plan wk 3; 3) first full paper draft wk 5 + peer review feedback wk 6; 4) final paper wk 8; 5) presentation sessions each week after

References for the above

• DC Schmidt, Model-driven engineering. Computer, December 2006 at http://origin-www.computer.org/csdl/mags/co/2006/02/r2025.pdf
• Weske, Business Process Management, Chapter 7: BPM Architecture at http://link.springer.com/chapter/10.1007/978-3-642-28616-2_7#page-1
• Geoff Coulson, What is reflective middleware? at http://www.comp.lancs.ac.uk/~geoff/Publications/RMARTICLE1.pdf .
• MARKUS C. HUEBSCHER and JULIE A. McCANN, A survey of Autonomic Computing—Degrees, Models, and Applications.  ACM Computing Surveys, Vol. 40, No. 3, Article 7 at http://delivery.acm.org/10.1145/1390000/1380585/a7-huebscher.pdf ip=128.214.166.173&acc=ACTIVE%20SERVICE&key=C2716FEBFA981EF128E0569D9715865F6DA88B0F8E95CB9F&CFID=213076604&CFTOKEN=79434524&__acm__=1367589891_dc29d99b7b5ce17dfb235503d99d67d8
• CINCO group publications