
- Forum
- Testing
- Software Patterns
- Which design pattern should I use?
Which design pattern should I use?
This is a discussion on Which design pattern should I use? within the Software Patterns forums, part of the Testing category; I am about to start constructing class diagrams for this system: http://groups.google.co.uk/group/com...4e027c6c71e05e or http://tinyurl.com/7bztt I obviously want to reuse a ...
-
10-08-2005, 06:00 AM #1Davey Guest
Which design pattern should I use?
I am about to start constructing class diagrams for this system:
http://groups.google.co.uk/group/com...4e027c6c71e05e
or
http://tinyurl.com/7bztt
I obviously want to reuse a tried and tested design pattern for such a
system but unfortunately I don't have great experience in designing systems
like this.
Which design pattern(s) would you recommend I use for this system?
-
10-09-2005, 12:44 AM #2Roedy Green Guest
Re: Which design pattern should I use?
On Sat, 08 Oct 2005 10:00:27 GMT, "Davey" <davey@hotmail.com> wrote or
quoted :
>I obviously want to reuse a tried and tested design pattern for such a
>system but unfortunately I don't have great experience in designing systems
>like this.
Design patterns can't be chosen from such broad brush information.
They are for solving particular problems that come up in coding.
--
Canadian Mind Products, Roedy Green.
http://mindprod.com Again taking new Java programming contracts.
-
10-09-2005, 03:46 AM #3Nick Malik [Microsoft] Guest
Re: Which design pattern should I use?
"Davey" <davey@hotmail.com> wrote in message
news:%MM1f.40$967.37@newsfe1-gui.ntli.net...
>I am about to start constructing class diagrams for this system:
>
> http://groups.google.co.uk/group/com...4e027c6c71e05e
>
> or
>
> http://tinyurl.com/7bztt
>
> I obviously want to reuse a tried and tested design pattern for such a
> system but unfortunately I don't have great experience in designing
> systems like this.
>
> Which design pattern(s) would you recommend I use for this system?
>
I read a good bit of the thread you indicated.
a) don't write a high-end system with low-end software and hardware. Assume
less than 100 transactions per second and write accordingly. When you have
the customers, you can afford a better system. Be agile. Write what you
need right now.
b) Each of your components will have different needs, and therefore will
need different patterns applied. RTFM. An excellent starting place for a
beginner in DP is "Design Patterns Explained" by Shalloway and Trott.
(Examples are in Java).
c) Mixing the technology like that is going to cost you a fortune to
maintain. Write the whole thing in Java or in C#. Don't swap back and
forth between Java, C++, and PHP.
Good Luck,
--
--- Nick Malik [Microsoft]
MCSD, CFPS, Certified Scrummaster
http://blogs.msdn.com/nickmalik
Disclaimer: Opinions expressed in this forum are my own, and not
representative of my employer.
I do not answer questions on behalf of my employer. I'm just a
programmer helping programmers.
--
-
Sponsored Ads

Reply With Quote





