Platform Architecture Standardization via Segmentation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current platform architecture creation methods lack standardization and efficiency in delivering customer-centric solutions, particularly in cloud computing environments, leading to inconsistencies and increased complexity in managing customer systems across different architecture types.

Innovation Solution

The implementation of a standardized method for creating and assessing platform architectures using platform architecture type unit definitions, specifically defining Go-To-Market, Platform Environment, Platform Component, and Platform Information architectures, with success gates and continuous delivery processes to ensure consistency and compliance.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Manufacturing precision

If standardized platform architecture type unit definitions are implemented, then manufacturing precision and reliability of platform architectures improve, but device complexity and implementation difficulty increase

Engineering Contradiction:
Improvearchitecture consistencyVSAvoidstandardization complexity
Core Design Contradiction:
Manufacturing precisionVSDevice complexity

Solution Approach 1:

The platform architecture is segmented into distinct architecture types (Go-To-Market, Platform Environment, Platform Component, Platform Information) with specific architecture type units for each segment. This segmentation allows standardized definitions to be applied to manageable portions of the overall architecture, improving consistency without overwhelming complexity.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The standardized architecture type unit definitions serve multiple functions: they define architectural structures, establish assessment criteria, enable compliance verification, and facilitate continuous delivery processes. This multi-functionality reduces the need for separate standardization mechanisms across different architecture domains.

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

2Reliability

If comprehensive architecture assessment with success gates is implemented, then reliability and compliance of platform architectures improve, but loss of time and productivity decrease

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

Solution Approach 1:

Success gates are defined in advance for each architecture type, establishing assessment criteria before the actual architecture creation process begins. This preliminary definition of assessment points and success criteria enables streamlined verification processes that reduce time loss during implementation while maintaining comprehensive compliance checking.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The assessment process provides continuous feedback through success gate evaluations at defined milestones. This feedback mechanism allows for early detection of compliance issues and iterative corrections, reducing the total time required to achieve reliable architectures compared to end-to-end verification approaches.

Inventive Principle:
Principle #23Feedback

3Adaptability or versatility

If multiple architecture types with specific definitions are defined, then adaptability and versatility of platform solutions improve, but device complexity and difficulty of operation increase

Engineering Contradiction:
Improvearchitecture flexibilityVSAvoidarchitecture management ease
Core Design Contradiction:
Adaptability or versatilityVSEase of operation

Solution Approach 1:

The platform architecture is divided into four distinct architecture types (Go-To-Market, Platform Environment, Platform Component, Platform Information), each with specific type units tailored to its domain. This segmentation provides adaptability for different architectural needs while managing complexity through clear boundaries and focused definitions for each type.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS10372421B2Platform provider architecture creation utilizing platform architecture type unit definitions
Publication Date: 2019.08.06 SALESFORCE INC
  • US10372421B2 patent drawing
  • US10372421B2 patent drawing
  • US10372421B2 patent drawing

AI summary

In an example, a method for developing a customer system utilizing a preexisting cloud-computing platform is provided. The method may include defining a platform architecture for the customer system to be developed in terms of a plurality of architecture types—and their predefined architecture type unit. The method may include displaying an indicator of first and second indicators, the first and second indicators corresponding to confirmation of the platform architecture and non-confirmation of the platform architecture, respectively, based on information about a subset of deliverables corresponding to the architecture types.