Hello verification experts,
This is something that has been puzzling me for a while I know there is this keyword in constraints 'soft', but I'm not sure about its usage, I've heard about soft constraints in specman but never used them, what is the benefit, if you need to 'override them' you can extend from the class containing the orignal constraint and write a new one with the same name (please correct me if I'm mistaken) or you could use some array of knobs to change its behaviour as described by Dave in this thread which doesn't seem to difficult to implement.
From the 1800-2012 LRM I see section 18.5.14 I read the idea of more complete and easily to extend verification environments and IPs, but in the end IMHO it may lead to unintended 'negative testing' since maybe the engineer using this environment is wrongly creating invalid scenarios with new constraints.
Can somebody please provide an example and reasoning behind this construct, and its usage (not the ones in LRM) and apologies for the lengthy post.
Cheers,
-R