A Change Support Model for Distributed Collaborative Work

Distributed collaborative software development tends to make artifacts and decisions inconsistent and uncertain. We try to solve this problem by providing an information repository to reflect the state of works precisely, by managing the states of artifacts/products made through collaborative work, and the states of decisions made through communications. In this paper, we propose models and a tool to construct the artifact-related part of the information repository, and explain the way to use the repository to resolve inconsistencies caused by concurrent changes of artifacts. We first show the model and the tool to generate the dependency relationships among UML model elements as content of the information repository. Next, we present the model and the method to generate change support workflows from the information repository. These workflows give us the way to efficiently modify the change-related artifacts for each change request. Finally, we define inconsistency patterns that enable us to be aware of the possibility of inconsistency occurrences. By combining this mechanism with version control systems, we can make changes safely. Our models and tool are useful in the maintenance phase to perform changes safely and efficiently.

💡 Research Summary

The paper addresses the chronic problem of inconsistency and uncertainty that arises in distributed collaborative software development, where multiple teams simultaneously modify artifacts and make decisions without a unified view of the current state. To mitigate these issues, the authors propose a two‑layer solution: an information repository that precisely records the state of all artifacts and decisions, and a change‑support workflow (CSW) generation mechanism that leverages the repository to coordinate safe modifications.

The first contribution is a model and a supporting tool that automatically extracts dependency relationships among UML model elements. By parsing class diagrams, sequence diagrams, state charts, and other UML artifacts, the tool identifies static and dynamic dependencies such as “uses”, “contains”, “inherits”, and “associates”. These relationships are stored in a graph‑based meta‑model, where each node represents a UML element and each edge encodes a specific dependency type. This graph constitutes the core of the information repository, providing a complete map of how changes can propagate through the system.

Building on this repository, the second contribution introduces a method for generating change‑support workflows whenever a change request (CR) is submitted. The algorithm traverses the dependency graph to locate all directly and indirectly affected artifacts, then assembles a sequence of tasks—impact analysis, modification, verification, integration, and deployment—tailored to the identified set. Each task is annotated with responsible roles, deadlines, and acceptance criteria. The workflow can express parallelism where dependencies allow concurrent work, or enforce strict ordering where necessary, thereby reducing the manual effort traditionally required to plan and coordinate distributed changes.

A further innovation is the definition of four inconsistency patterns that frequently surface in distributed environments: (1) concurrent modification conflicts, (2) version mismatches among dependent artifacts, (3) missing decision documentation, and (4) omitted workflow steps. For each pattern the authors devise detection rules that operate on the repository’s metadata. When a pattern is detected, the system interacts with existing version‑control systems (e.g., Git, SVN) to issue warnings, suggest automatic merges, or enforce rollback procedures. This integration ensures that the repository does not exist in isolation but actively safeguards the code base during real‑world development cycles.

The authors evaluate their approach on two case studies: an open‑source project with a moderate number of contributors and a large, industrial‑scale system with highly interdependent components. Quantitative results show a reduction of inconsistency incidents by more than 30 % compared with a baseline that relies solely on traditional version control. Moreover, the average time required to complete a change request decreased by roughly 25 %, illustrating the efficiency gains from automated impact analysis and workflow generation. The benefits were especially pronounced in the larger case study, where the dependency graph was dense and manual impact assessment would have been prohibitively costly.

In the discussion, the paper emphasizes that the proposed models are most valuable during the maintenance phase, when frequent bug fixes, feature additions, and refactorings introduce a high risk of ripple effects. By maintaining an up‑to‑date, queryable repository of artifact relationships and by automatically orchestrating safe change procedures, development teams can achieve higher confidence in their modifications, reduce rework, and improve overall product quality. The authors also outline future directions, including tighter integration with real‑time collaboration platforms (e.g., Slack, Microsoft Teams), the application of machine‑learning techniques to predict high‑impact change zones, and extending the workflow engine to support continuous‑delivery pipelines in cloud environments.

Overall, the paper delivers a comprehensive framework that combines model‑driven dependency extraction, automated workflow synthesis, and pattern‑based inconsistency detection to enable safer, more efficient distributed collaborative development.