Model-Driven State Management for Application Reliability

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing client-services architectures lack effective mechanisms for managing the state transitions of applications, particularly in complex business processes, leading to cumbersome and error-prone hard coding of property value settings and inadequate runtime checks.

Innovation Solution

A model-driven state management system that instantiates business objects and defines models based on application and business object contexts, allowing for the checking of state transitions and providing indications to user interfaces, thereby enabling structured data management and transitions between application states.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If state transitions are managed through hard coding of property value settings, then the application can maintain state information, but the development becomes cumbersome and error-prone

Engineering Contradiction:
Improvestate management reliabilityVSAvoiddevelopment ease
Core Design Contradiction:
ReliabilityVSEase of manufacture

Solution Approach 1:

The patent introduces models as an intermediary layer between the application code and state management. These models define valid state transitions and property value settings externally, allowing the system to automatically validate states without hard-coding validation logic. The models act as mediators that separate the business logic from state management constraints, improving both reliability through formal validation and ease of development through model-driven configuration.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent applies preliminary action by defining all valid state transitions and property settings in models before runtime execution. The system pre-validates transition rules and constraints during the modeling phase, so that during actual application execution, state management becomes a matter of checking against pre-defined valid states rather than performing complex validation logic. This shifts the validation work to design time, making runtime operations simpler and more reliable.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If comprehensive runtime checks are implemented for state transitions, then the reliability of state management improves, but the complexity of the system increases

Engineering Contradiction:
Improvestate transition validationVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The models serve as intermediaries that encapsulate complex validation rules in a separate, manageable format. Rather than embedding complex validation logic throughout the application code, the system uses models to externalize and structure validation rules. This reduces system complexity by concentrating validation logic in dedicated model definitions while keeping the application code simpler and more focused on business logic.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system implements self-service by enabling automatic validation of state transitions against the defined models. The state management mechanism automatically checks whether transitions and property settings conform to the model definitions without requiring manual intervention or complex validation code. This automation reduces the apparent system complexity while maintaining comprehensive validation, as the models themselves drive the validation process.

Inventive Principle:
Principle #25Self-service

3Reliability

If developers manually code property value settings for each state, then the application can enforce state constraints, but the development time and effort increase significantly

Engineering Contradiction:
Improvestate constraint enforcementVSAvoiddevelopment productivity
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent applies preliminary action by defining all state constraints, valid transitions, and property value settings in models during the design phase. Instead of manually coding these constraints throughout the application development process, developers create comprehensive model definitions upfront that automatically enforce state rules. This preliminary modeling effort pays dividends during implementation, as the models automatically generate validation logic and reduce manual coding requirements, thereby improving development productivity while maintaining constraint enforcement.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The models act as intermediaries that translate high-level state management requirements into concrete validation logic. Rather than requiring developers to manually code each property value setting and state constraint, the models serve as a intermediate layer that automatically generates and enforces these constraints based on model definitions. This intermediary approach maintains reliable state constraint enforcement while significantly reducing the manual development effort required.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS7930251B2Model driven state management of applications
Publication Date: 2011.04.19 SAP SE
  • US7930251B2 patent drawing
  • US7930251B2 patent drawing
  • US7930251B2 patent drawing

AI summary

The subject matter disclosed herein provides methods and apparatus, including computer program products, for model driven state management of applications. In one aspect, there is provided a computer-implemented method. The method may include instantiating one or more business objects associated with an application. The transitions between states of the application may be checked using one or more models defined based on at least one of a context of the business object and a context of the application. An indication regarding the results of checking of the transitions may be provided to a user interface. Related apparatus, systems, methods, and articles are also described.