Originally posted by Maki Jav:But what is "clearly" an association then?
Originally posted by Barry Brashear:
What design pattern would you use to transfer the data coming from one
application into another?
Originally posted by Paul Croarkin:
Empower yourself and just do it.
I'm not sure what you mean by "unit testing phase"
Did it's better to start with learning JUnit or TDD first (as big picture then JUnit is to apply TDD)?[/QB]
Originally posted by Dirk Schnelle:
When the project starts, developers also start developing tests. But as the project continues the developers have less time to maintain their tests and turn to pure hacking.
maybe I am outside the realms of design patterns here
Originally posted by Vladas Razas:
For my project I chose to have simple beans and I keep relationship information in other classes. I still have my lightweight beans. Did I chose correctly?
Originally posted by Maxim Katcharov:
What do you call any sort of class that is used by the owner, but no client of the owner is aware of that class?
But what if you're trying to define an inheritance tree? It is my understanding that abstract classes are used to define inheritance trees
I usually hear that abstract classes are to be used when some common functionality can be factored out of a set of classes.
What if there is no common functionality, but you want to create a superclass for polymorphism? Would a good designer ever do this?
"Software Architecture Design Patterns in Java"