The case for an Architecture Knowledge Graph (KG): Part 1
In my previous post, I suggested that reverse engineering legacy software into a Codebase KG could give an LLM the right context to perform a task. However a Codebase KG only gives you application code artifacts and the relationships between them. There is still an analytical task that needs to be undertaken to analyse the codebase. So what's the best way to examine a codebase and describe its' system context?