The fifth time of software testing--experience

the method of construction--modern software engineering

Experience

For students majoring in software engineering, this course should be very familiar. I have a long history with it--we have learned software Engineering services outsourcing, engineering, and this semester's "testing", and I am still a general and hazy course for this subject. Fortunately, the teacher recommended to us the Xin Zou Teacher's "Construction law" This book, Let me to "software engineering" This concept has a deep understanding.

In the previous software learning, I understand the software concept is "SOFTWARE = program + Engineering", while the software engineering includes: Requirements analysis, software design, software construction, software testing and software maintenance. In my previous concept, software code writing is the most important, to occupy a long time, but after learning to find that I was wrong, no matter what the link, all require the programmer to spend a lot of energy. and software not only has the programmer this post, we can also develop ourselves as a project manager, user experience, product management, software testers and many other positions for our choice.

"The Law of Construction" in this book, I did not understand the past, feel particularly boring software engineering is very interesting, it is very important to the "people" in software development plays a role, full of strong practicality and super fun. In the written first edition of the reader's feedback, Mr. Liu Xin said: "This book is a good solution to the Software engineering knowledge field" from 0 to 1 "problem. This shows that the law of construction is a very good book.

The law of Construction contains 17 chapters, each of which is simple and easy to understand, with examples to answer questions. The contents of the book include: Software Technology, code requirements analysis, design, writing, testing, quality assurance. There are also the programmer's personal professional ethics requirements, teamwork ability requirements, innovation requirements and so on.

The most impressive chapter in this book is the fourth chapter, "Cooperation between two people". The contents of this chapter: 1, code specification, 2, limit programming, 3, pair programming, 4, the different stages of cooperation between two people, 5, the skill of influencing others. For a student of software writing, the teacher in the first class to us to ask us to good code writing habits, whether in code style or code design, should be standardized, because our code is not only the machine to see, we are also looking at. After the code is written, we review our code to find out what's wrong with the code, and to improve the quality of the code by refining the gaps. I believe we have a problem with pairing programming. Why do we have to pair programming, why can't we do it alone? There are many advantages of pairing programming, the so-called "three-line must have my teacher Yan", pair programming, can assemble two people's respective advantages, ideas, make better works. Of course, there will be no friction, but there will be a running-in to progress, in the process, to learn how to get along with people, in a team how to locate their role, and then play their greatest role.

Whether I am in the future or not in the work of software, the "Construction of the law" This is a great impact on my work, thank you for this book.

Some personal minor problems:

1, for the software engineering, girls can be qualified for what work?

2, do a good job of software engineering, what should we need to do?

3. What is the qualification requirement for the project manager?

4, teamwork is the basic requirements of each project, how should we locate their role in the team to play a greater role?

5, for want to do the user experience of the work, what books can be recommended?

The fifth time of software testing--experience