In an object-oriented program, UI, database, and other support code often gets written directly into the business objects. Additional business logic is embedded in the behavior of UI widgets and database scripts. This happens because it is the easiest way to make things work, in the short run.
When the domain-related code is diffused through such a large amount of other code, it becomes extremely difficult to see and to reason about. Superficial changes to the UI can actually change business logic. To change a business rule may require meticulous tracing of UI code, database code, or other program elements. Implementing coherent, model-driven objects becomes impractical. Automated testing is awkwar...
- Four. Isolating the Domain
- from Domain-Driven Design: Tackling Complexity in the Heart of Software
- Publisher: Addison-Wesley Professional
- Released: August 2003
why isolate business logic
Share this highlighthttp://www.safaribooksonline.com/a/domain-driven-design-tackling/329494/