Hotspots: Admin Pages | Turn-in Site |
Current Links: Case Final Project Summer 2007
M6 - Domain Coding
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.
- 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
Our code:
m6.st
Recommendations:
- M6 takes great amount of time. Therefore, we advise you to start as early as possible
- A good strategy is assigning each class to a member(or ask them which class they prefer to code) and if one of your team members wants to change something in that class of which someone else is in charge of it, talk to them first, this avoids a lot of problem.
- Having a team of five members, it's good to have two people who are leading the team, who will keep track of how everyone is going in terms of the assignment, set up meeting times, know everyone personally so they would know the strengths and weaknesses of each team member. And based on their strengths suggest a given plan for them (telling them it would be better if they worked at a particular class, etc).
- SU Unit test are really good to test your classes so it would be better to use them for every method in your classes. Do it seperately so you do not get frustrated with MANY errors that may occur.
- You could also use the debugging button to find out where the error occurred. Do not worry if you have to add a new class or method.
Link to this Page