Saved in:
Bibliographic Details
Main Author: Kamath, Suresh
Format: Preprint
Published: 2024
Subjects:
Online Access:https://arxiv.org/abs/2407.17273
Tags: Add Tag
No Tags, Be the first to tag this record!
_version_ 1866917731895345152
author Kamath, Suresh
author_facet Kamath, Suresh
contents The development of an IT strategy and ensuring that it is the best possible one for business is a key problem many organizations face. This problem is that of linking business architecture to IT architecture in general and application architecture specifically. In our earlier work we proposed Category theory as the formal language to unify the business and IT worlds with the ability to represent the concepts and relations between the two in a unified way. We used rCOS as the underlying model for the specification of interfaces, contracts, and components. The concept of pseudo-category was then utilized to represent the business and application architecture specifications and the relationships contained within. Contracts are used for the specification of both IT and Business architecture components. The linkages between them is now established using the matching of the business component contracts with the application component contracts. Typically, the matching was based on manual process, in this paper we extend the work by considering automated component matching process. In this paper we provide implementation of the matching process using graph matching.
format Preprint
id arxiv_https___arxiv_org_abs_2407_17273
institution arXiv
publishDate 2024
record_format arxiv
spellingShingle Component Matching as a Graph Matching Problem
Kamath, Suresh
Software Engineering
The development of an IT strategy and ensuring that it is the best possible one for business is a key problem many organizations face. This problem is that of linking business architecture to IT architecture in general and application architecture specifically. In our earlier work we proposed Category theory as the formal language to unify the business and IT worlds with the ability to represent the concepts and relations between the two in a unified way. We used rCOS as the underlying model for the specification of interfaces, contracts, and components. The concept of pseudo-category was then utilized to represent the business and application architecture specifications and the relationships contained within. Contracts are used for the specification of both IT and Business architecture components. The linkages between them is now established using the matching of the business component contracts with the application component contracts. Typically, the matching was based on manual process, in this paper we extend the work by considering automated component matching process. In this paper we provide implementation of the matching process using graph matching.
title Component Matching as a Graph Matching Problem
topic Software Engineering
url https://arxiv.org/abs/2407.17273