Software Architecture Design Interface Using Standardized Templates

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Software development teams face challenges in creating and documenting software architecture and sharing it across teams due to a lack of suitable tools, leading to extended development times and inefficient resource usage.

Innovation Solution

A software development interface with a library of symbols and a template that includes sections for technical capabilities, interaction sequences, service topology, integration flows, and logging, allowing architects to design and document software architecture at multiple levels, enabling programmers to write code based on these specifications and facilitating reuse of design patterns.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If software development teams create custom software architecture documentation from scratch, then the documentation can be tailored to specific project needs, but the development time is extended and resource usage becomes inefficient

Engineering Contradiction:

Improvecustomization of software architecture documentationVSAvoidsoftware development time

Core Design Contradiction:

Adaptability or versatilityVSLoss of time

Solution Approach 1:

The patent segments software architecture documentation into standardized templates covering different aspects (system overview, component diagrams, data flow, etc.). These modular templates can be selected and customized for specific projects, reducing the time needed to create comprehensive documentation while maintaining adaptability to project-specific requirements.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The patent enables parameter changes by allowing users to customize template content, add project-specific details, and adjust documentation depth. The standardized templates serve as a baseline that can be modified through parameter adjustments rather than creating documentation from scratch, thus reducing development time while preserving customization capability.

Inventive Principle:

Principle #35Parameter changes

2Adaptability or versatility

If software architects document architecture without standardized templates, then each project can have unique documentation structure, but the ability to share and reuse architecture designs across teams is lost

Engineering Contradiction:

Improveunique documentation structure per projectVSAvoidcollaboration efficiency among teams

Core Design Contradiction:

Adaptability or versatilityVSProductivity

Solution Approach 1:

The patent implements universal standardized templates that serve multiple functions: they provide a consistent structure across different projects, enable easy sharing and reuse of architecture designs between teams, and still allow project-specific customizations. The templates act as a common language that enhances collaboration efficiency while preserving the ability to adapt to unique project requirements.

Inventive Principle:

Principle #6Universality (Multi-functionality)

3Loss of information

If comprehensive software architecture documentation is created manually, then all project details can be captured, but the documentation process becomes complex and resource-intensive

Engineering Contradiction:

Improvecompleteness of architecture documentationVSAvoidcomplexity of documentation process

Core Design Contradiction:

Loss of informationVSDevice complexity

Solution Approach 1:

The patent applies preliminary action by providing pre-configured standardized templates that already contain the necessary structure, sections, and formatting for comprehensive architecture documentation. Users start with these prepared templates and simply fill in project-specific details, rather than building the documentation structure from scratch. This reduces the complexity of the documentation process while ensuring all necessary information is captured.

Inventive Principle:

Principle #10Preliminary action

Data Source

PatentUS11029923B2Technical building block

Publication Date: 2021.06.08 STATE FARM MUTAL AUTOMOBILE INSURANCE COMPANY

AI summary

A virtual technical building block software development tool and a software development interface that speed accurate and quality software design are provided. The tools develop enterprise software architecture designs, and utilize a library of symbols and a virtual template. The library of symbols includes service oriented architecture symbols and enterprise application integration symbols. The template includes multiple sections to be displayed on a computing device screen. Each section includes a blank space bounded by a frame, and all of the sections are vertically aligned with one another to guide design flow. The sections of the template include, from top to bottom vertically, (1) a technical capabilities section; (2) an interaction sequence section; (3) a service topology section; (4) an integration flow section; and (5) a logging section. The technical building block software development tool streamlines software development and significantly reduces implementation and design time, and ensures reproducible quality of design.