Introduce certain design/coding level constraints to developers while implementing the functionalities with ArchUnit.
Join the DZone community and get the full member experience. How often have you experienced a well-defined and understood software architecture on paper, but then it falls apart when developers start implementing it? Recently, while re-architecting legacy components in an application, I experienced the same. As more and more developers joined the team, it became a constant routine to make them aware of the design thought adopted in the architecture and how to adhere to it. I know some of you may say, « Why not control the implementation during code-review? » Well technically you can, but in that case, the reviewer becomes the bottleneck in the whole SDLC process.
