• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Tim Cooke
  • Campbell Ritchie
  • Ron McLeod
  • Junilu Lacar
  • Liutauras Vilda
Sheriffs:
  • Paul Clapham
  • Jeanne Boyarsky
  • Henry Wong
Saloon Keepers:
  • Tim Moores
  • Tim Holloway
  • Stephan van Hulst
  • Piet Souris
  • Carey Brown
Bartenders:
  • Jesse Duncan
  • Frits Walraven
  • Mikalai Zaikin

Design patterns used in the SCJD assignment

 
Author
Posts: 587
6
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
The following design patterns are typically used in the SCJD assignment:

Adapter
Facade
Factory Method
Modified MVC
Proxy
Singleton
Value/Transfer Object

Does anyone utilize the following patterns within their assignment?

Abstract Factory
Bridge
Chain of Responsibility
Command
Composite
Decorator
Flyweight
Interpreter
Iterator
Mediator
Memento
Prototype
State
Strategy
Template Method
Visitor

Note: Check out the free Design Patterns refcard from DZone: http://refcardz.dzone.com/
[ June 22, 2008: Message edited by: Robert Liguori ]
 
Ranch Hand
Posts: 152
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I used a singleton, a facade, a value object, and maybe some more without realizing it or knowing the name.

One you didn't mention which I used is the Service Locator pattern.

But I believe patterns are a too much hyped phenomenom. The main goal is to get good sollutions; the use of patterns is at most a guideline, but not a goal in itself. Before deciding to use patterns one should always realize this.
 
Robert James Liguori
Author
Posts: 587
6
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
To quote Bert and Kathy from Head First Design Patterns, "Instead of code reuse, with patterns you get experience reuse."

Everyone has heard a billion times, "no need to reinvent the wheel"... reusing design patterns is a good thing and (in my opinion) candidates *should* be thinking about different patterns as they design their project.
 
Ranch Hand
Posts: 44
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi all,

I agree that developer should think and reuse design pattern but in my opinion design pattern is a guideline solution for specific problem. If you run into the problem that can solve with design pattern then you should use it. But not just use design pattern because other people use them. Using too much design pattern not only complicate your code but you may also get side effect of those patterns. Do not forget that nothing is perfect.

And for the question, I use typical pattern plus Abstract Factory (for create different type of connector), Command (for network communication) and Visitor (for record locking) design patterns.
 
Ranch Hand
Posts: 40
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I did actually used Strategy pattern without realizing it, while making the search mechanism.
 
Ranch Hand
Posts: 169
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
hi;

i used
Adapter
Facade
Factory Method
Modified MVC
Proxy
Value/Transfer Object
Decorator

regards.
Mohamed Darim.
SCJP, SCJD ...
 
pie. tiny ad:
Building a Better World in your Backyard by Paul Wheaton and Shawn Klassen-Koop
https://coderanch.com/wiki/718759/books/Building-World-Backyard-Paul-Wheaton
reply
    Bookmark Topic Watch Topic
  • New Topic