1) A design pattern is a set of techniques or a methodology for writing your code. I tend to think of design patterns as named coding tips/tricks on how you write you code. Patterns are a very well thought out ways of solving a coding problem. I say named because each pattern has a name. The reason that they are named is that everyone discussing how to implement the code knows what you mean when you say your coding something using the Observer or factory pattern.
An architecture on the other hand are the different parts of the application and how they fit together. For instance, the UI might be part of the architecture. If your using a webservice that might be part of the architecture.
if you are using both terms, then Architecture encompasses more technical or structural decisions about how to build or construct something, especially those decisions that will be hard (or harder) to change once implemented, whereas Design encompasses those decisions that either are easy to change later (like method names, class <-> file organizational structure, design patterns, whether to use a singleton or a static class to solve some specific problem, etc. ) and/or those that effect the appearance or esthetic aspects of a system or application (Human Interface, ease of use, look and feel, etc.)
No comments:
Post a Comment