CSC 335 Fall 2006 Final Project Instructions, Exams of Computer Science

The instructions for the final project in csc 335 during the fall 2006 semester. Teams are required to submit their project, including team name, team members' names and email addresses, tasks to be completed for iteration 1, main objects and their responsibilities, a uml class diagram, and a sequence diagram for the scenario 'player makes one move'.

Typology: Exams

Pre 2010

Uploaded on 08/31/2009

koofers-user-xh9
koofers-user-xh9 🇺🇸

9 documents

1 / 3

Toggle sidebar

This page cannot be seen from the preview

Don't miss anything!

bg1
Artifact: C Sc 335 Fall 2006 Final Project
Each team turn in a copy on Thursday, 2-Nov at the beginning of class 4:45
1. Team Name ____________________________
2.Team members
Name Primary Email Address
3. What is the name of your CVS repository? ____________________________
4. Write the tasks (a class with a unit test, a feature of the system such as "Set Armies" or "Build
Community Cards", ...) you plan to complete for Iteration 1, by Mon. 6-Nov
Feature or Task Estimate
in hours
pf3

Partial preview of the text

Download CSC 335 Fall 2006 Final Project Instructions and more Exams Computer Science in PDF only on Docsity!

Artifact: C Sc 335 Fall 2006 Final Project

Each team turn in a copy on Thursday, 2-Nov at the beginning of class 4:

  1. Team Name ____________________________ 2.Team members Name Primary Email Address
  2. What is the name of your CVS repository? ____________________________
  3. Write the tasks (a class with a unit test, a feature of the system such as "Set Armies" or "Build Community Cards", ...) you plan to complete for Iteration 1, by Mon. 6-Nov Feature or Task Estimate in hours
  1. Main Objects and Responsibilities: Object Name Major responsibility(ies) in 1 or 2 sentences
  2. Draw a UML class diagram showing all of your candidate objects and any relationships between them. Show inheritance relationships, interface implementation, or general association such as dependency by drawing a line. Write any multiplicity adornment you can think of. You will likely have 1, and or * in a few places at least. The classes only need the class name, one or more method names