Software Inconsistency Resolver

From Computer Laboratory Group Design Projects
Revision as of 11:05, 27 October 2024 by afb21 (talk | contribs) (Created page with "Proposed to Jasmin Jahić <jj542@cam.ac.uk>, to pass on to Chris Cooper-Bland of Endava A problem with software architectures is when they are inconsistent [** because X1, for example X2**]. These inconsistencies could be detected automatically by using an LLM to identify [** property Y **]. The inconsistent architecture can then be visualised using the interactive diagram tool draw.io, allowing developers to resolve the inconsistency with direct manipulation of the mod...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigationJump to search

Proposed to Jasmin Jahić <jj542@cam.ac.uk>, to pass on to Chris Cooper-Bland of Endava

A problem with software architectures is when they are inconsistent [** because X1, for example X2**]. These inconsistencies could be detected automatically by using an LLM to identify [** property Y **]. The inconsistent architecture can then be visualised using the interactive diagram tool draw.io, allowing developers to resolve the inconsistency with direct manipulation of the model, and outputting the results as XML that can be ingested by [** maintenance tool Z**].