FrmameWork and Design Pattern

[Brijesh NK <br...@sysarris.soft.net>]

Hi,
I am totally confused with the word FrameWork and Design Patters. Could any
body explain the distinct difference between these two. Or how these words
are related to each other?


Thanks & Regards


Brijesh


--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>

Re: FrmameWork and Design Pattern

[Eddie Bush <ek...@swbell.net>]

Have you ever seen a new building going up?  You know - when there's 
just steel beams there?  That would be a framework (roughly speaking). 
 Now, the design patterns would deal with how the beams should be 
situated so that the building will hold-up over time -- or so that the 
building may be added onto later more easily (if this is a design goal).

Frameworks are super-generic "libraries" (APIs) which allow you to 
become productive with something faster by taking care of most of the 
"muss and fuss" and allowing you to build upon their base to bring 
things to fruition faster.  Patterns may be used to design the framework 
- in fact, Struts makes use of several J2EE Blueprint patterns.  All in 
the world a pattern is ... is just "a solid, proven way for solving a 
problem".  Have you read any design pattern books?  That would make for 
good research material to help better understand what a pattern is.

Brijesh NK wrote:

>Hi,
>I am totally confused with the word FrameWork and Design Patters. Could any
>body explain the distinct difference between these two. Or how these words
>are related to each other?
>
>
>Thanks & Regards
>
>
>Brijesh
>

-- 
Eddie Bush





--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>

Re: FrmameWork and Design Pattern

["Craig R. McClanahan" <cr...@apache.org>]

On Mon, 25 Nov 2002, Brijesh NK wrote:

>
> I am totally confused with the word FrameWork and Design Patters. Could any
> body explain the distinct difference between these two. Or how these words
> are related to each other?
>

To me (at least informally), there are a couple criteria that distinguish
the two concepts:

* Design patterns are "smaller", while frameworks are "larger".  You
  might use several design patterns in a single class, while frameworks
  (like Struts) might implement many design patterns.

* Design patterns are "abstract" while frameworks are "concrete".
  The design patterns describe general relationships between the actors,
  without any definition of specific APIs (or even of specific languages
  used to implement them).  Frameworks tend to provide concrete APIs,
  in a particular language, that provide the basic foundation on top of
  which you build an application solution.

* Design patterns are "flexible" while frameworks are "predefined".  The
  description of a design pattern often describes alternative strategies
  you can use to implement variations on the theme of that particular
  pattern.  Frameworks have typically chosen particular patterns for you
  (although they often give you extension points at which to modify the
  pre-chosen behavior).

Things that are similar (and tend to lead to confusion):

* A given application will often implement many design patterns, and
  can just as easily utilize multiple frameworks for different portions
  of the problem.  For example, one could consider the Servlet API to
  be a framework, on top of which the Struts framework runs.

* Both design patterns and frameworks describe relationships between
  multiple application components - the difference is in the specificity
  of the description.

>
> Thanks & Regards
>
>
> Brijesh
>

Craig


--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>