The 4 essentials of TMap

Business Driven Test Management (BDTM)

The test process will be arranged and controlled based on the BDTM-aspects results, risks, time and costs.

Structured test process

A complete and generic applicable description of the total test process.

Test goal table

Life cycle model

Preparation Specification Execution Completion Control

Master test plan and test plans

Master test plan Acceptance test System test Development test

Type of test goal Business processes A and B

Description Processes A and B must continue to function correctly after the change. Check of the credit worthiness ofthe application must be possible. Online offer must appear on the screen within one minute. Functionality, performance, user friendliness

Example of characteristics Functionality, performance, user friendliness Functionality

1
Critical success factors Change proposals Requirements Business processes ...
Assignment and test goals

User requirements Critical success factors Quality characteristics

B
Performance Functionality, performance, user friendlyness, suitabiliy
Master test plan risk table

S I

Evaluation

2
Determining risk class

Client

Characteristic: Object parts: Functionaliteit Chance of failure Test goals Damage Business process A H Business process B L Risk class =>

Subsys1 H A C A

Subsys2 M B C B

Totalsys L B B

Planning

Setting up and maintaining infrastructure

Activities diagram
Start 1 2 3 4 End Start

Results, Risks, Time and Costs

3
Determining Light/thorough testing

Master test plan strategy table

Characteristic/objectpart Functionality - subsys 1 - subsys 2 - total User friendliness Performance

RC

Evaluate

OT

ST

UAT

PAT

A B B B C

5
Allocating test techniques Test basis
Charasteristic Subsys1 Subsys2 Functionality A/ B/I functional Performance - -

I I
Test design table

C5.3 monitoring, reporting and adjusting

C5.2 Master test plan

management

1 Start 2 3 4 5 6

7 8 9 10 11 12 end

Totalsys B/ regression B/ usability

1 2 3 4 End

C6.3 monitoring, reporting and adjusting

C6.2 C6.2Test plan per test level

management

1 Start 2 3 4 5 6 7 8

9 10 11 12 13 14 end

C6.4-6.8 Test activities

C6.4 Setting up and maintaining infrastructure C6.5 Preparation C6.6 Specification C6.7 Execution C6.8 Completion

2 Start 1 3 2 1 2 Start Start 1 1 2 2 3 einde 4 einde 3 3 end 4 5 6 end

Test design table

Start Start

end

Creating test cases

6
Test execution

Characteristic Functionality Functionality User friendliness

Object part Test type Subsys1 Functional test (A/ ) Total system Regression (B/ ) Total system Usability (B/ )

Techniques te1: sample ST te2: sample ST te3: DCT te4: SUMI

Goal The objective of BDTM is the rearrangement and control of the test process. This is achieved in consultation with the client and involves finding a balance in the aspects results, risks, time and costs(4). Process First the assignment is formulated and the test goals are ascertained (1). Then the risk classes and depth of testing are determined (2 and 3). Subsequently the test techniques are allocated (5). From these the work activities of the tester can be mapped. The allocated test techniques are applied the test basis, the test cases are formulated and executed, and the results of the testing are reported (6). Test strategy In dialogue with the client and other stakeholders, the test aims, risks, objects and characteristics are linked together. Step by step a table is developed which will result in a strategy for each test type. Each strategy is translated into task packages for the tester: the test units. Test cases which are specified by applying the test design techniques are correlated to the strategies. The report concerning the execution of the test gives insight in the quality of the test object and the status of the BDTM aspects results, risks, time and costs.
Business driven test management

C5.2  Planning phase of the total test process 1. Establishing the assignment 2. Understanding the assignment 3. Analysing the product risks 4. Determining the test strategy 5. Estimating the effort 6. Determining the planning 7. Defining the test products 8. Defining the organisation 9. Defining the infrastructure 10. Organising the management 11.  Determining the test project risks and countermeasures 12. Feedback and consolidation of the plan

