Using design pattern

From: al (allin_at_168.net)
Date: 12/24/03 

Date: Tue, 23 Dec 2003 23:03:37 GMT

Reading "Design Pattern - Elements of Reusable Object-Oriented Software"
does help a lot about using patterns in software development.

There are many lines in the book, which doesn't make much sense to me. Hope
you can help clarify some for me.

1. "...represent algorithm as object." What does it means? Is it referring
to pattern like Strategy?

2. "application domain-specific patterns" What does it means?

3. "The consequences of a pattern include its impact on a system's
flexibility, extensibility, or portability." My understanding about
"flexibility" and "extensibility" here is changing/adding to one part
without affecting the rest. Is this a correct understanding? Regarding
"portability" am I totally lost: How could a pattern helps "portability"?

4. What does it mean by "Reusable" in Design Pattern? Is it referring to
reuse patterns, the implementation mechanism of patterns, or both?

5. The benefits of using patterns are summarized by me as shown below:

    a. decoupling objects.
    b. make a software system easier to maintain.
    c. make a system reusable.

Is this a complete list? Is there some important things missing from the
list?

Merry Christmas!

Relevant Pages

  • Re: PZ Myers on Evolution without Natural Selection
    ... Design is a subset of pattern. ... this may take the form of being white in a snowy environment, ... design pattern' to accurately describe the distinction you want to ... Do you understand the concept of a tautology ?http://en.wikipedia.org/wiki/Tautology_%28rhetoric%29 ...
    (talk.origins)
  • Re: advantages of forth over other languages
    ... Design patterns are nothing more than documentation that provides a name, an intent, context, and discussion. ... The Wikipedia article on design patterns gives a good overview of the usual sections found in a design pattern: ... The purpose of pseudocode is to describe abstractly an implementation. ... The basic idea in COR is that you have some notion of a command and you pass this command on down through code that either acts on the command or passes the command on to other code that can act on the command. ...
    (comp.lang.forth)
  • Re: DALC vs DAO
    ... DAO is a design pattern. ... >it is a GOF design pattern or at least a branch off of that. ... The J2EE DAO (Data Access Object) pattern is, ... equivalent to a "Table Data Gateway" or "Row Data Gateway" ...
    (microsoft.public.dotnet.general)
  • Re: Has anyone used design patterns in his/her C#.NET project?
    ... Although I read the entire book about Design Pattern, ... entire process and not currently need the flexibility of a factory. ... Where I routinely use factories is on communication type libraries. ...
    (microsoft.public.dotnet.general)
  • Re: should getInstance() be idempotent?
    ... should handle that (with, for example, the MonoState pattern) without ... in some pattern name that was never really there. ... Read about a design pattern. ... Does you using a complex word mean that ...
    (comp.lang.java.programmer)