Design Intent Interaction Between Schematics XL and Layout XL

Virtuoso Design Intent is run between Schematics XL and Layout XL. Generally, design intents are created in Schematics XL where they are stored in the schematic view. They are then transferred to Layout XL using syncing, where they are stored in the layout view.

To enable seamless syncing when working with design intents, the same up to date version of a cell must be open in both schematic and layout views. If working in Schematics XL, the corresponding layout view must also be open (read-only is acceptable) and vice versa if working in Layout XL. Many of the options are disabled in read-only mode.

Design intent can be launched directly from existing schematics. If your organization uses constraints, there are specific requirements that you need to consider.

The storage of constraints differs between schematic and layout. In the schematic, constraints created in Schematics XL are stored in an OpenAccess database (hierDesign.oa) that resides in the constraint view. In the layout, the constraints are stored in the layout database itself.

Design Intent complements the constraints flow in your organization by allowing schematic designers to capture their design goals in Schematics XL without actually creating constraints so a separate constraint view is not created. The design intent is synchronized to Layout XL, where the layout designer has the freedom to decide how to physically implement and achieve the design intent using constraints within Layout XL. The responsibility of creating constraints moves from Schematics XL to Layout XL.

To ensure that a constraint view is not created when transferring constraints from Layout XL to Schematics XL using the Update Schematic/Layout Constraints button, all design intents implemented using the constraint manager must have their constraints included in the design intent template (physical constraint). This ensures that device correspondence information is maintained during an Update Schematic/Layout Constraints transfer and that implementation constraints are not transferred.