Students may work on this assignment in their assigned, randomly selected groups of two. Alternatively, self-selecting pairs of such groups of two may join forces to form a gang of four.
The Assignment
Requirements- Each team must select a unique parent company name to be associated with the team's franchises. All names should be appropriate.
- Each team must submit one Java class and a set of five statements.
Each of the five statements must construct an instance of the submitted class using the
newkeyword. Each object created must have a unique business name and be associated with the team's parent company. - The class submitted must extend the version of the abstract
ApplePackerclass that was posted at the following URL as of 11 AM on Wednesday, 28 February 2018.http://scribbledecobble.blogspot.com/2018/02/them-apples.html
As of 11 AM on 28 February 2018, the code referenced by the URL above is frozen with the following exceptions:
- Critical bugs may be fixed.
- Additional code may be added to combine category scores into overall scores for each competing parent company.
- Changes may be made after the due date for the assignment has passed.
Cite all of your sources, including the names of all individuals who make any non-trivial contributions. Briefly describe the contributions of each individual on the team as well as any individuals outside the team. Embed your citations in a Javadoc comment that accompanies the class you submit. Do not give the impression that you are claiming credit for work that someone else did.
Events and Medals
Each team of franchises will compete in several events. Medals (gold, silver, and bronze) will be awarded to the top three franchises or parent companies (teams of franchises) in the following events:- PACK TIME Competition
- AVG AGE Competition
- WGT EFFICIENCY Competition
- VAL EFFICIENCY Competition
- VOL EFFICIENCY Compeition
- OVERALL Compeition
Grading
Failure to cite your sources may result in a zero.
Was: Failure to turn in the required code on time for either Part 1 or Part 2 of the assignment will result in a grade of minus minus (--). Revised (12 March): Since several teams missed the deadline, failure to turn in the required code for Part 2 on time resulted in the code turned in for Part 1 being used instead.
Everyone in a group (of two or four) will receive the same grade for this assignment. Collaboration is strongly encouraged, but if one person does all the work, then so be it. It’s your team, and sometimes that’s how the cookie crumbles.
Grades will be based on a) the performance of your ApplePacker class relative to the performance of other ApplePacker classes
and b) whether you followed all of the assignment instructions. Grades will be awarded as follows:
| Mark | Criterial | - / -- | Any team that does not submit a working ApplePacker class may receive a - or lower. |
|---|---|
| ✓- | Any team that does not enter a collection of franchises with an original packing strategy may receive a ✓- or lower. |
| ✓ | Any team that follows all of the instructions and enters a collection of franchises with an original packing strategy will receive a check or higher. |
| ✓+ | Any team that follows all of the instructions and has a franchise or a parent company that receives a gold, silver, or bronze medal in any category will receive a ✓+ or higher. |
| + | Any team follows all of the instructions and has a franchise or a parent company that receives a gold medal in any category or a parent company that receives a gold or silver medal in the overall competition will receive a + or higher. |
| ++ | Any team that follows all of the instructions and has the highest total medal count will receive a ++. (Note: Mr. Spurgeon will participate in the competition using franchises belonging to his own parent company.) |
Due Dates - The due dates for this project are firm. No extensions will be given.
Part 1
Due: 8:30 AM - Tuesday, 6 March 2018
A preliminary (working!) version of your team's class and the final set of statements that construct five instances of your class must be submitted to Mr. Spurgeon via email no later than 8:30 AM on Tuesday, 6 March 2018. Make sure your class includes a Javadoc comment. Your Javadoc comment should describe your packing strategy and include citations. Neither your preliminary code nor your preliminary comments will be shared with other teams. One person from your team should send your team's code and comments to jspurgeon@vcstudent.org with the subject: Programming Assignment 10 - part 1.
Part 2
Due: 8:30 AM - Monday, 12 March 2018
The final version of your team's class must be submitted to Mr. Spurgeon via email no later than 8:30 AM on Monday, 12 March 2018. Make sure your class includes a Javadoc comment. Your Javadoc comment should describe your packing strategy and include citations. Once all submissions have been received, your team's source code and comments may be shared with other teams. One person from your team should send your team's code and comments to jspurgeon@vcstudent.org with the subject: Programming Assignment 10 - part 2.
