note Biker <P> Sit down with paper and pen (and posibly a colleague of yours). <b>Talk</b> yourself through the usage of the future system. Go through everything that should be possible and how. <BR> <BR> Whenever you pronounce a <i>noun</i>, put it down as a potential class. If you also hear yourself mentioning that the <i>noun</i> must be able to <i>verb</i>, then you write down this as a potential method of the class. <BR> <BR> In Perl you're not <b>forced</b> to use objects and very often you will use procedural code to handle <i>entities</i>. These <i>entities</i> will become objects implemented in you class modules. <BR> <BR> Implement the skeletons for the classes and repeat the verbal session. Ask yourself if your classes really represent the <i>nouns</i> you need in the system and if they are able to perform all the <i>verbs</i> that must be done. Redo. ;-) <BR> <BR> Another thing to think about is a way to handle the numerous constant values and common Perl subs that must be shared by your (presumably) large number of Perl scripts. <BR> <BR> Decide the strategy for a/the database backend. <HR> Everything went worng, just as foreseen. </P> 160520 160520