Reference Architecture Framework for Enterprise Computing Systems

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Large enterprise computing systems with diverse devices and operating systems face increased technical support costs and complexity, making software updates and technology implementation time-consuming and costly.

Innovation Solution

A method of creating an architecture record comprising platform, domain, and channel reference architectures, stored in memory, which documents computing devices, their operating systems, and communication channels, allowing for evaluation and selection of suitable configurations for implementing new technologies based on set requirements.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If diverse computing devices and operating systems are used to meet various functional requirements, then system versatility and adaptability are improved, but technical support costs and system complexity increase

Engineering Contradiction:
Improvesystem versatilityVSAvoidsystem complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent segments the enterprise computing system into distinct platform definitions, domain reference architectures, and channel reference architectures. Each segment represents a standardized component that can be independently managed and reused across multiple devices and applications, reducing overall system complexity while maintaining versatility.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent creates universal platform definitions and reference architectures that can serve multiple computing devices with different operating systems. These standardized frameworks provide common structures, patterns, and best practices that can be applied across diverse hardware and software environments, reducing technical support costs while maintaining system adaptability.

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

2Adaptability or versatility

If multiple different hardware platforms and operating systems are supported, then system adaptability is improved, but implementation time and costs for new technology increase

Engineering Contradiction:
Improvesystem adaptabilityVSAvoidimplementation time
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The patent performs preliminary actions by establishing platform definitions and reference architectures before implementing new technology. These pre-defined frameworks contain standardized configurations, deployment patterns, and integration approaches that can be directly applied to new implementations, significantly reducing the time and effort required to deploy new technologies across diverse platforms.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent uses copying by replicating proven reference architectures and platform definitions across multiple hardware platforms and operating systems. Instead of creating custom implementations for each platform, the same standardized architectural patterns are copied and adapted, reducing implementation time while maintaining consistency and quality across diverse systems.

Inventive Principle:
Principle #26Copying

3Reliability

If comprehensive documentation of computing devices and communication channels is created, then system understanding and quality are improved, but initial setup and maintenance effort increase

Engineering Contradiction:
Improvesystem qualityVSAvoidsetup effort
Core Design Contradiction:
ReliabilityVSEase of manufacture

Solution Approach 1:

The patent implements self-service by creating architecture records that automatically document computing devices, operating systems, and communication channels. The system generates its own documentation through automated discovery and modeling processes, reducing the manual setup and maintenance effort while improving the completeness and accuracy of system documentation for quality assurance.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS7930321B2Reference architecture framework
Publication Date: 2011.04.19 BANK OF AMERICA CORP
  • US7930321B2 patent drawing
  • US7930321B2 patent drawing
  • US7930321B2 patent drawing

AI summary

An architecture record can be created for a computer system that includes a plurality of computing devices, each having an operating system. The architecture record includes platform definition architectures each associated with one of the computing devices and the operating system of the computing device, domain reference architectures each associated with one or more of the platform definition architectures and a service performed by the computing device of each platform definition architecture, and channel reference architectures each associated with one or more of the domain reference architectures, wherein the computing devices associated with the one or more domain reference architectures are configured to communicate with each other while performing the respective services associated with the one or more domain reference architectures.