Home > Articles > Certification > Microsoft Certification

  • Print
  • + Share This
Like this article? We recommend

Like this article? We recommend

Patterns Drilldown

Since the late 1980s and the popularity of object-oriented programming languages (one could argue that its precursor is in volumes such as Donald Knuth's Art of Computer Programming, from the 1970s), developers have been keen on deriving the key benefit of object-oriented programming (OOP): reuse. Although OOP goes a long way toward this goal by providing inheritance, encapsulation, and polymorphism, these alone do not produce flexible and reusable software.

In the early 1990s, some software developers drew an analogy with an architect (of actual buildings) named Christopher Alexander, whose books A Pattern Language (1977) and The Timeless Way of Building (1979) postulated and defined recognizable and repeatable patterns that are used in designing great architecture. Simply put, the definition of a pattern encompasses the following description written by Alexander:

Each pattern describes a problem which occurs over and over and over again in our environment, and then describes the core of the solution to that problem, in such a way that you can use this solution a million times over, without ever doing it in the same way twice.

These developers immediately realized that the same concepts could be applied to software design and that there likely were recognizable and, therefore, repeatable ways of solving common design problems. The result was the book Design Patterns: Elements of Reusable Object-Oriented Software, by the GoF (Addison Wesley Professional, 1994), which documented 23 such patterns. For framework developers, this book is an invaluable resource to get you thinking and seeing your difficult problems in terms of patterns. Other books, such as Design Patterns Explained: A New Perspective on Object-Oriented Design, by Alan Shalloway and James Trott (Addison Wesley Professional, 2001), help to explain the ideas behind some of the more common patterns more fully and serve as more of a tutorial for developers just getting their minds around patterns. In addition, magazines devoted to framework developers have more recently included regular discussions of patterns; MSDN Magazine has even begun a semi-regular column on the subject.

All design patterns are not created equal, however. In fact, the GoF grouped its 23 patterns into 3 categories, as follows:

  • Creational. These patterns (and there are five documented in the GoF) deal with the instantiation of objects. Specifically, they are concerned with how to abstract the instantiation process so that software can be independent of who creates the objects, when they are created, and which particular objects (runtime types) are created. Creational patterns often rely on inheritance as well as polymorphism. The goal of creational patterns is to decouple the process of instantiating objects and allowing a more dynamic approach.

  • Structural. This second grouping (seven documented in the GoF) documents patterns that deal with how objects can be combined to form larger structures. Several of these patterns are typically ones developers are familiar with intuitively, while others are more complex. Structural patterns sometimes use inheritance.

  • Behavioral. The final grouping of patterns (11 of which are documented in the GoF) include those that are concerned with the communication and assignment of responsibilities between objects. Behavioral patterns can be based on either inheritance (called behavioral class patterns) or aggregation (called behavioral object patterns).

As an example of a pattern, consider the creational Factory Method pattern. This pattern can be used when an application needs to create instances of a class but when the class to create is not known at runtime. The solution, as encapsulated in the pattern, is to defer the instantiation to a factory method.

Each pattern can be documented by a Unified Modeling Language (UML) static structure or class diagram, as shown in Figure 1. In this diagram, you'll notice that the goal is to create objects of the type Product (defined as an interface or, in this case, a base class) such as the derived ConcreteProduct class. This is accomplished as follows: The Creator exposes an abstract FactoryMethod that derived classes such as ConcreteCreator implement, to create instances of a particular ConcreteProduct. The client then manipulates the Creator and might not know at design time which ConcreteCreator was used to create the ConcreteProduct.

Figure 1Figure 1 The Factory Method pattern.

A simple code example in VB .NET of the pattern is shown here. ConcreteProduct is defined by the Book class, Creator by ProductCreator, and ConcreteCreator by BookCreator:

Public MustInherit Class Product
End Class

Public Class Book : Inherits Product
  Public Overrides Function ToString() As String
    Return "Book"
  End Function
End Class

Public MustInherit Class ProductCreator
  Public MustOverride Function CreateProduct() As Product

  Public Sub AddToCollection()
  End Sub
End Class

Public Class BookCreator : Inherits ProductCreator
  Public Overrides Function CreateProduct() As Product
    Return New Book
  End Function
End Class

A client can then write polymorphic code like the following to create a product object and call one of its methods:

Private Sub PrintProduct(ByVal creator As ProductCreator)
  Dim p As Product = creator.CreateProduct()
End Sub

As a result, the client code needn't be written with a particular product in mind, but can work with any product for which a factory method is in place. Note that the ProductCreator object would still need to be created at some point before passing it into the PrintProduct method. The GoF documents several different ways to implement this.

This example shows how using design patterns can benefit developers in two primary ways:

  • By providing a common design vocabulary. In his posthumously published work Sylva Sylvarum, Francis Bacon (1561–1626) identified a mode of human perception that he called "idols of the marketplace," in which ideas or concepts cannot even be conceptualized until an adequate vocabulary is in place. This highlights the primary use of design patterns as spurs to thinking about and solving design issues that we wouldn't even be aware of without the ability to recognize the pattern.

  • By speeding development and writing less code. Second, and closest to most developer's (or at least their manager's) hearts is the need to speed the development process. By applying patterns, a developer needn't reinvent the wheel, but can instead leverage the effort already undertaken to develop and document the pattern. Many of the patterns also provide optimized solutions, so in many cases, a developer ends up writing less code by applying the pattern.

  • + Share This
  • 🔖 Save To Your Account

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information

To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.


Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.


If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information

Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.


This site is not directed to children under the age of 13.


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information

If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information

Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents

California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure

Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact

Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice

We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020