Hotspots: Admin Pages | Turn-in Site |
Current Links: Case Final Project Summer 2007
M6: The Death of the Milestone
M6 Requirements
- Implement Domain Objects
- Create SUnit tests to unit test your core Domain Objects (you do not need to write tests for trivial accessor/modifier methods or for gui-specific methods)
- The TA's will not type anything in the workspace except XXXAppModel open. Or TestRunner open. You have to have code written for them to test your application.
Criteria Breakdown:
- Wagon Configuration to start Simulation................................................05
- Wagon Move changes location and consumes supplies based on configuration............05
- Random Events occur occasionally during move..........................................10
- Simulation ends when appropriate..................................................05
- Simulation can be saved ......................................................................10
- Saved Simulation can be loaded ............................................................10
- Professions influence game (starting money and events)..............................10
- Items can be purchased in stores and inventory updated.............................05
- Wagon max weight constraint enforced.................................................05
- Wagon pace ..........................................05
- Rations .................................................05
- River Crossing ........................................05
- SUnit Tests ...........................................................................10
- Good Smalltalk comments, code and style....................................10
Goals
Goal 1:
We wanted to have everything working the day before our demo and we wanted to start as soon as possible.
Goal 2:
We wanted to make sure we got loading/saving done and functioning properly after everything else had been completed.
Goal 3:
We wanted our all necessary methods with our wagon to be completed first.
Goal 4:
We then wanted all methods associated with our events and landmarks to then be properly implemented.
Goal 5:
We then wanted to develop good SUnit tests to make sure all things were properly functioning.
Implementation of M6:
M6
What Worked and What Didn’t Work
• This was the longest milestone to complete. We strongly encourage that you complete this milestone in a timely manner. M6 is basically coding all aspects of your game outside of the gui. This includes loading/saving, events, initializing the game with all Landmarks, Persons, Items, and Wagon, etc. The most tedious part is doing the loading and saving. We recommend the Boss approach and Bob supplied a lot of information on using this in class resources.
• For completing the task we recommend you all do it together or in an ordered fashion where there are deadlines. Initially we picked and chose what we wanted to do. However, we found that when you pick and choose what you want to do without any deadlines it creates issues with merging in the repository. That is why we recommend you do this as either 1 single cohesive team or as individuals with deadlines to publish.
• SUNIT Testing is a major part of this milestone as well. If you have good test setup it will help you greatly in debugging trust us. We used our test and the debug feature to solve a lot of our problems in development.
Link to this Page
- Team SXSI last edited on 8 December 2008 at 10:37 pm by lawn-128-61-24-229.lawn.gatech.edu