~~NOTOC~~ ======== Trimming ======== ==== General Information ==== |Name|Trimming| |Abbreviation|TRM| |Learning Cost|140| |Playing Cost|150| |Suggested Phases|2,3| == Engineers == ^ Mechanical Engineer ^ Industrial Design ^ System Engineer ^ Electrical Engineer ^ Production Engineer ^ Software Engineer ^ |✔|✔|✔|✔|✗|✗| == Technique and Issue Views == ^ BusinessNeeds ^ Stakeholder ^ Stakeholder Needs ^ System Requirements ^ System Structure Architecture ^ |✗|✗|✗|✗|✔| ^System Functional Architecture ^Detail Hardware Design ^Detail Service Design ^Detail Software Design ^Manufacturing Operations ^ |✗|✔|✗|✗|✗| == Technique Traits == ^Identify Stakeholders ^Elicit Needs ^Remove Ambiguity ^Layman's Terms ^Technical Terms ^Teamworkings^ | | 1 | 1 | 0 | 0 | 1 | ^Traceability ^Prioritizing ^Exploring Breadth ^Inside the Box ^Outside the box ^ V&V^ | 2 | 3 | 4 | 2 | 3 | 2 | == Verification and Validation == ^Analysis ^Calculus ^Inspection ^Demonstration ^Test ^ | ✔ | ✗ | ✗ | ✗ | ✗ | ==== Description ==== Oftentimes, much time and resources are wasted on developing and producing overly complex systems and products. [1] The objective of the trimming design technique is cutting down the design to be as lean as possible. By reviewing a design or product and critically analyzing at all its functions and components, for each element it can be asked: is the element really necessary and is the function of the design altered without that part? If the function of the design is compromised by removal of the part the follow-up question can be: Can the element be executed in a simpler way? If yes is the answer to either of these questions, then the design can be simplified. The versatility of this technique makes it ideal for a wide variety of uses, from simplifying the design of a product to reduce cost, to leaning down a system of process to make it run more smoothly. [2] {{:fTrimming.png|}}