Materials and process selection for a bicycle frame
Background
The principle components of the bike are familiar and their function needs no explanation. The largest of these is the frame. Frames can be made from a remarkable diversity of materials: CFRP, carbon steel, GFRP, nylon, wood, aluminium, titanium etc… How is it that such a diversity of materials can co-exist in a free market in which competition favours the fittest – sure there must be a single “best” material for the job?
The mistake here is to assume that all bikes have the same purpose. The specification of a “shopping” or “uni” bike is very different from that of one for speed or for the mountain, as are the objectives of the purchaser.
The Project
Explore materials and process selection for bike frames (illustrated below) or for any other component of the bike: forks, handle bars, cranks, wheels, brake or gear cables….
1) Analyse your chosen component, listing its function, the constraints it must meet and the objectives for the bike – This will require a decision about the type of bike you are designing (shopping (booze cruiser), speed / road / track bike, mountain bike, folding, children’s etc). Remember to include a lower cut-off constraint on fracture toughness (K1C > 15MPa √m is a good approximation to start at) – a brittle bike would be a bad idea!
2) List the requirements as Functions, Constraints, Objectives and Free V ariables.
3) Identify the materials indices you will use to rank / select your materials.
4) Identify a promising material for the component.
5) Make a choice of material and then use CES EduPack Joining database to
select ways of joining the frame.
6) Present the case study for your choice of material and process as a report. Use
the charts from CES EduPack and other sources to explain your reasoning.
For the purposes of simplicity it is suggested that you avoid accounting for shape in your selection criteria / indices identification. However, you should still consider the form of your component when considering an appropriate manufacturing process.
To make the right choices you will need to source some information on typical service conditions for you selected bike type, these might be mechanical, physical or environmental focussed properties. You will also need to consider the type of conditions experienced by the component e.g. bending, tension, torsion, abrasion etc.

Assignments will be assessed on the basis of the quality and clarity of the problem construction, the selection of indices, appropriate use of charts / figures and crucially the analysis and interpretation of the results presented.

Materials and process selection for a bicycle frame
Background
The principle components of the bike are familiar and their function needs no explanation. The largest of these is the frame. Frames can be made from a remarkable diversity of materials: CFRP, carbon steel, GFRP, nylon, wood, aluminium, titanium etc… How is it that such a diversity of materials can co-exist in a free market in which competition favours the fittest – sure there must be a single “best” material for the job?
The mistake here is to assume that all bikes have the same purpose. The specification of a “shopping” or “uni” bike is very different from that of one for speed or for the mountain, as are the objectives of the purchaser.
The Project
Explore materials and process selection for bike frames (illustrated below) or for any other component of the bike: forks, handle bars, cranks, wheels, brake or gear cables….
1) Analyse your chosen component, listing its function, the constraints it must meet and the objectives for the bike – This will require a decision about the type of bike you are designing (shopping (booze cruiser), speed / road / track bike, mountain bike, folding, children’s etc). Remember to include a lower cut-off constraint on fracture toughness (K1C > 15MPa √m is a good approximation to start at) – a brittle bike would be a bad idea!
2) List the requirements as Functions, Constraints, Objectives and Free V ariables.
3) Identify the materials indices you will use to rank / select your materials.
4) Identify a promising material for the component.
5) Make a choice of material and then use CES EduPack Joining database to
select ways of joining the frame.
6) Present the case study for your choice of material and process as a report. Use
the charts from CES EduPack and other sources to explain your reasoning.
For the purposes of simplicity it is suggested that you avoid accounting for shape in your selection criteria / indices identification. However, you should still consider the form of your component when considering an appropriate manufacturing process.
To make the right choices you will need to source some information on typical service conditions for you selected bike type, these might be mechanical, physical or environmental focussed properties. You will also need to consider the type of conditions experienced by the component e.g. bending, tension, torsion, abrasion etc.

Assignments will be assessed on the basis of the quality and clarity of the problem construction, the selection of indices, appropriate use of charts / figures and crucially the analysis and interpretation of the results presented.

