BA 12

i agree completely analyzing a problem before any work is done on design or programing is a very good idea. the problem is often times requirements or underlying software changes mid implementation. one sign of a good architecture is being able to adapt when requirements change during development. I'm no expert on KDE by any means but perhaps if KDE's architecture was more modular it may not have required a huge rewrite when QT 3 became QT 4. that's then easier statement to make then to actually accomplish. it's an example of a change that could never really be accounted for.