Component Debugging via Input Package Isolation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing debugging assistance technologies are inadequate for component-set whole processes due to the complexity of managing input values and dependencies between components, especially in large systems like data centers and cloud environments, where understanding which input values depend on others is difficult without expert knowledge.

Innovation Solution

A computer system exports input and output packages for each component, allowing users to import necessary input values directly into the debugging target component without executing preceding components, facilitating the understanding of input value dependencies and influences.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If all input values are stored in execution order for debugging, then debugging can be performed, but the procedure becomes complicated and time-consuming as program size increases

Engineering Contradiction:
Improvedebugging capabilityVSAvoidprocedure complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent segments the input values into packages associated with specific components rather than storing all input values in execution order. Each component has its own input package that can be independently managed and imported during debugging, reducing the overall complexity of the debugging procedure.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent extracts only the necessary input values for a specific component during debugging, rather than requiring all input values to be stored in order. The input package mechanism allows extraction of only relevant input values, simplifying the debugging process especially for large programs.

Inventive Principle:
Principle #2Taking out (Extraction)

2Loss of information

If input values of all components are managed in execution order, then complete debugging information is available, but it becomes difficult to understand dependencies without expert knowledge

Engineering Contradiction:
Improvedependency informationVSAvoiduser accessibility
Core Design Contradiction:
Loss of informationVSEase of operation

Solution Approach 1:

The patent introduces input packages as intermediary structures that mediate between the execution order and the debugging process. These packages organize input values by component, making dependency relationships explicit and accessible to users without requiring expert knowledge of execution order.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent changes the organizational dimension from execution order (temporal sequence) to component-based grouping (structural organization). This dimensional change makes dependency information more visible and easier to understand, as input values are now grouped by their associated components rather than by execution sequence.

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

3Reliability

If components are executed in order for debugging, then complete process flow is verified, but debugging time increases significantly for large component sets

Engineering Contradiction:
Improveprocess verificationVSAvoiddebugging time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent applies partial action by importing only the necessary input packages for the component being debugged, rather than executing or loading all components in order. This allows debugging to focus on specific components while still verifying necessary dependencies, significantly reducing debugging time for large component sets.

Inventive Principle:
Principle #16Partial or excessive action

Solution Approach 2:

The patent performs preliminary organization of input values into packages during the component definition phase, so that during debugging only the relevant packages need to be imported. This preliminary structuring eliminates the need to execute all preceding components, reducing debugging time while maintaining verification reliability.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS10235270B2Method for assisting with debugging, and computer system
Publication Date: 2019.03.19 HITACHI VANTARA LTD
  • US10235270B2 patent drawing
  • US10235270B2 patent drawing
  • US10235270B2 patent drawing

AI summary

In testing a component-set whole process which includes a plurality of components and in which the order of execution of the plurality of components is defined, a computer system exports, to a storage resource, an input package for at least one component to be executed. Each of the plurality of components is a module of a significant process as a set of one or more processing steps and independent of any other components. Each input package includes an input value of a component that corresponds to the input package. The computer system imports an exported input package of a component to be debugged into the component to be debugged in order to execute the component to be debugged, without executing a component the order of which precedes the order N (where N is a natural number) of the component to be debugged.