---
# System prepended metadata

title: SE475 Design Journal - Week 3

---

# SE475 Design Journal - Week 3
## 09/24

I helped create the Plan tab on our team channel and set up the environment on GitHub. Since I am in Taiwan this quarter, the time difference got me worried a bit. But at the same time, since this course is about global software development, I thought it would be a good opportunity to learn to collaborate with team members that are actually located in multiple time zones.

## 09/25
Since other team members don't seem to be that responsive, I took the initiative and created a few skeleton projects of different unit test framework for other team members to clone. 

The process of creating unit test project within Visual Studio was surprisingly easy. I encountered a few reference problems at first, but they resolved themselves after a while. I think it could be some internet-related issues that were preventing the IDE from recognizing the unit test frameworks because the problems disappeared after I swithced to a more stable network.

## 09/28
I decided to take the lead on the project. I emailed two of our members who have yet to response in our team channel. Meanwhile, in order to come up with the plan, I started several conversations so that we could decide on which framework to use, how the workflow should look like and the deadlines for next week. 

Given that people have different schedules and might not be responsive all the time, I provided a default option for each of those things so that people don't feel too stressed about it.


## 09/30
Finally, thanks to the time zone difference, I was able to flesh out the project plan in the early morning of CT. As expected, all the members were pretty flexbile and went with the default options that I provided, so I used those information to complete the plan. 

Since there were still two members that hadn't chosen the methods that they should work on, I went over the method lists and assign some to them randomly. Although the choosing process was random, I still took the time to skim through the method signature and evaluate whether it is easy to write unit test for. That was when I realise how important it is to write modular and testable code. Some of the functions are rather complex and coupled to test properly.