Software Work Item Dependency Detection System

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing software development management systems fail to effectively resolve conflicts by not considering how changes to one file in a work item affect other work items, leading to potential issues in software development processes.

Innovation Solution

A software development management system that includes an acquisition unit to identify files associated with work items, a dependency detection unit to detect dependencies among files, and a determination unit to determine if there are dependency relationships between work items, thereby notifying users of potential conflicts and allowing for proper executable module generation.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If the system only checks for source code conflicts between developers, then the conflict detection process remains simple, but the system fails to detect how file changes in one work item affect other work items

Engineering Contradiction:
Improveconflict detection accuracyVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system segments the conflict detection process into multiple independent modules: an acquisition unit that collects file association information, a dependency detection unit that analyzes file relationships, and a determination unit that identifies work item dependencies. This segmentation allows each module to perform a specific function, improving detection accuracy while keeping individual module complexity manageable.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system performs preliminary dependency detection by analyzing file associations and dependencies before work items are executed. The acquisition unit pre-collects file association information, and the dependency detection unit pre-analyzes relationships between files, so that when conflicts need to be detected, the system already has the necessary information ready, improving both accuracy and efficiency.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If the system analyzes dependencies among all files to determine work item relationships, then the system can detect potential conflicts between work items, but the processing time and computational resources increase

Engineering Contradiction:
Improvework item conflict detection accuracyVSAvoidprocessing time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system performs preliminary dependency analysis by detecting file dependencies in advance and storing this information. When work items need to be checked for conflicts, the system retrieves pre-computed dependency information rather than analyzing all files from scratch, significantly reducing processing time while maintaining detection accuracy.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system creates and maintains a copy of file dependency relationships in a structured format that can be quickly queried. Instead of repeatedly analyzing the actual file systems, the system uses pre-generated dependency models that replicate the essential relationship information, enabling fast conflict detection without time-consuming file system traversals.

Inventive Principle:
Principle #26Copying

Data Source

PatentUS9891911B2Software development work item management system
Publication Date: 2018.02.13 INTERNATIONAL BUSINESS MACHINE CORPORATION
  • US9891911B2 patent drawing
  • US9891911B2 patent drawing
  • US9891911B2 patent drawing

AI summary

A software development management system for use by multiple developers includes an acquisition unit configured to acquire, for each of a plurality of work items each representing a work to change at least one file, designation of a file associated with the work item. A dependency detection unit detects dependencies among a number of files. A determination unit determines, on the basis of the dependencies among the files, whether there is a dependency relationship between at least two work items based on the dependency relationship between the files detected by the dependency detection unit.