Towards an Ontological Foundation of Services Science: The General Service Model

Despite the ubiquity of services, there is still no consensus ontheir exact nature and structure. This consensus, however, isnecessary to unambiguously describe and trade servicesphysically as well as in an Internet of Service. To make someprogress towards a shared conceptualization, we present in thispaper a general service model based on the DOLCE foundationalontology. In our understanding, a service is essentially composedof a service process whose core actions (delivered by a serviceproducer to a service consumer) comply with the exposeddescription of a service provider’s commitment. Each servicebelongs to a larger service system process which obeys legal andpricing constraints. We illustrate the model’s usefulness andrelevance by the means of a continuous example

Inciting Networks Effects Through Platform Authority: A Design Theory for Service Platforms

The provisioning of software has shifted towards a service model, where applications are hosted, metered, and billed through service platforms rather than being sold as on-premise software. These services can exhibit network effects, which are self-enforcing effects of value generation. They describe the interdependency of service or platform value, service consumption, and third party service provisioning. Service platforms need to be designed to incite these network effects. We propose a design theory which is based on the operator’s platform authority as the key factor for controlling and influencing stakeholders in and around the service platform in different control modes. As a design method, we propose a conceptual modeling language which supports service platform design with staged areas of authority, process flows as well as control methods. We present the rationale behind the language, discuss its application, and propose testable hypotheses for an empirical evaluation

Abschlussbericht des Verbundprojekts Tools4BPEL

Unternehmensübergreifende Geschäftsprozesse werden zunehmend nach dem Paradigma der Services organisiert. Dabei stellen sich Fragen nach der Komponierbarkeit, Fehlerbehandlung, sowie der Rücksetzbarkeit (Kompensation) im Fehlerfall. In diesem Vorhaben werden Methoden und Werkzeuge zum Umgang mit solchen Fragen entwickelt und am Beispiel der Geschäftsprozess-Modellierungssprache BPEL und im Modellierungswerkzeug der Firma MEGA international erprobt. Es wurde zum einen der Übersetzer BPEL2oWFN entwickelt, der anhand einer Petrinetzsemantik für BPEL einen BPEL-Prozess in ein (offenes) Petrinetz transformiert. Zum anderen wurden Korrektheitskriterien (wie Bedienbarkeit und Verhaltenskompatibilität) für Services erarbeitet, Algorithmen zu ihrer Überprüfung entworfen und in Fiona implementiert. Die Algorithmen sind Petrinetz-basiert. Damit spielen Übersetzung und Analyse eng zusammen und ein vorhandener BPEL-Prozess kann auf bspw. Bedienbarkeit hin untersucht werden. In diesem Vorhaben wurden die Modellierungssprache BPEL4Chor, Choreographie-Erweiterungen für BPMN entwickelt, sowie die Transformation von BPMN nach BPEL angepasst, um den Weg von BPMN nach BPEL4Chor zu unterstützen. Weiterhin wurden Konzepte entwickelt, wie sich partner-übergreifende Fehlerbehandlung, Rücksetzbarkeit, sowie die Autonomie der Partner mittels BPEL4Chor darstellen lassen. BPEL4Chor kann als Standardsprache zur Spezifikation von Protokollen, die zwischen mehreren Partnern ablaufen, verwendet werden. Durch seine enge Verbindung mit BPEL kann BPEL4Chor sehr gut als Startpunkt für eine Webservice-Lösung verwendet werden

An Information Systems Design Theory for Service Network Effects

Service platforms make software applications available as a service to end users. Platforms enable noticeable economic benefits for scaling and transforming a business. Their long-term competitiveness is ensured in controlled cooperation with channel intermediaries and network partners. Hence, service platforms must be designed to harness self-enforcing effects of value generation, so-called network effects. In an exaptation of existing knowledge, we present an information systems design theory to inform the design of methods that analyze, describe, and guide the design of service platforms through the means of causal loops and control methods. We describe the theory’s purpose and scope as well as the underlying justificatory knowledge behind the constructs and principles of form and function. The design theory covers the design of all service platform participants and activities as well as their transactions and influences in areas of staged platform authority, using enforcing and incentivizing control methods. We demonstrate the principles of implementation with an expository instantiation and apply it to the M-Engineering service platform, which offers surveillance, control, and data acquisition solutions. Furthermore, we present and discuss testable propositions and a study design to evaluate our design principles

An architecture for managing the lifecycle of business goals for partners in a service network

