The IDesign Method
Tip?#5?-?The IDesign Method
Learning from the drawbacks of domain-driven design, Juval Lowy’s IDesign method aspired to solve the software architecture issues and make a more flexible paradigm that can grow and change with businesses. The central premise of IDesign was that business objects are less important than what they do, such that every dependency that is tightly integrated and might change should be isolated from the architecture and the decisions that are made based on it. It was called Volatility-Based-Decomposition, in which, in essence, every component in the system can be an accessor to something, an engine that drives one or more accessors, and managers coordinate the integration between these parts; there’s a large community around these ideas.
For more Tips -?CLICK HERE
By?Dror Gluska, Software Development, Automation and Architecture Consultant, with more than 20 years of experience, CTO @?Practical Software