April 29, 2010
- You must attend the VOOGA Final Demos in French 2237 from 7-10pm, Monday, May 3!
- Current Assignments
- VOOGA, Design Flaws, due by noon, Monday, May 3
- For each team, submit the three most important flaws in your project's design (they should be listed in order of importance)
- briefly describe each flaw, why you think it exists, and why you think it is important (you do not need to provide a solution)
- during the final presentations, you will be asked about these flaws and why your team ranked them as it did
- This deliverable is in lieu of an individual project analysis
- VOOGA, Final Version, due by 7pm, Monday, May 3
- Since the focus is on functionality over design, the features in this release should be as solid, i.e., bug-free, as possible
- you should refactor your public code as little as possible so as not to break other teams projects
- your code should still be reasonably cleanly implemented and include unit tests where possible
- At a minimum, this final release should include the following features
- one completely working game, i.e., a game that can be won and lost
- three other partially implemented games (one should have multiple levels, one should be networked, and one should have an AI player)
- view the high scores for all games (even if you have to make them up :)
- log in as a user, set some preferences, log out, log back in and see those changed preferences
- replay, i.e., re-display, a previously played game
- participate in multiple online chats at once, i.e., via different channels
- comment, rank, or rate a game and view them later
- visually create a level for a game, save that level, and then play a game using that level
- change the keys or images used within a game
- Your Javadoc comments should be complete at this time, you will not be able to change any part of the code later
- VOOGA, API Documentation, due by the end of the day, Tuesday, May 4
- For each team, submit an overview, the details, and considerations of your project's current design
- Also, submit a description of a new "ideal" API, i.e., apply what you have learned over the past month to re-design your project's current API
- this description should be in English at the level of the artifact's design detail section, not in Javadoc or raw code
- This deliverable is in lieu of the complete project artifact
April 21, 2010
- Current Assignments
- VOOGA, Revised Implementation, due by the end of the day, Monday, April 26
- Submit your revised implementation via Eclipse
April 16, 2010
- Javadoc is up for the VOOGA project!
- Log in to Bugzilla to report "bugs", changes, you want to other teams APIs.
- Please snarf the initial version of the entire project so that all teams can start from the same place
- Let me know if your team wants to change a package name or move a class to a different package
- Current Assignments
- VOOGA, Revised Implementation, due by the end of the day, Monday, April 19
- Submit your revised implementation via Eclipse
- VOOGA, Revised API, due by the end of the day, Thursday, April 22
- Update your Wiki API overview and your Javadoc comments
- Update your implementation to match other team's API updates
April 12, 2010
- Current Assignments
- VOOGA, Initial Implementation, due by the end of the day, Monday, April 12
- Update your API on the department Wiki
- This should be separate from your Javadoc comments and give an overview of your API design philosophy
- Submit your initial implementation via Eclipse
- It should be completely commented using Javadoc style comments so I can generate the complete project documentation
- It should be in a global package called
vooga
- VOOGA, Revised API, due by the end of the day, Thursday, April 15
- Update your Wiki API overview and your Javadoc comments
- Update your implementation to match other team's initial implementations
April 5, 2010
April 3, 2010
- Current Assignments
- VOOGA, Specifications and Priorities, due by the end of the day, Tuesday, April 6
Post your submission to the department Wiki:
- Core Goals (i.e., most vital to the project to get done in the next two weeks)
- Extensions (i.e., extra features to be added in the last two weeks)
- VOOGA, Initial API, due by the end of the day, Thursday, April 8
Post your submission to the department Wiki:
- Be as specific as possible when making class names and functions so that other teams can begin to use them in their own code
- Be as general as possible when passing information to other modules so they can have some flexibility in how they interface with you
- List other modules you think you depend on and questions you may have for them
April 2, 2010
March 29, 2010
- To prepare for Wednesday's class discussion,
- Current Readings
- Current Assignments
- VOOGA, Project Choice, due by the end of the day, Friday, April 2
- Each student must email me their top three choices for VOOGA projects to work on and I will create the groups to make sure as many projects are covered as possible.
- If you want to write a game for the final project, you must submit a description of your game with your email to be considered.
- Use the Bulletin Board to organize your choices or game ideas with other students.
March 26, 2010
- Current Assignments
- GEDIVA, Final version, due by the end of the day, Monday, March 29 (extended!)
- GEDIVA, Analysis, due by the end of the day, Wednesday, March 31 (extended!)
March 15, 2010
- Current Readings
- Current Assignments
- GEDIVA, API Presentation, due by noon, Monday, March 22
- GEDIVA, Final version, due by the end of the day, Sunday, March 28
- GEDIVA, Analysis, due by the end of the day, Tuesday, March 30
March 5, 2010
- Current Assignments
- GEDIVA, choose team, due by the end of the day, Sunday, March 14
February 20, 2010
- Current Readings
- Current Assignments
- PICASSA, choose team, due by noon, Monday, February 22
- PICASSA, design presentation, due by noon, Monday, March 1
- PICASSA, final version, due by the end of the day, Friday, March 5
- PICASSA, analysis, due by the end of the day, Tuesday, March 16
February 13, 2010
- Lilliana Beth Duvall was born at 12:29pm today, weighing 5 pounds 11 ounces
February 10, 2010
- Find out who you are partnered with for Jotto
- Current Assignments
- Jotto, refactoring, due by the end of the day, Saturday, February 13
- Jotto, final version, due by the end of the day, Friday, February 19
- Jotto, analysis, due by the end of the day, Saturday, February 20
February 8, 2010
February 1, 2010
- Current Readings
- Current Assignments
- Arithmetica, final version, due by the end of the day, Saturday February 6
- Arithmetica, analysis, due by the end of the day, Monday February 8
January 27, 2010
January 25, 2010
January 22, 2010
January 16, 2010
January 15, 2010
- Note the new room locations for the course
- Instructions for downloading Eclipse and Ambient are available online here.
- Current Readings
- Current Assignments
- Introductions, due by the end of the day, Wednesday January 20
- Bins, refactoring, due by the end of the day, Thursday January 21
- Bins, testing, due by the end of the day, Sunday January 24
- Bins, analysis, due by the end of the day, Monday January 25
January 13, 2010
- Welcome to CompSci 108!
- This website complements what you experience in class.
Course announcements will be posted on this web page and may also
be announced in class. You are responsible for all material that
appears here and should check for updates frequently.
- If you are taking this course, chances are you are qualified to
be an Undergraduate Teaching Assistant (UTA) for one of our
introductory courses (CompSci 1, 4, 6, or 100). If you want to help
your fellow students, get more involved in the department, or
just learn more about computer science,
then sign up to be a
UTA online here.
