One of the problems with this, of course is that "robustness", like "policy" and "session" is one of those words that really has no meaning. Or rather, it has so many meanings that it has no effective meaning.
The problem with "robustness" is that defining what robustness is is situational - the very qualities that define the robustness of a system depend on how and where it's deployed. Thus it is meaningless to consider robustness without first describing the scenario.
I should have probably posted this on my software testing blog, but its on msn spaces, and its much easier to post to blogger than it is to post to msn spaces.
