Home > Archive > Software Testing > November 2006 > Effectiveness of RTRT in automotive domain testing
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Effectiveness of RTRT in automotive domain testing
|
|
| Mohan Bellur 2006-11-18, 4:09 am |
| Hi ,
I wanted to know how suitable the IBM tool RTRT is for testing in the
automotive domain.
Does anyone have some idea/suggestions as to how best the tool can be used
to catch bugs in software?
regards
Mohan
| |
|
| Mohan Bellur a écrit :
> Hi ,
>
> I wanted to know how suitable the IBM tool RTRT is for testing in the
> automotive domain.
> Does anyone have some idea/suggestions as to how best the tool can be used
> to catch bugs in software?
>
> regards
> Mohan
Hi,
Actually, the efficiency/suitability of RTRT (or tools like RTRT) relies
on the test strategy it is used with. Attention must be paid at what you
want to test and how you want to test it. You should ask yourself what
"catch bugs in software" means. Basically you are supposed to test
software versus its specification. With a consistent enough
specification and the appropriate method (equivalence classes for
example) you should be able to design exhaustive test harnesses.
Maybe that abstract interpretation (Pr Patrick Cousot) oriented tools
may help you for the bugs catching oriented part...
Before spending all your money, remember that: Often, you can test
software with home made tools, you just have to bring the appropriate
proofs on your tool (i.e. for DO178B or EN58128 what is called the
qualification material... Be careful: you also do have to bring up
qualification material for COTS tools if your tool's vendor hasn’t any…)
Choosing the right tool for the right check is difficult to cope with
anyway.
Tools like IBM RTRT or VectorCast are already used to test software (in
C or Ada language) at (what IBM calls) “component” level (That is to say
Unit Testing, Integration Testing (Units between them), System Testing
(The Integrated software on the target hardware) and for coverage
analysis) in the aerospace and in the trainborne industry.
Remember: The power is not what the tool can do, but what you can do
with it.
Here are the test/verification tools that I know classified by
'orientation':
Test Based Tools:
-RTRT Tool suite
<http://www-128.ibm.com/developerwor...ts/testrealtime>
-VectorCast <http://www.vectors.com/>
"Bug Busters":
-WCET, StackAnalyzer and others <http://www.absint.com/>
-Polyspace <http://www.polyspace.com/>
Validation:
-MaTeLo by <http://www.all4tec.net/>
Well... Hope this helps...
Cheers,
Guillaume.
|
|
|
|
|