note IlyaM [chromatic] is obviously advocating [http://c2.com/cgi/wiki?YouArentGonnaNeedIt|YAGNI] approach to solve design problems. In short the idea is that you split your development process in short iterations: in each iteration you select functionality to implement, then you design the system in the simpliest possible way to pass [http://c2.com/cgi/wiki?FunctionalTest|functional tests]. While doing it you religiosly refactor code to remove [http://c2.com/cgi/wiki?CodeSmell|code smells] (i.e. code dublication, too big methods and subs, etc). In my experience it is actually very efficient approach which at the end produces more high quality and more flexible code compared with [http://c2.com/cgi/wiki?WaterFall|water fall] style development process when you try to design everything from the begining. Too often initial assumptions became wrong assumptions, functional requirements change and end result becomes [http://www.laputan.org/mud/mud.html|big ball of mud]. Word of warning though. If you try to develop using YAGNI way then [http://c2.com/cgi/wiki?TestDrivenDevelopment|TDD] is a must, constant [http://c2.com/cgi/wiki?WhatIsRefactoring|refactoring] is a must. If you don't follow these practices you'd better stick with waterfall way or result will be a disaster. In a sence waterfall is simplier model though less effective. -- Ilya Martynov, <a href="mailto:ilya@iponweb.net">ilya@iponweb.net</a> CTO IPonWEB (UK) Ltd Quality Perl Programming and Unix Support UK managed @ offshore prices - <a href="http://www.iponweb.net">http://www.iponweb.net</a> Personal website - <a href="http://martynov.org/">http://martynov.org</a> 271544 271579