SoEA4EE 2014: Sixth International Workshop on Service oriented Enterprise Architecture for Enterprise Engineering 2014

September 1, 2014-September 5, 2014 in Ulm, Germany

About the Conference


SCOPE

Several developments, such as the success of cloud-computing show that not the ownership of IT 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 (using an enterprise architecture).

Enterprise Engineering (EE) is the application of engineering principles to the design of Enterprise Architectures (EA). It allows deriving the EA from the enterprise goals and strategy and aligning it with the enterprise resources as shown in Figure 1, EA 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.

There are different paradigms for creating enterprise architecture. The most important is to encapsulate the functionalities of IT resources as services. By this means, it is possible to clearly describe the contributions of IT both in terms of functionality and quality and to define a service-oriented enterprise architecture (SoEA). SoEA easily integrates wide-spread technological approaches such as SOA or emerging ones as cloud computing because they also use service as structuring and governing paradigm. The enterprise goals and strategies are mapped to a SoEA.

SoEA differentiates four layers of services. Thus, its scope is much broader than the scope of 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 SOA 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.

GOALS

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 five themes of research shall be pursued: 1. Alignment of the enterprise goals and strategies with the SoEA 2. Design of the SoEA 3. Mapping of SoEA to cloud-based enterprise resources 4. Management of SoEA 5. SoEA and influence of social and big data in Enterprise Engineering

Conference Dates

Submissions: April 8, 2014
Notification: May 27, 2014
Event: September 1, 2014-September 5, 2014

Proceedings