COMP 310 Fall 2010	Lec05: UML continued, Source Control & Ballworld Demos

UML Diagrams continued...

Subclipse/SVN Source Control

Why use source control?

• Safety
  • Your code is stored on a remote server that is backed up regularly
  • Your development history is preserved
    • You can view a previous version of your work
    • You can "roll back" your work to a previous version
• Coordination
  • Multiple people can work on the same project without stomping on each other's code.
  • Code updates from one person are quickly and easily transmitted to everyone else in the group.
• Convenience
  • No need to explicitly turn in your work -- your last commit or tag is your turned-in assignment.
  • The staff, who has access to all student repositories, can easily obtain and work with your code without having to send anything though e-mails or dropboxes. 

Discussion continues on the Using Subclipse Resource Page.

BuggerLab Demo 

created by Erik Talvitie (BuggerLab was initially developed right after Erik's freshman OOP/D course with Dr. Wong at Oberlin College)

Here is a (hopefully!) fun and interesting example of what can be accomplished reasonably easily with the power of object-oriented programming and design.   By halfway through the semester, we will have all the tools necessary to write simulations on the scale of BuggerLab.

Download the JAR file and run it  (will not run as an applet because it accesses the local file system to store configurations).

Download and unzip some saved ecosystems and species that can be loaded into BuggerLab.

Inheritance-based Ballworld demo

© 2010 by Stephen Wong and Scott Rixner