-
Notifications
You must be signed in to change notification settings - Fork 11
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #59 from hyeminyoo/master
- Loading branch information
Showing
5 changed files
with
108 additions
and
35 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,12 +1,12 @@ | ||
Dong He | ||
Margaret Schmidt | ||
Hyemin Yoo (Minnie) | ||
|
||
1. Card matching game, click the cards to reveal them and click two of the same to permanently reveal them. | ||
2. As a player I can click cards so that they reveal their icon. As a player I can click two matching cards to permanently reveal them. As a player I can play the game and save my highscore. As a player I can click instructions and be given a instruction screen of how to play the game. | ||
3. The software runs except for a few brief freezes. It generates a board of x * x amount of cards and waits for you to click. | ||
4. As a player I should be able to access the highscores and instructions without being spammed with pop-ups. As a player I should be able to finish a level and see some sort of progression animation so I know when I have finished a level. | ||
5. The basic information is present, there is nothing detailed or project history. Notes present on not recommending this project for future students as it is well built and almost done. | ||
6. As far as we can tell nothing needs to be updated. It builds properly and there are no noticeable issues. Nothing old to remove either. | ||
7. https://github.com/UCSB-CS56-Projects/cs56-games-memory-card/issues/51 , https://github.com/UCSB-CS56-Projects/cs56-games-memory-card/issues/52 , https://github.com/UCSB-CS56-Projects/cs56-games-memory-card/issues/53 | ||
8. The code is divided into multiple java files, each one accomplishes a task given by the name of the file. Within each file, there are comments present on each method, contructor, and variable to tell the reader what the thing does. Honestly, for any future workers on this project, you can easily digest what everything does in this project. Only thing lacking in the comments is HighScoreBoard.java. Nothing to really fault the old programmers on. | ||
9. There are a decent chunk of tests, cover a lot of common things and the most used methods and constructors. Could have added more and future workers on this project can add more JUnit test cases if desired. If future test cases were to be added, I would expand the situations the tests cover and make sure every method is tested. | ||
1. Memory Card Game is a game that flips two cards each time to find matching pairs before time runs out. | ||
2. As a player I can click start/resume to start the game and to get the timer going/starting. As a player I can click a card to flip it and see which picture it has. As a player I can click two matching cards to earn score and to permanently flip the card until that round is over. | ||
3. The software runs except there are glitches here and there. It starts the game with x by x number of cards. | ||
4. As a player it might be more fun to play with more difficulties. As a player I could see some animation after I finish a level. | ||
5. The README.md tells you a brief description about the game, and that this project is well-built in terms of logic and design. It would be better if README.md has details about how many cards the player starts with and how to flip cards. Also, screenshots of the cards might be useful and more descriptive. | ||
6. The build.xml file does not have any targets that need descriptions, or old legacy JWS stuff that needs to be removed. | ||
7. There are enough issues to earn 1000 points by working on this project. The expectations to how the issues should be fixed are clear. | ||
8. There are no issues added because this is a switched repo. | ||
9. The code is in different files with names that straight-forwardly tell what each file does. The purposes of classes and the methods are clear and the code structure is well-built. There are issues here and there but overall, the code is pretty easy to comprehend. There are different files for making grid, using grid, using GUI, instruction screen, exceptions, etc.. | ||
10. There are tests, but they do not cover every possible situations. They cover constructors, methods, and different random cases. There can be more JUnit tests. |
Binary file not shown.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters