Queens College, CUNY, Department of Computer Science
Software Engineering
CSCI 370
Fall 2019
Sateesh R. Mane 2019
Due date: presentation in class (see demo policy below)
2a Project 2a
• All students must submit solutions individually for this project.
See below about grading policy.
• You are more than welcome to engage in Agile and Scrum methodologies etc. with others.
1. You do not have to tell me.
2. However the submitted solution must be in your own name only.
• This project is to play a game on a board (requires a GUI).
• This project does not require a database (no data is saved).
• Please submit your solution via email, as a file attachment.
1. The file attachment is a zip archive with the following naming format:
StudentId_first_last_CS370_project2a_Fall2019.zip
2. Important: do not encrypt the zip. Other formats such as RAR archive or OneDrive
or Google Drive, etc. will not be accepted.
3. You must submit your zip archive on or before the date of your demo in
class. See below for details of demo in class.
• All code must be written in Java and must compile and run when loaded into
Eclipse on my home computer.
1. Your zip archive must contain all your Java source code.
2. You are not required to submit a cover document.
3. The zip archive should contain only your program source code.
4. Do not send a jar file. You will receive no credit if I cannot read your code. Also
I will be unable to award partial credit if your code is mostly correct but has minor
mistakes, if I cannot read your program code.
• You may submit your solution only once. Updates are not allowed.
• Late submissions will not be accepted.
SAW game
• This project is to play a self-avoiding walk (SAW) game as illustrated in Fig. 1.
• The board has an n ⇥ n chessboard pattern, where n = 8 in Fig. 1.
• Players take turns to move, to generate a self-avoiding walk (SAW).
• In Fig. 1, the moves of the two players are indicated by red disks (Player 1) and blue triangles
(Player 2).
1. The first player can begin the SAW on any square, not necessarily a corner
or center square.
2. In Fig. 1, the first move is on square (3, 3) (red disk).
3. Each successive move is up/down or right/left (no diagonal moves) and must connect to
the end of the SAW.
4. Moves cannot extend beyond the edges of the board.
5. In Fig. 1, the current end-point of the SAW is indicated by an open triangle.
6. The last move was made by Player 2 hence it is now Player 1’s turn to move.
• The game ends when a player makes a self-intersecting move.
1. A player who makes a self-intersecting move loses the game, but there is a special case.
2. Special case: if the self-intersecting move creates a self-avoiding polygon
(SAP), then the player WINS THE GAME.
3. To avoid a trivial win, the SAP must contain at least 4 moves.
Scalable
• Your project solution must be scalable.
• The board size displayed in Fig. 1 is 8 ⇥ 8, but your project solution must support a board
of any size n ⇥ n, where n2.
• The game displayed in Fig. 1 is for two players, but your project solution must support k
players, where k
• The “token” of each player must be di↵erent, so that the players can be distinguished.
• It is your responsiblity to implement how the values of n and k are set before a
game begins.
• The same rules to terminate the game apply.
1. The game ends if a player makes a self-intersecting move, then that player loses. All the
other players are declared as “winners” of the game.
2. However, if a player makes a self-intersecting move that creates a self-avoiding polygon
(SAP) with at least 4 moves, then that player wins.
2
Demo and due date
• Each student is required to present a demo of his/her project solution in class.
• The three dates 11/14/2019, 11/19/2019, and 11/21/2019 will be reserved for student demos.
• Please send me an email by the previous evening to inform me of the date you wish to present
your demo.
1. I will not accept emails sent on the same day that you wish to present your demo.
2. Your zip archive with your program code must be submitted on or before
the date of your demo in class.
• For each of the above lectures, I will take a count of the number of students who emailed to
present demos in that lecture.
1. The time for each student demo will be divided equally between all the students who
wish to present demos in that lecture.
2. Hence if you wait till the last day and many other students also wish to present demos
in the same lecture, you may receive very little time for your demo and may not be able
to present your work e↵ectively, resulting in a reduced grade.
3. Any attempt to create a disturbance in class and/or grab extra time for yourself and/or
interfere with the demos by other students will be treated as a serious o↵ense, resulting
in an automatic failing grade.
Grading policy
• Your grade for this project will be applied as an addition to your grade for Project 2.
• Project 2 is a team project, hence team members will share the credit for Project 2.
• The grade for this project will be applied as a grade boost to you individually and not to your
team members.
• If you wish to present a demo on 11/12/2019, please notify me and send me a zip
archive as indicated above. If you do so and submit a correct working program
(and demo in class) you will receive bonus credit.
Figure 1: Example of self-avoiding random walk (SAW) on an 8 ⇥ 8 board. The moves of the two players
are indicated by red disks and blue triangles. The last move played is indicated by an empty triangle.