Test Management Approach

TMap ® ( Test Management Approach ) is a model in the field of testing and quality assurance of software in which all related aspects, the environment and the procedure to be structured.

This TMap is more special than process models such as ITIL or the V-model, looking at the whole process of software development. It was published in 1995 by Martin Pol, Ruud Teunissen and Erik van Veenendaal. TMap is standard in many organizations around the world. TMap is Sogeti Nederland BV registered trademark of TMap ® TPI can be compared. While structured TMap the tests themselves, wants TPI ® - Test Process Improvement - optimize the entire testing process. TPI ® This is at the management level, while TMap is to be used in a specific project. TMap is how TPI is a registered trademark of Sogeti Group ( an independent part of the Capgemini Group ). This TMap is based on practical experience and thus provides no theoretical, but a pragmatic method dar. TMap has grown into an internationally recognized standard and is used by companies in various industries.

Core areas of TMap

The testing process is divided into 4 areas, divided the so-called core modules:

Benefits of TMap:

  • TMap is based on experience from a variety of projects
  • Takes into account current trends
  • Focused on testing process
  • Optimized risk coverage and test depth
  • Maximum involvement of stakeholders

Business based test management ( BDTM )

The selection of test cases is due to the following considerations: what are the risks, what should be the result of how much time must take the test to complete and what it will cost. Based on these considerations that are taken in consultation with the customer, TMap support the business process and is close to the customer.

Characteristics of BDTM approach:

  • Total expenses for the testing refers to risks of the system to be tested for an organization. The use of human resources and budget is focused on parts of the system that are most important for the organization. TMap offers the possibility to determine how many risks are covered by the selected test and so estimate the residual risk.
  • The estimated cost and the planning of the test process are closely associated with the specified test strategy. So as to address changes slightly, there is always a plan available is how much time, budget and resources are needed.
  • The customer is involved in the testing process, it can be better addressed the needs of the customer. A BDTM approach can make the consequences of future and past decisions visible.

Fully structured testing process

The structured test process is divided into:

  • Master plan and management of the entire testing process
  • Acceptance and system testing
  • Developer tests

Master Plan

This is not unnecessarily tested twice in the entire test sequence, the so-called master plan in collaboration with the customer is created. The test thus Manager shall determine in consultation with the client and other stakeholders the distribution, which is in which test level tested with what intensity. The aim here is the most important defects as early and as economically as possible to discover. The master test plan forms the basis for the test plans of the individual test steps.

Activities:

Acceptance and System Test

Acceptance and system testing be considered an autonomous processes. They have their own test plan its own budget and often own test environment.

Developer test

Developer tests are tests in which knowledge of the technical implementation of the system are required. Developer tests shall not be treated as an autonomous TMap process. The developer runs the tests themselves.

Breakdown of the phase model

As a system development process is a test process from a variety of activities. The various activities are shown in the phase model. There are the following phases:

  • Planning phase
  • Control phase
  • Installation and maintenance of infrastructure
  • Preparation phase
  • Specification phase
  • Implementation phase
  • Final phase

Planning phase

The planning phase lays the foundation for a manageable and quality testing process. Therefore, it is important to begin this phase as early as possible.

Activities:

Control phase

The primary test process is performed infrequently according to plan, accordingly, the implementation of the test plan must be monitored and adjusted if necessary. This happens in the control phase.

Activities:

Installation and maintenance of infrastructure

Here the necessary test infrastructure and the necessary resources will be provided for. A distinction is made between test environments, test tools and jobs.

Activities:

Preparation phase

Here's a Testbarkeitsreview the test basis is carried out first and foremost. The objective of this phase is to arrive at a test basis with appropriate quality.

Activities:

Specification phase

The specification phase defines the required tests and their initial situation fixed (s). The goal is to prepare as much as possible, so that the tests can be carried out as quickly as possible if the developers deliver the test object.

Activities:

Implementation phase

The main goal of the implementation phase is to get an insight into the quality of the test object, since the stipulated tests are performed.

Activities:

Final phase

TMap offers many advantages with respect to repeatability of processes. The aim of this phase is to preserve the products of the implementation phase, so they can be reused later products can include test cases, test environment, experiences and reviews.

Activities:

Full set of tools

TMap supports the correct implementation of the structured test process with a complete set of tools. This work focuses on the following topics:

  • Techniques: How is testing

The following techniques are available:

  • Test effort estimation
  • Fault Management
  • Creating metrics
  • Product Risk Analysis
  • Test Design
  • Product testing
  • Infrastructure: Where and what is tested

To test, a test environment, test tools and jobs are needed.

  • Organization: Who is testing

Structured testing requires attention to the following points:

  • Testing Guidelines
  • Permanent test organization
  • Test organization in the project
  • Test experts
  • Test roles

Adaptive, flexible testing process

TMap is an approach that can be applied in all test situations and in combination with all system development methods. The adaptability can be described by four characteristics:

  • Responding to changes
  • Use products and processes (again)
  • Learning from Experience
  • Try before trying

Since today approaches to IT developments can be extremely variable, here are some application areas are mentioned where TMap can be used.

  • Customer -supplier relationship (outsourcing)
  • Interactive, incremental, waterfall and agile approaches
  • New development, maintenance and migration of information systems
  • When combined development process, such as in-house, based on the re-use, use of standard packages, assembly of purchased modules, all within a single IT architecture
  • To cover non-functional requirements of the information system in the test procedure
  • In situations where the communication processes and the associated skills much attention must be paid to
766413
de