An Interoperability Model for Process-Centered Software Engineering Environments and Its Implementation in Oz

Israel Ben‐Shaul, Gail E. KaiserColumbia 1995 · DOI

TL;DR

This paper introduces the "International Alliance" model, comprising "Treaty" and "Summit" abstractions, to enable interoperability between decentralized and autonomous software engineering environments (PSEEs). It addresses the challenge of balancing collaboration with autonomy by allowing sites to explicitly define shared subprocesses and their execution, while retaining local control.

What Problem Does This Paper Address?

Modern software development often involves multiple teams, potentially distributed across different organizations, each with its own tools, processes, and data. This creates a need for process-interoperability – allowing these independent "Process-Centered Software Engineering Environments" (PSEEs) to collaborate effectively without sacrificing their autonomy. The challenge lies in defining how these disparate environments can work together on shared tasks while respecting their individual operational and developmental freedom. This paper tackles this by proposing a model that allows for explicit, pairwise agreements on collaboration and a mechanism for executing these collaborative activities.

Methods

The core of the paper's contribution is the International Alliance model, which consists of two key abstractions:

  • Treaty: This defines the terms of collaboration between two PSEEs. It's a pairwise agreement that specifies which sub-processes will be shared and how they will be integrated. Treaties allow for explicit definition of shared subprocesses while preserving the autonomy of local, non-shared subprocesses. They are designed to be incremental, allowing sites to join or leave collaborations dynamically.
  • Summit: This is the execution abstraction for Treaty-defined subprocesses. It orchestrates the execution of shared activities across multiple sites by alternating between "shared" (synchronous) and "private" (autonomous) execution modes. This allows for coordinated execution of shared tasks while still enabling local, independent work.

The paper also details the implementation of this model within the Oz multi-site PSEE, which is a rule-based system.

Datasets

Not discussed in the paper.

Key Insights and Ideas

  • Autonomy by Default: The model prioritizes local autonomy, ensuring that sites are not forced into global constraints unless explicitly agreed upon via Treaties.
  • Pairwise Agreements: Treaties are defined pairwise, reflecting a peer-to-peer relationship and avoiding the need for a central authority. This supports a bottom-up approach to interoperability.
  • Separation of Concerns: The model clearly separates the definition of collaboration (Treaty) from its execution (Summit), allowing for flexibility in how shared activities are managed.
  • Dynamic Evolution: Treaties are designed to support local evolution of processes, meaning that changes in one PSEE don't necessarily break the collaboration, and dynamic Treaty verification ensures consistency.
  • System-Based Approach: Instead of inventing a new modeling language, the authors advocate for extending existing PSEE execution engines with system calls to support interoperability, making the model more generally applicable.

Key Results

The paper presents the conceptual model and its implementation in Oz. While specific quantitative results are not the primary focus, the authors report on experience gained from using Oz in a production environment with up to 14 users over 8 months. They also discuss the application of their model to Petri net-based and grammar-based PSEEs, demonstrating its generality. The evaluation highlights that the model successfully addresses key requirements like autonomy, locality, and interoperability.

Limitations and Future Work

The authors acknowledge that while their model provides a strong foundation, there are areas for further exploration. These include:

  • Extensions to the Treaty/Summit Model: Developing more advanced abstractions to support alternative modes of interoperability, including simultaneous local activities and enhanced groupware modeling.
  • Site Hierarchy: Exploring how to model and support hierarchical relationships between sites, which could be beneficial for top-down oriented environments.
  • Heterogeneity: Further addressing heterogeneity at the PSEE and PML levels in conjunction with their interoperability model.
  • Formalizing Behavior: Extending the idea of formally describing the behavior of autonomous entities to support interoperability beyond software process modeling, such as for autonomous Internet repositories.

Summary updated

Abstract

A process-centered software engineering environment (PSEE) enables to model, evolve, and enact the process of software development and maintenance. This paper addresses the problem of process-interoperability among decentralized and autonomous PSEEs by presenting the generic International Alliance model, which consists of two elements, namely Treaty and Summit. The Treaty abstraction allows pairwise peer-peer definition of multi-site shared sub-processes that are integrated inside each of the participating sites, while retaining the definition- and evolution-autonomy of non-shared local sub-processes. Summits are the execution abstraction for Treaty-defined sub-processes. They enact Treaty sub-processes in multiple sites by successively alternating between shared and private execution modes: the former is used for the synchronous execution of the shared activities, and the latter is used for the autonomous execution of any private subtasks emanating from the shared activities. We describe the realization of the models in the Oz multi-site PSEE and evaluate the models and system based on experience gained from using Oz for production purposes. We also consider the application of the model to Petri net-based and grammar-based PSEEs.
BibTeX
@inproceedings{benshaul1995interoperability,
  author = {Israel Ben‐Shaul and Gail E. Kaiser},
  title = {{An Interoperability Model for Process-Centered Software Engineering Environments and Its Implementation in Oz}},
  booktitle = {Columbia},
  year = {1995},
  doi = {10.7916/d8057q20},
}
Figure