Code Monitoring Subsystem for Reducing Work Duplication in Parallel Development

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In parallel and concurrent software development environments, work duplication occurs frequently as developers work on similar functionalities across multiple projects, leading to inefficiencies, resource strain, and ownership conflicts.

Innovation Solution

A system comprising a Code Monitoring Subsystem (CMS) and a Parallel Code Monitoring Subsystem (PCMS) that scans for active jobs, identifies code modification requirements, and notifies developers. The system also includes a Code Resolution Subsystem (CRS) with machine learning capabilities to suggest code options and a non-fungible token (NFT) generator for recording code changes and quality metrics.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If multiple developers work on similar functionalities across multiple projects in parallel and concurrent environments, then development speed and productivity are improved, but work duplication occurs and resource strain increases

Engineering Contradiction:
Improvedevelopment speedVSAvoidresource strain
Core Design Contradiction:
ProductivityVSLoss of energy

Solution Approach 1:

The system implements real-time feedback mechanisms where the code monitoring subsystem continuously tracks code changes across multiple projects and notifies developers of potential duplications. This feedback loop enables developers to adjust their work in real-time, avoiding redundant efforts while maintaining parallel development workflows.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The code monitoring subsystem acts as an intermediary between multiple developers working on similar functionalities. It detects code changes, identifies potential duplications, and coordinates notifications to developers, thereby managing resource allocation and reducing work duplication without hindering parallel development progress.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Productivity

If multiple teams work on similar tasks simultaneously, then overall productivity increases, but it becomes difficult to determine ownership leading to delays or conflicts

Engineering Contradiction:
Improveoverall productivityVSAvoidownership information
Core Design Contradiction:
ProductivityVSLoss of information

Solution Approach 1:

The system provides continuous feedback about code ownership and modification status to all developers. When code changes are detected, the monitoring subsystem notifies relevant developers and tracks ownership information, ensuring that ownership data is preserved and accessible even in concurrent development environments with multiple teams.

Inventive Principle:
Principle #23Feedback

3Reliability

If developers work on similar functionalities across multiple projects, then code quality may improve through diverse perspectives, but work duplication occurs leading to inefficiencies

Engineering Contradiction:
Improvecode qualityVSAvoidtime wasted on duplication
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The code monitoring subsystem implements real-time feedback by detecting code changes across projects and notifying developers of potential duplications. This enables developers to maintain diverse perspectives for code quality while avoiding time-wasting duplication through immediate awareness of concurrent work on similar functionalities.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The system performs preliminary detection of code changes and potential duplications before developers complete their work. By identifying overlapping efforts in advance, the system allows developers to coordinate and avoid duplication while still benefiting from diverse perspectives on code quality.

Inventive Principle:
Principle #10Preliminary action

4Loss of time

If the system monitors and notifies all developers of code modification requirements in real-time, then work duplication is reduced, but system complexity and computational resources increase

Engineering Contradiction:
Improvetime saved from reduced duplicationVSAvoidsystem complexity
Core Design Contradiction:
Loss of timeVSDevice complexity

Solution Approach 1:

The system extracts and monitors only the essential elements needed to detect work duplication - specifically code change patterns and developer notifications. By focusing on extracting only the critical information needed to prevent duplication rather than monitoring all system activities, the complexity is reduced while maintaining effectiveness in reducing time waste.

Inventive Principle:
Principle #2Taking out (Extraction)

Data Source

PatentUS20250130775A1System for reducing work duplication in parallel and concurrent software development environments
Publication Date: 2025.04.24 BANK OF AMERICA CORP
  • US20250130775A1 patent drawing
  • US20250130775A1 patent drawing
  • US20250130775A1 patent drawing

AI summary

Embodiments of the invention provide a comprehensive system for monitoring, evaluating, and managing code changes in a software development environment. The system comprises a Code Monitoring Subsystem (CMS) that continuously scans servers to identify active jobs and issues alerts based on various conditions. A Code Resolution Subsystem (CRS) aids developers in resolving issues and may include a machine learning (ML) subsystem for suggesting code options. The system also features a Parallel Code Monitoring Subsystem (PCMS) that generates atomic versions of code changes for real-time collaboration among developers. Containers corresponding to code changes are created and subjected to specific tests, with quality assessed through smart contracts. A composite value, serving as a metric for assessing a container's susceptibility to errors, is determined for each container. The system enhances code quality, reduces duplication, and facilitates efficient development.