<br>
This is an essay exam and should not be organized like an academic paper. I suggest answering each question with your word processor then carefully proofreading before copy/pasting into the boxes provided. Quote correctly from the texts when necessary to back up your assertions and show your understanding. <br>
<br>
Part of what I�m doing here is checking to see if you know how to introduce and comment on quotations, and if you know how to select appropriate quotations that support the point you�re trying to make. Here is a copy/paste from the Virtual Salt website.<br>
<br>
1. Introduce your quotations. A quotation should never suddenly appear out of nowhere. Some kind of information about the quotation is needed. Name the author, give his or her credentials, name the source, give a summary. You won’t do all of these each time, but you should usually name the author. For example: <br>
<br>
a. But John Jones disagrees with this point, saying, “Such a product would not sell.” <br>
<br>
b. In an article in Time Fred Jackson writes that frogs vary in the degree of shyness they exhibit: “The arboreal tree frogs seem to be especially. . . .”<br>
<br>
2. Discuss your quotations. Do not quote someone and then leave the words hanging as if they were self-explanatory. What does the quotation mean and how does it help establish the point you are making? What is your interpretation or opinion of it? Quotations are like examples: discuss them to show how they fit in with your thesis and with the ideas you are presenting. Remember: quotations support or illustrate your own points. They are not substitutes for your ideas and they do not stand by themselves.<br>
<br>
It is often useful to apply some interpretive phrasing after a quotation, to show the reader that the you are explaining the quotation and that it supports your argument:<br>
<br>
�Here we see that<br>
<br>
�This statement shows<br>
<br>
�Clearly, then,<br>
<br>
�We can conclude from this that<br>
<br>
�This tells us that<br>
<br>
�From this we can understand that<br>
<br>
<br>
Below is the rubric I will use in evaluating your paper.<br>
<br>
Quality: A good response will have a focus that will interest the reader and will not be totally obvious. It will go beyond class discussion and show evidence of your own thought. <br>
20<br>
<br>
Accuracy: You should not distort the works or conveniently leave out evidence that doesn�t fit your purpose. While varying interpretations are possible, you must be correct about the factual details of the works.<br>
20<br>
<br>
Clarity: I must be able to understand what you’re saying, and your rationale for your rankings must be developed in enough detail that I can understand you.<br>
20<br>
<br>
Quotation: You must refer to the texts by direct quotation and paraphrase in order to back up your assertions. You must incorporate quotations gracefully into your discussion, introducing them and commenting on their significance. Remember that the quotation doesn�t speak for itself � you are the interpreter. If you are unsure about how to do this, see “Using Quotations Effectively” below.<br>
20<br>
<br>
Format and Editing: Your work must be spell-checked and carefully proofread. You must have a reasonable command of the conventions of formal academic writing Name your file Lastname,Assn 3. Include a Works Cited page in MLA format, in which you list all sources referred to in your paper <br>
20<br>
<br>
TOTAL POINTS<br>
100

