System Architecture Generation Using Templates

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

The development of complex computing systems is labor-intensive and varies significantly based on the system architect's expertise and preferences, often requiring bespoke architecture design using hardware and software from a single vendor, which limits efficiency and scalability.

Innovation Solution

A templatized approach is introduced, where general system architecture templates, available hardware and software specifications, and specific requirements are used to generate a particular system architecture, allowing for the selection of optimal components from multiple vendors, and enabling iterative 'what if' analyses for sizing and cost optimization.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If bespoke architecture design is used by system architects, then system functionality and customization are improved, but development time and labor intensity increase significantly

Engineering Contradiction:

Improvesystem customizationVSAvoiddevelopment efficiency

Core Design Contradiction:

Adaptability or versatilityVSProductivity

Solution Approach 1:

The patent applies preliminary action by pre-defining system architecture templates that encapsulate best practices and proven designs. These templates are prepared in advance and can be directly applied to new projects, eliminating the need to create architecture from scratch each time. This resolves the contradiction by maintaining customization capability through template selection and adaptation while dramatically reducing development time and labor intensity.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The patent uses copying by creating reusable system architecture templates that can be replicated across multiple projects. Instead of designing unique architectures for each system, the same proven templates are copied and adapted to different requirements. This maintains design quality and adaptability while significantly improving productivity through reuse.

Inventive Principle:

Principle #26Copying

2Ease of manufacture

If vendor-specific hardware and software are selected, then system integration simplicity is improved, but solution flexibility and vendor neutrality deteriorate

Engineering Contradiction:

Improveintegration simplicityVSAvoidvendor neutrality

Core Design Contradiction:

Ease of manufactureVSAdaptability or versatility

Solution Approach 1:

The patent applies universality by designing system architecture templates that are vendor-neutral and can accommodate multiple hardware and software vendors. The templates define functional requirements and integration patterns that work with different vendors' products, allowing the same architecture to be implemented with various components. This resolves the contradiction by maintaining integration simplicity through standardized interfaces while achieving vendor neutrality through multi-vendor compatibility.

Inventive Principle:

Principle #6Universality (Multi-functionality)

3Manufacturing precision

If expert system architects perform bespoke design, then architecture quality and optimization are improved, but dependency on expert availability and cost increase

Engineering Contradiction:

Improvearchitecture qualityVSAvoidarchitect availability

Core Design Contradiction:

Manufacturing precisionVSEase of operation

Solution Approach 1:

The patent applies self-service by enabling system architects to generate quality architectures using pre-defined templates without requiring expert intervention. The templates encapsulate expert knowledge and best practices, allowing any architect to produce high-quality results by selecting and configuring appropriate templates. This resolves the contradiction by maintaining architecture quality through embedded expert knowledge in templates while eliminating dependency on expert availability.

Inventive Principle:

Principle #25Self-service

4Measurement precision

If iterative what-if analysis is implemented, then cost optimization and sizing accuracy are improved, but analysis time and computational resources increase

Engineering Contradiction:

Improvesizing accuracyVSAvoidanalysis time

Core Design Contradiction:

Measurement precisionVSLoss of time

Solution Approach 1:

The patent applies preliminary action by pre-calculating and storing optimal configurations, cost parameters, and performance characteristics in the system architecture templates. When performing what-if analysis, the system retrieves these pre-computed values and performs rapid comparisons rather than conducting full analyses from scratch. This resolves the contradiction by maintaining sizing accuracy through comprehensive template data while reducing analysis time through pre-computation and efficient querying.

Inventive Principle:

Principle #10Preliminary action

Data Source

PatentUS10089414B2System architecture generation

Publication Date: 2018.10.02 HEWLETT PACKARD ENTERPRISE DEV LP

AI summary

A template corresponds to a general system architecture for providing a desired functionality. A particular system architecture for providing the desired functionality is generated based on the template and based on specifications of requirements for the particular system architecture. The particular system architecture is implementable using hardware and software that are specified and that are available to implement the general system architecture. One or more of a logical diagram of the particular system architecture, a physical diagram of the particular system architecture, and a bill of materials of the hardware and the software selected to implement the particular system architecture are provided.