Capstone, Gearbox - Coggle Diagram
Concept Development Week of 10/18
Target values for the system and subsystems
Section E of the requirements matrix
Justification for concept selection, including model analysis and/or prototype test data demonstrating concept feasibility
List, chart, or summary of considered concepts;
Evaluation summary of considered concepts demonstrating feasibility of selected concept;
Model and/or prototype test reports demonstrating validity of selected concept;
Rough technical models of the product concept
Low-fidelity fundamental models of concept's operating principles. Statistical models describing the performance of experimental prototypes or related existing products.
Rough protypes of the product concept
Geometric and other appropriate definition of the concept
One or more of the following: Annotated hand sketches of concept. Overall system CAD model. Layout drawing. Skeleton drawing...
Decomposition of product concept into subsystems
Tree or other diagram that shows structure of decomposition.
Subsystem interface definitions
Interface matrix showing where subsystems interact. Product-focused requirement statements for each of the interfaces. Performance measures for each of the interfaces. Subteam responsibility assignments for each interface
Preliminary Bill of Materials
Useful Tools: Bill of materials,..., brainstorming, competitive benchmarking, controlled convergence, decomposition, interviews, literature reviews,..., mind maps, prototyping,..., requirements matrix, scoring matrix,...
Common pitfalls: Concept fixation, premature concept critique, reinventing the wheel, vague interfaces, decision delay
Opportunity Development: Week of 9/27
Section C of the requirements matrix
Section B of the requirements matrix
Section D of the requirements matrix
Section A of the requirements matrix
Useful Tools: Basic design process, competitive benchmarking, financial analysis, focus groups, interviews, observational studies, patent searches, planning canvas, project objective statement, quality function deployment, requirements matrix, surveys.
Common pitfalls: Assuming, not validating; using only subjective performance measures; delaying feedback; devaluing the opportunity development stage; spending too much time.
Architecture Review Week of 11/15
Rear Gearbox to Front Gearbox