Building an ownership cartography of a system

Context When managing a software system, it is important to know who is responsible for which part of the system. This information can be useful for various reasons, such as identifying potential bottlenecks, understanding the impact of changes, and improving collaboration among team members. One major threat could, for example, come from a developer leaving the team. This is often referred to as…