<br>
This is an essay exam and should not be organized like an academic paper. I suggest answering each question with your word processor then carefully proofreading before copy/pasting into the boxes provided. Quote correctly from the texts when necessary to back up your assertions and show your understanding. <br>
<br>
Part of what I�m doing here is checking to see if you know how to introduce and comment on quotations, and if you know how to select appropriate quotations that support the point you�re trying to make. Here is a copy/paste from the Virtual Salt website.<br>
<br>
1. Introduce your quotations. A quotation should never suddenly appear out of nowhere. Some kind of information about the quotation is needed. Name the author, give his or her credentials, name the source, give a summary. You won’t do all of these each time, but you should usually name the author. For example: <br>
<br>
a. But John Jones disagrees with this point, saying, “Such a product would not sell.” <br>
<br>
b. In an article in Time Fred Jackson writes that frogs vary in the degree of shyness they exhibit: “The arboreal tree frogs seem to be especially. . . .”<br>
<br>
2. Discuss your quotations. Do not quote someone and then leave the words hanging as if they were self-explanatory. What does the quotation mean and how does it help establish the point you are making? What is your interpretation or opinion of it? Quotations are like examples: discuss them to show how they fit in with your thesis and with the ideas you are presenting. Remember: quotations support or illustrate your own points. They are not substitutes for your ideas and they do not stand by themselves.<br>
<br>
It is often useful to apply some interpretive phrasing after a quotation, to show the reader that the you are explaining the quotation and that it supports your argument:<br>
<br>
�Here we see that<br>
<br>
�This statement shows<br>
<br>
�Clearly, then,<br>
<br>
�We can conclude from this that<br>
<br>
�This tells us that<br>
<br>
�From this we can understand that<br>
<br>
<br>
Below is the rubric I will use in evaluating your paper.<br>
<br>
Quality: A good response will have a focus that will interest the reader and will not be totally obvious. It will go beyond class discussion and show evidence of your own thought. <br>
20<br>
<br>
Accuracy: You should not distort the works or conveniently leave out evidence that doesn�t fit your purpose. While varying interpretations are possible, you must be correct about the factual details of the works.<br>
20<br>
<br>
Clarity: I must be able to understand what you’re saying, and your rationale for your rankings must be developed in enough detail that I can understand you.<br>
20<br>
<br>
Quotation: You must refer to the texts by direct quotation and paraphrase in order to back up your assertions. You must incorporate quotations gracefully into your discussion, introducing them and commenting on their significance. Remember that the quotation doesn�t speak for itself � you are the interpreter. If you are unsure about how to do this, see “Using Quotations Effectively” below.<br>
20<br>
<br>
Format and Editing: Your work must be spell-checked and carefully proofread. You must have a reasonable command of the conventions of formal academic writing Name your file Lastname,Assn 3. Include a Works Cited page in MLA format, in which you list all sources referred to in your paper <br>
20<br>
<br>
TOTAL POINTS<br>
100

