DebugWare Patterns (Part 2)

Next pattern is called

Tool Façade (or Tool Facade)

It is used when there is a tool with a cumbersome interface like command line with many options and there is a need for a better and easier to use interface, for example, GUI. This can be illustrated on the following UML component diagram:

Excellent example of this pattern is:


designed as a GUI wrapper around command line tool AddPrinter. Adding the powerful GUI interface allowed to extend its functionality and even find new domains, like testing, where the tool can be used. Excellent information about this tool can be found in the article:

Understanding and using Citrix StressPrinters

- Dmitry Vostokov @ -

4 Responses to “DebugWare Patterns (Part 2)”

  1. Dmitry Vostokov Says:

    New version of StressPrinters tool is available:

    StressPrinters 1.3.2

  2. Crash Dump Analysis » Blog Archive » DebugWare Patterns (Part 4) Says:

    […] or when CUI interface was developed earlier and we don’t want to touch tool code (see Tool Façade pattern). Therefore this common pattern is called Dual Interface. Some tool […]

  3. Crash Dump Analysis » Blog Archive » DebugWare Patterns: A Case Study (Part 1) Says:

    […] problem. Would we start with GUI? Most tools are command line tools and we therefore choose Tool Façade pattern to decouple GUI from […]

  4. Crash Dump Analysis » Blog Archive » HP uses StressPrinters for driver stress testing Says:

    […] recent news about StressPrinters tool designed according to Tool Façade DebugWare […]

Leave a Reply

You must be logged in to post a comment.