Visible to Intel only — GUID: med1492538757230
Ixiasoft
2.1. Block-Based Design Terminology
2.2. Block-Based Design Overview
2.3. Design Methodologies Overview
2.4. Design Partitioning
2.5. Design Block Reuse Flows
2.6. Incremental Block-Based Compilation Flow
2.7. Setting-Up Team-Based Designs
2.8. Bottom-Up Design Considerations
2.9. Debugging Block-Based Designs with the Signal Tap Logic Analyzer
2.10. Block-Based Design Flows Revision History
2.11. Intel® Quartus® Prime Pro Edition User Guide: Block-Based Design Document Archive
Visible to Intel only — GUID: med1492538757230
Ixiasoft
2.3.1. Top-Down Design Methodology Overview
In a top-down design methodology, you plan the design at the top level, and then split the design into lower-level design blocks. Different developers or IP providers can create and verify HDL code for the lower-level design blocks separately, but one team lead manages the implementation project for the entire design.
In the top-down methodology, you can use core block reuse to preserve the core logic by exporting the .qdb file. Another developer working on the same project can then reuse the core logic .qdb file.
You can similarly preserve the root partition by exporting the root .qdb file, using the root partition reuse flow, and then reusing that root partition in the same project.