ENGINEERING PROCESS
Each team works through the processes below. Individual team members be responsible for specific engineering elements each project cycle.
RESEARCH
- Identify problem
- Research current solutions
- Understand requirements
- Brainstorm solutions
- Develop concept prototypes
PLAN
- Outline strategy
- Identify specifications
- Develop schedule
PROTOTYPE
- Build working prototype
- Conduct design reviews
TEST
- Iteratively improve
- Revise, etc.
PROJECT RESPONSIBLITIES
and PRODUCT RUBRIC
SOFTWARE ENGINEER
Identify problem, research current solutions, understand requirements, brainstorm solutions, develop concept prototypes and complete the software program, while making written comments in the software for that unit or section.
Points | 4 – Advanced | 3 – Proficient | 2 – Basic | 1 – Below Basic | 0 |
Daily Tasks | On task from bell to bell and communicates and works well with team | On task most of the class and communicates and works well with team | On task most of the class and / or does not communicate or work well with team | Observed off task numerous times and / or does not communicate well with team | Absent or off task |
Teamwork | Helped other team members solve the problems they faced while successfully completing their own | Worked well with team members, was pleasant and helpful, listened well and shared the responsibilities while successfully completing own tasks | Although there was disagreement the student completed the project | Had difficulty working with team members and the instructor had to manage the teams behavior | Absent or did not contribute to a positive working atmosphere |
Product | Program runs successfully with detailed comments that make the code easy to understand
Uses smallest amount of memory used to accomplish the task – use of loops, My Blocks , etc. |
Program runs successfully, some comments are included
Program efficiency attempted: Some use of loops, My Blocks , etc. |
Program runs successfully without comments
No efficiency in programming attempted |
Program runs partially | Program doesn’t run |
HARDWARE ENGINEER
Build working prototype, conduct design reviews and complete modifications, as necessary, for that unit or section.
Points | 4 – Advanced | 3 – Proficient | 2 – Basic | 1 – Below Basic | 0 |
Daily Tasks | On task from bell to bell and communicates and works well with team | On task most of the class and communicates and works well with team | On task most of the class and / or does not communicate or work well with team | Observed off task numerous times and / or does not communicate well with team | Absent or off task |
Teamwork | Helped other team members solve the problems they faced while successfully completing their own | Worked well with team members, was pleasant and helpful, listened well and shared the responsibilities while successfully completing own tasks | Although there was disagreement the student completed the project | Had difficulty working with team members and the instructor had to manage the teams behavior | Absent or did not contribute to a positive working atmosphere |
Product | Great care taken in construction process so that the robot is neat, robust, attractive and the electrical components are attached accurately.
Takes a licking and keeps on ticking, repeatable performance, doesn’t require tweaking between runs, doesn’t introduce unwanted friction or imbalance, etc. |
Construction was careful and accurate for the most part, but 1-2 details could have been refined for a more robust and attractive product.
One or two repeated performances, doesn’t require tweaking between runs |
Construction accurately followed the plans, but 3-4 details could have been refined for a robust and more attractive product. | Construction appears careless or haphazard. Many details need refinement for a robust or attractive robot. | Nothing constructed |
PROJECT MANAGER
Outline strategy and plan, identify specifications, develop schedule of who does what when, assist team members as needed and take daily notes detailing group work.
Points | 4 – Advanced | 3 – Proficient | 2 – Basic | 1 – Below Basic | 0 |
Daily Tasks | On task from bell to bell and communicates and works well with team | On task most of the class and communicates and works well with team | On task most of the class and / or does not communicate or work well with team | Observed off task numerous times and / or does not communicate well with team | Absent or off task |
Teamwork | Helped other team members solve the problems they faced while successfully completing their own | Worked well with team members, was pleasant and helpful, listened well and shared the responsibilities while successfully completing own tasks | Although there was disagreement the student completed the project | Had difficulty working with team members and the instructor had to manage the teams behavior | Absent or did not contribute to a positive working atmosphere |
Product | Successfully and consistently complete all elements:
|
Successfully and semi-consistently complete most elements:
|
With some success and semi-consistently completed most elements:
|
Little or no leadership observed and / or no written work completed | No leadership observed |
GROUP RUBRIC
4 – Advanced | 3 – Proficient | 2 – Basic | 1 – Below Basic | 0 |
Everyone does job, robot runs great The Project is not only completed but shows extensive effort and multiple levels of complexity. All participants were heavily involved | A few people do the job, robot runs good A project is completed that shows considerable effort and involved all participants and is ready to present on time |
Only one person is working, everyone else slacking; no robot present. Subjects are not on task and have partially completed or shows little effort or no work at all. |
Everyone leaning on a shovel | Negative toward other groups / poor sportsmanship |
PROJECT (BKM) REPORT RUBRIC
Points | 4 – Advanced | 3 – Proficient | 2 – Basic | 1 – Below Basic | 0 |
Data Analysis / Engineering Method | Make reasonable predictions based on prior knowledge
Correctly gather and record all data |
Make predictions based on prior knowledge
Correctly gather and record most data |
Predictions are irrational and not based on prior knowledge
Correctly gather and record some data |
No predictions made
Data is not gathered or recorded correctly |
|
Writing an Analytical Paragraph | Paragraph includes:
A topic statement accurately presenting information. A detailed explanation of how the results of the engineering method/process (brainstorming, research, prototypes, spec’s, schedule, design iterations, etc.) |
Paragraph includes:
A topic statement semi-accurately presenting information. A partially detailed explanation of how the results of the engineering method/process (brainstorming, research, prototypes, spec’s, schedule, design iterations, etc.) |
Paragraph includes:
A topic statement semi-accurately presenting information. Little detailed explained |
Partial paragraph with incomplete material | |
Summary | Student uses only 1-3 sentences to describe clearly what was learned | Student uses several sentences to accurately describe what was learned | Student summarizes some of what was learned in a sentence or two, though it is not very clear what was learned | Student has great difficulty summarizing what was learned | |
Observation | Clear, accurate, dated notes are cited regularly | Dated, clear, accurate notes are cited occasionally | Dated, notes are cited occasionally, but accuracy of notes might be questionable | Notes rarely cited or of little use | |
Reflection | Properly reflects on accuracy or inaccuracies of previous inferences | Makes some reflections on accuracy or inaccuracies of previous inferences | Minimally and/or incorrectly reflects on previous inferences | Does not make reference to previous inferences | |
Vocabulary | Exhibits skillful use of vocabulary that is precise and purposeful | Exhibits reasonable use of vocabulary that is precise and purposeful | Exhibits minimal use of vocabulary that is precise and purposeful | Lacks use of vocabulary that is precise and purposeful | |
Grammar / Spelling | 0-1 errors; complete sentences; correct tenses;good word order; agreement for capitalization and punctuation
0 spelling errors |
2-3 errors; mostly complete sentences; mostly correct tenses; good word order; agreement for capitalization and punctuation
1-2 spelling errors |
4-5 errors; some complete sentences; frequent errors in tense; word order questionable; mostly agreement for capitalization and punctuation
3-4 spelling errors |
6+ errors; weak sentences; many tense errors; poor word order; poor agreement for capital letters and punctuation
5+ spelling errors |
|
BKM / Take-aways and Connections | Captures salient points in concise and accessible language | Captures some salient points in nearly-concise and mostly accessible language | Attempt made to capture salient points but language is not very concise and nor accessible | Unsuccessful attempt made to capture salient points and language is not very concise and nor accessible |