<br>
Plagiarism Quiz<br>
You should complete the quiz and also visit the Skills@Library website for more information on academic integrity.<br>
<br>
Your work will be uploaded to Turnitin. If you plagiarise, you will be caught. Several students have been excluded from the University over the last couple of years for plagiarism. Don’t let it be you!<br>
<br>
Your report will also contain your code. This mini-project is an individual piece of work. Do not let your friends and classmates copy your code. This is collusion.<br>
<br>
<br>
Report Outline<br>
Create your report in Word or similar software. Use the following structure:<br>
<br>
Title Page (include your name and SID)<br>
Contents Page<br>
Introduction<br>
Hardware Description<br>
Software Description<br>
Results and Testing<br>
Conclusion<br>
References<br>
Appendix<br>
Use relevant subsections as you see fit <a href=”https://i.e” target=”_blank”>i.e</a>. <a href=”https://4.1″ target=”_blank”>4.1</a> LCD Display<br>
<br>
The suggested length is 10 to 14 pages. The appendix does not count towards the page length.<br>
<br>
<br>
Introduction<br>
This is your opportunity to set your report in context.<br>
What is an embedded system?<br>
What is a microcontroller?<br>
What are the possible applications of your project?<br>
List a set of clear aims and objectives for your project.<br>
To get the best marks, you are expected to do further reading and not just rely on the lab notes.<br>
<br>
<br>
Hardware Description<br>
Present an overall system block diagram.<br>
Discuss each block in depth (use sub-sections).<br>
Include images of each block.<br>
Link the operation of each block to the underlying theory.<br>
To get the best marks, you are expected to do further reading and not just rely on the lab notes (<a href=”https://e.g” target=”_blank”>e.g</a>. how does the LCD interface work?).<br>
<br>
<br>
Software Description<br>
If you followed good software engineering practice, your code should be split into different functions.<br>
Present flowchart of the overall software flow.<br>
You should not create a flowchart that mirrors the code line-by-line, it is more of a general overview.<br>
If the flowchart is too simple, the reader would not be able implement the algorithm.<br>
If the flowchart is too complex, it can be difficult for the reader to follow. Find the right balance.<br>
Present flowcharts of each function. <br>
<br>
Results and Testing<br>
This corresponds to the technical merit of the project in the report rubric.<br>
<br>
Present the testing of the temperature logger.<br>
You can take images of the LCD screen using a camera demonstrating the functionality.<br>
To achieve the highest marks, you are required to implement original features – ensure these are discussed here to obtain credit for them.<br>
<br>
Conclusion<br>
Discuss each of the aims and objectives presented in the introduction.<br>
If you did not meet them, explain why.<br>
Discuss how you could expand the project in fututre.<br>
<br>
References<br>
Reference any resources you have used.<br>
Avoid the use of Wikipedia.<br>
Use IEEE referencing style. There are good examples on the University of York website.<br>
<br>
Appendix<br>
Paste your code into the appendix so that it can be run through Turnitin and checked for plagiarism/similarity with your classmates.<br>
<br>
Formatting<br>
Do not use colourful/jazzy Word templates. They look amateurish and detract from the technical content.<br>
Use sections and sub-sections to break the text up. Technical reports are not like essays. Section titles are normally bold and can be slightly larger font.<br>
Use a consistent size for your images. Ensure they are of sufficient resolution. This is especially important for images with text in.<br>
Create your own images, avoid copying from online. If you do, respect copyright and include a reference.<br>
Taking pictures of images on the monitor using your smartphone is terrible practice and makes the report look amateurish. Use screen-shots.<br>
If you take pictures of hardware, do it on a clear background (<a href=”https://e.g” target=”_blank”>e.g</a>. white paper) and clip as much as the background out as possible. Pictures of PCB’s on a messy lab bench look awful in a report! <br>
Place images in between paragraphs. Do not embed them within paragraphs.<br>
Write in the passive voice.<br>
The multiplexer circuit was designed…<br>
<br>
Do not write in the first person<br>
I designed the multiplexer circuit…<br>
<br>
Include page numbers and a table of contents.<br>
Use consistent formatting. Do not jump between different fonts and font sizes within the body of the text (this usually happens when you cut-and-paste <a href=”https://i.e” target=”_blank”>i.e</a>. plagiarism!).<br>
Write in full sentences. Avoid informal language.<br>
The first time you use an abbreviation, you should include the expanded form <a href=”https://e.g” target=”_blank”>e.g</a>. SPI (Serial Peripheral Information).<br>
Write clearly. I appreciate that English may not be your first language, but you are studying at an English-speaking University. If an explanation does not make sense, it detracts from the technical content. <br>
For students who are registered with DSAS, your work is marked for content only.<br>
<br>
Please you need to do the last WEEK#10 because i didn’t finish it , it will be next Tuesday our last lab of WEEK#10 , so you can do the experiment.

<br>
Plagiarism Quiz<br>
You should complete the quiz and also visit the Skills@Library website for more information on academic integrity.<br>
<br>
Your work will be uploaded to Turnitin. If you plagiarise, you will be caught. Several students have been excluded from the University over the last couple of years for plagiarism. Don’t let it be you!<br>
<br>
Your report will also contain your code. This mini-project is an individual piece of work. Do not let your friends and classmates copy your code. This is collusion.<br>
<br>
<br>
Report Outline<br>
Create your report in Word or similar software. Use the following structure:<br>
<br>
Title Page (include your name and SID)<br>
Contents Page<br>
Introduction<br>
Hardware Description<br>
Software Description<br>
Results and Testing<br>
Conclusion<br>
References<br>
Appendix<br>
Use relevant subsections as you see fit <a href=”https://i.e” target=”_blank”>i.e</a>. <a href=”https://4.1″ target=”_blank”>4.1</a> LCD Display<br>
<br>
The suggested length is 10 to 14 pages. The appendix does not count towards the page length.<br>
<br>
<br>
Introduction<br>
This is your opportunity to set your report in context.<br>
What is an embedded system?<br>
What is a microcontroller?<br>
What are the possible applications of your project?<br>
List a set of clear aims and objectives for your project.<br>
To get the best marks, you are expected to do further reading and not just rely on the lab notes.<br>
<br>
<br>
Hardware Description<br>
Present an overall system block diagram.<br>
Discuss each block in depth (use sub-sections).<br>
Include images of each block.<br>
Link the operation of each block to the underlying theory.<br>
To get the best marks, you are expected to do further reading and not just rely on the lab notes (<a href=”https://e.g” target=”_blank”>e.g</a>. how does the LCD interface work?).<br>
<br>
<br>
Software Description<br>
If you followed good software engineering practice, your code should be split into different functions.<br>
Present flowchart of the overall software flow.<br>
You should not create a flowchart that mirrors the code line-by-line, it is more of a general overview.<br>
If the flowchart is too simple, the reader would not be able implement the algorithm.<br>
If the flowchart is too complex, it can be difficult for the reader to follow. Find the right balance.<br>
Present flowcharts of each function. <br>
<br>
Results and Testing<br>
This corresponds to the technical merit of the project in the report rubric.<br>
<br>
Present the testing of the temperature logger.<br>
You can take images of the LCD screen using a camera demonstrating the functionality.<br>
To achieve the highest marks, you are required to implement original features – ensure these are discussed here to obtain credit for them.<br>
<br>
Conclusion<br>
Discuss each of the aims and objectives presented in the introduction.<br>
If you did not meet them, explain why.<br>
Discuss how you could expand the project in fututre.<br>
<br>
References<br>
Reference any resources you have used.<br>
Avoid the use of Wikipedia.<br>
Use IEEE referencing style. There are good examples on the University of York website.<br>
<br>
Appendix<br>
Paste your code into the appendix so that it can be run through Turnitin and checked for plagiarism/similarity with your classmates.<br>
<br>
Formatting<br>
Do not use colourful/jazzy Word templates. They look amateurish and detract from the technical content.<br>
Use sections and sub-sections to break the text up. Technical reports are not like essays. Section titles are normally bold and can be slightly larger font.<br>
Use a consistent size for your images. Ensure they are of sufficient resolution. This is especially important for images with text in.<br>
Create your own images, avoid copying from online. If you do, respect copyright and include a reference.<br>
Taking pictures of images on the monitor using your smartphone is terrible practice and makes the report look amateurish. Use screen-shots.<br>
If you take pictures of hardware, do it on a clear background (<a href=”https://e.g” target=”_blank”>e.g</a>. white paper) and clip as much as the background out as possible. Pictures of PCB’s on a messy lab bench look awful in a report! <br>
Place images in between paragraphs. Do not embed them within paragraphs.<br>
Write in the passive voice.<br>
The multiplexer circuit was designed…<br>
<br>
Do not write in the first person<br>
I designed the multiplexer circuit…<br>
<br>
Include page numbers and a table of contents.<br>
Use consistent formatting. Do not jump between different fonts and font sizes within the body of the text (this usually happens when you cut-and-paste <a href=”https://i.e” target=”_blank”>i.e</a>. plagiarism!).<br>
Write in full sentences. Avoid informal language.<br>
The first time you use an abbreviation, you should include the expanded form <a href=”https://e.g” target=”_blank”>e.g</a>. SPI (Serial Peripheral Information).<br>
Write clearly. I appreciate that English may not be your first language, but you are studying at an English-speaking University. If an explanation does not make sense, it detracts from the technical content. <br>
For students who are registered with DSAS, your work is marked for content only.<br>
<br>
Please you need to do the last WEEK#10 because i didn’t finish it , it will be next Tuesday our last lab of WEEK#10 , so you can do the experiment.

<br>
Plagiarism Quiz<br>
You should complete the quiz and also visit the Skills@Library website for more information on academic integrity.<br>
<br>
Your work will be uploaded to Turnitin. If you plagiarise, you will be caught. Several students have been excluded from the University over the last couple of years for plagiarism. Don’t let it be you!<br>
<br>
Your report will also contain your code. This mini-project is an individual piece of work. Do not let your friends and classmates copy your code. This is collusion.<br>
<br>
<br>
Report Outline<br>
Create your report in Word or similar software. Use the following structure:<br>
<br>
Title Page (include your name and SID)<br>
Contents Page<br>
Introduction<br>
Hardware Description<br>
Software Description<br>
Results and Testing<br>
Conclusion<br>
References<br>
Appendix<br>
Use relevant subsections as you see fit <a href=”https://i.e” target=”_blank”>i.e</a>. <a href=”https://4.1″ target=”_blank”>4.1</a> LCD Display<br>
<br>
The suggested length is 10 to 14 pages. The appendix does not count towards the page length.<br>
<br>
<br>
Introduction<br>
This is your opportunity to set your report in context.<br>
What is an embedded system?<br>
What is a microcontroller?<br>
What are the possible applications of your project?<br>
List a set of clear aims and objectives for your project.<br>
To get the best marks, you are expected to do further reading and not just rely on the lab notes.<br>
<br>
<br>
Hardware Description<br>
Present an overall system block diagram.<br>
Discuss each block in depth (use sub-sections).<br>
Include images of each block.<br>
Link the operation of each block to the underlying theory.<br>
To get the best marks, you are expected to do further reading and not just rely on the lab notes (<a href=”https://e.g” target=”_blank”>e.g</a>. how does the LCD interface work?).<br>
<br>
<br>
Software Description<br>
If you followed good software engineering practice, your code should be split into different functions.<br>
Present flowchart of the overall software flow.<br>
You should not create a flowchart that mirrors the code line-by-line, it is more of a general overview.<br>
If the flowchart is too simple, the reader would not be able implement the algorithm.<br>
If the flowchart is too complex, it can be difficult for the reader to follow. Find the right balance.<br>
Present flowcharts of each function. <br>
<br>
Results and Testing<br>
This corresponds to the technical merit of the project in the report rubric.<br>
<br>
Present the testing of the temperature logger.<br>
You can take images of the LCD screen using a camera demonstrating the functionality.<br>
To achieve the highest marks, you are required to implement original features – ensure these are discussed here to obtain credit for them.<br>
<br>
Conclusion<br>
Discuss each of the aims and objectives presented in the introduction.<br>
If you did not meet them, explain why.<br>
Discuss how you could expand the project in fututre.<br>
<br>
References<br>
Reference any resources you have used.<br>
Avoid the use of Wikipedia.<br>
Use IEEE referencing style. There are good examples on the University of York website.<br>
<br>
Appendix<br>
Paste your code into the appendix so that it can be run through Turnitin and checked for plagiarism/similarity with your classmates.<br>
<br>
Formatting<br>
Do not use colourful/jazzy Word templates. They look amateurish and detract from the technical content.<br>
Use sections and sub-sections to break the text up. Technical reports are not like essays. Section titles are normally bold and can be slightly larger font.<br>
Use a consistent size for your images. Ensure they are of sufficient resolution. This is especially important for images with text in.<br>
Create your own images, avoid copying from online. If you do, respect copyright and include a reference.<br>
Taking pictures of images on the monitor using your smartphone is terrible practice and makes the report look amateurish. Use screen-shots.<br>
If you take pictures of hardware, do it on a clear background (<a href=”https://e.g” target=”_blank”>e.g</a>. white paper) and clip as much as the background out as possible. Pictures of PCB’s on a messy lab bench look awful in a report! <br>
Place images in between paragraphs. Do not embed them within paragraphs.<br>
Write in the passive voice.<br>
The multiplexer circuit was designed…<br>
<br>
Do not write in the first person<br>
I designed the multiplexer circuit…<br>
<br>
Include page numbers and a table of contents.<br>
Use consistent formatting. Do not jump between different fonts and font sizes within the body of the text (this usually happens when you cut-and-paste <a href=”https://i.e” target=”_blank”>i.e</a>. plagiarism!).<br>
Write in full sentences. Avoid informal language.<br>
The first time you use an abbreviation, you should include the expanded form <a href=”https://e.g” target=”_blank”>e.g</a>. SPI (Serial Peripheral Information).<br>
Write clearly. I appreciate that English may not be your first language, but you are studying at an English-speaking University. If an explanation does not make sense, it detracts from the technical content. <br>
For students who are registered with DSAS, your work is marked for content only.<br>
<br>
Please you need to do the last WEEK#10 because i didn’t finish it , it will be next Tuesday our last lab of WEEK#10 , so you can do the experiment.

Virus Paper