DebugWare Patterns (Part 8)

Troubleshooting Unit of Work is another pattern frequently used in manual troubleshooting and debugging. This is usually some independent and self-sufficient list of steps to perform to check something from a troubleshooting checklist or a manual and can be implemented as a separate loadable module, a class to reuse or a function to call. Output from such units of work can be stored in a blackboard system or processed by tools implementing Checklist DebugWare pattern. Typical example is an implementation of the following document:

Required Permissions and Rights for the Ctx_CpsvcUser Account

as a tool:

CTX_CpsvcUser Re-creation Tool for 32-Bit and 64-Bit Versions of Presentation Server 4.5

- Dmitry Vostokov @ -

3 Responses to “DebugWare Patterns (Part 8)”

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

    […] a manual. Checklist pattern summarizes this recurrent practice. Checklist Coordinator orchestrates troubleshooting units of work (TUWs) components from TUW Repository according to checklists from Checklist Repository (in the […]

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

    […] troubleshooting tools and their components (like TUW modules from checklists) reuse the same code over and over, for example, checking registry keys […]

  3. Crash Dump Analysis » Blog Archive » Welcome to Tool Objects! Says:

    […] very customizable and similar buttons can be created to launch troubleshooting tools and execute troubleshooting units of work for any client and server applications. It will also be covered in the forthcoming Software […]

Leave a Reply

You must be logged in to post a comment.