View this PageEdit this PageAttachments to this PageHistory of this PageHomeRecent ChangesSearch the SwikiHelp Guide
Hotspots: Admin Pages | Turn-in Site |
Current Links: Cases Final Project Summer 2007

Team Mortal Wombat

Helpful Team Hints
Utilize the swiki- it's good to add notes and keep people up-to-date. The Store is your friend - always make sure you have the most up-to-date code! Play to the abilities of your teammates. Don't force someone to do something they're not good at.

Be sure to keep focus- the internet will often get in the way. We suggest a room with very few distractions and a whiteboard. The study rooms in the residence halls are good, as are the conference rooms in the library.

Energy drinks are good for programming, not good for brainstorming sessions.

Assigning duties is important; if people don't know what they're doing stuff won't get done in time. Also, set times for regular meetings.

Project Suggestions
Get a head start on every step of the project or you will surely have trouble accomplishing them on time and efficiently.
Be sure to read the material surrounding the different concepts. Scenarios can be very confusing if you've never encountered them before. If you read and still don't understand the concepts be sure to utilize the newsgroup, a TA, or the professor, all are generally easy ways to find help. The newsgroup is especially useful because most of the time someone has already asked whatever you were intending to ask, so check there first.
Just like M1 be sure to understand the concepts as well as you can before even beginning this step. For the addition of UML diagrams we found it helpful to use a program rather than draw out the diagrams. We used a free open source program called Dia and there are a couple others out there that work even better. A little google searching will probably set you on the right path of finding a UML Diagramming program for your group. The most confusing part of the diagram for us was the representation of Application Objects. We suggest playing with some coding at this point so that you can begin to understand the interplay between the Model, View, and Controller in VisualWorks. Understanding the interplay between these aspects and how they actually work in VisualWorks will help immensely in designing the UML diagram properly. Also, as the write up suggests, definitely begin coding at least the back-end for this portion or you will have very little time to work on the next part.
Here's where division of labor comes in handy. Hopefully each of your group members have expressed their pros and cons at this point and you can decide as a group how to divide the labor of the project to permit the creation of an efficient project. In other words let those that aren't as good at programming create the designs and paint the guis. Group members that aren't as good at programming can have things to do. S-Unit is also a nice assignment that nearly anyone can do so I suggest assigning group members who are better designers the S-Unit portions of the project. On the programming end, dividing up the back-end domain code and the GUI code can be helpful. Overall just divide the program up based on who is good at what. It is important for each team member to be supportive of the other members as well during this phase so as to be as productive as possible.
Understanding how VisualWorks does custom views was essential for this part of the project. Again, dividing up the labor and discusses drawing algorithms can be very helpful during this part of the project. Overall, stay focused, utilize teammates and don't think that since there isn't much to add to the project it isn't going to take time. The GUI parts can be complicated and take a lot of reading just to understand the basic concepts.
For this one, remember that the slides and notes are very helpful. Two of our members were pretty proficient in evaluation techniques, so we used what we had learned in other classes and applied the concepts to this part. Demos are helpful but not really necessary- if you can get together with the other team(s), do so, but that's just more of a helpful gesture than a necessity.

Link to this Page