We have updated the content of our program. To access the current Software Engineering curriculum visit curriculum.turing.edu.
Connect Four - Evaluation Requirements
Please reference these instructions, to prepare for your project evaluation.
Evaluation Rubric
| Exceeds Expectations | Meets Expectations | Approaching Expectations | Below Expectations | |
|---|---|---|---|---|
| Functionality | 2 of the additional features in Iteration 4 are complete | All of the functionality in Iteration 3 is complete | Some of the functionality in Iteration 3 is not complete | Some of the functionality in Iterations 1 or 2 is not complete |
| Object Oriented Programming | Project includes at least one additional class not outlined in the spec that does no command line input or output, adheres to SRP, and acts as a crucial piece of functionality in the program. | Project includes at least one additional class not outlined in the spec contained in its own file with no executable code outside the class. Very little code is not contained within a class. | Project includes at least one additional class not outlined in the spec. Code that is crucial to the setup, play, or end of a game may not be contained in a class. | Project does not include a class not outlined in the spec. The project does not use the required objects appropriately to accomplish the task. |
| Test Driven Development | All methods throughout the project are fully unit and integration tested, including additional classes built in Iterations 3 or 4. No tests fail to accurately verify expected behavior. | No more than 2 tests fail to accurately verify expected behavior. All methods that do not rely on CLI are unit and integration tested. | Every method from iteration 1 or 2 does not include a test. More than 2 tests fail to accurately verify expected behavior. | Half the methods throughout the project are not tested or have tests that do not accurately verify expected behavior. |
| Version Control | Project includes at least 10 pull requests that include helpful comments from both partners. | Project includes at least 10 pull requests and 30 commits. Insights show that one partner contributed no more than twice as much as the other in terms of lines of code or commits. Pull Requests were never merged by the author. | Project includes at least 5 pull requests and 20 commits. | Project has 5 or fewer pull requests or less than 20 commits. |
| Presentation and Professional Development | All of the reflection questions are answered in the README, and all of the presentation topics are discussed. Students provide examples and ideas about how some things might be approaching differently on future projects in either/both the written and verbal presentations. | All of the reflection questions are answered in the README, and all of the presentation topics are discussed. | 1 reflection question or presentation topic is skipped or not answered thoughtfully. | More than 1 reflection question or presentation topic is skipped or not answered thoughtfully. |
