The Tetris assignment looks like it is going to be challenging. I think the most difficult part will be coordinating tasks between the whole class. Team D just had ~2 hr. meeting to discuss the project. We created a high level design document (https://docs.google.com/document/d/1hulnzMKJKc4yF4hQF0jSdSwSQvDA5h0T2xxzKcxOY_8/edit?hl=en&authkey=CKLy44cD#) and posted it on the class Tetris Wiki. The document broke out the design into 6 chunks. The idea behind this would be to create discussions between the class and hopefully each team could take a chunk of the design. That way, each team can hopefully have some time this week to work on the design activities for their chunk for Saturday's deliverable due date. I have my doubts that this is going to work like this in aneducation environment since it's Tuesday and communication is just now starting between the class. Hopefully the high level design document will get things rolling. We'll all have our work cut out compared to the last 2 assignments. The team projects have been building blocks on one another.
Prior to our meeting tonight, I took some time and played the benchmark at http://www.freetetris.org to to get familiar with the features. After that, I looked at the provided code posted in Perforce, but found that there were unresolved external symbol errors. However, somebody from the class (Perforce says jschrantz, thank you!) has already fixed that this evening and now the code compiles and runs a "Global Software Tetris!" GUI. That's pretty cool! The provided code has a lot of functionality already built in so hopefully we can work together to make this work well.
I hope that the team starts commenting on the design and we can get the work "partioned off". After that occurs, I think the progress will start happening. I see potential for us all to step on each other's toes a bit.
No comments:
Post a Comment