TMap®

Test Management Approach (TMap) is a software testing methodology created by Sogeti Netherlands which is a part of the French Capgemini. The main target of TMap is to provide the user of this methodology with a complete software testing guide. Although TMap is a Dutch product by origin, the method has become a worldwide standard and the book has been translated into several languages (e.g. French and English).
The first method was created in 1995 and written by Martin Pol, Ruud Teunissen en Erik van Veenendaal. At the end of 2006 a new version was published called TMap Next by other authors (Tim Koomen, Leo van der Aalst & Bart Broekman). The main reason for this new version is that the old authors were no longer working for Sogeti and the company wanted to make the method its own again.

Test Management Approach (TMap) is a software testing methodology created by Sogeti Netherlands which is a part of the French Capgemini. The main target of TMap is to provide the user of this methodology with a complete software testing guide. Although TMap is a Dutch product by origin, the method has become a worldwide standard and the book has been translated into several languages (e.g. French and English).

The 4 essentials of TMap
The specific TMap content of a structured test approach can be summarised in four essentials.

The first method was created in 1995 and written by Martin Pol, Ruud Teunissen en Erik van Veenendaal. At the end of 2006 a new version was published called TMap Next by other authors (Tim Koomen, Leo van der Aalst & Bart Broekman). The main reason for this new version is that the old authors where no longer working for Sogeti and the company wanted to make the method its own again.

  1. TMap is based on a business-driven test management (BDTM) approach.
  2. TMap describes a structured test process.
  3. TMap contains a complete tool box.
  4. TMap is an adaptive test method.

The first essential can be related directly to the fact that the business case of IT is becoming ever more important to organisations. The BDTM approach provides content that addresses this fact in TMap and can therefore be seen as the ‘leading thread’ of the structured TMap test process (essential 2). The TMap life cycle model is used in the description of the test process. Furthermore various aspects in the field of infrastructure, techniques and organisation must be set up to execute the test process correctly. TMap provides a lot of practical applicable information on this, in the form of e.g. examples, checklists, technique descriptions, procedures, test organisation structures, test environments and test tools (essential 3). TMap also has a flexible setup so that it can be implemented in different system development situations: both for new development and maintenance of a system, for a self-developed system or an acquired package, and for outsourcing (parts of) the testing process. In other words, TMap is an adaptive method (essential 4).

The TMap model of essentials represent the 4 essentials. For more information, click on each of the essentials.