[Paper Review] A Change Support Model for Distributed Collaborative Work

Phan Thi Thanh Huyen, Koichiro Ochimizu|arXiv (Cornell University)|Dec 8, 2012

Software Engineering Techniques and Practices8 references6 citations

TL;DR

This paper proposes a Change Support Model (CSM) for distributed collaborative software development that generates Change Support Workflows (CSWs) from UML model dependencies to enable safe, efficient change management. By detecting potential inconsistencies through predefined patterns and integrating with version control, CSM supports early awareness and resolution of conflicts during concurrent artifact modifications.

ABSTRACT

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.

Motivation & Objective

• Address inconsistency and uncertainty in distributed collaborative software development caused by concurrent changes to shared artifacts.
• Reduce the risk of conflicts by detecting potential inconsistencies before they occur, rather than at check-in time.
• Support change workers with comprehensive, automated workflows that reflect artifact dependencies and change impact.
• Improve collaboration by providing awareness of concurrent changes and inconsistency risks through a centralized information repository.
• Integrate with version control systems to ensure safe and traceable change implementation in the maintenance phase.

Proposed method

• Automatically generate Basic Dependency Relationships among UML model elements using a dedicated model and tool to capture artifact interdependencies.
• Construct Change Support Workflows (CSWs) from the dependency relationships to guide change workers through correct, consistent modification sequences.
• Define inconsistency patterns to detect potential conflicts among concurrently executing CSWs during both build and runtime phases.
• Integrate the CSM with version control systems to validate changes and prevent inconsistent states at check-in.
• Support inconsistency resolution through negotiation-based strategies, including fine-grained concurrent modification, merging CSWs, or creating new combined change requests.
• Provide awareness support by notifying change workers of risky points through collected local CSW data and pattern-based detection.

Experimental results

Research questions

• RQ1 How can dependency relationships among UML model elements be automatically generated to support change impact analysis in distributed environments?
• RQ2 What mechanisms enable the generation of Change Support Workflows (CSWs) that guide safe and efficient change implementation?
• RQ3 How can potential inconsistencies arising from concurrent CSW execution be detected early, before conflicts manifest in code or models?
• RQ4 What inconsistency patterns can be identified to improve runtime awareness and reduce the risk of inconsistent artifact states?
• RQ5 How can collaboration among change workers be enhanced through automated workflow generation and inconsistency warnings?

Key findings

• The CSM successfully generates CSWs from automatically derived UML model element dependencies, enabling structured and safe change execution.
• The model detects potential inconsistencies earlier than traditional version control systems by analyzing concurrent CSW behavior and applying predefined inconsistency patterns.
• The integration of CSM with version control allows for validation of changes at check-in, reducing the likelihood of introducing inconsistencies.
• The approach supports multiple resolution strategies—such as fine-grained modification, workflow merging, or new request creation—enabling flexible conflict handling.
• Awareness of concurrent changes and risky modification points is significantly improved through pattern-based detection and centralized repository monitoring.
• The method provides a comprehensive view of shared artifacts and their dependencies, reducing misunderstandings and improving coordination among distributed change workers.