Product Design Process
Created: 5/30/2020
Last Updated:07/06/2023
Introduction
New product introduction (NPI) is a process of bringing a new product to market. It involves many teams working together to define the product, design it, and test it. The simplified steps include:
The market requirements document (MRD) is generated from the market team. This document outlines the market needs and why there is a need for the product.
The product requirements document (PRD) is created. This document outlines the features that the product should have.
The engineering requirements document (ERS) is created. This document outlines the technical implementation of the product features.
The general design steps for developing a product are as follows
Generate a Product Requirements Document (PRD): The PRD is based on user needs and outlines the desired features of the product.
Translate Product Requirements to an Engineering Requirements Specification (ERS): The ERS specifies the system requirements, including the component list (Plan of Record - POR), system performance, and constraints.
Translate Engineering Requirements to System Architecture: This step involves creating a system architecture, which includes a block diagram, power tree, clock tree, and physical design.
Design and Implementation: This stage includes tasks such as schematic capture, board layout, and simulation.
Develop a System Validation and Verification Plan: A comprehensive plan is created to validate and verify the system design. This plan includes tests for signal integrity and power integrity, power system validation, basic functional validation, RF validation, thermal validation, and reliability validation, among others.
Test and Update the Design: The design goes through multiple development iterations (such as prototype, EVT - Engineering Validation Test, and DVT - Design Validation Test) until the engineering requirements are met.
Practical Example: Development of a Consumer-Friendly Streaming Dongle for Emerging Countries
1. Market Requirements Document (MRD):
Motivation: Crafting a streaming dongle that's not just a piece of tech, but a bridge to a universe of entertainment, tailored for the vibrant diversity of emerging countries.
Objective: Develop a consumer-friendly, cost-effective streaming dongle tailored for emerging countries.
User Experience Considerations: Simple setup process, multilingual support, intuitive UI, and compatibility with major streaming platforms.
2. Product Requirements Document (PRD):
Plan of Record (POR) Core Tech Specs:
2K streaming capability.
1 GByte of RAM.
8 GByte of storage.
Support for 2.4 GHz band Wi-Fi only.
Package: 1-meter HDMI cable, 5V 1A USB power supply, remote control with 2x AAA batteries.
User-friendly remote with voice recognition capability.
Performance metrics: range of remote, keypress response latency, remote battery life, support for 4K60FPS future upgrades.
Compliance: HDMI 1.4, FCC, CE certifications.
Connectivity: WLAN 802.11 b/g/n/ac, Bluetooth 5.0 for connecting peripherals like headphones.
3. Engineering Requirements Specification (ERS):
Component Selection:
Choice of SoC, RAM, eMMC, PCB layers.
Wi-Fi module selection based on power consumption and range.
Thermal design for heat dissipation.
HDMI cable type to ensure quality output.
Power supply vendor selection based on reliability and cost.
Performance Metrics:
EMC requirements, ESD test criteria.
Emission/immunity criteria, surge/lightning protection.
Power budget to be kept below 5W to ensure safety and energy efficiency.
RF Specifications:
Link budget, rate vs. range considerations.
Peak TX and RX throughput.
Conducted and radiated test parameters.
Competitive benchmark analysis to ensure superior performance.
SIPI Compliance: Ensure physical layer testing standards for high-speed digital interfaces like USB3.0 are met.
Design Aspects:
Power distribution network (PDN) design.
Maximum IC case temperature guidelines.
Thermal considerations for user safety.
Reliability tests: drop, vibration, tumble, environmental tests.
System architecture considerations: digital interface designs, power tree planning, clock tree, and a physical layout floor plan for each subsystem.
4. Validation and Verification:
Comprehensive test plans covering:
Audio quality.
RF performance.
Low-speed and high-speed digital interface checks.
Software stability and user interface responsiveness.
Over-the-air software update capability without disruptions.
5. User Feedback & Iterations:
Pilot testing in selected regions to gather user feedback.
Iterations based on feedback to ensure product-market fit.
Summary & Conclusion
The design process for developing a product involves several key steps, starting with understanding market needs and translating them into product requirements. These requirements are then further translated into engineering specifications, which guide the system architecture design, schematic capture, layout, and validation and verification testing. The goal is to create a product that meets the market demands while considering factors such as performance, compliance, connectivity, power, RF, signal integrity, and thermal considerations.
Designing a system based on market requirements and product specifications is crucial for system design engineers to make informed decisions regarding scope, schedule, and cost trade-offs. By following a systematic approach and ensuring the alignment of market needs with product features, engineers can develop successful products that meet customer expectations.