Bookmark and Share
Blog powered by Typepad
Member since 03/2007

Become a Fan

« Cost and Schedule Aspects of DO-178B | Main | Rationale for Safety-Related Design Decisions »

September 18, 2010


Feed You can follow this conversation by subscribing to the comment feed for this post.


You are assuming that the code is identical to the pseudo-code. It might not be. That's the reason you are doing a verification in the first place, isn't it?
As long as you are generating test cases based on the pesudo-code (and not looking at the source code), it is an RBT.
In any case, Unit Test goes beyond merely figuring out how faithfully you have implemented the requirements. It also determines if the code is robust, for example.


Hi Amitabh
I have a queary regrading structural coverage analysis. If design is a pseudo code( these are low level requirements in our project) and requirement based test cases are written and are executed. As implementation is same to same with respect to the pseudo code .Is this a structural testing or RBT?

Bharathi Raja

Can you explain what is to be mentioned in SDD for Level A software as per DO-178B Section 11.10 (l) "Rationale for those design decisions that are traceable to safety-related system requirements"??

The comments to this entry are closed.

My Photo

Life sometimes turns on a dime. Especially when you are actively looking out for a change. I now work at HCL Technologies. And all I am looking for is to make a difference. By the way, the blog contents remain my own. It does not reflect the official position of HCL.

Your email address:

Powered by FeedBlitz