Work in your project groups to further develop the game based on your wicked problem. Then create a report and short presentation addressing the issues below.
Include the following:
Game_State
and defined in your COMMON CODE area.)
The Game_State
class should support the following methods:
__str__(self), __eq__(self, other), __hash__(self)
,
in addition to any methods you wish to define in order to make it easy to define
your operators, such as can_move
and move
.
By defining these specified methods, you will make it possible
not only for some automatic testing of your game, but also for an intelligent
(or not-so-intelligent) agent to play your game.
__str__
method.
If you have a visualization of it, you can include that.
For Milestone C, please prepare a SHORT presentation involving 3 slides. One slide should be a revised timeline slide, which is an update of the timeline or map slide from Milestone B. Put an asterisk ("*") next to each item on the timeline that is different from what it was at Milestone B.
Your second slide should be a list representing the BACKLOG of your Scrum right after Milestone B.
Your third slide should be a list representing the BACKLOG of your Scrum here at Milestone C. (What code changes and features remain to be performed or added before Milestone D?)