






Hotspots: Admin Pages | Turn-in Site |
Current Links: Case Final Project Summer 2007
M6 -- Domain Implementation
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)
Comments
- Meeting 3 times to get this done before the due date, and then meeting again after we submitted it to work out the kinks. The beauty of this class is that you can submit code that isn't quite perfect, but as long as you get it working by the demo, you're in good shape, and even if you don't have it working by the demo, you can get it working by the next demo and get back the points you lost.
- Dividing up the work evenly amongst the programmers and giving a different milestone to the CM majors in our group. They weren't really able to help us with this milestone so we let them take the reins on another milestone and we divide this up into perfect thirds. It was fair, even, and it worked beautifully.
- SOURCE CONTROL!!!! This point cannot be stressed enough. We chose to use a Google Code page for our code, but only because we didn't feel like setting up a Store account with Cincom. Our lives would have been hellish if we had not done some sort of source control for this project. It made moving to the CoC or working at home or transferring files insanely easy. Best choice we made as a group, by far!
- SUnit is time consuming. We did not plan for that. Our SUnit tests were not strong enough during the first round, and many of them failed very poorly. We learned fairly quickly that we are very new the to testing world and the skills we learned are probably going to stick with us for a while. Some good advice, learn how to write good test code early on, it will save you a TON of time and headache in this class, and I'm sure, in your job.
- What We Would've Done Differently
- We didn't put all of our code together early enough, and in the end found out that it didn't integrate perfectly. There is a saying about this somewhere on Bob's slides, something to the effect of "integrate early and often." Follow those words, so you're not up at 4 am in the CoC trying to figure out cryptic Smalltalk errors.
Examples
- Look at all non-gui code for this milestone (GUIs are denoted by a sideways square symbol in the editor)
http://www.prism.gatech.edu/~fcatalano3/SupplyChain.st
Link to this Page