Chapter 29 integration Reading Notes

Let's talk about it first. Yesterday the computer added a 1 GB memory, which is now 2 GB. It feels great. The speed of opening live writer is obviously faster, and the mood of blog writing is also great. Today, code Daquan has finished reading 30 chapters and saw 772 pages. There are only 912 pages in total. It will be done next week. This is the second Original English book I have read on more than 800 pages (the testing chapter was not carefully read.

I am about to leave SK tomorrow, and I will go back to Ziguang. The biggest goods receipt estimation in the past two months is to look at the code, I also read Zhou aimin's book "The greatest truths to Jane", which is a very good book. It's all what I saw and thought, but I didn't have the idea of writing a blog at that time. I have not written down some of my experiences. I will try again in two days. There is also the recently released "dream breaking code", translated by Han Lei. When you go to bed every day, you should also write it after reading it. In the past, 800 words in high school compositions were a test for me. Now I have written a four-month summary, and one thousand words a day have greatly improved my writing. In the future, I will write a book like Zhou aimin and Han Lei. The title is tentatively set to "the art of ABAP programming" or "The ABAP programming lanaugae", which is definitely better than Huang. After a lot of other things, let's get started.

1.Importance of the integration approach

The most interesting part of foreign writers is that they like to use examples in their daily lives, or use the words of famous writers as the beginning of the article. to prove the importance of integration, take an image of the Washington University Stadium as an example. the image is as follows:

Steve McConnell is strong. He can think of integrated testing when he sees a pile of scrap iron. this gymnasium was originally designed with no defect. After being built, the stress of each place met the requirements. however, it is not guaranteed that the stress is within the tolerable range during the construction process. like our software, if we make a mistake, it may make the software difficult to test, it is difficult to debug, and so on, and eventually it will collapse like this stadium.

The author believes that inheritance testing is a very complex activity and should not be part of the test. in any case, we only need to recognize its importance. What name is not important. we can get many benefits from the inheritance test, but I still have zero project experience and I don't know much about it.

2.Integration frequency-phased or incremental?

This is a conventional talk about whether to conduct inheritance tests or incremental tests in stages. It is easy for stages, and it is okay for small projects. However, too many classes and components are tested for a large project at a time, which significantly increases complexity and makes it difficult to track and discover some errors. The incremental type is like a snowball rolling. One point at a time may be just a class, but errors are easy to find. In addition, if the same class has been inherited for a long time, it will be tested repeatedly to make the system more reliable. At the same time, the project manager can better check the project progress and control the progress. It is better to see that the system has completed 50% of the functions than to hear that the Code has completed 50%. The customer will be very happy to see that the functions of the system are implemented one by one. It is estimated that you will have a good time.

3.Incremental integration strategies

Incremental inheritance tests have many different strategies, but they are not optimal. It is more appropriate to choose one in different situations. I am very familiar with some of them. Let's introduce what I didn't hear in the software engineering class before.

• Feature-oriented integration

What is feature? I think it should be a system function. Each inheritance test is divided by function.

One problem that you may encounter is that a function may contain too many classes, so you can test the inheritance of a function in iteration. During iteration, you can use other methods to inherit the function. I think this method is clear and has the following benefits. First, there is no need for pile functions, and no additional code needs to be written. Each module called by a feature contains its own. The second reason is that the added features are relatively independent and complete, so you can determine that the project is moving forward steadily. Third, it seems that this method is born for Object-Oriented Systems and works well with object-oriented systems.

Of course, there are more than one integration method. You can view other methods on the code list. In practice, I think we can mix several methods to achieve better results.

4.Daily build and smoke test

I think there is a lot of talk in this section. Code is compiled every day to reduce project complexity. Update the version and make an error. It is said that Windows NT was developed in this way, even though building takes 19 hours. What's more unusual is that the office and Windows 2000 teams had a bpserver in the late project, and they had to fix it even if they found an error at a.m.