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 (NUMAD17S-[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) | Grids properly show letters | Game switches properly from phase 1 to phase 2 | Consistent, logical scoring scheme | 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 | Small boards are populated properly with 9-letter words | In Phase 1, letters cannot be reused when making words but in Phase 2 they can be (but not consecutively) | Phase 2 of game plays properly | Visual or audio indicator for the last few seconds when Phase 1 is about to end | Visual or audio indicator for the last few seconds when Phase 2 is about to end | 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 formatted, 0 = no instructions or sloppy) | Plays music (different from Ultimate Tic Tac Toe) and there is an option to turn it off | Provides some type of feedback about what what words are found | Does not allow the same word to be used twice | Quit button is available | Acknowledgements screen included, well formatted, 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 | 3 | 3 | 1 | 1 | 1 | 2 | 2 | 2 | 5 | 2 | 2 | 1 | 1 | 2 | 1 | 2 | 3 | 1 | 3 | 1 | 1 | 2 | 2 | 1 | 5 | 2 | 1 | 1 | 1 | 1 | 5 | 5 | 74 |