Category Archive: 'Case History'
One of the recurring challenges in software maintenance is unexpected interactions between components. Although architectural boundaries should isolate components, large systems often have unexpected couplings between components. In a richly featured application, a full investigation can be prohibitive. This inability to ensure isolation can impede necessary changes. A bug fix in DepAn demonstrates an effective strategy […]
Remodularization work is fraught with well-meaning teams that get in over their heads. Lack of experience with the practices of large-scale refactoring is common. Although some individuals may have experience with this, it is very rare for a development team to repeatedly remodularize their project. Without experience, it’s very easy for a team to find themselves trapped in an unproductive cycle of […]