Constraining Asynchronous I/O´s

They create a clock like:

create_clock -name notaclock -period 1.0

and use that.

Note that I said they put in the constraint(to satisfy the unconstrained paths check) and then do a set_false_path assignment so it's not analyzed, and the clock doesn't really matter.

The min is up to you. In general it doesn't hurt and some people feel like they're doing everything, while others think it's more confusing.

My only comment is to be sure you comment where each I/O timing constraint came from. Be as verbose as necessary:

set_min_delay -from -to 0ns ;# I made up this 0ns delay just to have a constraint, even though it could never be violated 2009_06_09.

Designs get passed around, picked up years later, etc., and I hate when they have timing constraints that no one knows where it came from or why it's important, but yet they won't change it and have to continue meeting it.