The fifth job of software testing--the law of construction

Because the time is only a week, so the book to see the relatively hasty, did not carry out too much of the drill, just simple to talk about their first simple to see after the feeling.

The first is to re-examine their own study of the major, what is software engineering? 1000 people in the eyes of 1000 hamlet, throw away the official definition, everyone has a knowledge of software engineering, I re-thinking is: A project from the requirements to after-sales maintenance of a set of human operations, and the algorithm coupled with the data structure of the program is logically cold, What the software engineering does is to give these cold program souls a way to form what we know now.

Secondly, so far I have little experience in actual combat projects, so I did not form a good code specification, fortunately, in the book has given the corresponding guidance, and how to build a complete project through the strength of a team, and then I covered the course of our semester-software testing, The book also tells us about unit tests, regression tests, acceptance tests, and other analytical methods that are different from the methods taught in the classroom, which may make it easier for me to accept this argument.

From the beginning of the sixth chapter of the agile process is I have not touched the content, because I am a small white, not involved in the practical work to go, so can only literally understand, and not very deeply aware of the advantages of agile process, but the mind has already been impressed.

The two chapters,MSF and MP , are more understandable than the sixth chapter, and the overall reading is also smoother, without too many obscure places, perhaps MSF and PM Not only relates to ideas, but also to a commercial software development, from the requirements of a team leader, the software engineering and PM itself and the quality of the team put forward the corresponding requirements.

Again is the conversion perspective, from the research and development team to the user's needs experience point of view, to tell us as developers need to prepare content, I personally feel that the most important thing is the user experience this chapter, after all, we developed software is intended for outsiders to use, so we must take into account the user's feelings from all aspects.

Finally, the book describes the IT Industry's future development and innovation model, and added a little software engineer's professional ethics content, in the face of the rapid development of it , we can do countless innovations, The premise is that we emerge from the existing curing thinking, in order to continue to explore the new software road.

Here are some of the questions I read:

1. As a new software engineer, how to better communicate with the team members during the development process, and to complete the change of project manager in the next few years?

2.MSF is the basic principle of commercial application value greater than the value of development?

3. Where is agile process agile? Time? Space?

4. Since the test case is unable to become perfect, the late need for patches, that directly before the release of a "Patch library" to replace the later frequent problems will not be better?

Where is the 5.MSF support for Agile and CMMI ?

The fifth job of software testing--the law of construction