Second Workshop on Service oriented EA for Enterprise Engineering (EDOC2010) (SoEA4EE'2010)
|Event Date/Time: Oct 25, 2010||End Date/Time: Oct 25, 2010|
|Paper Submission Date: Apr 17, 2010|
CALL FOR PAPERS (http://crinfo.univ-paris1.fr/users/nurcan/SoEA4EE_2010/SoEA4EE_2010_flyer.pdf)
Second International Workshop on Service oriented Enterprise Architecture for Enterprise Engineering (SoEA4EE)
in conjunction with EDOC 2010
October 25th, 2010, VitÃ³ria, Brazil
Papers submission deadline: April 17, 2010
Selmin Nurcan â€“ University Paris 1 PanthÃ©on Sorbonne, France
Rainer Schmidt â€“ University of Applied Sciences, Aalen, Germany
There is a more and more common understanding, that not the ownership of information technology resources but their management is the foundation for sustainable competitive advantage. According to Ross et al., smart companies define how they (will) do business (using an operating model) and design the processes and infrastructure critical to their current and future operations (enterprise architecture), which guide the evolution of their foundation for execution. More and more companies would like their existing technology to enable their future capabilities. This capability to exploit the foundation, embedding new initiatives to make it stronger and using it as competitive weapon to develop new business opportunities, is estimated as 5% of companies.
Enterprise engineering is the application of engineering principles to the design, restructuring and operation of enterprises and their cooperation with other enterprises. It allows deriving the Enterprise Architecture from the enterprise goals and strategy and aligning it with the enterprise resources. Enterprise architecture aims (i) to understand the interactions and all kind of articulations between business and information technology, (ii) to define how to align business components and IT components, as well as business strategy and IT strategy, and more particularly (iii) to develop and support a common understanding and sharing of those purposes of interest. Enterprise architecture is used to map the enterprise goal and strategy to the enterpriseâ€™s resources (actors, assets, IT supports) and to take into account the evolution of this mapping. It also provides documentation on the assignment of enterprise resources to the enterprise goals and strategy. To this end, advantageous patterns (best practices) can be reused and alternative design solutions can be compared. Furthermore, enterprise architecture may be checked for compliance with laws, regulatory rules etc. Finally, enterprise architecture facilitates the measurement the performance and efficiency of the resources used.
Service is the most important paradigm for the organisation of enterprises and the cooperation with other enterprises in order to achieve competitive advantage. Therefore it does not surprise, that leading enterprises in the U.S. derive more than 50% of their revenues from services. Through services, enterprises stabilize their revenues. 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. By exchanging services within partnerships, enterprises are able to combine their competences and thus provide solutions to the customer not possible for the single enterprise. Moreover meta-services (services acting upon other services) highly reduce the administrative overhead of enterprise services by encapsulating administrative functionalities as a service.
Furthermore, due to the technical advancements, e.g. Software as a Service, Cloud Computing and Service-Oriented-Architectures for information systems (SOA), enterprises are able to apply service-orientation to new areas. Service-oriented enterprise engineering further develops the enterprise engineering approach selecting service as governing paradigm. The enterprise goals and strategies are mapped to a service-oriented enterprise architecture.
Service-oriented enterprise architecture differentiates four layers of services. Thus, its scope is much broader than the scope of the service-oriented architecture (SOA) and also includes services not accessible through software such as business and infrastructure services. Services of different layers may be interconnected in service (value) nets to provide higher level services.
1. Business services are services, which directly support business processes. Business processes can also be developed dynamically (on-the-fly) using business services which are available in a repository for a given business domain. An example is call-centre services provided by an external service provider.
2. Software services exist as two types: (i) human-oriented applications, which are provided as Software as a Service, (ii) application services which are part of so-called Service-Oriented-Architectures that are a popular paradigm for creating enterprise software.
3. Platform Services provide support of the development of applications. They provide services for the execution of applications, middleware stacks, web servers etc.
4. Infrastructure 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.
The goal of the workshop is to develop concepts and methods to assist the engineering and the management of service-oriented enterprise architectures and the software systems supporting them. Especially three themes of research shall be pursued:
1. Alignment of the enterprise goals and strategies with the service-oriented enterprise architecture
2. Design of the service-oriented enterprise architecture
3. Mapping of service-oriented enterprise architecture to enterprise resources
TOPICS OF DISCUSSION:
During the workshop we will discuss the following topics:
1. Alignment of the enterprise goals and strategy with the service-oriented enterprise architecture
- 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 non-functional requirements derived from enterprise goals and strategy?
- How are services aligned with non-functional requirements?
- How are services aligned with compliance requirements?
- Are the compliance and governance requirements enforced using service-oriented enterprise architectures?
2. Design of service-oriented enterprise architecture
- How are business, software, platform and infrastructure services defined?
- How are business services assigned to business processes?
- How are business services assigned to non-functional requirements?
- How are service (value) nets -consisting of business, software, platform and infrastructure services- created?
- How does service-oriented enterprise architecture, interrelate with cloud computing?
- How do meta-services differentiate for business, software, platform and infrastructure services?
- How are appropriate meta-services designed?
- Which phases do the lifecycle of business, software, platform and infrastructure services contain?
- How can the fulfilment of non-functional requirements be monitored?
- Which benchmarks and key performance indicators should be applied to services?
- Which approaches exist for the continual improvement of services?
3. Mapping of service-oriented enterprise architecture to enterprise resources
- Which resources are relevant for Service-oriented Enterprise Architecture?
- How are services mapped to enterprise resources?
- Which approaches exist to map services to resources?
- Which information system architectures are adequate for services?
- How can non-functional requirements be mapped to capacity planning of resources?
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 contributions will be peer reviewed based on the complete version, being full or short.
All papers published in the EDOC 2010 workshop proceedings must be in the IEEE Computer Society format (http://www2.computer.org/portal/web/cscps/formatting). 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.
Please submit your paper to Selmin.Nurcan@univ-paris1.fr
Proceedings of EDOC 2010 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 2010 conference and attend the workshop to present the paper. Analogously to previous years, there will be no workshop-only registration at EDOC 2010. 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 (www.soea4ee.org) 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: April 17, 2010
Author notification: June 4, 2010
Camera-ready due: June 16, 2010
PROGRAM COMMITTEE :
JoÃ£o Paulo A. Almeida - Federal University of EspÃrito Santo, Brazil
Judith Barrios - Universidad de Los Andes, Venezuela
Claudio Bartolini - Palo Alto HP Labs, USA
Khalid Benali - Loria, Nancy, France
Ilia Bider - IbisSoft, Sweden
Remco Dijkman - Eindhoven University of Technology, The Netherlands
Joao Falcao e Cunha, University of Porto, Portugal
Chiara Francalanci - Politechnico Milano, Italy
Xavier Franch - Universitat Politecnica de Catalunya, Spain
Francois Habryn - KSRI, Karlsruhe Institute of Technology, Germany
Sung-Kook Han - Won Kwang University, South Korea
Ron Kenett - KPA Ltd., Israel
Peter Kueng - CrÃ©dit Suisse, Switzerland
Lin Liu - Tsinghua University, Beijing, China
Hui Ma - Victoria University of Wellington, New Zealand
Selmin Nurcan - UniversitÃ© Paris 1 PanthÃ©on Sorbonne, France
Liam O'Brien - NICTA, Canberra, Australia
Joan A. Pastor - Universitat Oberta de Catalunya & UPC, Spain
HervÃ© Pingaud - Ecole des Mines, Albi, France
Gil Regev - EPFL & Itecor, Switzerland
Sebastian Richly - University Dresden, Germany
Colette Rolland - UniversitÃ© Paris 1 PanthÃ©on Sorbonne, France
Shazia Sadiq - University of Queensland, Australia
Rainer Schmidt - University of Applied Sciences, Aalen, Germany