Short answer

Designers should develop a robust process for defining and analyzing requirements, explicitly mapping them to physical components to understand and proactively manage mass implications throughout the design lifecycle.

Field
Modelling
Source
TigerPrints (Clemson University) (2010)
Method
Systematic requirement analysis and modelling
Evidence
Strong effect

By systematically linking engineering requirements to physical components and their associated mass, designers can identify significant mass reduction opportunities at the earliest stages of product development. This modelling research insight is drawn from a 2010 study published in TigerPrints (Clemson University). Using Systematic requirement analysis and modelling, researchers explored how this design variable affects real-world outcomes. The key design takeaway: Designers should develop a robust process for defining and analyzing requirements, explicitly mapping them to physical components to understand and proactively manage mass implications throughout the design lifecycle.

Study
ModellingHigh ImpactStrong effect

Systematic Requirement Analysis Identifies Mass Reduction Opportunities Early in Design

By systematically linking engineering requirements to physical components and their associated mass, designers can identify significant mass reduction opportunities at the earliest stages of product development.

TigerPrints (Clemson University) · 2010

01

Key Findings

  • 01A systematic method can link engineering requirements to physical components and their mass.
  • 02Design Structure Matrices (DSMs) and Domain Mapping Matrices (DMMs) can represent these relationships.
  • 03This linkage enables the quantification of mass affected by individual requirements and their coupling.
02

Application

Design takeaway

Designers should develop a robust process for defining and analyzing requirements, explicitly mapping them to physical components to understand and proactively manage mass implications throughout the design lifecycle.

How to apply

When initiating a new design project or undertaking a product redesign, create a matrix that lists all requirements and maps them to the specific components they affect. Quantify the mass of these components to understand which requirements have the most significant impact on overall product mass.

Project actions

  • 01Clearly define your product requirements before starting any physical design.
  • 02Create a clear mapping between each requirement and the specific components or systems that fulfill it.
  • 03Use matrices to visualize and analyze these relationships, focusing on components with significant mass.
03

Method & Evidence

AimCan engineering requirements be systematically represented and processed to identify their impact on physical components and systems, thereby enabling mass reduction during product redesign?
MethodSystematic requirement analysis and modelling
ProcedureEngineering requirements were standardized using pre-processing and syntax rules. These processed requirements were then linked to physical components and assemblies based on their influence, captured in Design Structure Matrices (DSMs) and Domain Mapping Matrices (DMMs). Software tools, including a systems engineering tool and a spreadsheet application, were used to model the system and perform data analysis.
ContextProduct development, reverse engineering, and vehicle subsystem design (FMTV truck)

Variables

IVStandardized engineering requirements, linkage rules
DVQuantified mass affected by requirements, level of requirement coupling
CVProduct subsystems (FMTV truck), software tools used for modelling and analysis
04

Strengths & Limitations

Strengths

  • +Provides a structured, systematic approach to requirement analysis for mass reduction.
  • +Emphasizes early-stage intervention in the design process.

Limitations

The accuracy of mass estimations for components can be a limitation. Defining clear and unambiguous requirements is essential for effective mapping.

Reliability & validity

Reliability would depend on the consistency of requirement interpretation and the accuracy of component mass data. Validity is supported by the systematic approach to linking abstract requirements to concrete physical attributes.

Think critically

How might the complexity of interdependencies between requirements and components in highly integrated systems affect the accuracy of this mass impact analysis?

05

Design Principles

"Early and systematic analysis of requirement-mass relationships is crucial for effective product mass reduction."

Early identification of mass-impacting requirements allows for proactive design decisions, leading to more efficient resource utilization, reduced material costs, and improved product performance. This approach shifts mass reduction from a late-stage optimization problem to an integrated design consideration.

06

What This Means for Your Design

By carefully writing down what a product needs to do and then figuring out which parts of the product are affected by each need, you can find the best ways to make the product lighter early on.

How to use in your project

  • 1.Use this method to justify design choices related to mass reduction in your design project.
  • 2.Document your requirement analysis process, including the matrices used, to show how you identified opportunities for mass reduction.
07

Add to My Project

08

Quick Cite

Paragraph starter

The research by McLellan (2010) proposes a systematic method for analyzing engineering requirements to identify significant mass reduction opportunities. By standardizing requirements and linking them to physical components using matrices like DSMs and DMMs, designers can quantify the mass impact of each requirement early in the design process, enabling more efficient and targeted mass reduction strategies.

09

Source

TigerPrints (Clemson University)

A Proposed Method to Identify Requirements Significant to Mass Reduction

journal · 2010

View source

Questions About This Research

What does the research say about systematic requirement analysis identifies mass reduction opportunities early in design?
Designers should develop a robust process for defining and analyzing requirements, explicitly mapping them to physical components to understand and proactively manage mass implications throughout the design lifecycle. Evidence: TigerPrints (Clemson University) (2010).
Why does "Systematic Requirement Analysis Identifies Mass Reduction Opportunities Early in Design" matter for design?
Early identification of mass-impacting requirements allows for proactive design decisions, leading to more efficient resource utilization, reduced material costs, and improved product performance. This approach shifts mass reduction from a late-stage optimization problem to an integrated design consideration.
How can designers apply this research?
Designers should develop a robust process for defining and analyzing requirements, explicitly mapping them to physical components to understand and proactively manage mass implications throughout the design lifecycle.
What were the main findings?
A systematic method can link engineering requirements to physical components and their mass.. Design Structure Matrices (DSMs) and Domain Mapping Matrices (DMMs) can represent these relationships.. This linkage enables the quantification of mass affected by individual requirements and their coupling.
What research method was used?
Systematic requirement analysis and modelling.
How strong is the evidence?
Evidence strength is rated Strong effect, based on a 2010 journal from TigerPrints (Clemson University).
What should I do differently in my next project?
When initiating a new design project or undertaking a product redesign, create a matrix that lists all requirements and maps them to the specific components they affect. Quantify the mass of these components to understand which requirements have the most significant impact on overall product mass.
What are the limitations?
The effectiveness of the method relies on the accuracy and completeness of requirement documentation and the established pre-processing and syntax rules. The complexity of large systems may require sophisticated software tools.