Project 3 - Implementation Week 1

During our implementation phase each group took responsibility for the classes that they wrote the APIs for. This allowed for an easy transition as each team already have a high-level understanding of the classes they are looking to implement. As team leader I started by pulling a development branch off of our team-8 branch and ensuring that everything worked. Then our team met on Saturday (10/31) in the morning to begin our implementation. As a group we began by reviewing our MovementManager class API and writing in the basic implementation based on our design. During this process we encountered several design questions that we would need to address. I made note of these questions to take to our team leader meeting. We then completed the implementation of MovementManager and divided the work of unit testing to two members of our group.

I attended a team leader meeting later that Saturday to go over any questions. I was able to bring up my questions to the division leader who’s team is implementing the classes that are more heavily coupled with our class. Having the answers in hand I was able to pass along the details to our team.

Due to scheduling conflicts the sub-team had to reschedule for Tuesday in order to complete the unit testing work. We were also informed that team 5 had completed enough of their implementation for us to merge their branch in to do more practical testing of our implementation.

We rescheduled to have our one sub-team complete the MovementManager class early Tuesday and then have our other sub-team work on completing the template for the GameManager class. This should put us properly on track to meet our division goals for implementation.