ENGINEERING DESIGN
APPROACH
NEW PRODUCT DEVELOPMENT AND CONCEPT DEVELOPMENT
Introduction to New Product Development in
Engineering Design
New Product Development (NPD) is a systematic and strategic
engineering process used to transform an idea into a market-ready
product. It involves multiple stages, from identifying market needs
to concept development, detailed design, prototyping, testing, and
finally, launching the product. Within this framework, concept
development is one of the most critical early stages. It connects
the creative aspects of innovation with the technical foundation of
engineering design, acting as a bridge between what should be
built and how it will be built.
Steps in New Product Development (NPD)
1.Idea Generation
2.Screening of Ideas
3.Concept Development and Strategy formulation.
4.Product Roadmap and Business analysis
5.Prototyping and MVP(Minimum Viable Product) development.
6.Product deployment and Testing
7.Product Launch
8.Feedback and Continuous Improvement
CONCEPT DEVELOPMENT
What is Concept Development?
Concept development is the initial stage of the product development lifecycle where ideas are transformed into
viable product concepts that align with business objectives, technical feasibility, and user needs. It defines what the
product will do, how it might look, and why it will succeed in the market.
STEPS IN CONCEPT DEVELOPMENT
Stage Details
Conduct surveys, interviews, or market analysis to
understand what the user wants. Use tools like Voice of
1. Identify Customer Needs
the Customer (VOC) and Quality Function Deployment
(QFD).
Convert needs into clear technical challenges or functions
2. Define Problem Statements
the product must address.
Study competitors’ products for performance, materials,
3. Benchmarking
design ideas, and weaknesses.
Brainstorm multiple concepts using sketches, mood
4. Generate Concepts boards, and early CAD models. Include both innovative
and proven ideas.
Use decision matrices, SWOT analysis, or Pugh charts to
5. Evaluate Concepts compare alternatives based on cost, feasibility,
performance, etc.
Choose the concept that best balances design goals,
6. Select Best Concept(s)
manufacturing feasibility, customer satisfaction, and ROI.
Create early prototypes (e.g., foam models, 3D printed
7. Refine and Iterate
parts) to test form, function, and ergonomics.
PRODUCT REQUIREMENTS AGAINST
SPECIFICATIONS
Introduction to Product Requirements and Specifications
In the field of engineering design, clearly defining product requirements and translating them into precise specifications is a
critical step toward successful product development. Requirements describe what the product must achieve, while specifications
define how those requirements will be met through engineering decisions. This process ensures the end product aligns with
customer needs, regulatory standards, and performance expectations. Understanding the difference and relationship between
these two aspects is essential for design engineers, product managers, and quality assurance teams.
Product Requirements: Understanding What the Product Should Do
Product requirements are broad, descriptive statements that identify the functions, capabilities, and constraints of a product
from a user or system-level perspective. These are usually derived from customer expectations, market research, safety norms,
and business goals. They do not provide technical details but describe what the product is expected to deliver. For example, in
an electric two-wheeler, a product requirement might state that "the scooter should travel 80 km on a single charge" or "the
braking system should stop the vehicle safely at high speeds." These requirements help the design team focus on end-user
satisfaction, safety, and product utility.
Product Specifications: How Requirements are Technically Achieved
Specifications, on the other hand, are precise and measurable technical details that explain how each requirement will be
fulfilled. These are developed by engineers and designers during the design process and are used for modeling, simulation,
prototyping, and testing. Specifications might include parameters such as dimensions, materials, voltage, weight, torque,
temperature range, tolerances, or regulatory compliance figures. For the earlier example of range, the corresponding
specification might be "Battery capacity: 4.4 kWh with a voltage of 72V and motor efficiency ≥ 90%." Such measurable
figures help guide engineers during product development and ensure every aspect can be validated and tested.
Introduction to Specifications in Engineering Design
In engineering design, specifications are the precise, technical descriptions of a product’s characteristics, functions,
dimensions, performance limits, materials, and other parameters. They serve as a bridge between the product concept and the
actual implementation by engineers, technicians, and manufacturers. Specifications act as detailed blueprints that guide the
product’s development, assembly, testing, and quality assurance processes. They are essential in ensuring that the final design
fulfills the intended product requirements.
Role and Purpose of Specifications
The primary role of specifications is to clearly communicate what is expected from each component, system, or assembly of
a product. This prevents ambiguity and reduces the possibility of errors during design and manufacturing. Specifications provide
objective, measurable criteria that can be used to verify whether the product meets the functional requirements, industry
standards, and user expectations. They also enable teams to conduct simulations, tolerancing, performance analysis, and
ensure interchangeability between parts in complex assemblies.
Types of Specifications
Specifications can be categorized based on their function:
•Functional Specifications: Describe what a system or component must do (e.g., "must withstand 100 kg load").
•Performance Specifications: Define measurable performance criteria (e.g., "motor must deliver 4.5 kW power at
4300 RPM").
•Material Specifications: Specify material types and properties (e.g., "use AISI 1020 steel with yield strength ≥ 350
MPa").
•Geometric Specifications: Include sizes, shapes, tolerances, and surface finishes (e.g., "shaft diameter 40 mm ± 0.05
mm").
•Environmental Specifications: Mention conditions under which the product should perform (e.g., "operating
temperature: -10°C to +45°C").
•Regulatory/Compliance Specifications: Define legal or safety standards the product must meet (e.g., "must comply
with AIS 156 battery standards").
Example of Specifications in an EV Scooter Design
Let's consider an electric two-wheeler as an example. Below are
some sample specifications derived during design:
•Battery Capacity: 4.4 kWh, Voltage: 72 V
•Motor Type: Brushless DC hub motor, 4.5 kW, 140 Nm torque
•Chassis Material: Mild steel (AISI 1020), 2.5 mm wall thickness
•Brake Disc Diameter: 220 mm front, 180 mm rear
•Tire Size: 90/90-12, Diameter: 466 mm
•Suspension Travel: Telescopic fork, 110 mm travel
•Ingress Protection Rating: IP67 for electronics
•Frame Load Capacity: 180 kg with FOS ≥ 2.5
In the engineering design approach, defining clear and measurable product specifications from high-level requirements
ensures that:
• The final product aligns with customer expectations
• All components are engineered with precision
• The design is testable, manufacturable, and compliant
This bridge between "what is needed" and "how it’s delivered" is what turns an idea into a functional product.
Maps each requirement to one or more Translates customer voice into
measurable specifications engineering terms
Requireme Quality
nt Function
Specificati Deployme
on Matrix Tools and nt (QFD)
Methods to
Align
Requirement
s and
Specification
s Failure
System Mode and
Engineerin Effects
g V-Model Analysis
(FMEA)
Ensures every requirement is validated Evaluates risks in failing to meet specs
by testing a corresponding specification derived from critical requirements
