Centralized Feature Workflow Feedback for Duplicate Code Detection

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing software development lifecycle tools fail to provide adequate visibility across separate workstreams, leading to unintentional code duplication and inefficiencies due to independent teams developing similar or identical modules without unified oversight, resulting in redundant processing cycles and network communication.

Innovation Solution

A software development lifecycle tool that dynamically determines temporal alerts and dependencies, selectively sending alerts to relevant users based on threshold proximity, reducing unnecessary computing and network resources by consolidating duplicate operations across workflows.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If independent teams develop modules in isolation without unified oversight, then each team can work autonomously and maintain its own development pace, but unintentional code duplication occurs and efficiency decreases

Engineering Contradiction:
ImproveTeam autonomyVSAvoidDevelopment efficiency
Core Design Contradiction:
Ease of operationVSProductivity

Solution Approach 1:

The system implements automated code analysis that continuously monitors development progress across teams and provides feedback about potential duplications. The centralized communication platform sends alerts to teams when similar code patterns are detected, enabling them to adjust their development approach while maintaining autonomy.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

A centralized communication platform acts as an intermediary between independent development teams. It coordinates communication, shares development status information, and alerts teams to potential code duplications without directly controlling their development processes, thus maintaining autonomy while improving efficiency.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Productivity

If teams develop similar modules independently, then each team can focus on its specific tasks without interference, but redundant processing cycles and network communication occur

Engineering Contradiction:
ImproveTask completion rateVSAvoidComputing and network resources
Core Design Contradiction:
ProductivityVSLoss of energy

Solution Approach 1:

The system merges development status information from multiple teams into a centralized view, allowing the system to detect duplicate code patterns across teams. By combining data from different development streams, the system can identify redundancies and alert teams to avoid unnecessary processing.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

Automated analysis tools provide feedback to teams about redundant processing and network communication opportunities. The system monitors code development in real-time and alerts teams when similar operations are being performed independently, enabling resource optimization.

Inventive Principle:
Principle #23Feedback

3Loss of information

If text-based analysis of source code is used to detect duplications, then code similarities can be identified, but unnecessary computing and network resources are consumed and teams are overwhelmed with irrelevant information

Engineering Contradiction:
ImproveCode duplication detectionVSAvoidComputing resources
Core Design Contradiction:
Loss of informationVSUse of energy by moving object

Solution Approach 1:

The system applies different analysis depths to different code segments. Instead of analyzing all code uniformly, it focuses computational resources on areas where duplications are most likely to occur, such as commonly used modules and functions, thereby reducing overall computing resource consumption.

Inventive Principle:
Principle #3Local quality

Solution Approach 2:

The system performs partial analysis by focusing on specific code patterns and metrics that are most indicative of duplication rather than analyzing entire codebases in detail. This selective approach reduces computing resources while maintaining effective duplication detection.

Inventive Principle:
Principle #16Partial or excessive action

4Loss of information

If centralized communication is implemented across all workflows, then visibility across workstreams improves, but irrelevant alerts overwhelm teams and reduce focus on critical dependencies

Engineering Contradiction:
ImproveWorkflow visibilityVSAvoidTeam focus
Core Design Contradiction:
Loss of informationVSEase of operation

Solution Approach 1:

The communication system provides differentiated information to different teams based on their specific workflows and contexts. Alerts are tailored to each team's development stage and type of work, ensuring that each team receives relevant information without being overwhelmed by unrelated updates from other teams.

Inventive Principle:
Principle #3Local quality

Solution Approach 2:

The system implements intelligent alerting that provides feedback to teams only when it is relevant to their current work. By analyzing workflow context and development stage, the system filters out irrelevant alerts and delivers targeted communications about critical dependencies and potential issues.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS12554484B2Systems and methods providing centralized communication across feature programming workflows
Publication Date: 2026.02.17 CITIBANK N A
  • US12554484B2 patent drawing
  • US12554484B2 patent drawing
  • US12554484B2 patent drawing

AI summary

Systems and methods that provide status indications in response to detection of one or more duplicate operations between a first software programming workflow and a second software programming workflow are disclosed herein. By selectively generating status indications on display devices associated with designated users during separate software programming workflows as described, systems can be configured to accurately determine when redundant operations are to be executed across different software programming workflows and provide indications that reduce or eliminate the need for subsequent, duplicative operations to be executed when developing corresponding portions of different software programming workflows.