Verifying large industrial designs is getting harder undetected bugs? In which modules the verification team each day. The current verification methodologies are not able to should concentrate their effort? The objective of this paper is to guarantee bug free designs. Some recurrent questions during use software engineering techniques to answer these questions. a design verification are: Which modules are most likely to contain undetected bugs? In which modules the verification The novelty of this work Si to poit which hardware modules team should concentrate their effort? This information is very are most likely to have design bugs using history information useful, because it is better to start verifying the most bug-prone available in concurrent versioning systems [13], [14]. Mining modules. In this work we present a novel approach to answer software repositories to track design history changes and bug these questions. In order to identify these bug-prone modules the revision history of the design is used. Using information of re isoa w idely se te e insotre velon t.an academic experiment, we demonstrate that there is a close The iformation available i these concurrent versionig sysrelationship between bugs/changes history and future bugs. Our tems are useful to predict future bugs and to model bugs results show that allocating modules for verification based on patterns that helps reducing future bugs. bugs/changes leaded to the coverage of 91.67% of future bugs, This paper is outlined as follows. Section 2 discusses related while random based strategy covered only 37.5% of the future work mainly focused in software engineering techniques to bugs.identify bug-prone modules. In Section 3 we present the