Project Selection - Software Methodology

Students are required to collaborate in teams of 4-6 people to undertake a significant software engineering project.

Term projects in CS 115 involve, briefly, creating a game, subject to the following guidelines:

• It must be written in Java.
• It must support multiple players.
• It must have network capability. That is, the different players must be able to be interacting with different machines, which can communicate with each other to update game state.
• It must have some sort of state that persists between invocations of the program. For instance, it might keep track of high scores, or all scores. Or it may remember recently-used hostnames or IP addresses.
• It must run on the machines in one of the Baskin Engineering labs.

Each team should:

• select a suitable project;
• create a DForge Web site containing the source code and outer project documents (as described on the syllabus);
• have an agenda for every team meeting;
• maintain notes recording major decisions made at each meeting;
• conclude each meeting with a list of “action items” that the team members need to work on;
• record the time spent by each team member on the project;
• maintain a project notebook of all design documents, meeting notes, etc.

For this project, you will only be creating the "materials" for the game. That is, your program will contain the cards/stones/objects, communication, and organization, but not intelligence. The players will be people, not your program.

First: you should fill out a Project Selection Template describing your project.

Next: You must use DForge (http://dforge.cse.ucsc.edu) and the Subversion software configuration management (SCM) tool to manage your project.  You are required to keep all code and electronic documentation in your Subversion repository. To learn more about Subversion, check out the online Subversion book, or there’s some shorter documentation.

In addition to tracking changes made to a software project, SCM tools also provide workspaces, allowing project members to work on the project in isolation from the ongoing changes made by other project members. It also provides the confidence that your individual changes will not affect other project members until you decide to make those changes visible.

The goal of this project phase is to demonstrate that you have successfully placed your project's initial documentation (the project selection document) under the control of the Subversion. The deliverable for this project is simple. Just run the command:

svn ls -v {repository URL}

For example:

svn ls -v http://dav.cse.ucsc.edu/svn/DandD/

Turn in a printout of the output, after your project has been loaded into the repository. The output will show a listing of the members of the top level directory of your repository. At this point, you probably won't have much actual code and documentation, but what you do have must be in the repository.

As part of this deliverable, you must add the professor (username: cormac) and TA (username: dolsen) as members to your project, so that they can access your project documents.

On the CATS lab computers, you can use Subversion by adding the directory /afs/cats.ucsc.edu/users/k/cormac/svn/bin to your PATH.