Dynamic Constraint Solver with Placeholder UI for Ambiguity Resolution

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing constraint-based systems fail to effectively distinguish between increasing the required number of instances or connections and specifying characteristics of already inferred instances or connections, leading to ambiguity in user interfaces for dynamic constraint satisfaction problems.

Innovation Solution

A dynamic constraint solver that uses a user interface to display placeholders for missing sub-problems, allowing users to interactively configure required instances or connections, and visually differentiate between known and inferred instances or connections, thereby clarifying the solution state and enabling users to increase the required number of instances or connections.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Loss of information

If a constraint-based system displays all instances and connections in a dynamic constraint satisfaction problem, then the user can see the complete solution state, but it becomes ambiguous whether instances are known or inferred

Engineering Contradiction:
Improveclarity of solution stateVSAvoiduser interface clarity
Core Design Contradiction:
Loss of informationVSEase of operation

Solution Approach 1:

The patent applies local quality by differentiating the visual representation of instances based on their origin. Known instances are displayed with one visual style while inferred instances are displayed with a different visual style (e.g., placeholders). This allows the system to maintain overall information completeness while providing local visual differentiation that eliminates ambiguity about the solution state.

Inventive Principle:
Principle #3Local quality

2Adaptability or versatility

If the system allows users to interactively configure instances, then users can specify characteristics of already inferred instances, but it becomes difficult to distinguish this from increasing the required number of instances

Engineering Contradiction:
Improveuser configuration capabilityVSAvoidsystem complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent introduces placeholders as intermediary elements that mediate between the system's inferred instances and the user's configuration actions. These placeholders serve as a clear visual indicator that an instance can be configured, separating the concept of instance creation from instance configuration. This intermediary representation simplifies the user interface by providing a distinct target for user interaction without increasing overall system complexity.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Ease of operation

If the system uses placeholders to represent missing sub-problems, then users can easily identify what needs configuration, but the system must track and manage placeholder states

Engineering Contradiction:
Improveuser interface clarityVSAvoidsystem management complexity
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The patent implements self-service by designing the placeholder system to automatically manage its own state throughout the constraint solving process. As the solver infures instances or determines cardinalities, placeholders are automatically created, updated, or removed without requiring manual system management. This allows the user interface to remain clear and simple while the system handles the complexity of placeholder state tracking automatically.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS8301582B2Dynamic constraint satisfaction problem solver with sub-problem placeholder
Publication Date: 2012.10.30 ORACLE INT CORP
  • US8301582B2 patent drawing
  • US8301582B2 patent drawing
  • US8301582B2 patent drawing

AI summary

A dynamic constraint solver for solving a constraint satisfaction problem network that includes a plurality of nodes and a plurality of constraints determines a cardinality for a set of sub-problems. The cardinality is a numeric domain that represents the minimum number of instances in a port. The solver determines if a number of identifiable instances of sub-problems is less than the minimum number of instances. The solver then causes a user interface to display the identifiable instances and a placeholder for each instance that is below the minimum number of instances and is not identifiable.