SUBJECTS
|
BROWSE
|
CAREER CENTER
|
POPULAR
|
JOIN
|
LOGIN
Business Skills
|
Soft Skills
|
Basic Literacy
|
Certifications
About
|
Help
|
Privacy
|
Terms
|
Email
Search
Test your basic knowledge |
Introduction To Mechanical Engineering Design
Start Test
Study First
Subject
:
engineering
Instructions:
Answer 47 questions in 15 minutes.
If you are not ready to take this test, you can
study here
.
Match each statement with the correct term.
Don't refresh. All questions and answers are randomly picked and ordered every time you load a test.
This is a study tool. The 3 wrong answers for each question are randomly chosen from answers to other questions. So, you might find at times the answers obvious, but you will see it re-enforces your understanding as you take the test each time.
1. ALL parts must function for system to work
Design space
Series system
Clients problem statement
Designer
2. Clarify objectives - establish metrics for objectives - identify constraints - revise clients problem statement
Problem definition
Constraints
Designer
Fantasy analogy
3. Establish funcions - establish requirements - establish means for functions - generate design alternatives - refine and apply metrics to design alternatives - choose a design
Interface requirements
Constraints
Contrasting solutions
Conceptual design
4. Model and analyze the chosen design - test and evaluate the chosen design
Personal analogy
Interface requirements
Preliminary design
Fantasy analogy
5. Working drawings showing major parts - without tolerances
Layout drawings
Assembly drawings
Continguous solutions
Symbolic analogy
6. ANY part must function for the system to work
Continguous solutions
Parallel system
Norming
Manufacturability
7. In a design with multiple systems the points where systems could interact with each other are known as boundaries.
Assembly drawings
Performing
Interface requirements
Problem definition
8. If this were a sci- fi scenario
Series system
Personal analogy
Fantasy analogy
Black box/transparent box
9. Refine and optimize chosen design - assign and fix design details
Design space
Detailed design
Constraints
Parallel system
10. A way to measure achievement of an objective
Metrics
Conceptual design
User
Storming
11. Absolute limits - what the design MUST do
User
Requirements
Design space
Function
12. What should it be?
Objectives
Personal analogy
Series system
Layout drawings
13. Written ideas are replaced with sketches
Final documentation
C- sketch method
Enumeration
Constraints
14. What if I were to do the opposite?
Contrasting solutions
Forming
Final documentation
User
15. Drawings of individual parts with every detail filled in
Clients problem statement
C- sketch method
Layout drawings
Detail drawings
16. Things that the design must NOT be or do
C- sketch method
Black box/transparent box
Constraints
Dissection/Reverse engineering
17. Take apart a similar item asking - 'How does it do that?'
Dissection/Reverse engineering
Dimensional consistency
Design communication
Interface requirements
18. # of group members - # of ideas - (# of group members -1)
6-3-5 method
Final documentation
Enumeration
Problem definition
19. List functions as they come to you
Personal analogy
Metrics
Enumeration
Symbolic analogy
20. A box that list the various inputs and outputs to a system.
Function means tree
Black box/transparent box
Design space
Forming
21. Actual work
Performance requirements
Series system
Performing
Procedural requirements
22. Team is called together
Detail drawings
Conceptual design
Forming
Performance requirements
23. Specific units in yeild specific units out
Fantasy analogy
Adjourning
C- sketch method
Dimensional consistency
24. Using metaphors and similies
Parallel system
Black box/transparent box
Symbolic analogy
Manufacturability
25. Values for attributes
Prescriptive requirements
Direct analogy
Continguous solutions
C- sketch method
26. Engineering economics
Performing
Client
Affordability
Performance requirements
27. 'If I were the object...'
Performing
Personal analogy
Detailed design
Continguous solutions
28. Those who will use the final product
Clients problem statement
Client
Designer
User
29. Presentation - report
Personal analogy
Prescriptive requirements
Design communication
Adjourning
30. Something is physically like something else
Direct analogy
Adjourning
Assembly drawings
Clients problem statement
31. Those who want the product
Function
Client
Series system
Interface requirements
32. Something related that serves a different purpose
Assembly drawings
Continguous solutions
Enumeration
Layout drawings
33. Describe successful functional behavior
Performance requirements
User
Enumeration
Clients problem statement
34. Settling into place
Designer
Final documentation
Conceptual design
Norming
35. Start with one function - expand each branch until it is no longer practical
Function means tree
Fantasy analogy
Black box/transparent box
User
36. Probablility that a system will not fail
Reliability
Conceptual design
Constraints
C- sketch method
37. Generaly vague - possibly biased toward a particular solution - will need to be revised
Final documentation
Clients problem statement
Metrics
Interface requirements
38. Size is proportional to how many designs there are
Design space
Assembly drawings
Function
Parallel system
39. The task that the object has to perform
Problem definition
Direct analogy
Function
Enumeration
40. Those who create the desired design
Performance requirements
Designer
Design communication
Dimensional consistency
41. Understanding of manufacturing processes - Design for manufacturing process
Problem definition
Parallel system
Manufacturability
Clients problem statement
42. Project finished
Assembly drawings
Prescriptive requirements
Objectives
Adjourning
43. Drawings showing how individual parts should fit together
Requirements
Conceptual design
Assembly drawings
C- sketch method
44. Who will lead
Storming
Client
C- sketch method
Symbolic analogy
45. How an attribute or behavioral will be calculated
Continguous solutions
Forming
Procedural requirements
Design communication
46. Presentation - report
Final documentation
Personal analogy
User
Problem definition
47. Everyone comments on the sketches
Procedural requirements
Gallery method
Performance requirements
Conceptual design