First Workshop on Service oriented Enterprise Architecture for Enterprise Engineering (SoEA@EE'09)
|Event Date/Time: Sep 01, 2009||End Date/Time: Sep 01, 2009|
|Abstract Submission Date: May 31, 2009|
|Paper Submission Date: May 31, 2009|
Services have become an impressive factor for growth and the creation of jobs. 93% of the new jobs created in the U.S. between 1970 and 2000 are jobs in services . Leading enterprises in the U.S. derive more than 50% of their revenues from services. This applies not only to pure services such as transportation but also for material products that are augmented by services such as maintenance, consulting and training. Through services, enterprises stabilize their revenues. There is no accepted general definition of service, but many definitions contain the idea, that a service is â€œthe application of specialized competences (knowledge and skills) for the benefit of another entity, rather than the production of units of outputâ€ . Services are more and more considered as part of a so-called service system. A service system is defined â€œas a value co-production configuration of people, technology, other internal and external service systems, and shared information (such as language, processes, metrics, prices, policies, and laws)â€.
Therefore it is no surprise that the term service has also become very popular in enterprise computing. However, the term service may have different meanings in enterprise computing. Three flavours of services can be differentiated: technology services, software-services, and business services.
1. Technology services are more hardware flavoured services which are provided using computers. They may have a human addressee but contain many infrastructure services such as providing computing power, storage etc. They are an important topic in management and practice collections such as ITILV3 or standards such as ISO/IEC 20000 have gained a high popularity.
2. Software services are managed in so-called Service-Oriented-Architectures that are a popular paradigm for creating enterprise software. A service in the context of SOA is a special kind of interface for an encapsulated unit of software.
3. Business services are services which directly support business processes. They may be further differentiated into those visible to the customer and those that are not. Business processes can also be developed dynamically (on-the-fly) using business services which are available in a repository for a given business domain.
In the field of Information Systems and -in a broader sense- Enterprise Computing, the notion of â€œEnterprise modellingâ€ refers to a collection of conceptual modelling techniques for describing different facets of the organisation including operational (IS), organisational (business processes, actors, flow of information etc), and teleological (purposes) considerations. Existing enterprise modelling frameworks stress the necessity of representing and structuring enterprise knowledge taking into account all these facets in order to develop IS and IT architectures that enterprises need. The contribution of the software systems to the realization of the business processes and consequently to the objectives of the company is of primary importance. A change in one of these facets of the organization implies multiple impacts on the two other facets. In other words, it seems unrealistic to consider an organizational change without any impact on the information system or an evolution of the IS which does not call into question the processes or even the objectives of the organization.
An enterprise architecture,,defines the interactions and articulations between business and information technology and their alignment or congruence. A service-oriented enterprise architecture uses services to describe the articulations of business and information technology. It has to identify the business services needed to support the business processes of the enterprise, and to map the business services to technology and software services as shown in the figure below. Technology and software services are both called IT services in the following.
The enterprise computing systems which shall manage Service-oriented Enterprise Architectures have to support the creation, administration and execution of services. Thus, they must be able to store the service definitions and make them available for a consumer in a service catalogue. The same applies to the so-called service-level agreements that define the quality of service agreed upon with consumers. Upon a service request from a consumer entity, the service support system has to monitor the fulfilment of the service-level agreements and also to provide remediation procedures which contain so-called escalation mechanisms. Furthermore, based on the monitoring, improvement procedures shall be established.
The goal of the workshop is to clarify the relationship between business process management and service provisioning. The objective of this workshop is twofold:
(i) To characterise the strong relationship existing between Business Process Management (BPM) and Service oriented Enterprise Architecture (SoEA)
(ii) To develop concepts and methods to assist the engineering and the management of Service-Oriented Enterprise Architectures (SoEA) and their support systems.
TOPICS OF INTEREST:
During the workshop we will discuss the following topics:
1. Service engineering
- Do we need new paradigms to cope with service engineering?
- How are business services discovered, defined, composed, adapted?
- How are business services assigned to business processes?
- How are technology-services discovered, defined, composed, adapted?
- How are technology-services assigned to business services?
- Are there design patterns for developing service-oriented systems?
- How can the MDA/MDD techniques and methods be applied for engineering SoEA?
- Which test methods exist for technology-services?
- How are business services and technology-services rolled out?
- Which change management procedures have to be applied during the deployment of SoEA?
2. Service management
- Which benchmarks and key performance indicators should be applied to services?
- Which information system architectures are adequate for services?
- Which approaches exist for mastering the migration of legacy systems to SoEA?
- Which triggers exist and what mechanisms should be applied for escalation?
- Which approaches exist for the continual improvement of services?
- Which evaluation and validation techniques can be applied for SoEA?
3. Alignment with business strategy
- Which interdependencies exist between services and business strategy?
- Which concepts and methods are necessary to align services with the business strategy?
- Which new potentials to reengineer business processes are created by services?
- How are services aligned with compliance requirements?
- How are compliance and governance requirements enforced?
Full papers (8-10 pages in the IEEE-CS format) describing mature results are sought. In addition, short papers (4 pages in the IEEE-CS format) may be submitted to facilitate discussion of recent research results and ongoing projects. The paper selection will be based upon the relevance of a paper to the main topics, as well as upon its quality and potential to generate relevant discussion.
All papers published in the EDOC 2009 workshop proceedings must be in the IEEE Computer Society format (http://www.computer.org/portal/site/cscps/ information for authors). It is strongly recommended that all papers are already in this format when they are first submitted to workshops. This gives precise picture of the paper length and avoids rework if the paper is accepted.
All papers will be peer reviewed based on the paper. Please submit your paper to Selmin.Nurcan.@univ-paris1.fr
Proceedings of EDOC 2009 workshops will be published after the conference as ePub by the IEEE Computer Society Conference Publishing Services (CPS) and included in the IEEE Computer Society Digital Library (CSDL) and the IEEE Xplore. There will be one electronic volume containing proceedings from all workshops.
At least one author of each accepted workshop paper will have to register for the whole EDOC 2009 conference and attend the workshop to present the paper. Analogously to previous years, there will be no workshop-only registration at EDOC 2009. If a paper is not presented in the workshop, it will be removed from the workshop proceedings published in the IEEE Xplore digital library.
All papers will be published in the workshop wiki before the workshop, so that everybody can learn about the problems that are important for other participants. The workshop will consist of long and short paper presentations, brainstorming sessions and discussions. A workshop report will be created collaboratively using the workshop wiki.
Paper submission: May 31, 2009
Author notification: July 12, 2009
Camera-ready: July 24, 2009
PROGRAM COMMITTEE :
JoÃ£o Paulo A. Almeida - Federal University of EspÃrito Santo, Brazil
Karim BaÃ¯na - ENSIAS, Morocco
Judith Barrios - Universidad de Los Andes, Venezuela
Claudio Bartolini, Palo Alto HP Labs, USA
Khalid Benali - Loria, Nancy, France
Ilia Bider - IbisSoft, Sweden
Chiara Francalanci - Politechnico Milano, Italy
Francois Habryn KSRI, University Karlsruhe, Germany
Carsten Holtmann - FZI Karlsruhe, Germany
Dimka Karastoyanova University Stuttgart, Germany
Ron Kenett - KPA Ltd., Israel
Peter Kueng CrÃ©dit Suisse, Switzerland
Selmin Nurcan - University Paris 1 Pantheon Sorbonne, France
Gil Regev - EPFL & Itecor, Switzerland
Sebastian Richly University Dresden, Germany
Shazia Sadiq - University of Queensland, Australia
Rainer Schmidt - Aalen University, Germany
Pnina Soffer - University of Haifa, Israel
Marco von Mevius - FZI Karlsruhe, Germany