Designing or testing?

Ing. Büro Munkes News •   March 10, 2018

S

ometimes i get asked if i can design something and save the costs for testing.

In this article i will write about.

Yes and no should be my answer to this question. I can design and today a can simulate a lot. But, not everything. Very fast, things gets to complex for simulation. Generally simulation supports design to be sure that the design stays in requirements. But at least only testing will prove this and therefore testing is the way to validate design aginst requirements. 

On the other hand, testing soon gets real expensive. Testing should be limited by a solid riskmanagement.

Yes, this sounds crasy but we are talking about spending money to reduce risk of failure.

Let´s look at both extrem ends of this way….

Full risk, no tests, not even when they are mandatory by law. How long will this company exist? You will find such products from off-shore with no company label on it or with fake label. It´s a fire and forget buisnessmodel.

No risk, and you will be never on market in no time and you need gigantic budget.

In the middel of this you find the level of compromice with riskmanagement.

Input will be requirements by law (FCC,CE…..) and product requirements.

For every requirement setup a row in your risksheet.

What could happen, cost of mitigation(test), cost if happend, propability of risk, possible trigger of risk, descission of prevent or absorb risk.

With this you get a clear view of what to test.

 

Keep It Simple

As projectmanager i can tell you, it´s classic riskmanagement, not more.

And that´s not complicated.

1. Setup risk list

2. Get the costs for Tests and decide about risk/test

3. Set priority accourdingly to the results of your list.

4. Calulate your budget.