Most modern software is E-type systems, and by that very nature [d]evolve into API specifications even if your team intended something completely different. Rea

Most modern software is E-type systems, and by that very nature [d]evolve into API specifications even if your team intended something completely different. Reasonable frameworks tend to accelerate this common trend by starting off with a well defined visitor and or facade pattern. The current key design principle is to colocate problem domains in confined modular partitions with those responsible. If the team leads don't do this, than the infrastructure rots with fragile products in less than 18 months. Sisyphus design principles are rarely excusable. Best of luck, =)