Constraint-Based Software Systems for Rapid Adaptation

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing software systems face disconnects between domain experts and software experts during development, leading to potential faulty system components and the need for repeated redevelopment due to changing conditions, which is time-consuming and unworkable in rapid response scenarios.

Innovation Solution

Constraint-based software systems and methods that generate domain level constraints, translate them into system level constraints, and control systems using these constraints, allowing for rapid adaptation to changing conditions through a graphical user interface and incident detection.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If traditional software development process is used with domain experts and software experts working separately, then specialized domain knowledge can be incorporated, but disconnects between domain experts and software experts lead to faulty system components and require repeated redevelopment

Engineering Contradiction:

Improvesystem component accuracyVSAvoidredevelopment time

Core Design Contradiction:

ReliabilityVSLoss of time

Solution Approach 1:

The patent introduces constraint specifications as an intermediary formalism between domain expert knowledge and software implementation. Domain experts define constraints in a formal language that software experts can directly implement, eliminating the need for repeated redevelopment while ensuring accurate translation of domain knowledge into system behavior.

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent segments the software development process into distinct phases: constraint specification by domain experts, constraint compilation into executable code, and system execution. This segmentation allows each expert type to work independently on their respective phase while ensuring seamless integration, preventing faulty components and reducing redevelopment needs.

Inventive Principle:

Principle #1Segmentation

2Adaptability or versatility

If system components are redeveloped to adjust to changing real world conditions, then system adaptability is improved, but the time-consuming task of redeveloping system components becomes difficult or unworkable

Engineering Contradiction:

Improvesystem adaptability to changing conditionsVSAvoidcomponent redevelopment time

Core Design Contradiction:

Adaptability or versatilityVSLoss of time

Solution Approach 1:

The patent enables dynamic adaptation by allowing domain experts to modify constraint specifications at runtime without requiring system component redevelopment. The constraint compilation mechanism automatically translates updated constraints into executable code, enabling the system to adapt to changing conditions rapidly and efficiently.

Inventive Principle:

Principle #15Dynamics

Solution Approach 2:

The patent performs preliminary compilation of constraint specifications into executable code during system initialization or before runtime changes. This preliminary action prepares the system for rapid adaptation by having the translation mechanism ready, so that when constraints need to change, only the constraint specification needs updating rather than entire system components.

Inventive Principle:

Principle #10Preliminary action

3Manufacturing precision

If detailed requirements of system components are defined by specialists, then component functionality is optimized, but the disconnect between domain level goals and system level implementation leads to erroneous translations

Engineering Contradiction:

Improvecomponent requirement specification accuracyVSAvoidtranslation accuracy between domain and system levels

Core Design Contradiction:

Manufacturing precisionVSLoss of information

Solution Approach 1:

The patent changes the parameter of communication between domain experts and software experts from natural language requirements to formal constraint specifications. This parameter change ensures precise translation by using a mathematically rigorous formalism that eliminates ambiguity and ensures accurate translation of domain level goals into system level implementation.

Inventive Principle:

Principle #35Parameter changes

Solution Approach 2:

The patent replaces the mechanical process of manual requirement translation with an automated constraint compilation mechanism. The compiler automatically translates formal constraint specifications into executable code, eliminating human error in translation while preserving the precision of domain expert specifications.

Inventive Principle:

Principle #28Mechanics substitution (Replace mechanical system)

Data Source

PatentUS7823119B2Constraint based software systems and methods

Publication Date: 2010.10.26 SAP SE

AI summary

Embodiments of the present invention provide constraint based software systems and methods. In one embodiment, the present invention includes a method of controlling the operation of system software comprising generating a plurality of domain level constraints, translating the plurality of domain level constraints into system level constraints, and controlling a system using the system level constraints. System level software may respond rapidly to changing conditions through modification of domain level constraints and translation of domain level constraints into system level constraints. Preprocessing of raw data from RFID or sensors may trigger incidents that automatically trigger the modification of domain level constraints, thereby changing the system level software automatically in response to changes in the operational environment.