Docsity
Docsity
Prepare for your exams
Prepare for your exams

Study with the several resources on Docsity

Earn points to download
Earn points to download

Earn points by helping other students or get them with a premium plan

Guidelines and tips
Guidelines and tips
Sell on Docsity
Sell on Docsity
Docsity AI
Docsity AI
Log inSign up

Prepare for your exams

Study with the several resources on Docsity

Find documents

Prepare for your exams with the study notes shared by other students like you on Docsity

Search for your university

Find the specific documents for your university's exams

Docsity AINEW

Summarize your documents, ask them questions, convert them into quizzes and concept maps

Explore questions

Clear up your doubts by reading the answers to questions asked by your fellow students

Earn points to download

Earn points by helping other students or get them with a premium plan

Share documents
download point icon20 Points

For each uploaded document

Answer questions
download point icon5 Points

For each given answer (max 1 per day)

All the ways to get free points
Get points immediately

Choose a premium plan with all the points you need

Study Opportunities

Choose your next study program

Get in touch with the best universities in the world. Search through thousands of universities and official partners

Community

Ask the community

Ask the community for help and clear up your study doubts

Free resources

Our save-the-student-ebooks!

Download our free guides on studying techniques, anxiety management strategies, and thesis advice from Docsity tutors

Risk Game Development Project, Exams of Computer Science

University of Arizona (UA)Computer Science

A final project for c sc 335 fall 2006 class where students are required to develop a computer version of the popular board game risk. The project involves analyzing, designing, and implementing the game in teams of 4, using the rules of risk from 1975. The project is divided into three iterations with specific requirements and due dates.

Typology: Exams

Pre 2010

Uploaded on 08/31/2009

koofers-user-7pd-1
koofers-user-7pd-1 🇺🇸

5

(2)

9 documents

1 / 4

Toggle sidebar

This page cannot be seen from the preview

Don't miss anything!

bg1
C Sc 335
Fall 2006
Final Project
Risk®
Version 2.1, 31-Oct-2006 Subject to edits, modification, comments from developers,and changing requirements
Overview
Risk is a popular board game of strategy in which a player can conquer the world. You are to
implement a computer version of this game. In teams of 4, you are to analyze, design, and
implement your own version of the board game Risk®.
Rules
Though there are many variants, use the Rules of Risk from 1975 (see attachment).
Note: Do not implement the Two Player Risk described at the end.
Preview of Due Dates and Point Values 180 points max (20% of final grade)
Artifacts: Due Thu 2-Nov in class: Design Documents
Due Thu 14-Dec (final exam time): UML Class Diagram 20pts
Iteration 1: Live Grading by Mon. 6-Nov 10:00 pm Set up game 30pts
Iteration 2: Live Grading by Mon. 20-Nov 10:00 pm View & Play game to end 60pts
Iteration 3: Due Monday 4-Dec 10:00 pm Additional Features 30pts
Usability, Robustness, Appearance in Final Version (Subjective) 20pts
Individual: Weekly preceptor meetings & Team Participation (teammate input) 20pts
Artifacts
Due Thursday, 2-Nov at 3:30 (20 points)
At the beginning of Thursday's class, turn in a copy your Artifacts
Iteration 1: Ready to Play a Game
Due Monday 6-Nov 10:00pm (30 points)
This iteration asks you to initialize the game with armies set on territories, no turns required.
___ / 5 Game has six continents, 42 territories
___/ 5 Each territory knows the territories it can attack
___/ 5 Can initialize a game with 2-6 computer players or 1 human plus 1-5 computer players
and it is know who goes first
___/ 5 Can determine player's territories and/or continents
___/ 5 Can set all armies for all players, whether human or computer, from 2-6 players
All 42 territories have 1 or more armies
___/ 5 Well tested with JUnit
Can see assertions that initialized a game that can begin
pf3
pf4

Partial preview of the text

Download Risk Game Development Project and more Exams Computer Science in PDF only on Docsity!

C Sc 335

Fall 2006

Final Project

Risk®

Version 2.1, 31-Oct-2006 Subject to edits, modification, comments from developers,and changing requirements

Overview

Risk is a popular board game of strategy in which a player can conquer the world. You are to implement a computer version of this game. In teams of 4, you are to analyze, design, and implement your own version of the board game Risk®.

Rules

Though there are many variants, use the Rules of Risk from 1975 (see attachment). Note: Do not implement the Two Player Risk described at the end.

Preview of Due Dates and Point Values 180 points max (20% of final grade)

Artifacts: Due Thu 2-Nov in class: Design Documents Due Thu 14-Dec (final exam time): UML Class Diagram 20pts Iteration 1: Live Grading by Mon. 6-Nov 10:00 pm Set up game 30pts Iteration 2: Live Grading by Mon. 20-Nov 10:00 pm View & Play game to end 60pts Iteration 3: Due Monday 4-Dec 10:00 pm Additional Features 30pts Usability, Robustness, Appearance in Final Version (Subjective) 20pts Individual: Weekly preceptor meetings & Team Participation (teammate input) 20pts

