How to Write an ASIC specification: Tell Me What You Want, What You Really Really Want.
The specification is central to the on-time and on-budget development of an “application specific” integrated circuit, often described as an ASIC. What can be done? Can a document really help? Weak definition of a product leads to costly redesign work and could result in a competitor launching their product first and taking the market. Specification of software used on the Ariane 5 rocket suffered from poor definition of detailed requirements and functionality, which ultimately led to software performing 64-bit operations with 16-bit precision but failing to correctly detect overflow conditions. The maiden flight of Ariane 5 lasted one minute before the rocket along with the $500M payload were destroyed. This article describes the content of a typical product specification, how the specification is created and how the document is used with particular emphasis on the customer contributions.
Table of Contents
- The 7 Pitfalls of Bad Specifications
- Specification Audience
- Purpose of The Specification
- How Is the Specification Used?
- What Are the Requirements?
- What Make A Good Requirement?
- Terminology
- Specification Compliance
- Functionality Vs Implementation
- Production Related Functionality
- Document Revisions
- Document Review and Approval
- Change Requests
- ASIC Specification Content
- Approvals
Request White Paper
You will be taken directly to the white paper and will also receive an email with a direct link to download
https://www.ensilica.com/news/how-to-write-an-asic-specification/