Object-Oriented Scripting Tool with XML Parser and Type Table

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing scripting tools lack object-oriented features, making it difficult to efficiently manage and extend software development and domain management tasks, leading to inefficiencies in code reuse and maintenance.

Innovation Solution

An XML-based scripting tool is enhanced with object-oriented features, allowing for the definition of scripting classes and methods using tags, enabling encapsulation, extension, and reuse of scripts, similar to object-oriented programming languages like Java, with a parser and type definition table to support object-oriented syntax.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If traditional scripting tools are used, then simplicity and ease of use are maintained, but code reuse and extensibility are limited

Engineering Contradiction:
Improvecode reuse and extensibilityVSAvoidscripting tool complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent segments scripting functionality into reusable class components that can be independently defined, instantiated, and extended. Scripts are divided into modular units (classes) with specific functionalities, allowing selective reuse and combination without requiring complete script rewriting.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent creates universal scripting classes that can serve multiple purposes through parameterization and inheritance. A single class definition can be extended to create multiple specialized scripts for different tasks, making the scripting tool versatile while maintaining a core reusable framework.

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

2Ease of manufacture

If object-oriented features are added to scripting tools, then code organization and reuse improve, but parser and type management complexity increases

Engineering Contradiction:
Improvecode organization and maintenanceVSAvoidparser and type definition complexity
Core Design Contradiction:
Ease of manufactureVSDevice complexity

Solution Approach 1:

The patent performs preliminary actions by pre-defining class templates and type definitions before script execution. The parser is prepared with knowledge of expected class structures and type hierarchies in advance, allowing it to efficiently parse and validate scripts without complex runtime analysis.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent introduces a type definition table as an intermediary between the parser and script execution. This table stores pre-processed type information and acts as a mediator that simplifies the parser's workload by providing ready-to-use type validation rules and class hierarchies.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Productivity

If generic scripting classes are created for reuse, then development efficiency improves, but instance management complexity increases

Engineering Contradiction:
Improvesoftware development efficiencyVSAvoidinstance pool management complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent implements an instance pool that creates and manages copies of generic scripting class templates. When a script is needed, the system copies the relevant class definition from the template and instantiates it with specific parameters, allowing rapid script generation without manual rewriting while maintaining centralized template management.

Inventive Principle:
Principle #26Copying

Data Source

PatentUS9569181B2System and method for supporting an object oriented scripting tool
Publication Date: 2017.02.14 ORACLE INT CORP
  • US9569181B2 patent drawing
  • US9569181B2 patent drawing
  • US9569181B2 patent drawing

AI summary

A system and method can support an object-oriented scripting tool. The system can comprise a parser that operates to parse a document that specifies a software class in a scripting language using one or more tags that are defined in a markup language environment. Furthermore, the system can include a type definition table that includes a plurality of type definitions, wherein this type definition table operates to use a tag name of a said tag as a key that is associated with a type definition. Additionally, the system can include an instance pool that operates to store one or more instances of the software class for the object-oriented scripting tool.