Rules-Based Decision Tree for Computer System Architecture

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In large enterprises, developing and maintaining software and computer systems is complex due to varied applications and systems, leading to inconsistent and inefficient system architectures, as knowledge sharing and design decisions are often based on limited understanding and past experiences.

Innovation Solution

A method and system utilizing a rules-based decision tree for reference architecture modeling, where applications are categorized by criticality level to select appropriate computer systems and configurations, integrating business impact assessments and engineering standards to define optimal architectures.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If varied applications and systems are deployed in large enterprises, then application functionality and versatility are improved, but system architecture consistency and complexity management deteriorate

Engineering Contradiction:
Improveapplication functionalityVSAvoidsystem architecture complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent applies parameter changes by introducing criticality level parameters to classify applications and systematically varying system architecture parameters based on these classifications. This allows the system to adapt its complexity and configuration parameters according to the criticality level, maintaining consistency while supporting diverse application functionalities.

Inventive Principle:
Principle #35Parameter changes

Solution Approach 2:

The patent segments the enterprise system architecture into distinct criticality levels (e.g., Level 1 for mission-critical, Level 2 for business-critical, etc.). This segmentation allows different architecture standards and configurations to be applied to different segments, managing overall system complexity while maintaining consistency within each segment.

Inventive Principle:
Principle #1Segmentation

2Productivity

If ad-hoc design decisions are made based on limited understanding and past experiences, then implementation speed is improved, but architecture consistency and reliability deteriorate

Engineering Contradiction:
Improveimplementation speedVSAvoidarchitecture consistency
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The patent implements preliminary action by establishing comprehensive architecture decision guides and criticality level classifications before actual system deployment. These pre-defined frameworks enable consistent architecture decisions to be made rapidly without ad-hoc analysis, improving both reliability and implementation speed.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent introduces architecture decision guides as intermediary artifacts that mediate between business requirements and technical implementations. These guides translate criticality levels into specific architecture standards and configurations, ensuring consistent and reliable decisions while maintaining implementation efficiency.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Reliability

If application criticality levels are systematically classified and reference architectures are applied, then architecture consistency and reliability are improved, but analysis time and processing complexity increase

Engineering Contradiction:
Improvearchitecture consistencyVSAvoidanalysis time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent applies preliminary action by pre-classifying applications into criticality levels and pre-defining reference architectures for each level. This eliminates the need for time-consuming analysis during deployment, as the criticality level and corresponding architecture can be determined quickly using the pre-established frameworks.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent uses copying by creating standardized reference architecture templates for each criticality level. These templates can be copied and applied repeatedly to similar applications, significantly reducing analysis time while maintaining architecture consistency and reliability.

Inventive Principle:
Principle #26Copying

Data Source

PatentUS7917407B1Computer-implemented system and method for defining architecture of a computer system
Publication Date: 2011.03.29 T MOBILE INNOVATIONS LLC
  • US7917407B1 patent drawing
  • US7917407B1 patent drawing
  • US7917407B1 patent drawing

AI summary

A method of determining a computer system is provided. The method comprises categorizing the criticality level of each application based on a business impact assessment. The method includes identifying computer system configurations for an application based on a decision tree and on the criticality level of the application. The method also includes providing a computer system selected based on the computer system configurations.