Total Design: From Market Needs to Final Product
Total Design: From Market to Sales
Total Design: A systematic approach starting from identifying consumer market needs to delivering a satisfactory final product.
Total Design Phases:
Market Requirements, Conceptual Design, Detailed Design, Manufacturing, Sales
Collaborative Development: Teamwork
To develop innovative product designs, two approaches are used: Synchronous and Asynchronous.
Phase 1: Market Demand
Techniques:
Parametric Analysis: This technique identifies the product’s position in the market relative to the competition.
Analysis of Customer Needs: Identifying the real needs of consumers through surveys, interviews, experimental methods, and the Delphi method.
Matrix Analysis: Useful for comparing products with regard to competition.
Phase 2: Requirements
(QFD) Steps:
- Identify customer requirements (What’s).
- Identify the technical requirements (How’s).
- Identify the relationships between What’s and How’s.
- Identify the relationships between the How’s.
- Determine the weight of each element.
- Evaluate competition.
Requirements / Design Specification Product: May be preferred or required.
Design and Product Specifications: Environment, Customers, Service, Quantity, Cost, Storage, Weight, Law, Quality.
Phase 3: Conceptual Design
Conceptual Design Stage: Identify design alternatives, evaluate them, and select those that best meet and transform product requirements into a more detailed level.
Conceptual Design Phase:
-
Identification of Key Features: Express key characteristics by:
- Black Box
- QFD
- Morphological Matrix
- Ishikawa Diagram
-
Identification of Key Resources: By:
- Cost per Design: Analyzing the cost to minimize it and increase sales.
- Test Domain: Add the various criteria.
- Tradeoff Analysis: Analysis of design alternatives to optimize performance and reduce technical risks.
- Life Cycle Cost: Developing a cost model for maintenance acquisition throughout its life using the trade-off.
Phase 4: Detailed Design
Group tasks used to complete product design, which meets the requirements and design approach defined.
Design Analysis: Assesses the ability of the design to meet product specifications at the lowest possible cost.
Synthesis of Design: Highly abstract descriptions used to develop physical representations.
Prototype: Physical models and software used to ensure the information to: Reduce uncertainty, optimizing the parameters.
Modeling: A model is a simplified representation of a system designed to understand, predict, and control the behavior of the system.
It allows the designer to: Have the basis to experiment with requirements, optimize design decisions, and verify product performance.
Simulation: The simulation is used to experiment with different design requirements to ensure they are feasible and conform to the desired final product.
Methodology for Generation (SIM): Define the system and environment, so it is unknown. Enlist the system, list the effects of the environment, create the simulation, and verify the simulation.
Techniques for Reducing the Risk of the Design:
Finite Element Analysis: Uses mathematical tools to predict stress and its effect on the physical behavior of the system.
Analysis of Environmental Stress: Evaluates the performance of the product under ambient conditions.
Analysis and Failure Mode Effect: Technique to assess and reduce the effects caused by potential failure modes. Serves to identify: The effects of a potential flaw in a product, methods to avoid a failure.
Test and Evaluation: Serves to: Improve the product, identify and correct problems, and reduce technical risk.
Validation: Ensuring that the design meets the expectations.
Verification: Ensuring that the design and manufacturing can meet all design requirements.
Design Reviews: Used to identify problems and technical risks in the processing and use.
Mature Design: One that has been validated, verified, and evaluated.
Best Practices in Testing and Evaluation: Test and evaluation strategy, design review, production inspection, testing and evaluation of software.
Rules of Evidence: Discover error, it is unknown # of tests, tests for all conditions.
The goal of all testing and design review should be to identify areas for design improvement.