Ben Bucksch wrote:
> Gervase Markham wrote:
>
>> We could say that MTBF has to be, say, 200
>> hours - but we'd just be pulling numbers out of the air.
>>
> Of course. We can't reach "no crashs at all". We must not crash every 2
> minutes. Everything in between (including the "acceptable" level, as
> percieved by the user) is somewhat arbitary. I.e. we must pull a number
> out of the air. Or go by "feeling", which is even less rational.
>
> My "MTBF 250-500 hours" comes from 'Mozilla should crash at most once a
> month on the average'.
>
I'm not sure that overall MTBF is all that useful. It might be better to
say that x% of users should have at least n hours MTBF.
If we have an average MTBF of 1000 hours, that may simply mean that it's
2000 hours for half of the users and 5 minutes for the rest.
--
http://www.classic-games.com/ http://www.indie-games.com/
I've often thought intelligence agencies should recruit idiots, as
idiots seem able to infiltrate any group in large numbers.
