Style Component System for Data Model Validation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current software engineering approaches lack efficient methods for defining and utilizing style components in data models, which limits the ability to validate data properties and provide user interface aspects across multiple entities and languages.

Innovation Solution

A system and method for providing modeled components that include a styles designer module for defining style components, which can be specified at both the model and property levels, allowing for validation, message display, and masking expressions, enabling consistent user interface aspects and multi-language support.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If style components are defined at multiple levels (model and property), then user interface consistency and reusability are improved, but system complexity increases

Engineering Contradiction:
Improveuser interface consistencyVSAvoidsystem complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The style component system is segmented into two hierarchical levels: model-level styles that define general UI aspects for entire entities, and property-level styles that customize specific property behaviors. This segmentation allows independent definition and reuse of style components at appropriate granularities, achieving UI consistency without requiring a monolithic complex system.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

Style components are designed as universal, reusable elements that can be applied across multiple entities and properties. A single style component defined at the model level can be referenced by multiple properties, and property-level styles can inherit from model-level styles, creating a multi-functional system that reduces overall complexity through reuse.

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

2Reliability

If validation expressions are applied at property level, then data integrity is improved, but processing time increases

Engineering Contradiction:
Improvedata integrityVSAvoidprocessing time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

Validation expressions are defined and prepared in advance as reusable style components rather than being evaluated dynamically each time data is processed. The validation logic is pre-compiled into the style component structure, allowing for faster execution during data validation operations while maintaining comprehensive data integrity checks.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS8972927B2Method and system for providing modeled components
Publication Date: 2015.03.03 ADOBE INC
  • US8972927B2 patent drawing
  • US8972927B2 patent drawing
  • US8972927B2 patent drawing

AI summary

A system for providing modeled components is described. An example system comprises a request detector, an entity component, a style component, and a property module. The request detector may be configured to receive requests to create modeled components. The entity builder may be configured to create entities associated with models. The styles designer may be configured to create style components. A style component defines a user interface to be applied to a property of an entity in a modeled component. The property module may be configured to associate a style component with one or more properties of one or more entities.