Home/Glossary/ASIC Development Services
Semiconductor knowledge

ASIC Development Services

Engineering services that contribute to creating an ASIC, such as architecture, RTL design, IP integration, verification, physical design or silicon bring-up. The exact scope is project-specific.

← All glossary termsTechnical guide · 5 min read
In this article

Engineering services that contribute to creating an ASIC, such as architecture, RTL design, IP integration, verification, physical design or silicon bring-up. The exact scope is project-specific.

An iterative ASIC development flow
Reviews and feedback connect the stages. This conceptual flow is not a fixed project schedule.

Development covers more than a layout

ASIC development services bring a product from its requirements toward a validated custom device. The scope can include architecture, design, verification, physical implementation, product engineering and support for silicon evaluation. Define which stages are included and which inputs the customer supplies. A project described as development may otherwise mean very different things to different parties. The most useful starting point is a shared view of the product objective, the current maturity of the design and the evidence required at each major handover.

Organize around development risks

Identify the uncertainties most likely to affect feasibility, schedule or product behavior. They may involve an algorithm, a demanding interface, analog performance, IP integration or a difficult power target. Plan experiments and reviews that reduce those uncertainties early. Writing large amounts of source code is not necessarily the fastest route to a sound result if a central assumption remains untested. A development plan should explain which decisions are already supported, which are provisional and how the team will obtain the missing evidence.

Manage revisions and acceptance

Requirements, models, RTL, constraints and test collateral evolve together. Keep their revisions linked and define how changes are approved. An acceptance milestone should identify what was delivered, what was checked and which issues remain. If a customer changes the specification, the impact should be visible across verification, implementation and manufacturing preparation. This avoids treating every change as either automatically included or automatically impossible. Controlled development gives both teams a practical basis for discussing scope, risk and readiness using the same technical record.

Plan beyond first samples

Bring-up software, evaluation boards, instruments, test programs and diagnostic access should be ready for silicon. Define who performs characterization and how results feed back into the product decision. First samples may confirm some assumptions while exposing others that need refinement. Preserve the evidence and distinguish a test-setup problem from a design or manufacturing issue. Development is successful when the customer can make a supported product-release decision, not merely when the project reaches a date or produces a fabricated chip.

Questions about development engagements

Can development services be limited to one phase?

Yes. A focused engagement can be useful when its inputs, outputs and responsibilities are explicit. The remaining phases still need owners in the overall product plan.

Does a completed design database prove the product is ready?

No. Physical release, silicon evaluation, manufacturing readiness and system validation provide different evidence. The required product-release criteria should be agreed before development is considered complete.

Requirements that can be checked

Turn each important behavior into a requirement with an observable result. Describe valid inputs, invalid inputs, ordering rules, throughput expectations and the response to interrupted transactions. Identify which clocks and resets are involved. A good review asks whether another engineer could write an independent test from the description. Where the answer is unclear, improve the requirement before adding more implementation detail. Keep assumptions about the surrounding system visible, including how long an interface can stall and whether input data can arrive while a block is unavailable. These details determine whether the implementation and its test environment are solving the same problem.

Verification across normal and unusual operation

Check ordinary workloads alongside stressful combinations of events. Reset during activity, a full queue, simultaneous requests and an error response can expose behavior that an ideal sequence misses. Use appropriate simulation, assertions or formal methods for the properties being examined. Preserve reproducible inputs and expected results. If a check is excluded, record why and who reviewed the decision. Coverage helps organize evidence, but its interpretation depends on what the tests actually check. A regression that executes many cycles without observing meaningful outcomes can provide less confidence than a smaller set of well-targeted checks tied to requirements.

Implementation handover

The source design needs constraints, technology assumptions and integration context before a receiving team can use it reliably. Include the intended operating modes, clock relationships, IP versions and any known limitations. Check that source files, models and reports describe the same configuration. Define how changes are communicated while implementation is in progress. When physical results challenge an assumption, route the finding back to the responsible architecture or logic owner. A controlled handover keeps the project from optimizing an obsolete version or interpreting an undocumented exception as an intentional requirement.

Evidence for the next decision

Separate predicted results from measured behavior and state the conditions behind both. An early synthesis estimate can support architecture exploration, but it is not equivalent to a final implemented result. A prototype can support software integration without proving final ASIC timing. Before a release, identify the evidence required for the particular stage and list unresolved issues with owners. Preserve the approved revision and enough context to reproduce the relevant checks. This makes later debugging, engineering changes and product maintenance more efficient than relying on a single successful run whose inputs are no longer clear.

A practical cross-discipline review

Before committing the next stage, bring the design, verification and product-engineering owners together around the same revision. Confirm the assumptions that pass between them: operating modes, interfaces, test access and the evidence expected at release. List unresolved issues with a responsible owner and a concrete way to close them. An open question is easier to manage when its consequence is understood than when it is hidden inside a general progress estimate. Preserve the decision record so a later change can be evaluated against the original reasoning. This review is useful even for a narrow specialist task, because the surrounding product still determines whether the delivered result is usable.

Include the receiving team's acceptance question in the review: what must be demonstrated before this result can be used safely in the next engineering stage? Agree how that demonstration will be recorded and how a subsequent change triggers a focused reassessment of the affected evidence.

Explore the related Avnet offering or discuss your project requirements.

Let's talk about your next project.

Explore design, technology enablement and manufacturing with Avnet ASIC Solutions.

Contact our team →