Solution Modeling Toolset for Enterprise Architecture Roadmaps

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Current Enterprise Architecture Management Frameworks, such as TOGAF and Zachman, face challenges in matching off-the-shelf technology capabilities with business needs due to a lack of traceability between technology capabilities and business requirements, leading to difficulties in transforming business goals into effective architecture roadmaps.

Innovation Solution

A method and system that construct alternative technical solutions comprising technology components supporting desired business capabilities, generate an implementation roadmap, and output the roadmap to align technology components across multiple domains, facilitating the selection and implementation of technologies based on business needs.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If manual construction of solutions is performed by Service Engineers according to existing business architecture, then flexibility in creating customized solutions is improved, but time consumption and labor intensity increase significantly

Engineering Contradiction:

Improvesolution customization flexibilityVSAvoidtime consumption

Core Design Contradiction:

Adaptability or versatilityVSLoss of time

Solution Approach 1:

The system pre-generates multiple alternative technical solutions by matching technology components with business requirements before the Service Engineer needs them. This preliminary automated matching reduces the time required while preserving flexibility, as engineers can review and select from pre-prepared options rather than constructing solutions from scratch.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The patent introduces an intermediary system that acts as a bridge between business architecture and technical implementation. This intermediary automatically performs the matching and mapping between business requirements and technology components, reducing direct manual effort while maintaining solution quality and adaptability.

Inventive Principle:

Principle #24Intermediary (Mediator)

2Measurement precision

If three different modeling environments and nomenclatures are used across business architecture, software design, and implementation domains, then domain-specific precision is improved, but traceability and integration between domains deteriorate

Engineering Contradiction:

Improvedomain-specific modeling precisionVSAvoidtraceability between domains

Core Design Contradiction:

Measurement precisionVSLoss of information

Solution Approach 1:

The patent creates a universal mapping framework that can handle multiple domain-specific modeling languages and nomenclatures simultaneously. This framework enables traceability across domains by establishing correspondence relationships between different modeling environments while preserving their individual precision and characteristics.

Inventive Principle:

Principle #6Universality (Multi-functionality)

Solution Approach 2:

An intermediary mapping layer is introduced that connects business architecture models, software design models, and implementation models. This intermediary maintains traceability by establishing and managing the relationships between different domains, allowing information to flow accurately across domain boundaries while preserving domain-specific precision.

Inventive Principle:

Principle #24Intermediary (Mediator)

3Productivity

If off-the-shelf technology is selected to meet business needs, then implementation speed and cost efficiency are improved, but difficulty in matching technology capabilities with specific business requirements increases

Engineering Contradiction:

Improveimplementation speedVSAvoidcapability matching difficulty

Core Design Contradiction:

ProductivityVSDifficulty of detecting and measuring

Solution Approach 1:

The system implements automated feedback mechanisms that evaluate off-the-shelf technology capabilities against specific business requirements. This feedback loop identifies the degree of match between technology offerings and business needs, enabling informed selection decisions that balance implementation speed with requirement satisfaction.

Inventive Principle:

Principle #23Feedback

Solution Approach 2:

The patent replaces manual capability matching processes with automated computational methods. Algorithms automatically analyze and match technology capabilities with business requirements, reducing the difficulty of assessment while maintaining implementation efficiency of off-the-shelf solutions.

Inventive Principle:

Principle #28Mechanics substitution (Replace mechanical system)

Data Source

PatentUS9244655B1Solution modeling and analysis toolset for enterprise software architecture and skeleton architecture

Publication Date: 2016.01.26 CA TECH INC

AI summary

Analyzing technical solutions for supporting desired business capabilities includes constructing a plurality of alternative technical solutions, wherein each alternative technical solution comprises a respective set of technology components, wherein each technology component provides support for a respective requirement associated with fulfilling a respective one of a plurality of desired business capabilities. Then an implementation roadmap can be generated comprising any technology component that is a member of more than one of the respective sets of technology components; and this implementation roadmap can then be provided as output.