Let’s illustrate the concept of modules by an example. Assume there’s a requirement for a rich-client application to perform an auto-update process. This requirement during the design process will become the application’s responsibility. If we assign it to an Auto-Updater Module, it will mean that fulfillment of this responsibility lies solely with this module. Not-modular approaches often lead to scattering responsibility among so-called “modules” like “model”, “database”, “infrastructure”, “domain”. But in the modular approach, if it’s decided that auto-update is not needed anymore, we should be able to get rid of this responsibility by deleting just one module (and its wiring to other modules), without the need for the shotgun surgery throughout layers.
Copyright © 1997-2026 by www.people.com.cn all rights reserved
。业内人士推荐服务器推荐作为进阶阅读
It turned out that a motherboard able to run Pentium from 60Mhz to 223Mhz could not exist for the good reason that all these CPUs use different sockets.，详情可参考体育直播
В России изменились программы в автошколах22:30