Artefact · Design & Architecture
Reuse standard
The set of rules a design block must meet before other teams may reuse it, such as verification evidence, documentation, configuration options, coding and interface rules, and clear licence terms.
- Also known as
- IP reuse standard
- Type
- Artefact
- Domain
- Design & Architecture, IP and reuse
Overview
A reuse standard is an organisation's written bar for reusable design blocks. It says what a block must have, and what evidence must exist, before it can be offered to other teams or added to a platform. Its aim is that a team picking up a block can use it without having to rediscover how it works or re-verify it from the start.
How it works
A typical reuse standard covers several areas. Design rules set coding style, clocking and reset conventions, and standard interfaces. Verification rules set the test environment to be delivered, the coverage to be reached and the results to be recorded. Documentation rules set the specification, integration guide, register description and known issues list. Release rules set versioning, the deliverables package and how changes are announced. Legal rules set where the block came from and the licence under which it may be used.
A block is assessed against the standard before release, often with a checklist and a review by a reuse or platform team. Blocks that pass are published in a catalogue with their status. Blocks that fall short may still be used, but with the gaps stated and accepted by the team taking them.
The standard itself is revised as the organisation learns, and platform versions may require a minimum version of it.
Examples
- A rule that every reusable block ships with its test environment and a coverage report.
- A checklist reviewed by the platform team before a new interface controller joins the platform.
- A block accepted with a stated gap in its documentation, recorded against its release.
- A requirement that every reused block has a recorded origin and licence.
Why it matters
Reuse saves time only if reused blocks are trustworthy. Without a common bar, each team that picks up a block repeats work or inherits hidden problems. A reuse standard lets a platform grow from blocks of known quality. Platform architects, IP development leads, verification leads and IP portfolio managers use it.
In the platform lifecycle it is defined early, applied to every block before it joins the platform, and checked again for each platform release.
It matters most to: IP Development Lead, IP Portfolio & Reuse Manager, IP Quality Engineer, Platform Architect
Common confusions
- Not the same as design reuse
- Design reuse is the practice of building from existing blocks. A reuse standard is the written rule set that decides which blocks are fit to be reused.
- Not the same as an industry standard such as IP-XACT
- IP-XACT is a published format for describing blocks. A reuse standard is an organisation's own rules, which may require IP-XACT descriptions among many other things.
Related standards
- IEEE 1685 (IP-XACT)
Sources
- IEEE 1734-2011 Standard for Quality of Electronic and Software Intellectual Property Used in System and System on Chip (SoC) Designs (opens in a new tab), IEEE Standards Association, 2026-11-10
- IEEE 1685-2022 Standard for IP-XACT, Standard Structure for Packaging, Integrating, and Reusing IP within Tool Flows (opens in a new tab), IEEE Standards Association, 2026-11-10
- IP-XACT (opens in a new tab), Accellera Systems Initiative, 2026-11-10
Related terms
Part of the Design & Architecture glossary, with every term in the topic and the lifecycles, tools and standards that use them.
Where it appears on the Hub
Used on 2 pages of the Hub. In each group, the pages that mention it most come first.
Lifecycle stages and gates
Suggest an improvement
Suggest an improvement to this entry
A clearer definition, an example, a correction or a source an editor can check. Editors review every suggestion before the entry changes.
Last reviewed . Written by The Semiconductor Hub editorial team. The full glossary