Business Object Management via Database Segmentation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Modifying and adding business objects in the business layer is a complex task, limiting flexibility, especially when implementing applications across multiple environments or in response to changing business environments.

Innovation Solution

A data-driven approach where substantive business object data is maintained in a database, allowing for flexible modification and instantiation of business objects based on page call-up requests, enabling dynamic interaction between the presentation layer and the database.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If business objects are defined within the business layer with fixed structure, then system stability is maintained, but flexibility to modify business objects is limited

Engineering Contradiction:
Improveflexibility to modify business objectsVSAvoidcomplexity of modifying business objects
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent segments the business object definition into two parts: the structural framework remains in the business layer code, while the configurable attributes are separated into database tables. This allows modification of business object properties without changing the core business layer code, reducing complexity while maintaining flexibility.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent makes the business object structure dynamic by loading object definitions from the database at runtime rather than hardcoding them. This allows the business objects to adapt their structure based on database content, enabling flexibility to modify objects without redeploying code.

Inventive Principle:
Principle #15Dynamics

2Adaptability or versatility

If business objects are hardcoded in the business layer, then system reliability is improved, but adaptability to changing business environments deteriorates

Engineering Contradiction:
Improveadaptability to changing business environmentsVSAvoidsystem reliability
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The patent introduces the database as an intermediary layer between the hardcoded business layer and the variable business requirements. The database stores configurable business object definitions that mediate between the stable code structure and the need for adaptability to changing environments.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system achieves adaptability while maintaining reliability by making the business object instances dynamic (loaded from database) while keeping the business layer framework static and reliable. This allows the system structure to remain stable while the business logic can adapt to changing environments.

Inventive Principle:
Principle #15Dynamics

3Adaptability or versatility

If business objects are modified to support multiple business environments, then versatility is improved, but complexity of object definition increases

Engineering Contradiction:
Improvesupport for multiple business environmentsVSAvoidcomplexity of business object definition
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent creates a universal business object framework that can serve multiple business environments through a common structure. The database stores environment-specific configurations that allow the same business layer code to function across different business environments without increasing code complexity.

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

Data Source

PatentUS9075863B2Systems and methods for managing business objects
Publication Date: 2015.07.07 HONEYWELL INTERNATIONAL INC
  • US9075863B2 patent drawing
  • US9075863B2 patent drawing
  • US9075863B2 patent drawing

AI summary

Described herein are systems and methods for managing business objects. In overview, various embodiments provide software, hardware and methodologies underlying a data driven application including a data driven business layer, optionally in combination with a data driven user interface and presentation layer. In overview, an object-oriented computer program includes a presentation layer, a business layer, and a database. The business layer provides business objects, which effectively interpose the presentation layer with the database. Substantive business object data is defined within the database, and loaded to the business layer following the receipt of a page call-up request at the presentation layer.