The three concepts are orthogonal to each other.

A design pattern defines a successful solution to a common design
problem, which is largely independent of programming language or
platform. An example of a pattern is the "Model View Controller" (aka
MVC) pattern that is found in user interface code. The pattern is
implemented in C++, Delphi, Java, Ruby, etc.

A framework is a specific implementation that provides a well-defined
interface to already written code, freeing the programmer to work on the
application without being too concerned about how the tedious stuff
behind the solution implementations are handled. An example is Struts,
which is a specific implementation of MVC for servlet engines written in
Java. While frameworks generally implement patterns, implementing
patterns is not a prerequisite for a framework.

An architecture defines the surrounding environment in which the
application must run. It may be fairly rigid, or fairly loosely
defined. Architectures may define acceptable frameworks and platforms,
but it does not generally specify patterns and coding style.

Examples of architecture are "x86 hardware", "J2EE", "CICS COBOL",
etcetera.

Does this help?

On Mon, 2006-05-29 at 16:39 +0000, java_kalyan wrote:
> what is the difference between design patterns ,Framework, arcitecture
>
>
>
>
>
>
>
>
> SPONSORED LINKS
> Basic programming
> language
> Computer programming
> languages
> Programming languages
> Java programming
> language
>
>
> ______________________________________________________________________
> YAHOO! GROUPS LINKS
>
> 1. Visit your group "Firebird-Java" on the web.
>
> 2. To unsubscribe from this group, send an email to:
> Firebird-Java-unsubscribe@yahoogroups.com
>
> 3. Your use of Yahoo! Groups is subject to the Yahoo! Terms of
> Service.
>
>
> ______________________________________________________________________
>