Best practice #2: Design for change with Dynamic Domain Model

Modern developers need to have domain models that are nimbly changed. With the emergence of iterative development and shorter development cycles, there is almost certainty that changes to an application will occur after the initial design. To effectively handle changes, developers shouldn’t have to completely rework tested code. An application needs to be able to nimbly handle changes in a way that ensures a high level of quality.

No comments:

Post a Comment