MDA Transformation Engine Using Configuration Files for WSDM Compliance

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The complexity of transforming a Platform Independent Model (PIM) into a Platform Specific Model (PSM) in Model Driven Architecture (MDA) systems is a challenging step, requiring sophisticated transformation engines and tools like Model Wizard, AndroMDA, and Muse, which often struggle to efficiently abstract implementation-independent models into implementation-specific models, especially in generating WSDM-compliant interfaces.

Innovation Solution

A transformation engine system that utilizes Model Wizard, AndroMDA, and Muse to abstract UML models into WSDM-compliant interfaces by defining managed resources and capabilities through configuration files and template engines like Velocity, enabling the generation of WSDL and XSD files that expose managed resources and capabilities as Web Services Distributed Management (WSDM) compliant endpoints.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If sophisticated transformation engines and tools are used to transform PIM to PSM, then the transformation capability is improved, but the device complexity increases

Engineering Contradiction:
Improvetransformation capabilityVSAvoidtransformation engine complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent introduces configuration files as intermediary artifacts that mediate between the PIM and PSM transformation process. These configuration files contain transformation rules and metadata that guide the transformation engine, reducing the complexity of the engine itself while maintaining versatile transformation capabilities. The configuration files act as a bridge, allowing complex transformations to be defined in a structured, manageable format rather than requiring complex built-in engine logic.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Manufacturing precision

If detailed transformation rules are defined to generate WSDM-compliant interfaces, then the manufacturing precision is improved, but the ease of manufacture deteriorates

Engineering Contradiction:
Improveinterface compliance precisionVSAvoidtransformation process ease
Core Design Contradiction:
Manufacturing precisionVSEase of manufacture

Solution Approach 1:

The patent applies preliminary action by pre-defining transformation rules, metadata formats, and WSDM-compliance specifications in configuration files before the actual transformation process. These pre-prepared configuration files contain all the necessary rules for generating WSDM-compliant interfaces, allowing the transformation engine to execute straightforwardly without requiring complex real-time decision-making. This preliminary preparation maintains high precision in interface compliance while simplifying the actual transformation execution.

Inventive Principle:
Principle #10Preliminary action

3Ease of operation

If the transformation process is simplified by using configuration files, then the ease of operation is improved, but the productivity may deteriorate

Engineering Contradiction:
Improvetransformation operation easeVSAvoidtransformation speed
Core Design Contradiction:
Ease of operationVSProductivity

Solution Approach 1:

The patent uses configuration files as templates or copies of transformation rules that can be reused across different transformation tasks. Instead of defining transformation rules from scratch for each PIM-to-PSM transformation, the system copies and adapts existing configuration file templates, significantly improving ease of operation. The configuration files serve as reusable blueprints that maintain transformation quality while reducing the manual effort and time required for each transformation operation.

Inventive Principle:
Principle #26Copying

Data Source

PatentUS8127270B1Abstracting transformation for model driven architecture
Publication Date: 2012.02.28 CISCO TECHNOLOGY INC
  • US8127270B1 patent drawing
  • US8127270B1 patent drawing
  • US8127270B1 patent drawing

AI summary

An example embodiment of the present invention provides a process for abstracting an implementation-independent model to an implementation-specific model during transformation in a MDA system. In the example embodiment, the MDA system comprises a transformation engine whose components might include software tools such as AndroMDA and Muse. The transformation engine accepts as input an implementation-independent model written in a modeling language such as UML that provides graphical notation to describe inheritable classes and their attributes and relationships. The transformation engine also accepts a configuration file which allows the designation of a class in the model as a manageable resource. From these inputs, the transformation engine creates a manageable resource corresponding to the class, which resource includes any subclasses by inheritance from the designated class unless the subclass is specifically excluded in the configuration file. In one embodiment, the manageable resources created by the transformation engine are WSMD manageable resources.