Multi-Tenant Development Configuration for Early Conflict Detection

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing multi-user development systems face challenges with conflicting modifications, version control issues, and reduced development velocity due to incompatible changes made by different users to shared objects, leading to system integrity and functionality problems.

Innovation Solution

Implementing object-oriented and feature-based configuration files in JSON format, centrally accessible to multiple environments, which enable conflict detection and resolution, enforce version control, and facilitate sequential deployment.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If multiple users simultaneously customize objects in a multi-user development system, then development parallelism and velocity are improved, but conflicting modifications and version control issues arise

Engineering Contradiction:
Improvedevelopment velocityVSAvoidsystem integrity
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The system performs preliminary conflict detection by comparing proposed changes against the baseline version before allowing customization. This prevents conflicting modifications from being applied, ensuring system integrity while maintaining development parallelism. The conflict detection mechanism checks version numbers and change compatibility proactively rather than reactively.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent introduces an intermediary conflict detection and resolution mechanism that mediates between multiple users' customization requests. This intermediary layer compares proposed changes, identifies conflicts, and manages version control, allowing parallel development while preventing integrity violations.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Ease of operation

If users propose changes independently without coordination, then ease of operation is improved, but incompatible changes and dependencies violations occur

Engineering Contradiction:
Improvecustomization easeVSAvoidchange compatibility
Core Design Contradiction:
Ease of operationVSManufacturing precision

Solution Approach 1:

The system provides feedback to users about potential conflicts and compatibility issues with their proposed changes. Before applying customizations, the system checks against the baseline and other pending changes, informing users of incompatibilities. This maintains ease of operation while ensuring change compatibility through informative feedback loops.

Inventive Principle:
Principle #23Feedback

3Adaptability or versatility

If conflict detection is performed later in the development process, then development freedom is improved, but loss of time due to rework increases

Engineering Contradiction:
Improvedevelopment freedomVSAvoidconflict resolution time
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The system performs conflict detection preliminarily, before changes are applied to the system. By checking proposed changes against the baseline version and detecting conflicts early in the customization process rather than later during deployment or testing, the system maintains development freedom while minimizing time loss through early conflict identification.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS20250284491A1System, Method, and Device For Managing Multi-Tenant Development Systems
Publication Date: 2025.09.11 THE TORONTO DOMINION BANK
  • US20250284491A1 patent drawing
  • US20250284491A1 patent drawing
  • US20250284491A1 patent drawing

AI summary

A device, method, and system for managing multi-user development systems is disclosed. Illustratively, the method includes providing a platform that enables customization of objects associated with the platform through record based configurations and providing a plurality of configuration files, each configuration file associated with a distinct functionality of the platform. The method includes, for each configuration file of the plurality of the configuration files, structuring the respective configuration file to be an objected oriented and a feature-based data file for entering record based configuration changes for the respective functionality. The method includes accepting requests for customizations of objects in the platform through the plurality of configuration files.