Structure of Design Patterns
page 1 of 9
Published: 06 Dec 2006
Abstract
This article helps the reader to understand how a series of articles describing design patterns are structured, thereby helping the reader to get the most out of the articles. It also helps the reader to locate the particular section of the article which is of interest to them.
by David Simmonds
Feedback
Average Rating: This article has not yet been rated.
Views (Total / Last 10 Days): 30304/ 75

Introduction

Each of the patterns in this tutorial has the following structure.  A complete list of my articles can be found here:
http://aspalliance.com/author.aspx?uId=59827

Name of Pattern 

P+ P- E A R D M+ M- S+ S-

The subscripts which appear at the end of the name indicate how the pattern is affected by other issues.  Knowing this helps us to compensate for the deficiencies or make use of the advantages.  Below are the meanings to each of they symbols.

P+: Helps the code to perform faster.

P-: If used unwisely, the pattern may slow down the code.

E :  Helps to create code that is maintainable in an Extensible way (adding functionality).

A :  Helps to create code that is maintainable in an Adaptable way (Changing functionality).

R : Aids in code reuse (several applications will be able to use it as a library).

D : Allows you divide up tasks based on team member strengths.

M+: Helps with efficient memory management.

M- : If used unwisely, the pattern may cause improper memory usage.

S+: Naturally helps to improve application security.

S-: If used improperly, the pattern may compromise application security.


View Entire Article

User Comments

No comments posted yet.

Product Spotlight
Product Spotlight 





Community Advice: ASP | SQL | XML | Regular Expressions | Windows


©Copyright 1998-2017 ASPAlliance.com  |  Page Processed at 2017-07-27 10:17:52 AM  AspAlliance Recent Articles RSS Feed
About ASPAlliance | Newsgroups | Advertise | Authors | Email Lists | Feedback | Link To Us | Privacy | Search