Changes between Version 2 and Version 3 of Oct4Notes

Show
Ignore:
Timestamp:
10/05/2011 12:36:27 AM (3 years ago)
Author:
hwu
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Oct4Notes

    v2 v3  
    66'''What went right and what went wrong? Did you achieve the goals you had set out? What can you do to avoid similar problems in the future?''' 
    77 
     8We completed all deliverables on time. Stephen was sick during the weekend, so we didn't quite get to finish the make policy use case, which involves adding an intermediate step (capital glows). All other goals were completed despite a bit of assignment switching.  
     9 
     10Again, we are quite pleased with the progress on our prototype as we made overestimates for the amount of early work to be completed in order to maximize productivity. In fact, many extra subtasks and enhancements were implemented in the progress of completing other subtasks. This puts us at a position to split up the rest of alpha release use cases this week! This also allows us to refactor the code during the last weeks of alpha release to ensure that our design provides a good architectural structure for coding the beta release.   
    811 
    912'''How good were your predictions on how long the goals would take to achieve? ''' 
    1013 
    11  
     14Some of our predictions were a bit off this week. In particular, we realized that the class components was already completed from last week, and therefore didn't take time. Meters took around ~2 hours more than expected. However, we implemented enhancements for the meters also (delta value display) so this is reasonable.  
    1215 
    1316== Goal Plan for Prototype == 
    1417 
    15 Our prototype goal for this week is to have all B and C subtasks completed. See [wiki:Sept20Notes] for B/C subtask rationale. Note that we have combined two of the Play Game subtasks. These two subtasks came to be very similar after designing the UI. In addition, note that we will not implement the hover/click part of the tutorial for alpha release unless we have extra time. However, the rest of the tutorial will be implemented.  
     18Our prototype goal for this week is to have all B and C subtasks completed. See [wiki:Sept20Notes] for B/C subtask rationale. Note that we have combined two of the Play Game subtasks. These two subtasks came to be very similar after designing the UI. In addition, note that we will not implement the hover/click part of the tutorial for alpha release unless we have extra time. However, the rest of the tutorial will be implemented. Since all hover subtasks are similar we combined them into one task again. Note that the two uncompleted subtasks are very similar because "highlighting appropriate icons" is the only part that "apply generic policy" requires.  
    1619 
    1720We believe that this is a feasible plan because: 
    18   *  
     21  * The tutorial and goal screens will most likely take up the largest chunk of time. However we will implement this part of the game using the popup class. Thus the base code already exists and the art will be taken from the UI Design. 
     22  * The code for hover is already set up, so this part shouldn't take a long time.  
     23  * Enhancements are relatively simple and should be feasible to complete within this week 
     24   
    1925 
    2026Here is the modified and updated Subtask Table. Updated entries are bolded.  
     
    2329 ||Play Game    || create turn mechanism, button || A* || done || 1-2 hrs || 
    2430 ||             || '''add initial game instructions, tutorial''' || B || '''this week''' || ''' 4 hr''' || 
    25  ||             || include additional event dialogs || C || '''this week''' || 4-5 hrs || 
    2631 || Make Policy || write instructions in info box for implementing policy || A || done || 1 hr || 
    2732 ||             || highlight appropriate icons when choosing a policy || A || this week || 1 hr || 
     
    4550|| '''Deliverable''' || '''Due Date''' || '''Time Estimate''' || '''Priority'''  || '''Mainly Assigned to''' || '''Reasoning''' || 
    4651|| Management Plan Update || 10-4 || 2 hour || 1 || Helen || We discussed last week's progress and divided up work during this meeting. We still need to write up our goal plan, update the goal stack, do risk analysis, and write a progress report. This is important to set up this week's plan! || 
    47 || Architectural Design Review Package || 10-6 || 1 hour || 1 || Helen || || 
    48 || Design Review Use Cases|| 10-11 || 
    49 || Design Review Other Models|| 10-11 || 
    50 || Design Review Class Diagram|| 10-11 || 
    51 || Design Review Sequence Diagrams+Buildability+Extensibility|| 10-11 || 
    52 || Final UI Design || 10-11 || 30 min || Helen || || 
    53 || Test Plan: Main || 10-11 || 1 hour || Stephen || || 
    54 || Test Plan: Economic Model || 10-11 || Paul || || 
    55 || Prototype Update 10/11: B Tasks || 10-11 || Everyone || 
    56 || UC Make Policy: resource glow after policy button clicked || 10-11 || 
    57 || UC Play Game: Tutorial|| 10-11 ||  
    58 || UC Hover || 10-11 || 
    59 || Text Content || 10-11 || 
    60 || Model Enhancement || 10-11||  
     52|| Architectural Design Review Package || 10-6 || 1 hour || 1 || Helen || Most of the package is already put together from the last two weeks. Some more text to put the design parts in context are needed. Due Thursday for review, so high priority!|| 
     53|| Design Review Use Cases|| 10-11 || 1 hour || 2 || Helen || We split up the design review into four parts. Since we don't get the package until Thursday, this will be completed in the later part of the week.  || 
     54|| Design Review Other Models|| 10-11 || 1.5 hour || 2 || Colin || same as above || 
     55|| Design Review Class Diagram|| 10-11 || 2 hour || 2 || Stephen || same as above || 
     56|| Design Review Sequence Diagrams+Buildability+Extensibility|| 10-11 || 1.5 hour || 2 || Paul || same as above || 
     57|| Final UI Design || 10-11 || 30 min || 2 || Helen || There were not too many suggestions during the UI Test so far, so this should not take too long to complete. || 
     58|| Test Plan: Main || 10-11 || 1 hour || 2 || Stephen || The test plan should be fairly simple since our game only allows mouse interactions and can't really generate errors || 
     59|| Test Plan: Economic Model || 10-11 || 1 hour || 3 || Paul || An added part of the test plan to ensure that the model teaches economic concepts and cannot be abused || 
     60|| __Prototype Update 10/11: B and C Tasks__ || 10-11 || 8 hrs || 2 || Everyone || || 
     61|| UC Make Policy: resource glow after policy button clicked || 10-11 || 1 hour || 2.1 || Stephen || intermediate step in policy making process || 
     62|| UC Play Game: Tutorial|| 10-11 || 4 hour || 2.3 || Helen, Colin || Implement tutorial from UI design (not click/hover) || 
     63|| UC Hover || 10-11 || 1 hour || 2.2 || Helen || Since hover has been implemented throughout phase II, most of it is already done. All hover subtasks are similar so we grouped them together again || 
     64|| Text Content || 10-11 ||  1 hour ||2.4 || Colin || Make text content more fun for middle schoolers || 
     65|| Model Enhancement || 10-11||  1 hour ||2.5 || Paul || Add a consequence to having low consumer happiness so that players cannot abuse high taxes || 
    6166 
    6267 
     
    7176We are working both top down and bottom up to produce the alpha release. Given this fact, we are at risk of implementing code that violates design principles, because the design is still a work in progress. To minimize this risk, we constantly critique our design and apply what we've learned to the code. As we finalize our design, we can refactor to also improve the design of our code.  
    7277 
    73 Time is always a major risk, especially with the heavy work load of other classes. Similar to last week, we have designed our prototype goals to minimize risk. See [wiki: Sept20Notes]. In addition, we have designed our subtasks so that the amount of tasks is higher in the beginning of the phase than the end. Thus, if subtasks are not completed on time, they can be carried over to the next week, but will not result in a large number of goals that are impossible to finish during the week.  
     78Time is always a major risk, especially with the heavy work load of other classes. We can see that we are at very low risk of completing the alpha release. If we complete this week's subtasks we will have completed the core of alpha release, allowing us to have time to refactor the code, provide a good architectural structure, test, and possibly implement further use cases.