Evolve your architecture in lock-step with the ever changing market-needs:
 |
Requirements change – anytime. That is a given. And as long as your software’s architecture supports those changes, you’re fine. But imagine your architecture needs to evolve as well in order to support the necessary changes:
|
Can you pull this off? And if so, how do you go about to make all the existing code follow the architectural changes?
Do you really find the time to refactor and redesign your existing code-base just to keep it in synch with your software’s architecture?
And if you don’t: Are you willing to let your architecture degrade into a meaningless set of concepts that have no correspondence in the code?
Do you really find the time to refactor and redesign your existing code-base just to keep it in synch with your software’s architecture?
And if you don’t: Are you willing to let your architecture degrade into a meaningless set of concepts that have no correspondence in the code?