The easiest way to get the Fmax for your clock, just remove your timing contraints, or overconstrain your clock, and check the timequest report. With no timing constraints, it will auto-constrain any signal it thinks is a clock to 1000Mhz, and give you the fmax based on the slow (high temp) and fast (low temp) models - you want the high temp number.
The max frequency of variation of the input data will be the same as your clock?
This all assumes your design is completly synchronous. Timequest cannot work on asynchronous data paths without a lot of timing constraints.
- - - Updated - - -
The easiest way to get the Fmax for your clock, just remove your timing contraints, or overconstrain your clock, and check the timequest report. With no timing constraints, it will auto-constrain any signal it thinks is a clock to 1000Mhz, and give you the fmax based on the slow (high temp) and fast (low temp) models - you want the high temp number.
The max frequency of variation of the input data will be the same as your clock?
This all assumes your design is completly synchronous. Timequest cannot work on asynchronous data paths without a lot of timing constraints.