Shorr 22-23 PLTW EDD-Per 5 Assignments
- Instructor
- Mr. Garrett Shorr
- Term
- 2022-2023 School Year
- Department
- Mathematics
- Description
-
Upcoming Assignments
No upcoming assignments.
Past Assignments
Due:
Presentation Length: 8 to 10 minutes
Topics to cover with suggested timing:
Brief reminder of what the problem was (30 seconds)
Demo of your product and how it meets your customer requirements (4-6 mins)
Description of build process (1-2 mins)
Sample test framework (1-2 mins)
Reflection on what you would have done differently and/or what you would iterate next. What are you most proud of from this year? (1-2 mins)
Reflections Topics:
Elements A-C: Research
How were you successful in this phase? What pitfalls did you fall into? What would you have done differently knowing what you know now? Include any issues regarding time management, group size and dynamics, or anything else that might help next year's students avoid problems you may have had.
Elements D-F: Design
What did you find most difficult about this section?
What took up too much time and how would you avoid that if you had to do it again?
Was your design detailed enough when you started your build phase or did you have to do a lot more design while building?
Elements G-I: Build & Testing
Discuss the time management of the research and design phases and what impact it had on your build and testing phases. Did your expectations for how long each part of the build & test phase would take match up with reality? Discuss any other things you wish you had known prior to starting elements G-I.
Elements
Submissions:
Your presentation slides
A group reflection on what you would have done differently if you could do it all over again for elements A-C (research), elements D-F (design), ands element G-I (build & testing). Also, what are you most proud of from this year?
Topics to cover with suggested timing:
Brief reminder of what the problem was (30 seconds)
Demo of your product and how it meets your customer requirements (4-6 mins)
Description of build process (1-2 mins)
Sample test framework (1-2 mins)
Reflection on what you would have done differently and/or what you would iterate next. What are you most proud of from this year? (1-2 mins)
Reflections Topics:
Elements A-C: Research
How were you successful in this phase? What pitfalls did you fall into? What would you have done differently knowing what you know now? Include any issues regarding time management, group size and dynamics, or anything else that might help next year's students avoid problems you may have had.
Elements D-F: Design
What did you find most difficult about this section?
What took up too much time and how would you avoid that if you had to do it again?
Was your design detailed enough when you started your build phase or did you have to do a lot more design while building?
Elements G-I: Build & Testing
Discuss the time management of the research and design phases and what impact it had on your build and testing phases. Did your expectations for how long each part of the build & test phase would take match up with reality? Discuss any other things you wish you had known prior to starting elements G-I.
Elements
Submissions:
Your presentation slides
A group reflection on what you would have done differently if you could do it all over again for elements A-C (research), elements D-F (design), ands element G-I (build & testing). Also, what are you most proud of from this year?
Due:
Be prepared to do the following when guests arrive at your station:
Present your problem statement
Describe your customer requirements
Describe how you built your project
Describe what tests you were able to complete and their results, along with how you would complete the other tests given your time and resources.
Describe how you would proceed with a revised version of the project, or if you think a different approach or other existing solutions might simply be better.
It is okay that if your result is that you wouldn't pursue this further. The process is what's important, and the process can sometimes lead to something that doesn't work in the end.
Present your problem statement
Describe your customer requirements
Describe how you built your project
Describe what tests you were able to complete and their results, along with how you would complete the other tests given your time and resources.
Describe how you would proceed with a revised version of the project, or if you think a different approach or other existing solutions might simply be better.
It is okay that if your result is that you wouldn't pursue this further. The process is what's important, and the process can sometimes lead to something that doesn't work in the end.
Due:
Range of dates covered:
3-22 to 5-8
Make sure your notebooks are up to date and ready to go at the start of class Wednesday 5-10.
3-22 to 5-8
Make sure your notebooks are up to date and ready to go at the start of class Wednesday 5-10.
Due:
Element H - Testing plans
Number your tests so that you can refer to them again in the Element I section.
Test plans should cover the extent of your customer requirements from element C
Tests that you may not be able to actually perform (such as larger surveys, lack of materials, or time constraints) should still be included.
Follow the format from the sample test post for each. The instructions should be clear such that someone unfamiliar with the project would be able to read them and follow them.
Element I - Testing
For the tests you are able to complete, describe the results of the tests, including any data (qualitative or quantitative) you took. Include any pictures you took during the process and explain whether it met your passing criteria, and why.
Make sure you refer to the tests by the numbers you set in Element H.
Number your tests so that you can refer to them again in the Element I section.
Test plans should cover the extent of your customer requirements from element C
Tests that you may not be able to actually perform (such as larger surveys, lack of materials, or time constraints) should still be included.
Follow the format from the sample test post for each. The instructions should be clear such that someone unfamiliar with the project would be able to read them and follow them.
Element I - Testing
For the tests you are able to complete, describe the results of the tests, including any data (qualitative or quantitative) you took. Include any pictures you took during the process and explain whether it met your passing criteria, and why.
Make sure you refer to the tests by the numbers you set in Element H.
Due:
A narrative, chronological description of your build phase, including pictures, screenshots, etc. Include dead ends, redesigns, and other obstacles you had to overcome.
Due:
Range of dates covered:
2-23-3-20
Make sure your notebooks are up to date and ready to go at the start of class Wednesday 3-22.
2-23-3-20
Make sure your notebooks are up to date and ready to go at the start of class Wednesday 3-22.
Due:
Submit a screenshot (one per group) of your current, up to date, planning board (either the Gantt Chart or Github Project Board).
Due:
Range of dates covered:
1/26 - 2/21
Make sure your notebooks are up to date and ready to go at the start of class Thursday 2/23.
1/26 - 2/21
Make sure your notebooks are up to date and ready to go at the start of class Thursday 2/23.
Due:
Submit a screenshot (one per group) of your current, up to date, planning board (either the Gantt Chart or Github Project Board).
Due:
Range of dates covered:
1/9 - 1/24
Make sure your notebooks are up to date and ready to go at the start of class Thursday 1/26.
1/9 - 1/24
Make sure your notebooks are up to date and ready to go at the start of class Thursday 1/26.
Due:
Submit a screenshot (one per group) of your current, up to date, planning board (either the Gantt Chart or Github Project Board).
Can be submitted as early as today (1/20) if you do have some stuff alright up there.
Can be submitted as early as today (1/20) if you do have some stuff alright up there.
Due:
This is to be in a single google doc that can be joined with the other elements of your portfolio.
Element D Section
Screenshots or photos of your groups preliminary designs with one sentence descriptions for each
The more detailed designs you narrowed down for the presentations including the following for each: a visual, description of the design and how it works, what technology is used and materials it would be made of, and how it would address your customer requirements
decision matrix like you did with the prior solutions but include your solutions
explain the result of the matrix as well as why you chose various 1, 3, 9 values
Element F Section
1. If your highest rated design is viable, explain why you think you have the means, skills, technology, and materials to build it.
2. If not, explain why it isn't viable.
Drop down to the next highest rated design and repeat those two steps above until you have something you will build in element G.
Soft deadline is Wednesday, January 18th.
Element D Section
Screenshots or photos of your groups preliminary designs with one sentence descriptions for each
The more detailed designs you narrowed down for the presentations including the following for each: a visual, description of the design and how it works, what technology is used and materials it would be made of, and how it would address your customer requirements
decision matrix like you did with the prior solutions but include your solutions
explain the result of the matrix as well as why you chose various 1, 3, 9 values
Element F Section
1. If your highest rated design is viable, explain why you think you have the means, skills, technology, and materials to build it.
2. If not, explain why it isn't viable.
Drop down to the next highest rated design and repeat those two steps above until you have something you will build in element G.
Soft deadline is Wednesday, January 18th.
Due:
Everyone will give feedback to each group. Every students fills out 1 form per group (except for your own). Forms will be handed out in person and what that form looks like is attached.
1 minute for group introduction going over your business problem statement so the guests have an idea of what your problem is about before seeing your solutions.
Then, each member will have 2 to 3 minutes to describe 1 product concept each and address these topics:
General description of the solution with a sketch or other visual to accompany
Explanation of the technology and working principles
Justification -- Concise description of how the
product satisfies customer needs and the specifications
While others are presenting, you will be filling out forms to help give feedback to other groups.
Group Order:
1. Campus Litter
2. Gun Violence in Schools Awareness
3. Newbie Lifting Bad Technique
4. Ill-fitting Shoes
5. Static Electricity
6. Unsanitary Keyboards
7. Better Dishracks
1 minute for group introduction going over your business problem statement so the guests have an idea of what your problem is about before seeing your solutions.
Then, each member will have 2 to 3 minutes to describe 1 product concept each and address these topics:
General description of the solution with a sketch or other visual to accompany
Explanation of the technology and working principles
Justification -- Concise description of how the
product satisfies customer needs and the specifications
While others are presenting, you will be filling out forms to help give feedback to other groups.
Group Order:
1. Campus Litter
2. Gun Violence in Schools Awareness
3. Newbie Lifting Bad Technique
4. Ill-fitting Shoes
5. Static Electricity
6. Unsanitary Keyboards
7. Better Dishracks
Due:
Range of dates covered:
10/16-12/8
Make sure your notebooks are up to date and ready to go at the start of class Monday 12/12.
10/16-12/8
Make sure your notebooks are up to date and ready to go at the start of class Monday 12/12.
Due:
Due end of class Tue 11/15
Requirements:
List of customer requirements with explanation of how each was derived from the pros and cons. Should have coverage of the Eight Fundamental Design Criteria from the Element C powerpoint.
List of product specifications (concrete, measurable) with an explanation for why those metrics were chosen.
Similar Solution Matrix consisting of your Element B solutions judged against your customer requirements using a 1-3-9 scale. 1 = doesn't meet requirement. 3 = meets requirement. 9 = exceeds requirements. Should have some brief explanation about why the various solutions received the scores they did.
On the importance of the research phase so you really understand the problem before starting the design phase: https://www.ted.com/talks/timothy_prestero_design_for_people_not_awards/transcript?language=en
Requirements:
List of customer requirements with explanation of how each was derived from the pros and cons. Should have coverage of the Eight Fundamental Design Criteria from the Element C powerpoint.
List of product specifications (concrete, measurable) with an explanation for why those metrics were chosen.
Similar Solution Matrix consisting of your Element B solutions judged against your customer requirements using a 1-3-9 scale. 1 = doesn't meet requirement. 3 = meets requirement. 9 = exceeds requirements. Should have some brief explanation about why the various solutions received the scores they did.
On the importance of the research phase so you really understand the problem before starting the design phase: https://www.ted.com/talks/timothy_prestero_design_for_people_not_awards/transcript?language=en
Due:
Just heard back from LA Public Works. They are free on Thursday 11/3 and will be joining us on Google Meet. We'll talk about what's in the presentations on Wednesday.
These are the questions I have sent to the engineers ahead of time as the lenses to look at your presentations through.
Did they describe a real problem and adequately justify its existence?
Do their customer requirements follow from their research into prior and existing solutions?
Are their product specifications concrete, measurable, and are they supported by their research?
Will those product specifications be able to adequately guide their design of a solution to the problem?
Presentation ideal max timing in minutes:
3.5 element A
Engineering problem statement
Your top 2 or 3 best sources of evidence to support the existence of said problem.
2 element B
- Briefly describe a few of the existing solutions you saw, also highlighting the breadth of the solutions you looked at
talk about the general trends of pros and cons
3.5 element C
go through the customer requirements and product specs
explain what it means to meet, fail to meet, or exceed each spec.
Make a google slides deck and follow the good practices of presentations that we talked about before (no walls of text, etc).
These are the questions I have sent to the engineers ahead of time as the lenses to look at your presentations through.
Did they describe a real problem and adequately justify its existence?
Do their customer requirements follow from their research into prior and existing solutions?
Are their product specifications concrete, measurable, and are they supported by their research?
Will those product specifications be able to adequately guide their design of a solution to the problem?
Presentation ideal max timing in minutes:
3.5 element A
Engineering problem statement
Your top 2 or 3 best sources of evidence to support the existence of said problem.
2 element B
- Briefly describe a few of the existing solutions you saw, also highlighting the breadth of the solutions you looked at
talk about the general trends of pros and cons
3.5 element C
go through the customer requirements and product specs
explain what it means to meet, fail to meet, or exceed each spec.
Make a google slides deck and follow the good practices of presentations that we talked about before (no walls of text, etc).
Due:
Range of dates covered:
9/21 - 10/14
Make sure your notebooks are up to date and ready to go at the start of class 9/19.
9/21 - 10/14
Make sure your notebooks are up to date and ready to go at the start of class 9/19.
Due:
Range of dates covered:
8/27 - 9/19
Make sure your notebooks are up to date and ready to go at the start of class 9/19.
8/27 - 9/19
Make sure your notebooks are up to date and ready to go at the start of class 9/19.
Due:
Due end class Friday 9/23
You'll make a single google doc for your project portfolio. I'll show you how to use headers and other styles to make generating a table of contents super easy.
This is general description for a 5 on Element A:
The problem is clearly and objectively identified and defined with considerable
depth, and it is well elaborated with specific detail; the justification of
the problem highlights the concerns of many primary stakeholders and is based on comprehensive,
timely, and consistently credible sources; it offers consistently objective
detail from which multiple measurable design requirements can be determined.
Scored Examples are attached.
The 5 is more like a 6 with its thoroughness and more like a 3 or 4 with its problem statement including solutions in it and including personal motivations for pursuing the problem. Take cues from this about how to make a nice organization and structure, as well as including diagrams. Otherwise, absolutely no need for you to write anything this long.
The 4 is more like a 3. It's got some thorough-enough information but it's organized pretty poorly. If you took the same info and organized it similar to the 5, it would be a very solid 4. And with a little more detail in the problem statement, it would be a 5.
The 3 is barely a 3...more 2ish...because the organization and terrible fonts and squished appearance in places.
Probably don't bother looking at the 2 to 0, but they are there just in case you are super curious.
Summary: Start with your problem statement and then spend a couple paragraphs elaborating on it. Support your problem statement with lines of evidence and cite all your sources. Do so in narrative form.
You'll make a single google doc for your project portfolio. I'll show you how to use headers and other styles to make generating a table of contents super easy.
This is general description for a 5 on Element A:
The problem is clearly and objectively identified and defined with considerable
depth, and it is well elaborated with specific detail; the justification of
the problem highlights the concerns of many primary stakeholders and is based on comprehensive,
timely, and consistently credible sources; it offers consistently objective
detail from which multiple measurable design requirements can be determined.
Scored Examples are attached.
The 5 is more like a 6 with its thoroughness and more like a 3 or 4 with its problem statement including solutions in it and including personal motivations for pursuing the problem. Take cues from this about how to make a nice organization and structure, as well as including diagrams. Otherwise, absolutely no need for you to write anything this long.
The 4 is more like a 3. It's got some thorough-enough information but it's organized pretty poorly. If you took the same info and organized it similar to the 5, it would be a very solid 4. And with a little more detail in the problem statement, it would be a 5.
The 3 is barely a 3...more 2ish...because the organization and terrible fonts and squished appearance in places.
Probably don't bother looking at the 2 to 0, but they are there just in case you are super curious.
Summary: Start with your problem statement and then spend a couple paragraphs elaborating on it. Support your problem statement with lines of evidence and cite all your sources. Do so in narrative form.
Due:
Estimated Date: Sep 13. More details about making a good slideshow will be discussed as we get closer to this date.
You'll be presenting your problem statement to the class along with at least 3 lines of supporting evidence.
Each group will have 5 minutes to present and there will be 3 minutes for questions.
Each member should speak.
A google slides would be helpful, but it doesn't have to be elaborate. Five or six slides will do:
Slide 1: Group Name and Team Member Names (group name doesn't have to be what I called you--you get to choose your own)
Slide 2: Problem Statement. This will be the only wall of text allowed in a presentation.
Slide 3: Supporting Evidence #1: use bullet points and only write the key ideas. Do not read word for word from the slide.
Slide 4: Supporting Evidence #2: use bullet points and only write the key ideas. Do not read word for word from the slide.
Slide 5: Supporting Evidence #3: use bullet points and only write the key ideas. Do not read word for word from the slide.
(and if you have more than 3 solid pieces of evidence, continue the above pattern for the rest)
Submit your google slides--Only 1 per group.
You'll be presenting your problem statement to the class along with at least 3 lines of supporting evidence.
Each group will have 5 minutes to present and there will be 3 minutes for questions.
Each member should speak.
A google slides would be helpful, but it doesn't have to be elaborate. Five or six slides will do:
Slide 1: Group Name and Team Member Names (group name doesn't have to be what I called you--you get to choose your own)
Slide 2: Problem Statement. This will be the only wall of text allowed in a presentation.
Slide 3: Supporting Evidence #1: use bullet points and only write the key ideas. Do not read word for word from the slide.
Slide 4: Supporting Evidence #2: use bullet points and only write the key ideas. Do not read word for word from the slide.
Slide 5: Supporting Evidence #3: use bullet points and only write the key ideas. Do not read word for word from the slide.
(and if you have more than 3 solid pieces of evidence, continue the above pattern for the rest)
Submit your google slides--Only 1 per group.
Due:
Range of dates covered:
8/11 - 8/23
Submit a google doc with self-grading of each category and a reflection on what you need to do to improve for next time.
8/11 - 8/23
Submit a google doc with self-grading of each category and a reflection on what you need to do to improve for next time.
Due:
Have one person per group respond to this and list your group members and tentative topic(s) you shared interest in.
Group Norms should at least address:
timeliness and responsibility
fair division of labor
conflict resolution
modes of communication
handling absences
general attitudes
Possible numbers of groups:
5x3 2x2 (or 1x4)
3x3 5x2 (or 3x2 1x4)
1x3 6x2 1x4
Group Norms should at least address:
timeliness and responsibility
fair division of labor
conflict resolution
modes of communication
handling absences
general attitudes
Possible numbers of groups:
5x3 2x2 (or 1x4)
3x3 5x2 (or 3x2 1x4)
1x3 6x2 1x4
Due:
Please bring back the signed back page of the syllabus next class.
Due:
https://docs.google.com/presentation/d/1XiPXT585xXThhYXGMDIeODzCoRNCuzyXLLSfbxHuzk4/edit?usp=sharing
We want to do these presentations the second half of class on Friday.
Edit *ONLY* your 3 slides with your favorite 3 problems from your brainstorming (you must be logged onto your school email account to access and edit the slides)
We want to do these presentations the second half of class on Friday.
Edit *ONLY* your 3 slides with your favorite 3 problems from your brainstorming (you must be logged onto your school email account to access and edit the slides)