Book notes in the Building Method

This time I personally read the book of choice: the method of building: modern software engineering (xin ). We also refer to the structure, content, and methods of this book. Reading this book is not only a review and refinement of the learned knowledge, but also a preview of future courses.

The following summarizes several points that are difficult to understand or have doubts during the reading process, some are details, and some are big methods. Then I searched for and learned the relevant content on the Internet and shared it with you.

 

1. Chapter 2 cooperation between two persons-4th code design specifications-4.3.3 error handling

The concept of "assertion" is mentioned here, but there is not much ink.

The problem is that the excavator ...... No. What is an assertion?

When writing code, if the programmer believes that a certain expression value (Boolean) at a specific point in the program is true, it can be labeled as assert ).

Example:

Public class assertiondemo {

Public static void main (string [] ARGs ){

Int I; int sum = 0;

For (I = 0; I <10; I ++) {sum + = I ;}

Assert I = 10;

Assert sum> 10 & sum <5*10: "sum is" + sum;

}

}

The assert I = 10 asserted I value in the preceding program is 10. If the I value is not 10, an assertionerror exception is thrown. Statement assert sum> 10 & sum <5*10: "sum is" + sum asserted sum <5*10. If it is false, an assertionerror with the message "sum is" + sum is thrown.

If it is certain that something is going to happen, you can use assertions. If there is another possibility, apply if ...... Else processing.

Assertion Verification can be enabled and disabled at any time, so assertion can be enabled during testing and assertion can be disabled during deployment. Similarly, after the program is put into operation, the end user can re-use the assertions in case of problems.

P.s. This problem is not enough personal knowledge. I didn't know the concept of assertion before.

 

2. Chapter 4 team and process-5th development process-5.3.2 Waterfall Model

The waterfall model defines various activities of the software life cycle as several stages of work connected in a fixed order, such as Waterfall flow, and finally gets the software product. It was proposed by Winston Royce in 1970 and was the only widely used software development model until the early 1980s S.

 

Book notes in the Building Method