Software Object Behavior Association with Operational Modes

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing systems lack user-friendly methods for end users to control and modify software behavior and functionality, often requiring time-consuming reprogramming for detailed changes, leading to inefficient resource usage and software conflicts due to unused or inapplicable components.

Innovation Solution

A method that allows users to associate object behaviors with specific operational modes during software installation or runtime, enabling the selection and disassociation of behaviors based on operational needs, thereby optimizing software resource usage and reducing conflicts.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If users want to control or modify software behavior and functionality, then software customization capability is improved, but reprogramming time and cost increase

Engineering Contradiction:
Improvesoftware customization capabilityVSAvoidreprogramming time
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The patent segments software behavior into distinct object behaviors that can be independently associated with different operational modes. Each object behavior can be selectively enabled or disabled based on the operational mode, allowing users to customize software behavior without reprogramming. This segmentation enables fine-grained control over software functionality while avoiding the time-consuming process of reprogramming entire software components.

Inventive Principle:
Principle #1Segmentation

2Adaptability or versatility

If all object behaviors are installed in software, then software functionality is improved, but resource usage efficiency deteriorates

Engineering Contradiction:
Improvesoftware functionalityVSAvoidcomputing resource usage
Core Design Contradiction:
Adaptability or versatilityVSLoss of energy

Solution Approach 1:

The patent implements dynamic association between object behaviors and operational modes, where the software selectively activates only the behaviors needed for the current operational mode. This dynamic approach allows the software to adapt its resource consumption based on the operational context, enabling full functionality when needed while optimizing resource usage when certain behaviors are not required.

Inventive Principle:
Principle #15Dynamics

3Adaptability or versatility

If multiple object behaviors are associated with a single operational mode, then software versatility is improved, but software conflicts increase

Engineering Contradiction:
Improvesoftware versatilityVSAvoidsoftware conflict resolution
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The patent applies local quality by allowing different object behaviors to be selectively associated with different operational modes. This enables the software to have different behavior configurations for different operational contexts, reducing conflicts by ensuring that only compatible behaviors are active simultaneously. Each operational mode can be optimized with specific behaviors relevant to that mode, improving overall software reliability.

Inventive Principle:
Principle #3Local quality

Data Source

PatentUS8826267B2Association of object elements to operational modes
Publication Date: 2014.09.02 ORACLE INT CORP
  • US8826267B2 patent drawing
  • US8826267B2 patent drawing
  • US8826267B2 patent drawing

AI summary

A method characterized by association of object elements to operational modes is adapted for use during installation or runtime of a software package. In an example embodiment, the software package includes objects and object behaviors, wherein a particular object has at least two different object behaviors associated with the particular object, and wherein different object behaviors are each associated with a different operational mode. The example method includes accepting a signal from a user input device to specify an operational mode in a target system for the software package and determining an object behavior that is associated with the specified operational mode. In one implementation, the determined behavior is installed in the target system while at least one other object behavior that is not associated with the specified operational mode is not installed in the target system. In another implementation, the software package is run via the target system, where the software package implements the determined behavior and does not implement at lease one other object behavior that is not associated with the specified operational mode.