MDA Model Transformation Using UML Profiles for Service Apps

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current Model Driven Architecture (MDA) tools lack a standardized approach for transforming Platform Independent Models (PIMs) to Platform Specific Models (PSMs) and generating source code, limiting flexibility and efficiency in developing large, distributed service provisioning applications.

Innovation Solution

A generalized MDA compliant framework that uses MOF compliant models to separate core and process-specific entities, encodes PIM associations to PSM associations with UML profiles and stereotypes, and generates customized code templates for multiple platforms, allowing incremental transformation and decoupling of core models from specific properties.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If current MDA tools are used for transforming PIMs to PSMs and generating source code, then code generation can be automated, but the tools lack standardized approach limiting flexibility and efficiency

Engineering Contradiction:
Improveprogrammer productivityVSAvoidflexibility in generating PSMs
Core Design Contradiction:
ProductivityVSAdaptability or versatility

Solution Approach 1:

The patent segments the MDA transformation process into distinct standardized components: PIM definition phase, transformation rule application phase, and PSM generation phase. This segmentation allows each phase to be independently configured and reused, providing both automation and flexibility for generating different PSMs from the same PIM through standardized transformation rules.

Inventive Principle:
Principle #1Segmentation

2Reliability

If MDA framework is implemented with customized transformation rules, then system robustness is improved, but the complexity of encoding and enacting transformations increases

Engineering Contradiction:
Improvesystem robustnessVSAvoidtransformation encoding complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent applies preliminary action by pre-defining standardized transformation rules and templates before the actual PIM to PSM transformation. These pre-configured rules encapsulate the complexity of transformation logic, making the transformation process itself simpler and more reliable. The standardized rules can be reused across multiple transformations, reducing the complexity burden while maintaining system robustness.

Inventive Principle:
Principle #10Preliminary action

3Adaptability or versatility

If incremental transformation framework is implemented, then flexibility in generating richer PSMs is improved, but the process complexity increases

Engineering Contradiction:
Improveflexibility in generating PSMsVSAvoidtransformation process complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent implements dynamics by allowing the transformation process to be executed incrementally and adaptively. The framework supports dynamic selection and application of transformation rules based on the specific PIM characteristics and desired PSM targets. This dynamic approach enables flexibility in generating richer PSMs while managing process complexity through modular, on-demand transformation rule application.

Inventive Principle:
Principle #15Dynamics

Data Source

PatentUS8418125B2Incremental model refinement and transformation in generating commerce applications using a model driven architecture
Publication Date: 2013.04.09 INTERNATIONAL BUSINESS MACHINE CORPORATION
  • US8418125B2 patent drawing
  • US8418125B2 patent drawing
  • US8418125B2 patent drawing

AI summary

In one embodiment of the invention, a method for profile mapped model transformation for model driven architecture (MDA) development of service provisioning applications can be provided. The method can include mapping elements of a platform independent domain specific model to a platform specific domain specific model for a target platform with stereotypes in a uniform modeling language (UML) profile defined for the target platform. The method further can include transforming a platform independent domain specific model into a platform specific domain specific model for a target platform by applying the stereotypes of the UML profile defined for the target platform. Finally, the method can include generating shell source code for the transformed platform specific domain specific model.