Extended MVC Application Contexts for Data Redundancy

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In the MVC design methodology, defining relationships between data elements, especially when no predefined relationships exist in databases, leads to significant redundancy in application code and inefficient data transport, requiring manual state management by developers.

Innovation Solution

The extended MVC design pattern introduces application contexts as intermediary storage, structuring data into design-time and run-time contexts with hierarchical relationships, allowing for dynamic modification and resetting, which reduces redundant data storage and improves data consistency by interposing contexts between views and models.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If predefined relationships are defined through dependencies in a relational database, then data relationships can be established, but significant portions of application code are required to define relationships and enable data transport

Engineering Contradiction:
Improvedata relationship definitionVSAvoidapplication code volume
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent introduces an intermediary layer between the database and application code. This intermediary structure automatically defines relationships and enables data transport without requiring extensive manual coding in the application layer, thus reducing code complexity while maintaining reliable data relationship definition

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent replaces the mechanical approach of manually writing code to define relationships and transport data with an automated system. The system automatically infers relationships and generates data transport mechanisms, eliminating the need for developers to write significant portions of application code for these purposes

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

2Loss of information

If application code is written to memorize and administer state, then current interaction status can be tracked, but code redundancy increases

Engineering Contradiction:
Improvestate managementVSAvoidapplication code redundancy
Core Design Contradiction:
Loss of informationVSDevice complexity

Solution Approach 1:

The patent implements self-service state management where the system automatically tracks and manages interaction state without requiring developers to write custom state administration code. The intermediary structure automatically maintains state information, eliminating code redundancy while preserving complete state management capabilities

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The patent creates a universal state management mechanism that handles all types of state information through a single intermediary structure. This multi-functional approach eliminates the need for separate code modules for different state management tasks, reducing overall code redundancy while maintaining comprehensive state tracking

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

3Productivity

If data binding is used for data transport between view and model, then data can be transported efficiently, but predefined relationships must be manually defined

Engineering Contradiction:
Improvedata transport efficiencyVSAvoidrelationship definition
Core Design Contradiction:
ProductivityVSEase of manufacture

Solution Approach 1:

The patent introduces an intermediary layer that automatically establishes data binding relationships between views and models. This intermediary structure handles the relationship definition automatically, making data transport efficient without requiring manual definition of predefined relationships

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS7581204B2Dynamic contexts
Publication Date: 2009.08.25 SAP SE
  • US7581204B2 patent drawing
  • US7581204B2 patent drawing
  • US7581204B2 patent drawing

AI summary

Methods, apparatus, and computer program products that implement techniques for extending the MVC design pattern by structuring data of an application into application contexts. The techniques feature accessing a predetermined structure for a storage area, modifying the predetermined structure and creating an instance of the storage area according to the predetermined structure. The storage area relates to a controller. The controller is operable to manipulate a model and a view. The view includes multiple UI elements for presenting data from the model. The predetermined structure includes multiple design-time context elements and relationships between the design time-context elements. At least one of the UI elements is bound to one of the design-time context elements. The instance of the storage area includes multiple run-time context elements. Each run-time context element corresponds to one of the design-time context elements.