Software Artifact Evaluation via Issue Tracking and Source Control

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional systems lack the ability to effectively identify, evaluate, and interpret the quality and stability of software artifacts, relying on machine-level analysis that does not consider long-term impact and limited in scope, failing to provide comprehensive insights for developers choosing from a vast array of open-source software.

Innovation Solution

A computer system that gathers and combines issue tracking and source code management information to assess the quality and stability of software artifacts by analyzing their historical data, including issue frequency, severity, and commit periodicity, providing a comprehensive evaluation and interpretation of artifact quality.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Measurement precision

If machine-level analysis based on source code metrics is used to evaluate artifact quality, then quantifiable code checks can be performed, but long-term impact and historical quality trends cannot be assessed

Engineering Contradiction:
Improvecode quality measurementVSAvoidhistorical quality information
Core Design Contradiction:
Measurement precisionVSLoss of information

Solution Approach 1:

The patent combines machine-level source code analysis with human-level historical evaluation data from issue tracking systems and code repositories. This merging allows the system to simultaneously perform quantifiable code checks and assess long-term quality trends, resolving the contradiction between precise measurement and information loss.

Inventive Principle:
Principle #5Merging (Combining)

2Reliability

If comprehensive historical data from multiple sources is collected to evaluate artifact quality, then better insights can be provided, but system complexity increases

Engineering Contradiction:
Improveartifact quality evaluationVSAvoidevaluation system
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent introduces an intermediary evaluation system that collects data from multiple sources (issue tracking systems, code repositories, build systems) and processes it through standardized metrics. This intermediary layer simplifies the complexity by providing a unified interface while maintaining comprehensive data collection for reliable artifact quality evaluation.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Reliability

If detailed historical analysis of issues and commits is performed, then artifact stability can be determined, but evaluation time increases

Engineering Contradiction:
Improveartifact stability assessmentVSAvoidevaluation time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent performs preliminary actions by continuously collecting and pre-processing historical data from issue tracking and code repositories. This allows the system to have evaluation-ready data prepared in advance, enabling rapid stability assessment when needed without performing time-consuming analysis from scratch.

Inventive Principle:
Principle #10Preliminary action

4Ease of operation

If traditional single-score evaluation methods are used, then simple artifact assessment can be provided, but granular quality insights are lost

Engineering Contradiction:
Improveartifact evaluationVSAvoidquality detail information
Core Design Contradiction:
Ease of operationVSLoss of information

Solution Approach 1:

The patent segments the overall artifact quality evaluation into multiple dimensions including code quality metrics, issue frequency, commit activity, and stability indicators. This segmentation provides granular quality insights while maintaining ease of operation by presenting structured, multi-faceted evaluation results that can be selectively analyzed.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS9141378B2Method and system for evaluating a software artifact based on issue tracking and source control information
Publication Date: 2015.09.22 SONATYPE INC
  • US9141378B2 patent drawing
  • US9141378B2 patent drawing
  • US9141378B2 patent drawing

AI summary

A computer system includes a transceiver and a processor that is cooperatively operable with the transceiver. The processor gathers, over the transceiver, (i) issue tracking information stored in an issue tracking storage system, the issue tracking information having a history of issues filed against a plurality of artifacts, and (ii) source code management information stored in a source code management storage system, the source code management information having a history of code changes committed against another plurality of artifacts. The processor checks a combined history of the issue tracking information and the source code management information for a history of issues filed against an artifact and a history of commits and corresponding source code changes committed against the artifact. The processor provides an interpretation of the current state of the artifact based on the combined history of the issue tracking information and source code management information about the artifact.