Integrating assertion results of OneSpin 360 DV with planning tools
In a systematic verification flow, requirements tracking and coverage plays an indispensable role. Generally, this starts from requirements specification, where individual requirements are broken down into features, implementations, verification goals and metrics. In order to achieve these goals, verification engineers are taking different approaches, like writing testbenches for simulation environment or properties for assertion- basedformalverification. For each approach taken, to keep track of what requirements have been met users are generating coverage databases from simulation and formal environments. Because these are coming from different vendors, the big challenge is how can these coverage databases can be merged into one and to annotate the results into existing verification plans.