The TMap Test Management approach is based on years of practical software testing experiences and developed by the R&D department of IQUIP Informatica B.V. It enjoyed an overwhelming interest from its first publication in Dutch in 1995. Many companies and government departments arranged their organization and performed their test processes as much as possible according to TMap. Within a few years, it became the standard for software testing within the Dutch-speaking countries. The generic approach of the model offers ample space to tune the TMap standard to specific applications and organizational needs. TMap withstands the frequent innovations in IT since one of its main advantages is the possibility to create extensions for progressing IT developments, such as object orientation (OO), enterprise resource planning (ERP), component-based development (CBD), test automation, the Internet, etc.
This book describes TMap as the approach for the structured (white-box and black-box) testing of information systems. It answers the what, when, how, by what, and by whom questions regarding testing. In order to make the design and execution of test processes more structured, TMap is based on four cornerstones related to those questions.
The "what/when" questions are answered by the lifecycle model, a description of the test cycle related to the development cycle. The "how" question is answered in the description of the techniques for planning, preparation and execution of several tests. The ‘by what’ question is considered in the description of the infrastructure. And the description of the organization aspects answers the "by whom" question.
Review By: Marybeth Norton 05/07/2005Your mission, if you accept it, is to control the risks associated with the introduction of a new information system. If you choose to accept your mission, obtain a copy of this book. It is an excellent reference book for everyone involved in the quality assurance software process.
It seems the authors wrote this book on the premise that it would become the standard text on the subject. It effectively describes all aspects and combinations for implementation of TMap into all company information systems, both for high- and low-level structured testing. The style of the book is to describe the main topic first and drill down and down, guiding you meticulously through each step. The book comprises six parts. In places, it is difficult and heavy reading; other parts are easy reading, with checklists, forms, templates, and lots of guidance.
Part I (General Principles) gives anyone who does not have any experience in software testing a good background of the QA process and types of testing that exist. Part II (Lifecycle) provides an overview of the four cornerstones of a structured test approach, consisting of a lifecycle of test activities, good organizational embedding with the right infrastructure, and usable techniques. The Technique section is more difficult—geared to the more sophisticated tester interested in Test Point Analysis and structural path techniques. Part IV (Organization) looks at a lot of job descriptions and job requirements regularly posted in HR as well as justifications for why organizational charts are the way they are. Part V (Infrastructure Guidelines) is included for test environments. It lists pros and cons of test tools, and when and how to use them successfully. Part VI (Variations) goes into all the different flavors and combinations of TMap that can be incorporated into any corporation. This book is highly recommended.