Design patterns are kinds of "recipes" an abstract description of a best practice to overcome a particular problem. Access a DataBase? check out DataAcessObject. Does your user interface change a lot? check out MVC.
If you want to get in depth into the world of design patterns (an excellent thing to do) check out these two books:
Core J2EE Patterns: Best Practices and Design Strategies, Second Edition
Design Patterns (also known as the Gang of Four book)
These are the two objectives for the
test regarding design patterns:
13.1 Given a scenario description with a list of issues, select the design pattern (Value Objects, MVC, Data Access Object, or Business Delegate) that would best solve those issues.
13.2 Match design patterns with statements describing potential benefits that accrue from the use of the pattern, for any of the following patterns:
* Value Objects
* MVC
* Data Access Object
* Business Delegate
[ July 31, 2003: Message edited by: Jessica Sant ]
