defect pooling nothing but defect seeding

what is meant by defect seeding ?

defect seeding and defect pooling both are different..
see the below site for detailed answer
http://www.stevemcconnell.com/ieeesoftware/bp09.htm
-----------
involvement makes you important
gkyes

defect seeding means intentionally introducing defects in 
to the application and check the ratev of its detection and 
its residual effects

Another simple defect prediction technique is to separate 
defect reports into two pools. Call them Pool A and Pool B. 
You then track the defects in these two pools separately. 
The distinction between the two pools is arbitrary. You 
could put all the defects discovered on Mondays, 
Wednesdays, and weekends into Pool A, and the rest of the 
defects into Pool B. Or you could split your test team down 
the middle and put half of their reported defects into one 
pool, half into the other. It doesn’t really matter how you 
make the division as long as both reporting pools operate 
independently and both test the full scope of the product.

Once you create a distinction between the two pools, you 
track the number of defects reported in Pool A, the number 
in Pool B, and—here’s the important part—the number of 
defects that are reported in both Pool A and Pool B. The 
number of unique defects reported at any given time is:

DefectsUnique = DefectsA + DefectsB - DefectsA&B 

The number of total defects can then be approximated by the 
simple formula:

DefectsTotal = ( DefectsA * DefectsB ) / DefectsA&B

If the GigaTron 3.0 project has 400 defects in Pool A, 350 
defects in Pool B, and 150 of the defects in both pools, 
the number of unique defects detected would be 400 + 350 - 
150 = 600. The approximate number of total defects would be 
400 * 350 / 150 = 933. This technique suggests that there 
are approximately 333 defects yet to be detected (about a 
third of the estimated total defects); quality assurance on 
this project still has a long way to go.