Procedure Dependency Visualization in Form Definitions

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing user interface technologies complicate the understanding of procedure dependencies in form definitions, as they are often stored in non-user readable formats, making it difficult for users to visualize and navigate the relationships between procedures.

Innovation Solution

A method that converts procedure sets from non-user readable formats to user-readable formats, incorporating links to display dependencies, allowing users to view and interact with procedures by selecting hyperlinks, and storing these modified procedures in a non-volatile memory for easy access.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Quantity of substance

If procedures are stored in non-user readable formats, then data storage efficiency is improved, but user accessibility and understanding of procedure dependencies deteriorates

Engineering Contradiction:
Improvedata storage efficiencyVSAvoiduser accessibility
Core Design Contradiction:
Quantity of substanceVSEase of operation

Solution Approach 1:

The patent creates a user-readable copy of the procedure set by converting binary format procedures into a formatted text representation. This copy includes procedural identifiers, names, and dependency relationships in a human-readable format, allowing users to access and understand procedure dependencies without requiring conversion tools, while the original binary storage remains efficient.

Inventive Principle:
Principle #26Copying

Solution Approach 2:

The patent introduces an intermediary layer between the binary procedure storage and user access. This intermediary converts the non-user readable binary format into user-readable text format, enabling users to navigate and understand procedure dependencies through formatted displays without directly interacting with the binary data structure.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Device complexity

If procedure dependencies are not visually linked, then form definition simplicity is maintained, but user navigation and understanding of relationships becomes difficult

Engineering Contradiction:
Improveform definition simplicityVSAvoiduser navigation
Core Design Contradiction:
Device complexityVSEase of operation

Solution Approach 1:

The patent segments the procedure set into individual procedural units, each with its own identifier and name. Dependencies between procedures are represented as separate link elements connecting these segmented units. This segmentation allows the system to maintain simple individual procedure definitions while enabling clear visualization of relationships through explicit links.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent adds a dimensional layer to procedure representation by introducing explicit link elements that connect procedures. This additional dimension of relationship information is superimposed on the basic procedure structure, allowing users to navigate dependencies without complicating the fundamental procedure definitions themselves.

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

3Adaptability or versatility

If additional conversion tools are required, then data format flexibility is improved, but system complexity and user effort increases

Engineering Contradiction:
Improvedata format flexibilityVSAvoidsystem complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent enables the system to perform self-conversion by embedding the conversion capability within the form definition itself. The procedure set includes both binary data and formatted text representations, allowing the system to automatically provide user-readable versions without requiring external conversion tools or additional software components.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS10635455B2Simplifying understanding of procedure dependencies in a form definition
Publication Date: 2020.04.28 ORACLE INT CORP
  • US10635455B2 patent drawing
  • US10635455B2 patent drawing
  • US10635455B2 patent drawing

AI summary

Simplifying understanding of procedure dependencies in a form definition used in user interfaces. In an embodiment, a form definition including a set of procedures (identified by a corresponding identifier) are examined to determine pairs of procedures such that a caller procedure of a pair invokes/refers a called procedure in the pair. For each of pair of procedures determined, a link associated with an identifier identifying the called procedure is included in the caller procedure. The link is designed to display the called procedure in response to a user action associated with the identifier in a display of the caller procedure.