SW-QUARTUS-SE-FIX Altera, SW-QUARTUS-SE-FIX Datasheet - Page 23

• Manufacturer Part Number: SW-QUARTUS-SE-FIX
• Description: QUARTUS II ANNUAL SUBSCRIPTION
• Manufacturer: Altera
• Type: Design Softwarer
• Series: QUARTUS IIr

Specifications of SW-QUARTUS-SE-FIX

• Mfg Application Notes: Software Licensing App Note
• Core Architecture: CPLD, FPGA
• Supported Families: Quartus II, Nios II
• Software Edition: Standard
• License Type: Fixed - Node
• Supported Hosts: Windows
• Rohs Compliant: NA
• For Use With/related Products: Altera Devices
• Lead Free Status / RoHS Status: Lead free / RoHS Compliant
• Other names: 544-1247; FIXEDPC

C
D
Design Methodologies and Planning
14
HAPTER
ESIGN
■
M
ETHODOLOGIES AND
1: D
I
NTRODUCTION TO THE
ESIGN
When you are creating a new design, it is important to consider the design
methodologies the Quartus II software offers, including incremental
compilation design flows and block-based design flows. You can use these
design flows with or without EDA design entry and synthesis tools.
Incremental Design Flows
Your design flow affects how much impact design partitions have on design
optimization, and how much design planning may be required to obtain
optimal results. In the standard incremental compilation flow, the design is
divided into partitions, which can be compiled and optimized together as
parts of one Quartus II project. If another team member or IP provider is
developing source code for the design, they can functionally verify their
partition independently, and then simply provide source code for the
partition to the project lead for integration into the larger design. If the
project lead wants to compile the larger design when source code is not yet
complete for a partition, they can create an empty placeholder for the
partition to facilitate compilation until the actual partition code is ready.
Compiling all design partitions in a single Quartus II project ensures that all
design logic is compiled with a consistent set of assignments and allows the
software to perform global placement and routing optimizations. Compiling
all design logic together is beneficial for FPGA design flows because in the
end all parts of the design must use the same shared set of device resources.
If required for third-party IP delivery, or in cases where designers can not
access a shared or copied top-level project framework, you can create and
compile a design partition logic in isolation and export a partition that is
included in the top-level project. If this type of design flow is necessary,
planning and rigorous design guidelines may be required to ensure that
designers have a consistent view of project assignments and resource
allocations. Therefore developing partitions in completely separate
Quartus II projects can be more challenging than having all source code
within one project or developing design partitions within the same top-level
project framework.
F
LOW
P
LANNING
Q
UARTUS
II S
OFTWARE
A
LTERA
C
ORPORATION