EuroSTAR Copenhagen 2010

Dirk van Dael, Capgemini

TEST ACCOUNTING

Sounds familiar?

I had this issue before?!

I can’t find it in the design!

What is in the current release?

This worked fine last week!

Users will not like this!

Test everything again?

Do you understand this requirement?

…

Some causes

No proper impact analysis

Vague responsibilities

Ambiguous requirements

There are no processes

Test data is not maintained

Release notes are missing

No priorities available

…

Some solutions

Where to start?

Lessons learned don’t seem to change?!

Accept imperfections?

Or learn from other disciplines?!

The art of communicating...

Accounting (a definition)

Accounting is the art of communicating

financial information about a business entity

to such users as shareholders and managers

Test Accounting is the art of communicating

product en project information about an it entity

to users such as stakeholders and managers?

Example balance sheet

Results (profit-and-loss)

Balance sheet (year +1)

Accounting provides

Control (e.g. bookkeeping, overview)

Ownership (e.g. accounts for actors)

Message (e.g. management information)

Priority (e.g. ‘fair value’ pricing)

Alignment (e.g. product lifecycle)

Scope (e.g. currency denomination)

COMPAS for projects

Control (e.g. bookkeeping)

Ownership (e.g. responsibilities)

Message (e.g. knowledge transfer)

Priority (e.g. business priority)

Alignment (e.g. lifecycle organizations)

Scope (e.g. impact analysis, scope control)

Ownership

Creating a functional design:

Responsible: Functional analyst

Accountable: Project leader

Consulted: User, Developer, Tester!

Informed: Business owner

Alignment

Agile projects are more successful!

Me

My team

My project

Scope

Disciplines using the same unit of scope!

DesignSmart -

Use Case

BuildModule

TestTest unit

Scope• Menus

• Pages

• Buttons

Interfaces offer:

• unit of scope

• unit of work

Scope control!

Control

Message 1

Page Euronext Fund Service

Test Cases are ORD50P10

Is in Menu Funds and Test Unit ORD50

Smart Use Case is UC-185.FND (8 pages)

Has one button and Action word Order

Test estimates 27 hours (design 18, execution 9)

Message 2

Test Case ORD50P10

Design status Test scripted (T) (UC-185.FND)

Build status Test executed (T) (change tested, 1

defect (B203), priority B)

Business process P12 Funds Transfer (not yet

available, has 1 regression test case OVZ40P10)

Lifecycle overview of changes and results

Clear responsibilities for all disciplines

Value and status via product coupling

Instant impact analysis and issue handling

Ease of delegation and economies of scale

Basis for ‘knowledge management’

COMPAS Accounting