Modeling Services Using ISE Framework

Abstract

The Internet of services introduces new requirements for service engineering in terms of addressing both business and technical perspectives. The inherent complexity of the new wave of services that is emerging requires new approaches for an effective and efficient service design. In this chapter a novel service engineering framework is introduced: the Integrated Service Engineering (ISE) framework. With its ISE workbench, it can address the emerging requirements of Internet of services. The chapter presents the foundations on how the service engineering process can be conducted by applying the separation of concerns to model different service dimensions within various layers of abstraction. Additionally, three novel extensions are presented to the aforementioned ISE workbench in order to enrich the capabilities of the service modeling process.

Internet-Based Self-Services: From Analysis and Design to Deployment

“…We have previously developed the ISE (Inter-enterprise Service Engineering) methodology and workbench [10], [11], one of the first attempts to devise a Service Engineering procedure for designing business services [12]. ISE has some similarities with the method presented in this paper since it was also inspired by the Zachman framework (see [12]) and relies on model-driven development concepts.…”

“…The taxonomy for the 'what' dimension was composed by the concepts: Incident, Solution, Customer, etc. The reader is referred to our previous work on service analysis with the ISE methodology (see [10], [21], [12]). …”

“…The enterprise architecture adopted to provide a service architecture was the Zachman framework for four main reasons: (1) our previous research on using this framework for the [10]); (2) there is a clear mapping between the framework and the components of the approach proposed in this paper. For instance, MDD maps to the logical perspective of the Zachman framework and MVC maps to the 'as build' perspective; (3) it provides simple cognitive models, such as mindmaps and nested bullet lists, which help stakeholders dealing with abstraction and supports the complexity of services using a divide-and-conquer approach; and (4) it addresses the separation of concerns paradigm raised by [18] by dividing and structuring services' important aspects into six dimensions relevant for ISS: data, processes, networks, people, time, and motivation.…”

“…This decision made the approach simpler to use and more appealing to stakeholders. On the other hand, the focus of ISE was on the horizontal/vertical integration, synchronization, and transformation of models using model transformation languages and toolkits such as MOF QVT or ATL (see [10], [12], [11]). This approach revealed to be too complex since management tools for model transformation were not mature for multi-model scenarios.…”