Micro-Component Process Visualization Toolkit API

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Developers face limitations when creating custom process visualizations for applications like web performance measurement and project management, as existing pre-developed components offer limited customizability and functionality, forcing them to choose between using pre-developed solutions with restrictions or developing from scratch.

Innovation Solution

A process visualization toolkit with micro-components and an API that allows developers to create customizable and interactive visualizations by selecting and combining micro-components, setting display properties, and initializing time-related properties, enabling unlimited functionality and rendering options without starting from scratch.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Loss of time

If a pre-developed bar graph component is used, then development time is reduced, but customization capability is limited

Engineering Contradiction:
Improvedevelopment timeVSAvoidcustomization capability
Core Design Contradiction:
Loss of timeVSAdaptability or versatility

Solution Approach 1:

The bar graph component is divided into multiple independent micro-components (bar container, bar, label, icon, tooltip) that can be selectively combined. Each micro-component has its own API and can be configured independently, allowing developers to build customized visualizations by selecting only the needed components rather than using a monolithic pre-developed solution.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The micro-component framework creates a universal base component that can serve multiple visualization needs. The same bar component can be used in different contexts (performance monitoring, project management Gantt charts, scheduling) with different configurations, eliminating the need for separate pre-developed components for each application scenario.

Inventive Principle:
Principle #6Universality (Multi-functionality)

2Productivity

If a pre-developed Gantt chart component is purchased, then implementation speed increases, but configuration flexibility is restricted

Engineering Contradiction:
Improveimplementation speedVSAvoidconfiguration flexibility
Core Design Contradiction:
ProductivityVSAdaptability or versatility

Solution Approach 1:

The Gantt chart is constructed from segmented micro-components that can be independently configured. Developers can select specific micro-components (timeline, task bars, milestone markers) and configure them through a unified API, achieving both rapid implementation and full configuration flexibility without being constrained by pre-packaged options.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The component configuration is made dynamic and adjustable at runtime. Developers can modify display properties, data bindings, and component compositions after initialization through the API, allowing the Gantt chart to adapt to different project management needs without requiring a complete redesign or selection of different pre-packaged solutions.

Inventive Principle:
Principle #15Dynamics

3Adaptability or versatility

If visualization is developed from scratch, then unlimited functionality is achieved, but development time increases significantly

Engineering Contradiction:
ImprovefunctionalityVSAvoiddevelopment time
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The micro-components and their APIs are pre-developed and ready-to-use, providing common functionality that would otherwise require implementation from scratch. Developers can leverage these pre-built components (bar rendering, label positioning, tooltip display) while still achieving unlimited customization by combining and configuring them according to specific needs, significantly reducing development time compared to building everything from scratch.

Inventive Principle:
Principle #10Preliminary action

4Ease of manufacture

If existing technologies are used to define custom visualization, then development effort is reduced, but rendering control is limited

Engineering Contradiction:
Improvedevelopment effortVSAvoidrendering control
Core Design Contradiction:
Ease of manufactureVSDevice complexity

Solution Approach 1:

The micro-component API acts as an intermediary layer between simple component selection and complex rendering control. Developers interact with the standardized API to configure and control rendering of multiple micro-components, gaining fine-grained control over visualization appearance and behavior without directly managing complex rendering code, thus balancing ease of development with rendering control.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS10289388B2Process visualization toolkit
Publication Date: 2019.05.14 ORACLE INT CORP
  • US10289388B2 patent drawing
  • US10289388B2 patent drawing
  • US10289388B2 patent drawing

AI summary

A process visualization toolkit includes micro-component templates and application programmer's interfaces (APIs) to build a process visualization and show it in a graphical user interface (GUI) on a computer screen. Micro-components share compatible display properties that relate to process visualization. The APIs allow customization, but also allow mixing micro-components with components in standard technologies, such as HTML. Shared properties include display settings, position settings, time settings, and the time type (calendar time, work time, relative time). A time axis micro-component includes functions to convert time to pixel position, and pixel position to time, based on the time type. Developers add functionality and interactive functions using a standard language such as JavaScript, and may customize display rendering using, for example, cascaded stylesheets.