Networks of interdependent organizations cooperate to produce goods or, nowadays, services that are of value to their markets as well as to the participating organizations. Such co-operations can be supported by corresponding business processes which are based on SOA technology. Developing and managing SOA-based business processes in such service networks necessitates a comprehensive architecture which is on the one hand grounded on solid design principles, and on the other hand capturing best-practices and experiences. Such an architecture is currently lacking. This paper outlines a first attempt to develop and validate an architecture for developing, monitoring, measuring and optimizing SOA-enabled business processes in service networks. A case study from the telecommunications industry is analyzed, and different aspects of service networks are addressed

A theory and model for the evolution of software services

Software services are subject to constant change and variation. To control service development, a service developer needs to know why a change was made, what are its implications and whether the change is complete. Typically, service clients do not perceive the upgraded service immediately. As a consequence, service-based applications may fail on the service client side due to changes carried out during a provider service upgrade. In order to manage changes in a meaningful and effective manner service clients must therefore be considered when service changes are introduced at the service provider's side. Otherwise such changes will most certainly result in severe application disruption. Eliminating spurious results and inconsistencies that may occur due to uncontrolled changes is therefore a necessary condition for the ability of services to evolve gracefully, ensure service stability, and handle variability in their behavior. Towards this goal, this work presents a model and a theoretical framework for the compatible evolution of services based on well-founded theories and techniques from a number of disparate fields.

A theory and model for the evolution of software services.

Software services are subject to constant change and variation. To control service development, a service developer needs to know why a change was made, what are its implications and whether the change is complete. Typically, service clients do not perceive the upgraded service immediately. As a consequence, service-based applications may fail on the service client side due to changes carried out during a provider service upgrade. In order to manage changes in a meaningful and effective manner service clients must therefore be considered when service changes are introduced at the service provider's side. Otherwise such changes will most certainly result in severe application disruption. Eliminating spurious results and inconsistencies that may occur due to uncontrolled changes is therefore a necessary condition for the ability of services to evolve gracefully, ensure service stability, and handle variability in their behavior. Towards this goal, this work presents a model and a theoretical framework for the compatible evolution of services based on well-founded theories and techniques from a number of disparate fields.

Value Creation through Co-Opetition in Service Networks

Well-defined interfaces and standardization allow for the composition of single Web services into value-added complex services. Such complex Web Services are increasingly traded via agile marketplaces, facilitating flexible recombination of service modules to meet heterogeneous customer demands. In order to coordinate participants, this work introduces a mechanism design approach - the co-opetition mechanism - that is tailored to requirements imposed by a networked and co-opetitive environment

A Reference Architecture for Service Lifecycle Management – Construction and Application to Designing and Analyzing IT Support

Service-orientation and the underlying concept of service-oriented architectures are a means to successfully address the need for flexibility and interoperability of software applications, which in turn leads to improved IT support of business processes. With a growing level of diffusion, sophistication and maturity, the number of services and interdependencies is gradually rising. This increasingly requires companies to implement a systematic management of services along their entire lifecycle. Service lifecycle management (SLM), i.e., the management of services from the initiating idea to their disposal, is becoming a crucial success factor. Not surprisingly, the academic and practice communities increasingly postulate comprehensive IT support for SLM to counteract the inherent complexity. The topic is still in its infancy, with no comprehensive models available that help evaluating and designing IT support in SLM. This thesis presents a reference architecture for SLM and applies it to the evaluation and designing of SLM IT support in companies. The artifact, which largely resulted from consortium research efforts, draws from an extensive analysis of existing SLM applications, case studies, focus group discussions, bilateral interviews and existing literature. Formal procedure models and a configuration terminology allow adapting and applying the reference architecture to a company’s individual setting. Corresponding usage examples prove its applicability and demonstrate the arising benefits within various SLM IT support design and evaluation tasks. A statistical analysis of the knowledge embodied within the reference data leads to novel, highly significant findings. For example, contemporary standard applications do not yet emphasize the lifecycle concept but rather tend to focus on small parts of the lifecycle, especially on service operation. This forces user companies either into a best-of-breed or a custom-development strategy if they are to implement integrated IT support for their SLM activities. SLM software vendors and internal software development units need to undergo a paradigm shift in order to better reflect the numerous interdependencies and increasing intertwining within services’ lifecycles. The SLM architecture is a first step towards achieving this goal.:Content Overview List of Figures....................................................................................... xi List of Tables ...................................................................................... xiv List of Abbreviations.......................................................................xviii 1 Introduction .................................................................................... 1 2 Foundations ................................................................................... 13 3 Architecture Structure and Strategy Layer .............................. 57 4 Process Layer ................................................................................ 75 5 Information Systems Layer ....................................................... 103 6 Architecture Application and Extension ................................. 137 7 Results, Evaluation and Outlook .............................................. 195 Appendix ..........................................................................................203 References .......................................................................................... 463 Curriculum Vitae.............................................................................. 498 Bibliographic Data............................................................................ 49