- commercial off-the-shelf (COTS) for
stimulation and measurement HW

- flexible HW adotion

- free automation SW EXAM


All the latest news

We4Data GmbH joins ASAM e.V.

Juni 1st, 2016|Kommentare deaktiviert für We4Data GmbH joins ASAM e.V.

From May 2016 We4Data GmbH joins the ASAM e.V. With this membership We4Data have access to all ASAM related documents and

BeagleBone Black as Measurement unit

März 9th, 2016|Kommentare deaktiviert für BeagleBone Black as Measurement unit

We4Data starts to develop an Measurement unit basted on the BeagleBone Black board. The unit should interface to the We4Data Nail

EXAM 4.x integration

Februar 7th, 2016|Kommentare deaktiviert für EXAM 4.x integration

EXAM 4.x ready for distribution We4Data is working on a database migration from EXAM3.3 to EXAM 4.x. The target is to

Why Automation

Testautomation is a matter of Return of Investment (RoI). There are three important cost factors. The first factor is the Software (SW) library to control the Device Under Test (DUT) the second one is stimulation and measurement Hardware. The last factor are the Testcase– (TC) related SW parts. This SW depends on the number of tests and there complexity.

At the starting point the first two factors are the biggest investment which have to be done to get any kind of output. But we have also to find a way to reduce this cost as much as possible. In general this are one time cost which could be reinvested fast if you are not looking only to one project. But normally the target for automation is to reuse all factors of the Automation also for other project. This reduces the SW library cost for all further projects and change the decision to use a Testautomation also for test which are done not often in the project life cycle .

The following graph shows a typical RoI curve for a Testautomation.

We uses commercial off-the-shelf (COTS)  for stimulation and measurement HW

The COTS HW have the best factor of function to cost (ftc). For automation we need to connect to these HW with a SW interface. We try to generate driver which uses the HW without any additional SW executable which came from the HW vendor. This reduces the onetime cost for the SW licenses for each Testbench.

Due to the big sales quantity of COTS HW products we believe to have a long lifetime of our products and can believe to get alternative successors for old products with SW-compatible interface.

Supported Vendors:

Hey! Join Our Community

Join us we will contact you to enable your account for all required items we can support you

Sign up

Subscribe to our Newsletter