Project Description - overlord-supreme/checkers GitHub Wiki
(as described in Project Description CHECKERS.docx)
Description
- Design and Implement
- Software Application
- Two Player
- Checkers
- Interactively
- Over the Internet (Networked)
The objective of this project is NOT to develop a checkers program. Rather, the objective is to develop software that provides an environment for two people to play a game against each other. Your application should attempt to make this interactive experience as close to the physical playing experience as possible. This should be your guiding principle when designing the capabilities of your system.
- Graphical Representation of a checkers board, and support
- Move Validation
- Move/Slide Pieces to new positions
- Refresh the board on the opponent's screen
- see here for rules
- see also
Deliverables and Development Expectations
Make use of Version Control, Document and Track your bugs, Cover your Code, and perform Static Analysis.
The Version identifier should be displayed either in the application splash screen or the in an "About" menu item.
At selected times during the term the TA will review with your team the implementation of these practices.
All members of the team must be present during the final demo.
Grading
NOTE: If any "Required" item fails, the entire project fails
| Item | Value | Status |
|---|---|---|
| Requirements Document | 10% | Required |
| Design Document | 10% | |
| Test Case Document (with Execution Results) | 10% | Required |
| Release Notes | 5% | Required |
| Version Control | 5% | Required |
| Static Analysis | 5% | |
| Code Coverage | 5% | |
| Bug Tracking | 5% | |
| Version Identification | 5% | |
| Acceptance Test (Demo works) | 0% | Required |
| Source Code | 0% | Required |
| Produce Meets Expected Quality | 40% |