Last week, we had the author of TDD for a Shopping Website LiveProject. Friday at 11am Ranch time, Steven Solomon will be hosting a live TDD session just for us. See for the agenda and registration link
I think you should not worry about these numbers. For instance, I finished with 5 packages (and other 4 packages inside them), 56 classes and around 2000 lines of code. I think you should only worry if you have to many inner classes, and too many classes with too much code. I would say that this may be considered in the OO Design part of their evaluation.
Well, I would avoid this, you know... take a look at this article: http://developers.sun.com/mobility/midp/articles/slimming/. Even though it is about wireless Java applications, the behavior of the JVM theoretically is the same (in this case), and they do advise to avoid inner classes. I've also seen many discussions around the software engineering comunity, where people tend to avoid inner classes. I do too because I believe it makes the code more cohesive, maintainable, reusable and readable.
I also have a big number of classes because many of them are interfaces, and I created several components as well.
Cheers, Roberto Perillo
SCJP, SCWCD, SCJD, SCBCD
Don't mess with me you fool! I'm cooking with gas! Here, read this tiny ad:
free, earth-friendly heat - a kickstarter for putting coin in your pocket while saving the earth