Iteration 6: It's in Beta
Due on December 19th at 11:59 PM.
The master branches of your group’s repository and wiki will be pulled at that time and its contents will be graded. Be sure that all materials – documentation, code, build instructions, etc. – are available in that repository. If some materials cannot be placed in that repository, contact your instructor for instructions on how to compensate.
Please be sure to follow appropriate etiquette when interacting with your group.
Overview
The goal for this iteration is to get all of your core features to work well enough for an end user to use. We don’t have enough time in the semester to catch every bug, but the core part of the application should work smoothly and your feature set should be complete. This may or may not be practical depending upon how your iterations have gone so far and grading focused upon progress rather than position. This is your final project submission for the course, though, and it should reflect the culmination of your project work.
Note that the due date is after the end of the semester. You are not expected to work more on this iteration. The amount of effort you are expected to commit is the same as the previous iterations in this course. As during-semester final exams, homeworks, and projects are quite common, this extended due date is intended to allow you flexibility in sorting out your schedule and that of your group. (Don’t spend all of finals period working on this project instead of studying!)
As with previous iterations, you must:
- Maintain good repository discipline. (Don’t break the build!) Keep things tidy, use branches if you’re working on large changes, and merge as often as you can to keep conflicts at a minimum.
- Keep a robust set of unit tests. As with the last iteration, you will be evaluated on code coverage and test quality.
- Ensure that the build and deployment processes are as simple as possible. Build should be automated via Maven or Gradle. Deployment should be possible with a fixed set of resources (e.g. a database, an Android device, etc.) and through the adjustment of a few configuration files. Make sure you include build and deployment instructions as appropriate!
- Use the features of GitHub to your advantage. Continue creating issues for bugs. Use your project board or issue milestones to plan out your iteration.
- Observe design principles and use design patterns to solve the problems you’re facing!
Deliverables
Store the above materials in your GitHub repository. The code you would like graded should be on the master branch of your repository as of the due date.
Iteration Review
You are also required to submit an iteration review which assesses the work you and your peers completed and whether things are going well for you in class. This review is private; its content will not be shared without your consent. Click here to submit your Iteration 6 review.
It is in your interest to provide honest feedback, even if that feedback isn’t the most generous or positive; if there’s a problem, your instructor needs to know!