AUF XML Compiler for Automated Form Generation

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

The existing software systems for creating and updating forms, particularly in accounting and payroll software, face significant challenges due to their monolithic architecture, requiring extensive and skilled manual code modifications, lengthy verification processes, and frequent updates, which are time-consuming and error-prone, especially when new data types and record types need to be incorporated.

Innovation Solution

The implementation of a standardized system using AUF files and tools like the AUF Builder, which allows for the creation and modification of record types and data types independently of the main program code, enabling automated population of form fields with standardized data and real-time calculations, and facilitating the update of forms without altering the core code architecture.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If forms are updated frequently in a monolithic software system, then the software can adapt to changing requirements, but the time and skill required for code modification increases significantly

Engineering Contradiction:

Improveability to update formsVSAvoidtime for code modification

Core Design Contradiction:

Adaptability or versatilityVSLoss of time

Solution Approach 1:

The patent segments the monolithic codebase by introducing a separate form definition layer (XML files) that is independent from the core application code. This allows forms to be defined, stored, and modified separately without requiring changes to the main program code, thereby reducing modification time and skill requirements while maintaining adaptability.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The patent introduces an intermediary form definition language (XML-based AUF specification) that acts as a mediator between the core software system and the form representations. This intermediary layer allows form updates to occur through configuration file changes rather than direct code modifications, significantly reducing the time and expertise needed for form updates.

Inventive Principle:

Principle #24Intermediary (Mediator)

2Adaptability or versatility

If extensive code modifications are made to support new forms, then the software can accommodate new requirements, but the risk of introducing errors and bugs increases

Engineering Contradiction:

Improveability to add new formsVSAvoiderror-free operation

Core Design Contradiction:

Adaptability or versatilityVSReliability

Solution Approach 1:

By segmenting form definitions into separate XML configuration files, the patent isolates form-specific changes from the core application code. This segmentation ensures that modifications to new forms or existing forms do not propagate errors into the stable core codebase, thereby maintaining reliability while enabling adaptability.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The patent uses template-based form definitions where new forms can be created by copying and modifying existing form templates. This approach reduces the risk of errors by providing proven, validated form structures as starting points, rather than creating forms from scratch or modifying core code extensively.

Inventive Principle:

Principle #26Copying

3Manufacturing precision

If manual code revision is required for form updates, then precise control over changes is achieved, but the expertise and skill level required increases

Engineering Contradiction:

Improvecontrol over code changesVSAvoidease of form updates

Core Design Contradiction:

Manufacturing precisionVSEase of operation

Solution Approach 1:

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

The system provides self-service capabilities through automated form generation and validation tools that work with the XML configuration files. These tools automatically handle code generation, validation, and compilation, reducing the need for manual code revision while maintaining precise control over changes through the structured XML format.

Inventive Principle:

Principle #25Self-service

4Ease of operation

If the code is distributed across multiple locations, then accessibility is improved, but the complexity of updating and distributing code changes increases

Engineering Contradiction:

Improveaccessibility of codeVSAvoidcomplexity of code distribution

Core Design Contradiction:

Ease of operationVSDevice complexity

Solution Approach 1:

By segmenting form definitions into separate, location-independent XML files, the patent enables form data to be distributed across multiple locations without creating synchronization complexity. The core application code remains centralized and stable, while form configurations can be independently managed and distributed, simplifying the overall code distribution architecture.

Inventive Principle:

Principle #1Segmentation

Data Source

PatentUS11861302B2AUF XML specification compiler

Publication Date: 2024.01.02 AATRIX SOFTWARE

AI summary

The present invention relates to a method and apparatus for automating the process of form creation. In particular, the present invention relates to a method and apparatus for implementing an independent and standardized way to create new data records and data types, and amend existing data records and types, in a computerized form creation and processing system.