Rule-Based Binding via GUI for Data Model Integration

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Integrated development environments (IDEs) require extensive coding to bind data view components to data model properties, making workflows complex and error-prone, and limiting user productivity.

Innovation Solution

A graphical user interface (GUI) is used to associate data model properties with data view components, allowing users to specify access mode attributes and generate rules through drag-and-drop operations, menu selections, or mouse inputs, reducing the need for coding by creating bi-directional bindings and invoking web services to populate data model properties.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If extensive coding is used to bind data view components to data model properties in IDEs, then the binding functionality is achieved, but the workflow complexity increases and user productivity decreases

Engineering Contradiction:
Improveease of binding data componentsVSAvoidworkflow complexity
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The patent introduces a visual binding mechanism that acts as an intermediary between data view components and data model properties. Instead of requiring direct coding, the system provides a graphical interface where users can establish bindings through visual operations, thereby simplifying the interaction and reducing workflow complexity while maintaining the binding functionality

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent replaces the mechanical coding process with a visual interaction system. Users interact with the IDE through graphical elements and visual bindings rather than writing code manually. This substitution eliminates the need for extensive programming while achieving the same binding results, thereby improving ease of operation and reducing complexity

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

2Manufacturing precision

If extensive coding is required to create bindings, then precise control over data flow is achieved, but error-proneness increases and development time extends

Engineering Contradiction:
Improvebinding precisionVSAvoiderror rate
Core Design Contradiction:
Manufacturing precisionVSReliability

Solution Approach 1:

The visual binding mechanism enables the system to automatically manage and validate bindings without requiring manual coding. The IDE handles the complexity of data flow control automatically, reducing the likelihood of human errors while maintaining precise control over the binding relationships between data components and model properties

Inventive Principle:
Principle #25Self-service

3Adaptability or versatility

If users need programming experience to create bindings, then complex binding scenarios can be handled, but user accessibility is limited

Engineering Contradiction:
Improvebinding capabilityVSAvoiduser accessibility
Core Design Contradiction:
Adaptability or versatilityVSEase of operation

Solution Approach 1:

The patent segments the binding creation process into simple, discrete visual steps that users can follow without programming knowledge. The complex binding scenario handling is broken down into manageable graphical operations, making the system accessible to users with varying technical expertise while maintaining the ability to handle complex binding requirements

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS8909585B2Rule-based binding
Publication Date: 2014.12.09 ADOBE INC
  • US8909585B2 patent drawing
  • US8909585B2 patent drawing
  • US8909585B2 patent drawing

AI summary

Methods, systems, and apparatus, including computer programs encoded on a computer storage medium, for rule-based binding. In one aspect, a method includes receiving first input to a graphical user interface (GUI) associating a property of a data model presented in the GUI with a data view component of a document presented in the GUI, wherein a change to a value of the data view component is reflected in a value of the property in the data model when the document is used in a workflow, and wherein the workflow is a logical sequence of documents, including the document, that is processed according to the logical sequence such that values for one or more data view components associated with the documents are received.