article on aspect-oriented programming

[109]

Good system architecture considers present and future requirements. Therein lies a problem, however. Predicting the future is a difficult task. If you miss future requirements, you'll need to change, or possibly reimplement, many parts of the system. On the other hand, focusing too much on low-probability requirements can lead to an overdesigned, confusing, bloated system. Thus a dilemma for system architects: How much design is too much? Should I lean towards underdesign or overdesign?

хорошая статья. из процитированного, кстати, следует вывод, которого автор почему-то (по крайней мере в явном виде) не делает: важнейшим свойством системы является то, насколько легко её [частично] передизайнить.