Assignment 5: Word Game Part 2: Addictive Word Game
Points
These categories and point assignments are subject to change, but they should give you general sense of what we are looking for. Crashes will be reported to your Google Play development console, when possible, and some comments will be entered directly in BitBucket.
| Named properly (NUMAD15S-[YourFirstName][YourLastName]) | No extra app icons show up on launcher | Game added to prior assignment, all parts of which are still available | Activity is titled "Word Game" | Game starts up quickly (even after a full shutdown) | Scoring works as described | Rack of letters clearly shown | Click or vibration when letter selected | Clear how to select a word, and easy to do it | Good feedback when a word is detected | Board adjusts properly when a word is chosen | Board letter selection appears properly biased on Scrabble letter distribution | Words fade correctly, according to WordFade description | Visual or audio indicator for the last few seconds when word is about to fully fade out | Pause game works (and blocks board from view) | Resume button is not visible when there is no current game | Instructions and rules are easy to understand and concise so that someone who never played before can quickly start (2 = built into the game play or structured as a tutorial, 1 = instructions included and cleanly formated, 0 = no instructions or sloppy) | Plays music (different from Sodoku) and there is an option to turn it off | Split button availalble (when split is possible) | Dump button is availabe (when dump is possible) | Quit button is available | Acknowledgements screen included, well formated, and provides enough detail to understand what was used that the student didn't create from scratch | Nothing breaks when phone is rotated | Nothing breaks when Internet is not available | Formatting (buttons, graphics, text, bullet points) not sloppy (2) (2 = perfect, 1 = could use even small improvement, 0 = needs improvement) | No typos anywhere in app (0 or 2) | On the Play Store as alpha release (not full release) | Bug free (e.g., no crashes) | No timing issues that impact overall impressions (0 = broken, 1 = sluggish, 2 = snappy) | Source code on Bitbucket | Git code appears to have only needed files | Git code is well organized with logical package names | Git res directory code is well organized with clear naming convention | Git code shows appropriate, incremental commits on Bitbucket | Issue tracker being used incrementally and appropriately | Total points | Submitted at time of check? (Y/N) | Any special bells and whistles? (Impacts adjusted grade) | Note problems for feedback (but these should be entered in the Bitbucket issue tracker too) | Adjusted grade | |
| Possible points | 1 | 1 | 1 | 1 | 1 | 3 | 2 | 1 | 1 | 1 | 2 | 2 | 3 | 2 | 1 | 1 | 2 | 1 | 2 | 2 | 1 | 3 | 1 | 1 | 2 | 2 | 1 | 5 | 2 | 1 | 1 | 1 | 1 | 2 | 2 | 57 |