Modularizing by change patterns

An approach that I've found helpful to verify module boundaries is analyzing patterns of new feature additions to your application. If most of the typical changes you make to your code base involves having to modify multiple modules, that might be a clue that your modules are too fragmented or the separation of modules could be better. It's OK if you are modifying multiple low-level modules (that is, with horizontal concerns) for an average code change or enhancement. But if each change or enhancement to your application requires you to modify too many modules with vertical concerns, you might want to re-look at the module boundaries and see if those different modules contain code that should ideally be together in the same module.