Hotspots: Admin Pages | Turn-in Site |
Current Links: Case Final Project Summer 2007
Project Planning and Coding Decisions - Azhar Bande-Ali
Intro:
The approach our team took to tackling the task of coding up the project was to divide classes amongst us and code them separately. Although that may have worked for some teams, it didn’t quite help us much. Not having access to the Smalltalk group work base didn’t help either.
Problem:
Basically, our planning went perfectly with group meetings, discussions and group decisions. But when it came to coding, we were all working on separate versions of code (since we someone had to manually merge it), everybody was coding assuming the other would make certain coding choices which didn’t always work out and caused confusions in future projects.
Recommendations:
- Do not assume that you will find a way to share code by emailing each other. That’s not feasible. Over the semester, you’ll get lazy and slack off on it. Get subversion, smalltalk code share or group access to a server.
- Find time to code together. We tried otherwise and I don’t think it worked. It will only help you. (coding help, project understanding and discovering design issues)
- I would advise against assigning each other individual classes to code UNLESS you all have THOROUGHLY planned them and the only thing to do is put them in as code. We made the mistake of doing this without a complete understanding of what the classes required (and left it up to the individual coder to make the decisions) and it didn’t work out too well for us.
Links to this Page
- Case last edited on 29 July 2009 at 11:50 pm by c-76-97-208-233.hsd1.ga.comcast.net
- Index of Individual Cases last edited on 28 July 2009 at 3:01 pm by lwc029.ats.gatech.edu