Mastering the Semiconductor Product Requirements Document: A Comprehensive Guide and Checklist

EXECUTIVE SUMMARY

The status quo of requirements specification in non-dedicated authoring tools is no longer an option due to increased complexity/cost of post-silicon validation, increasingly stringent standards compliance, and specification quality issues due to reuse and best practice negligence. Fortunately, there are now requirements authoring tools that solve all of these issues by emphasizing authoring requirements right the first time by leveraging automated compliance, best practice, and consistency checks.

THE STATE OF REQUIREMENTS ENGINEERING FOR SEMICONDUCTOR PROJECTS

The semiconductor product requirements document has become so complicated that requirements management 101 is becoming more sophisticated by the day. Engineers understand that and are keeping up with the increasing levels of complexity, but it gets harder and more challenging to keep the executive decision-makers up to speed, so they implement marketing strategies that make sense for growth and innovation. The challenge arises because of the modern development environment of 5G communications and the ever-growing Internet of Things (IoT) markets.

The status quo of semiconductor requirements specification in non-dedicated authoring tools is no longer an option due to increased complexity/cost of post-silicon validation increasingly stringent standards compliance, and specification quality issues due to reuse and best practice negligence. If we look closely at the use case for developing requirements involving Marketing Requirements Documents (MRD), Product Requirements Documents (PRD), and technical specifications that run into the hundreds of pages, as well as the cross-functional deliverables that they apply to such as ecosystems of die, software, and firmware, we see that all of these complicated factors combined with the challenges of advanced reasoning algorithms, demands on semiconductor memory, and emerging sensor technologies, companies executives and stakeholders are in over their heads in delivering what their customers demand at an expected time-to-market.

USE CASE FOR SEMICONDUCTOR REQUIREMENTS DEVELOPMENT

Deloitte, in their July 2018 paper, IoT Opportunity in the World of Semiconductor Companies, developed an approach on how to deal with these massive levels of requirements complexity in a system of systems engineering view of the challenge.

The first thing to do is to recognize the constraints on your requirements development environment. We’ve subtly hinted at the issue, but let’s say it out loud. The situation in which you are doing your semiconductor project initiation work is not static. It’s a dynamic, constantly changing system. It would be best if you embraced those changes and champion a change requirements atmosphere within the project team. The best thing to do is understand what is forcing the changes and change your tack accordingly.

Let’s look at four changing features of semiconductor design.

  1. Increasing the performance of the semiconductor device no longer holds the power it once did. Moore’s Law has reached a level of constraint. Semiconductor product performance has peaked. The density of transistors on a chip is maxed out. New materials and new innovative methods must assume the challenge, and that’s a more difficult proposition. Traditional physics must give way to quantum physics with more RDT&E investments headed in that direction. However, the maturity of that technology is still years in the future.
  2. The semiconductor device market is a commodity market now with competitive equality among the players. There are many companies, large and small in the mix. The profit margins are razor-thin. As noted above RDT&E efforts will focus on emerging tech, where growth and innovation has a better ROI. That includes shifting elite technical talent to new endeavours so that companies can retain their valuable employees. Smaller companies are taking on the job of innovation, given that their growth strategies are better suited to these new limited semiconductor capability improvements.
  3. Larger companies are now forced to seek partnerships with smaller companies to maintain their profit margins if we carry forward the logic and reasoning from the previous two points. The RDT&E burden will then be a shared effort with larger companies providing seed money to their smaller partners. Thus, the risk is shared, and the inevitable failures of semiconductor projects based on misdirected requirements will be offset with other semiconductor projects that succeed and fuel the growth of both the large company and its orbit of smaller partners.
  4. What we have introduced is an innovative process disruption in the technology value chain. The smaller companies will pursue more automation and integration initiatives in building a real system of systems concept to deliver Industry 4.0 actions of developing faster-to-market and cheaper semiconductor technology through more accessible, smooth and efficient open-source API’s and dynamic architectures. In other words, bury the technical complexity under automation and open-source development.

Learn how QVscribe can transform your design process.

TEN TIPS FOR DEVELOPING REQUIREMENTS FOR SEMICONDUCTOR PROJECTS

The Deloitte use case points out some trending issues that impact developing requirements for semiconductor projects. Let’s start building a list as a guide as you go about creating a work plan in the initiation phase of your project. It should serve well in eventually developing a checklist tailored directly to the objective of the work you’ll be doing.

  1. Do Not Blindly Copy Paste Requirements Documents: Given the dynamic nature of the changes to the semiconductor ecosystem, one should not copy forward all of the requirements that were developed for a project constructed earlier in time. Sift through a previous list of requirements carefully to exclude those that are no longer a best practice.
  2. Use Systems Thinking Approaches to Develop your Requirements: Consider the entire IoT or Industrial IoT (IIoT) tech stack by constructing a system-level signal flow diagram to focus your effort. Create an end-to-end solution that realizes your final market solution. It will make your requirements list flow with the logic and reasoning necessary to prevent requirements from slipping through the cracks. Security and encryption requirements for data, in particular, come to mind in that regard to protect the data and predictive analytics being performed within the system.
  3. Develop your Requirements using a Strong Team, Process-Based Foundation: Make sure you develop your requirements using a strong team, process-based foundation that features the four basics of requirements management: (1) Planning: what are we building? (2) Collaboration: do we have a full team visibility? (3) Traceability and Version Control: are we using a structured requirements authoring tool? Does everyone have access to it? Is it accessible from anywhere, any time? Is the content protected from unauthorized changes? (4) Verification: Who is responsible for managing the tool and information to verify the applicability of each requirement, i.e., source authority, format, and description?
  4. Make an Informed Decision Regarding Requirements Management Tools: Make an informed and smart business decision regarding which requirements management tool you use to document your choices for requirements. The complexity of a semiconductor design process demands it. If that hasn’t been emphasized enough by now, please take note of it here. Your tool must be able to capture cross-functional system requirements in a system of systems environment so that everything is cross-referenced in a single, web-based location that cleared and entitled users can access it integrated with the other tools users understand.
  5. Connect your Requirements Across the Product Lifecycle: Consider all of your target markets and develop a tailored list of requirements for each vertical. Document expectations, preferences, standards, regulations, and governance, risk, and compliance measures from the diverse sources each product demands.

Interested in learning more on semiconductor requirement authoring? Download our guide to continue reading!

Semiconductors Digital Guide mockup