This document outlines the key phases of the electronics product design process: concept development, requirements gathering, specifications development, design and prototyping, testing, manufacturing, and disposal. It emphasizes that product development follows a systematic engineering approach involving thorough documentation at each phase, from initially defining customer needs to ensuring reliable, high-quality products that meet specifications. The goal is to deliver the best product at the lowest cost and time to market.

1. Dr. Anagha Parag Khedkar
Introduction to Electronics Product
Design

2. Outline
1/15/20192
 Basic flow of Product design and life cycle
 General Framework for Product Development
 Concept Development
 System Requirements
 System Specifications
 Design and Development
 Prototype and Testing
 Disposal
 Reliability and Failures
 Conclusion
 References

3. Basic Flow of Product design and its
Life Cycle
1/15/20193
 Design & development of electronic products comes
under Systematic Engineering.
 Systems engineering- follows systematic approach
 Systems engineering – provides a general framework
to develop product
 Product development framework : starts from Concept
till its disposal.
 All phases should maintain proper documentation
 Result expected- best product at lowest cost with
optimum time to market.

4. Systems Engineering Aspects: General
Framework for Product Development
1/15/20194
Product Concept
Development
Start Up
Requirements Collection
From Stakeholders
Marketing, Research and
Design
Preparation of system
specifications
Research and Design
Hardware and Software
Design
Research and Design
Prototype Development and
Testing and verification
Research and Design
and Testing
Mass Manufacturing Production
Maintenance and Support
Maintenance and
Repair
Disposal
Environmental
Department

5. Concept Development
1/15/20195
 Define the problem for development
 For defining the problem first look into
 customer objectives
 Customer and end user needs
 Regions of operation
 Constraints
 Regulations and standards

6. Customer Requirements
1/15/20196
Consider :
 Type and Culture of customer
 Corporate, social, economic, political etc.
 Requirements define What of the system but not how
 At the end, do analysis of requirements and refine the
requirements.

7. Identifying the Customer Requirements
1/15/20197
 Product development typically starts by
 Identifying-
 what the customer wants
Or
 User may be looking for
 automating the existing industrial process
 expanding his current manufacturing

8. Identifying the Customer Requirements
1/15/20198
 Understand the requirement: Marketing or
sales person should understand the requirements
thoroughly.
 Proper solution : A number of meetings are
required to correctly understand the process and
arrive at a proper solution.

9. Classify Requirements
1/15/20199
General Types:
1. Performance: range, speed, throughput, resolution
2. Reliability & maintainability: failure rate
3. Human factors & user interface: ease of use
4. Safety & failure mode : fault analysis
5. Operational regimes & environment: extreme
temperatures
6. Logistics support: maintenance tasks

10. System Requirements Specifications
(SRS) Document
1/15/201910
 After analysis and refinement of requirements,
prepare SRS document.
 It includes functional requirements, performance
requirements, interface requirements, design
requirements, and development standards.
 SRS provides a view from outside of the system.
 Follow standard formats for SRS preparation.

11. Convert Requirements to Specifications
1/15/201911
 Customer’s requirement must be correctly translated in
to the formal specifications of a product/system.
 Transform SRS document to System Design
Specifications (SDS) document.
 SDS is based on SRS and specifies how of the system,
but not what.
 SDS must specify how requirements are to be met by
internal functions of system.
 SDS is a complete document that contains all of the
information needed to develop the system.

12. Designing the Product
1/15/201912
 Systems design is the process of defining the architecture, components,
modules, interfaces, and data for a system to satisfy specified
requirements.
 Partitioning : Hardware design and Software Design
 Designed to specifications
 paper design
 prototyping with acceptable method(s),
 development of R & D prototype
 R & D prototype is thoroughly tested for technical and functional
specifications
• Field trials
• May requires some design modifications
• Engineering prototype

13. Engineering Prototype
1/15/201913
 Rapid prototyping – short duration
 Useful for human interface aspects (ease of use,
response latency)
 Field testing – longer duration
 Beta testing: setting up prototype at various
customer sites for initial evaluation

14. Validation, Verification and Integration
1/15/201914
 Validation: determines how well the requirements
suit the intent of system.
 Verification: evaluates how well the system
satisfies the requirements.
 Integration: process of assembling the components
and subsystems and performing the acceptance
tests of validation & verification.

15. Engineering Prototype Testing and
manufacture
1/15/201915
 Environmental tests
 Field Trials
 Modifications may be carried out
 This completes the first phase of product design.
 Making Pilot Production Batch
 Quality Assurance Check
 Mass manufacturing
 Maintenance

16. Disposal of Product: e-waste
1/15/201916
 Electronic waste(e-waste) management is essential
phase of product life cycle.
 To ensure environmental safety and effective use
of resources, follow
Reduce
Reuse
Recycle
 Continuous update of technology leads to large e-
waste.

17. Reliability
1/15/201917
 Reliability is the probability that a system will
perform its specified function successfully in a given
operating environment.
 It plays major role in cost effectiveness of system.
 Ensures quality over time and environmental
conditions
 Reliable product demands for reliable components
and subsystems.
 No. of tests performed throughout manufacture to
ensure reliability.
 An electronic product may fail due to number of
reasons.

18. Causes of failure
1/15/201918
 Noise coupling by various mechanisms into electronic product.
 Components used have incorrect values especially resistance,
inductance, capacitance, or dielectric properties.
 Vibrations and shocks.
 Extreme temperature conditions.
 Improper Packaging and enclosures.
 Due to improper shielding for EMI or due to Electrostatic
Discharge (ESD).
 Wiring problems in system.

19. Disposal of Product: e-waste
1/15/201919
 Electronic waste(e-waste) management is essential
phase of product life cycle.
 To ensure environmental safety and effective use
of resources, follow principles
Reduce
Reuse
Recycle
 Continuous update of technology leads to large e-
waste.

20. Conclusion
1/15/201920
 This is brief overview of basic product life cycle
and its various phases.
 Each phase itself is a thorough process associated
with proper and neat documentation.
 Following and standardizing each and every phase
makes the successful product design.

21. References
1/15/201921
1. Kim R. Fowler, “Electronic Instrument Design:
Architecting for the Life Cycle”, Oxford
University Press, 2nd Edition, 2007.
2. James K. Peckol, “Embedded Systems – A
Contemporary Design Tool”, Wiley publication,
2008.