Decoupling Validation Logic from Software Applications

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing software applications face challenges in efficiently managing data validation, as it is often tightly coupled with the application itself, making it difficult to change validation rules in response to evolving business requirements without modifying the software.

Innovation Solution

A rule-driven validation framework that decouples validation logic from the software application, using a validation rule book and manager to validate data values entered into input fields, allowing for changes in validation rules without altering the application.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If data validation is tightly coupled to the software application, then the validation logic is integrated and easy to implement, but the software application cannot adapt to changing business requirements without modification

Engineering Contradiction:
Improveadaptability to changing business requirementsVSAvoidsystem complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent segments the validation system into separate components: a validation rule book containing validation rules, a validation manager that executes the rules, and the software application that uses the validation services. This segmentation allows the validation logic to be independently modified without changing the application code, thereby improving adaptability while managing complexity through modular design.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent extracts the validation logic from the software application and places it in an external validation rule book. The validation rules are stored separately and can be modified without altering the application itself. This extraction enables the system to adapt to changing business requirements by simply updating the validation rules rather than modifying the application code.

Inventive Principle:
Principle #2Taking out (Extraction)

2Adaptability or versatility

If data validation is hard coded into the software application, then the validation is reliable and consistent, but any change in validation requirements requires software modification and redeployment

Engineering Contradiction:
Improveflexibility of validation rulesVSAvoidease of maintenance
Core Design Contradiction:
Adaptability or versatilityVSEase of manufacture

Solution Approach 1:

The patent implements dynamic validation rules that can be modified at runtime without requiring software re compilation or redeployment. The validation rule book stores validation criteria in a flexible format that allows business users to update rules as needed. This dynamic approach provides both flexibility for changing requirements and ease of maintenance, as updates can be made without involving software developers.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The patent introduces a validation manager as an intermediary between the software application and the validation rules. This mediator layer allows the application to remain unchanged while the validation rules in the rule book can be easily modified. The validation manager handles the complexity of rule management, providing ease of maintenance while maintaining flexibility.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Ease of operation

If validation rules are stored externally in a validation rule book, then changes can be made without modifying the application, but the system requires additional components and infrastructure

Engineering Contradiction:
Improveease of updating validation rulesVSAvoidvalidation system architecture
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The patent creates a universal validation framework that can be applied across multiple software applications through a common validation manager and rule book infrastructure. This multi-functional system handles various types of validation rules (numeric, date/time, custom business rules) through a unified architecture. While the initial setup requires additional components, the universal design reduces long-term complexity by providing a standardized approach that can be reused across different applications.

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

Data Source

PatentUS9292477B1Method and system for data validation
Publication Date: 2016.03.22 SUN MICROSYSTEMS INC
  • US9292477B1 patent drawing
  • US9292477B1 patent drawing
  • US9292477B1 patent drawing

AI summary

A method for validating a data value, the method including receiving a data value entered into an input field of a software application, obtaining a validation rule corresponding to the input field from a validation rule book, executing the validation rule to determine a validation result, and returning the validation result to the software application.