Unified Interface for Meta Model Consistency Checking

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

In software engineering, maintaining consistency across software models is challenging due to the need for manual checks and modifications by developers to ensure compliance with consistency rules, which is time-consuming and inefficient.

Innovation Solution

A model consistency engine is introduced that uses reusable software modules and handlers to perform batch checks, modifications, and reporting, allowing for automated consistency checks and modifications across multiple software models, thereby streamlining the development cycle.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If manual checks and modifications are performed by developers to ensure compliance with consistency rules, then model consistency can be maintained, but the development process becomes time-consuming and inefficient

Engineering Contradiction:

Improvemodel consistencyVSAvoiddevelopment speed

Core Design Contradiction:

ReliabilityVSProductivity

Solution Approach 1:

The system enables self-service by automatically performing consistency checks and modifications without requiring manual developer intervention. The batch checking and modification operations autonomously maintain model consistency while developers focus on core development tasks, resolving the contradiction between reliability and productivity.

Inventive Principle:

Principle #25Self-service

Solution Approach 2:

Manual mechanical processes of checking and modifying models are replaced with an automated computer-based system. The batch operations substitute human developers' manual efforts with automated software that performs consistency verification and modifications, thereby maintaining reliability while significantly improving development speed.

Inventive Principle:

Principle #28Mechanics substitution (Replace mechanical system)

2Productivity

If automated batch checking and modification operations are implemented, then development speed and efficiency are improved, but system complexity increases

Engineering Contradiction:

Improvedevelopment speedVSAvoidsystem complexity

Core Design Contradiction:

ProductivityVSDevice complexity

Solution Approach 1:

The batch checking and modification system provides multi-functionality by handling multiple model entities, various consistency rules, and different operation types (checking, modifying, reporting) through a unified interface. This universal approach manages system complexity while delivering high productivity through consolidated batch operations.

Inventive Principle:

Principle #6Universality (Multi-functionality)

Solution Approach 2:

The system segments complex consistency operations into discrete batchable units that can be independently processed. By dividing model checking and modification tasks into manageable batches with standardized interfaces, the system reduces operational complexity while maintaining high throughput and development speed.

Inventive Principle:

Principle #1Segmentation

3Ease of operation

If manual consistency checks are performed on individual models, then development flexibility is maintained, but time consumption increases significantly

Engineering Contradiction:

Improvedevelopment flexibilityVSAvoidtime consumption

Core Design Contradiction:

Ease of operationVSLoss of time

Solution Approach 1:

The batch checking and modification system enables continuous automated operation on multiple models simultaneously. Instead of interrupting development for individual manual checks, the system continuously performs consistency operations in the background, maintaining development flexibility while eliminating time consumption through parallel batch processing.

Inventive Principle:

Principle #20Continuity of useful action

Data Source

PatentUS9052845B2Unified interface for meta model checking, modifying, and reporting

Publication Date: 2015.06.09 SAP SE

AI summary

This disclosure provides various embodiments for performing operations on entities of a meta model modeling one or more software components. A request is received to perform a particular operation of a particular type on each of a plurality of model entities, each model entity modeling at least one attribute of a software component. The request includes an identification of the particular type of operation in a plurality of operation types. The model entities are retrieved in response to the request. A handler object is instantiated of the particular type adapted to perform the particular operation by calling a set of reusable software modules, each software module providing functionality used to perform at least a portion of the particular operation on at least one entity in the plurality of entities. Result data is generated based on the performance of the particular operation using the instantiated handler and reusable software modules.