I am not a reliability expert, but you should start asking the manufacturer as hakeen says, and if after adding up the failure rate of your components you have problems in reaching your required MTBF for the board, you shoul start lookin at the percentage of resources used, temperature derating, etc...
"I want a document of MTBF for clock domain crossing analysis ? "
You are mixing concepts. Maybe you are talking about metastability? This has nothing to do with reliability.
As for lucbra recomendation, MIL-HBK-217 will give you a very pesimistic number. I do not know the details but there are other references which are well accepted by the worlwide realibility experts. I will try to find the info and get back
But expert enough to qualify MIL-HBK as very pessimistic?
At least it'll give you a very good guidance on a lot of today's electronics world ...
and it's accepted throughout the world
I mean how we will calculate whether double Flop synchroniser or multiflop synchroniser wil be required to resolve all metastability issues in case of single bit crossings ?
"I want a document of MTBF for clock domain crossing analysis ? "
You are mixing concepts. Maybe you are talking about metastability? This has nothing to do with reliability.
As for lucbra recomendation, MIL-HBK-217 will give you a very pesimistic number. I do not know the details but there are other references which are well accepted by the worlwide realibility experts. I will try to find the info and get back
Like we said before: clock domain crossing is one thing (and not related to MTBF, MTTF, MTTR, or whatever has to do with reliability).
Process technology, gate count, voltage stress, ... are things that relate to MTBF.
If you don't understand these concepts, stay away from MTBF calculations.