Amy J. Ko

> Overall, I thought the chapter on comprehension was extremely insightful. I’m not really much of a developer despite having taken a few coding classes, but even those classes don’t...

> This chapter explains verification terminology and different types of testing well. One thing I would have liked to know more about is how we can automate testing. It is...

> One critique that I would like to give to this chapter is how and what ways can a software engineer increase test coverage? I head this terminology a lot...

> A question I like the chapter to answer is why unit tests, integration tests, and regression tests are common testing methods in software engineering. Though the chapter does do...

> I would like a quick summary about the differences between verifications. Although I love how Amy explained everything, I felt a bit overwhelming regarding this chapter, especially about all...

> I was hoping for more information about manual analysis.  In the example, there was a paragraph written about a manual analysis of the JavaScript code.  I am having a...

> I am struggling to find anything to say about these readings anymore. I guess for this reading I am confused on what the key idea is. The other readings...

> Something that I thought could be better explained is Herbsleb’s Socio-Technical Theory of Coordination. I felt that though the chapter did explain what his theory was, it failed to...

> I want more clear explanation about the spiral software development model. I wasn't able to fully understand how the model works based on the given definition and  the given...

> Overall, I thought Amy explained the concept of specifications fairly well, and the examples really helped me understand the terms better. If I were to critique anything about this...