Identifying objects using design patterns

Hi there!

I am a beginner learning OO design patterns. I hope some of U expeienced guys can help me with this...

I read that design patterns follow certain guidelines to identify objects. I had a brief look at patterns and got confused on where to start. Right now I am having the specifications of a system and I want to design it using design patterns. Can U tell me what are the pattern(s) that help identify objects.

Also it would be great if U can point me to some case studies on the Net, which shows some steps in designing using DP.

Any suggestions/feedback on this would be of great help.

best regards,

M

[657 byte] By [nmhb23a] at [2007-9-28 7:35:57]
# 1

There is no easy answer to your question.

To get started:

- get the book Design patterns by gamma et al.

- start reading it.

- pick a small area of your domain, which you expect to end up in a few classes

- try to come up with a model

- check if any of the patterns apply

- ask others (including the forum) what they think of your model

- repeat with the last four steps, until changes in the model become small or you run out of time.

Have a look at the coad letter (search google for it) gives many examples of good design.

regards spieler

spielera at 2007-7-9 18:49:25 > top of Java-index,Other Topics,Patterns & OO Design...
# 2
Hi spieler!Thanks very much for UR input. That helps me get going with DP.best regards,M
nmhb23a at 2007-7-9 18:49:25 > top of Java-index,Other Topics,Patterns & OO Design...
# 3

Don't worry so much about using patterns in a design - patterns are known solutions to common design/implementation problems.

Basically, don't go looking for the 'perfect set of patterns' for an application. Instead, just use good OO techinques; when you run into a problem (or when you run into something you think other people must have already solved) THEN go looking for the appropriate pattern to use.

Too many times I've seen otherwise good designs run into the ground where the architect looks for how to apply patterns when they should have looked for the problems.

Summary:

problem first, then solve by patterns

larsonaa at 2007-7-9 18:49:25 > top of Java-index,Other Topics,Patterns & OO Design...
# 4
larsona is correct... people sometimes run around with a hammer thinking everything is nail. Patterns also can have limitations. Strive to know when a pattern should be used and why, and what limitations the pattern imposes.
wcoonroda at 2007-7-9 18:49:25 > top of Java-index,Other Topics,Patterns & OO Design...