---
# System prepended metadata

title: SE475 Design Journal - Week 7

---

# SE475 Design Journal - Week 7
### 10/25
I began looking at the project code and learn about the Tetrs game this day. The project itself was not too complicated, but working together with other 15 people from other groups seem to be a big challenge. It was hard enough to communicate and set up meetings within a group, let alone between four groups. I doubt whether this kind of really flat structure would be used in real production environment. 

The engine looks pretty familiar, I am assuming that it comes from Ed's engine his space invader class (SE456). Having worked in the same engine, I felt pretty comfortable navigating the system.

The whole division decided that each team should come up with its own requirement and specification, then all leaders discuss and piece everything together into a unified version. Our team decide that we each should also do a list of specification, so I came up with a basic API list that I thought contained the core functions for the game to work. For me, it was quite easy to imaging what classes/methods/functions there should be, but to describe why we need those thing was really hard.

### 10/26
Our team planned on today to go over our suggestion and come up with our team's version of the specification list. However, the division leader hosted a last minute meeting with all team leaders and finalized the design doc before our team hold our own meeting. Our team leader wasn't available due to time zone difference, but luckily one of our team members was online and attended the division meeting. 

Our team meeting later then changed its purpose to distributing the tasks that our team was assigned and discussing when we should each finish the documentation of our part. The benefit of partitioning a project is that every member eventually only has to focus on a small portion of the code, with make the task less stressful. My part was the logic of generating the next Tetris shape. Most of the time spent was to come up with a formula that would make sense with increased difficulty, although this seems to be more like a task for the implementation phase.