DebugWare Patterns (Part 5)

Usually after writing and using a tool we think about an extension of it or we find another tool that is suitable as that extension. In such cases it is better to reuse existing components and adapt the former tool to use the latter. Tool Chain is a good pattern name here. A programming analogy could be a compiler and linker:

Typical example could be a logging tool that now acquires log viewer functionality by implementing a button that launches a separate log viewer or vice versa, a log viewer that can now do logging. Another simple example is a command file that launches different tools in a sequence. The tools might not be related by the data they produce and operate upon: this not the same as well-known architectural Filters and Pipes pattern. What is important is the fact that tools are related buy overall tool chain goal, for example, to debug problems by recording and analyzing log files or monitor some process activity and periodically create memory dumps:

- Dmitry Vostokov @ DumpAnalysis.org -

One Response to “DebugWare Patterns (Part 5)”

  1. Crash Dump Analysis » Blog Archive » DebugWare Patterns (Part 6) Says:

    […] pattern that logically flows from Tool Chain is called Tool Box. Their principal difference is that the former launches subordinated tools in […]

Leave a Reply

You must be logged in to post a comment.