Code Ownership Anomaly Detection via Organizational Mapping

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional static and dynamic code analysis techniques fail to detect issues related to code ownership and organizational structure, leading to inefficiencies such as resource misallocation, duplicate code, and increased build times due to ownership inconsistencies and architecture violations.

Innovation Solution

A computer-implemented method generates data structures indicating software module dependencies and organizational information to detect anomalies in code assignments, allowing for automatic remediation of ownership issues by reassigning teams or modifying code structures.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Measurement precision

If conventional static code analysis techniques are used to analyze source code, then programming issues can be detected, but issues related to code organization and maintenance by the organization cannot be detected

Engineering Contradiction:
Improvedetection capabilityVSAvoiddetection scope
Core Design Contradiction:
Measurement precisionVSAdaptability or versatility

Solution Approach 1:

The patent merges static code analysis with organizational structure analysis by integrating code dependency graphs with organizational charts. This combination allows the system to detect both programming issues and organizational maintenance issues within a unified analysis framework, resolving the contradiction between detection precision and detection scope.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The analysis system is designed to perform multiple functions: analyzing code structure, tracking dependencies, mapping to organizational units, and detecting various types of anomalies. This multi-functional approach enables the system to address both traditional code quality issues and organizational maintenance issues, expanding detection versatility while maintaining precision.

Inventive Principle:
Principle #6Universality (Multi-functionality)

2Productivity

If code ownership is not properly aligned with organizational structure, then development may proceed without coordination, but resource misallocation and duplicate code occur

Engineering Contradiction:
Improvedevelopment speedVSAvoidresource allocation efficiency
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The system establishes a feedback mechanism by continuously monitoring code ownership assignments against organizational structure and automatically detecting misalignments. This feedback loop enables timely corrections to resource allocation, preventing duplicate code and ensuring efficient utilization while maintaining development productivity.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The system performs preliminary analysis of code dependencies and organizational structure to identify potential ownership conflicts before they manifest as problems. By proactively detecting misalignments between code modules and organizational units, the system prevents resource misallocation and duplicate code creation while allowing development to proceed smoothly.

Inventive Principle:
Principle #10Preliminary action

3Stability of the object's composition

If code dependencies are not tracked against organizational structure, then module independence is maintained, but build times increase due to ownership inconsistencies

Engineering Contradiction:
Improvemodule independenceVSAvoidbuild time
Core Design Contradiction:
Stability of the object's compositionVSLoss of time

Solution Approach 1:

The system introduces an intermediary layer that maps code dependencies to organizational structure. This intermediary mapping enables the system to track ownership relationships without disrupting module independence, allowing for optimized build processes that respect both modular architecture and organizational boundaries, thereby reducing build times.

Inventive Principle:
Principle #24Intermediary (Mediator)

4Adaptability or versatility

If manual code ownership assignment is used, then flexibility in assignment is maintained, but anomalies in code assignments go undetected

Engineering Contradiction:
Improveassignment flexibilityVSAvoidanomaly detection capability
Core Design Contradiction:
Adaptability or versatilityVSDifficulty of detecting and measuring

Solution Approach 1:

The system implements self-service anomaly detection by automatically comparing code ownership assignments against organizational structure and dependency relationships. This automated self-check mechanism maintains assignment flexibility while continuously detecting anomalies, eliminating the need for manual verification while preserving managerial flexibility in ownership assignment.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS20240248691A1Detecting software code anomalies based on organizational information
Publication Date: 2024.07.25 DELL PROD LP
  • US20240248691A1 patent drawing
  • US20240248691A1 patent drawing
  • US20240248691A1 patent drawing

AI summary

Methods, apparatus, and processor-readable storage media for detecting software code anomalies based on organizational information are provided herein. An example computer-implemented method includes generating at least one first data structure comprising information indicating dependencies between software modules associated with a software project of an organization; determining portions of the software project that are assigned to respective groups of individuals associated with the organization based at least in part on a second data structure, where the second data structure includes information indicating an organizational structure; detecting one or more anomalies in the assignment of the portions of the software project corresponding to the dependencies in the first data structure using one or more anomaly criteria, with respect to the information in the second data structure; and automatically causing one or more actions to be performed to mitigate at least a portion of the one or more anomalies.