Solution modeling and analysis toolset for enterprise software architecture

Abstract

Modeling an enterprise architecture includes associating a plurality of desired business capabilities with a plurality of requirements and associating each of a plurality of technology components with one or more of the plurality of requirements, based on a respective technology supporting the one or more requirements. Then a model may be constructed that includes linking each of the technology components with one or more of the desired business capabilities based on the associating of the plurality of desired business capabilities with the plurality of requirements and the associating of each of the plurality of technology components with one or more of the plurality of requirements.

Description

CROSS REFERENCE TO RELATED APPLICATIONS[0001]This application claims priority to and is a continuation of U.S. Ser. No. 13 / 798,929 entitled SOLUTION MODELING AND ANALYSIS TOOLSET FOR ENTERPRISE SOFTWARE ARCHITECTURE, filed on Mar. 13, 2013, which was filed concurrently with U.S. Pat. No. 9,244,655 entitled SOLUTION MODELING AND ANALYSIS TOOLSET FOR ENTERPRISE SOFTWARE ARCHITECTURE AND SKELETON ARCHITECTURE and U.S. Pat. No. 9,189,203 entitled SOLUTION MODELING AND ANALYSIS TOOLSET FOR ENTERPRISE SOFTWARE ARCHITECTURE AND ARCHITECTURE ROADMAPS, the entire disclosure of each of these documents is incorporated by reference herein.BACKGROUND[0002]The present disclosure relates to managing an enterprise architecture, and more specifically, to modeling and analyzing the architecture.[0003]Current Enterprise Architecture Management Frameworks such as TOGAF and Zachman cater to information technology (IT) managers (e.g., a Chief Information Officer (CIO)) who need to provide an IT solution ...

AI Technical Summary

Problems solved by technology

However, when a CIO attempts to select off-the-shelf technology (e.g., software, hardware, or composite solution), they encounter difficulty matching offered capabilities of the technology with their business needs.

One reason for this difficulty is a lack of traceability of offered capabilities to needs and traceability of requirements to technology.

Because users in each of the three domains employ their own tools, it is difficult without intensive human interpretation and labor to decide which capability is implemented in which technology and the order that such an implementation should be accomplished.

In other words, transforming business goals into an architecture roadmap for a solution is difficult.

Images