Artifacts

Due Thursday, 2-Nov at 3:30 (20 points) At the beginning of Thursday's class, turn in a copy your Artifacts

Iteration 1: Ready to Play a Game

Due Monday 6-Nov 10:00pm (30 points) This iteration asks you to initialize the game with armies set on territories, no turns required. ___ / 5 Game has six continents, 42 territories ___/ 5 Each territory knows the territories it can attack ___/ 5 Can initialize a game with 2-6 computer players or 1 human plus 1-5 computer players and it is know who goes first ___/ 5 Can determine player's territories and/or continents ___/ 5 Can set all armies for all players, whether human or computer, from 2-6 players All 42 territories have 1 or more armies ___/ 5 Well tested with JUnit Can see assertions that initialized a game that can begin

Iteration 2: Observe play to end of game

Due Monday, 20-Nov 10:00pm (60 points) This iteration asks you to get the view virtually done and play a game of Risk to the end. The view should draw images, shapes, and other graphical entities to represent things (the map, who owns what territory, number armies per territory, etc.). The view should allow the user to interact with the game by listening to mouse and/or keyboard events. The view should allow human players should know whose turn it is, be able to see cards, choose when to stop playing, be able to cash in cards so the game plays well (a final subjective criteria will be applied to the view in iteration 3, so it need not be "perfect" during iteration 2). If you have any doubts as to whether your view is acceptable, check with a Risk grader. ___ / 5 View shows changing state of game and you can tell what is going on. View need not be wonderful yet ___ / 5 Computer AI can handle all requirements of a Risk player, even if not very clever ___ / 5 Can observe 2-6 computer players play in turn ___ / 5 Can observer an entire game until the winner is obvious ___ / 5 Can have humans and computer players playing together ___ / 35 Has all rules correctly implemented at each players turn (5 each)  Player receives reinforcements at the beginning of each turn  Handle cards: Deal them at the right time, and trades for more armies at the right time  Each player can attack other countries as long as they want and it is possible  Reinforcement can occur before each turn  Attacks are based on rolling dice  Correct number of armies moved after taking a territory  Can move armies from one territory to another before quitting turn

Iteration 3: Additional Features

Due Monday, 4-Dec 10:00pm (30 points) This iteration is your final release, which must include some of the additional features listed below. This is by no means an exhaustive list of extra features, but merely a list of suggestions for potential extra features. Some of these are much harder to implement than others, and are worth more accordingly (see points). Features not listed will receive extra points based upon their difficulty. Talk to your graders about your planned extra features to ensure that your extra features will receive the points that you expect. You may not receive more than the total of 30 points for additional features, however you are welcome to implement as many extra features as you like. Not to exceed 30 points, even if your total is 35 or 50. This is subject to change and negotiation. Some ideas and suggestions that we would consider valid extra features are:  Networking (30 points) o Make the game networked so you can play against other human players at another computer. Human players could register an interest to play or just watch. New human players must wait for the next round to begin. The human player could stop playing at any time (sit in at the beginning of the next round or sit out at the end of the current round). o How you choose to implement the server, and who controls the server, is up to you. For example, you may want the first player that starts up the game to be

Usability and Robustness in final version: 0, 5, 10, 15, or 20 points

20 Points: Virtually Flawless, awesome, we would buy it (may only be one in the class) 15 Points: Really good, can see what is happening clearly, it is very robust (only a few) 10 Points: Can understand how to play, what is happening, and mostly robust (typical) 5 Points: Hard to play and small bugs 0 Points: Hard to play, or hard to see what is happening, or not robust, or mostly crashes Individual: Weekly preceptor meetings & Team Participation (teammate input) 20 points We will maintain a record of your attendance at weekly preceptor meetings. ___ / 8 –2 each for any of the four preceptor meetings missed ___ / 12 Carried your weight to make your project a success according to teammate input 0 No help 4 Some help 12 Contributed roughly equally in terms of time and effort

Firing a Team Member

If you are having issues with one of your team members that you feel you cannot deal with on your own then you should:

  1. Contact a section leader or preceptor
  2. If the preceptor cannot resolve the issue with the team, talk to Rick
  3. If the issue still cannot be resolved, the team will have the option of firing the team member. This will involve each team member filling out some paperwork as to what happened and why it was not able to be resolved. At least two team members must agree this is the correct course of action for team success. A fired team member has two choices  If at least two team members agree to give the code to the fired member, that student can complete use that code to complete the project on their own with the 12 point deduction.  If two or more team members agree that the fired team member should not get the code, then the student will have to build the entire system alone with the 12 point deduction