Declarative Wizard UIs via Metadata for Business Logic

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Business applications require extensive user training due to complex user interfaces (UIs) that end users cannot effectively interact with without understanding the underlying logic, and existing UI wizards require procedural programming, making changes costly and inefficient.

Innovation Solution

A declarative tool for creating wizard-style UIs that allows intermediate users to design business tasks without coding, using a graphical editor to specify steps and execution flow, converting this into metadata for runtime processing, enabling guided user interactions through a sequence of task-specific UI views.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If procedural programming is used to create UI wizards, then the wizards can guide users through complex business logic, but the development complexity and maintenance cost increase significantly

Engineering Contradiction:

Improvewizard guidance accuracyVSAvoiddevelopment complexity

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The patent replaces procedural programming (mechanical system of code writing) with a declarative metadata-based system. Instead of requiring developers to write procedural code to create wizards, the system uses metadata definitions that automatically generate the wizard interface and logic, thereby reducing development complexity while maintaining guidance accuracy.

Inventive Principle:

Principle #28Mechanics substitution (Replace mechanical system)

Solution Approach 2:

The patent introduces metadata as an intermediary layer between business logic and UI implementation. The metadata serves as a mediator that translates business requirements into wizard interfaces without requiring direct procedural programming, thus reducing development complexity while preserving the ability to guide users through complex logic.

Inventive Principle:

Principle #24Intermediary (Mediator)

2Ease of operation

If extensive user training is provided for complex UIs, then users can effectively interact with the system, but the time and cost investment increase

Engineering Contradiction:

Improveuser interaction effectivenessVSAvoidtraining time

Core Design Contradiction:

Ease of operationVSLoss of time

Solution Approach 1:

The patent enables the system to serve itself by automatically generating contextual guidance and wizard interfaces that adapt to user needs without requiring external training interventions. The metadata-driven wizard system provides self-service guidance to users, reducing the need for extensive formal training while maintaining effective user interaction.

Inventive Principle:

Principle #25Self-service

3Adaptability or versatility

If business logic changes are made to existing wizards, then the system adapts to new requirements, but the modification cost and release cycles increase

Engineering Contradiction:

Improvebusiness logic adaptabilityVSAvoidmodification ease

Core Design Contradiction:

Adaptability or versatilityVSEase of manufacture

Solution Approach 1:

The patent makes the wizard system dynamic by using metadata that can be modified without changing the underlying code structure. Business logic changes can be made by updating metadata definitions rather than rewriting procedural code, enabling flexible adaptation to new requirements while reducing modification costs and accelerating release cycles.

Inventive Principle:

Principle #15Dynamics

4Reliability

If experienced developers create UI wizards using procedural programming, then the wizards can handle complex business logic, but the productivity of the development process decreases

Engineering Contradiction:

Improvewizard functionalityVSAvoiddevelopment productivity

Core Design Contradiction:

ReliabilityVSProductivity

Solution Approach 1:

The patent replaces the mechanical system of procedural programming with an automated metadata-driven approach. This substitution eliminates the need for experienced developers to manually code wizard logic, thereby increasing development productivity while maintaining reliable wizard functionality through automatic metadata processing.

Inventive Principle:

Principle #28Mechanics substitution (Replace mechanical system)

Solution Approach 2:

The system performs self-service by automatically generating wizard interfaces and logic from metadata definitions. This automation reduces the need for manual programming effort, increasing development productivity while ensuring consistent and reliable wizard functionality through systematic metadata processing.

Inventive Principle:

Principle #25Self-service

Data Source

PatentUS8255813B2Declarative task-based user interfaces

Publication Date: 2012.08.28 ORACLE INT CORP

AI summary

A method for building wizard-style user interfaces (UIs) for a business task is disclosed. The method includes receiving metadata at a computer system, where the metadata comprises information regarding the business task, generating an analysis by analyzing the metadata, generating user guidance information, and executing flow and business logic of the business task. The user guidance information is with regard to the business task, and the user guidance information is based on the analysis.