You will implement the basic functionality of your prototype. To guide your group plan and organize your work you will be asked to submit a list of features you are planning to implement.
Build on the implementation plan you submitted last week, and create a rank-ordered list of features you want to
implement in your application. Your list should reflect the entire completion of your application, from start to finish. Think about what functionality is most important, and how to divide your features
into good size chunks. Indicate when you plan to be done with each chunk and who is responsible for what. Give your most basic functionality (things your application simply could not work without) high priority. Some examples for what a "good size" feature chunk might be for a haiku generator are: "Create new haiku", "add soundtrack to haiku", or "post haiku online". Pay attention when defining your functionality chunks, it should be something that is concrete so we can assess if it has been completed or not.
Remember to include the features that you already have implemented in your list. Please indicate what has already been implemented. The list you submit will be part of the grading for the "functional prototype" assignment, where one rubric axis will be how much of the list you completed. In the feedback you get for this weeks assignment the TAs will indicate how much you will be expected to complete to reach a certain grade.
| Grading Dimension | Guiding questions | Bare minimum | Satisfactory effort & performance | Above & Beyond |
| Progress (10 points) |
How much of your functionality list have you implemented so far? | (0-5) Little implementation started or only trivial functionality from list implemented. | (6-8) Good progress, some basic functionality implemented. | (9-10) Most important functionality implemented. Project is in good shape to iterate on, and stable enough to start adding functionality further down the list. |
| Clarity of list (10 points) |
Is the list divided into good size implementation chunks? Does your rank-ordering make sense? Is it clear how long each item on the list is expected to take and who is responsible for making it happen? | (0-5) Chunks are too big or too small to provide a way of assessing actual progress. | (6-8) Chunks are of good size and will help implementation planning. Rank-ordering show that thought has been given to what is most important and follows a logical implementation order. Responsibilities are clear. | (9-10) Chunk size and rank-ordering show insightful planning of project. Organization of list and distribution of responsibilities help make development effective. Timeline is feasible and ensures that application will have full functionality in time for user testing. |