C5.3 Control phase of the total test process 1. Management 2. Monitoring 3. Reporting 4. Adjusting C6.2 Planning 1. Establishing the assignment 2. Understanding the assignment 3. Determining the test basis 4. Analysing the product risks 5. Determining the test strategy 6. Estimating the effort 7. Determining the planning 8. Allocating test units and test techniques 9. Defining the test products 10. Defining the organisation 11. Defining the infrastructure 12. Organising the management 13. Determining the test project risks and countermeasures 14. Feedback and consolidation of the plan C6.3 Control 1. Management 2. Monitoring 3. Reporting 4. Adjusting

C6.4 Setting up and maintaining infrastructure 1. Specifying the assignment 2. Realising the infrastructure 3. Specifying the infrastructure intake 4. Intake of the infrastructure 5. Maintaining the infrastructure 6. Preserving the infrastructure C6.5 Preparation 1. Collection of the test basis 2. Creating checklists 3. Assessing the test basis 4. Creating the testability review report C6.6 Specification 1. Creating the test specifications 2. Defining central starting point(s) 3. Specifying the test object intake C6.7 Execution 1. Intake of the test object 2. Preparing the starting points 3. Executing the (re)tests 4. Checking and assessing the test results C6.8 Completion 1. Evaluating the test process 2. Preserving the test ware

Adaptive

Structured test process

Method

TMap can be applied in all test situations, for instance when testing new development, maintenance, iterative and agile approaches, or of the shelf software, tailor-made and with outsourcing (parts) of testing.

Adaptive is the ability to split up an element into sub-elements that, in a different combination, result in a new, valuable element for the specific situation.

TMAP NEXT
Test consultant

TMap offers a complete and generically applicable approach for structured testing in all test situations. Being adaptive is part of the approach. BDTM results in strategy that is tailor-made for each situation. The phases of the test process can be adapted to the development method used and interaction with the test environment ensures a constant alignment with the test process. TMaps four adaptiveness properties:

Respond to changes  Adapting to changing priorities in results, risks, time or costs will be part of the process in the test strategy. The impact of changes in requirements or design will be assessed in co-ordination with the client.

Learn from experiences Fault tolerant parts of a test object will be tested with special attention. The test process gives on-going information to the stakeholders.

Life cycle model for test tool implementation

Tool policy Toolbeleid Initiation Quick scan

Coverage Coverage type Coverage ratio Test design technique Test basis Basic technique Test situations

Test cases

Try before use When it works in a pilot situation, it can be applied broadly. Develop ideas, try them out, but also dare to throw away.

Plan of approach Test tool configuration Set up preconditions Realisatio

Infrastructure (where, with what)

Test environments Test tools Workplaces

Use and maintenance

For more information, downloads (for instance checklists) www.tmap.net

TMap is a registered trademark of Sogeti Netherlands B.V.

(Re)use products and processes Test cases, test data and tools will be re-used for maintenance. The internal defect management procedure will also be used by external suppliers.

Selection

Training

Pilot

...

Operation

Adaptive

le

Complete toolbox

Complete toolbox
Many practical applicable tools like examples, checklists, description of techniques, procedures, test organisation structures, test environments and test tools.

ib x le

Carreer cube
Testmanager Testtoolconsultant

Organisation (who)
Test policy Permanent test organisation Test organisation in projects Test professional Test roles
Execution

Test meth. expert

Test Co-ordinator

Test tool expert

Functional growth

Tester

Test tool programmer

nt ent me m ge rove g a n p n ma s im sulti st s n nt o Te oce r tc me e n p e g st Te gem ana rm na a e ld M ho ed ke nc a t va ion S d A at ap din TM o-or c p st Te rshi ling e d nd a Le ct ha i fl n n Co rse tio da cou n on ou F ucti g s d o r tin ng Int raini mee / t g ol To iewin v r e Int Training

and coaching

Techniques (how)
Test estimation Defect management Metrics Product risk analysis Test design techniques Evaluation techniques Various checklists and overviews

Advice

Leadership

No experience Experience Expert

Functional differentiation

From test basis to test cases