PRACTISE3 read the law of construction 1-5 chapters

Chapter One: Introduction

This chapter is mainly about the basic concept of software engineering, the ultimate goal is to create "good enough" software.

Ask the question: What is a bug? (from 1.2.5 knots)

A: As far as I am concerned, in many games also have many bug,bug this word in the network game to belong to the high frequency word, the Chinese meaning is "the loophole", in the game these bug loophole often will bring to the player very big harm, will cause the game unfair, the game is also a large-scale software, So a game almost every week maintenance updates, mainly to repair the bugs in these games. In the book, the bug is simply that the behavior of the software is different from the user's expectations, which is called a bug. Easy to understand, the bug will appear in a test, a program it may be written by a person, it may be a team, or a larger team, even so, but when he put into the market for users, the face of a larger group. Each person has their own ideas, in the use of your software will have a different view, will produce a bug, so we write software people or team, to humbly collect users of the bug, and finally make the software closer to the user's satisfaction, such software can be done for a long time.

Chapter II: Personal Skills and processes

Ask the question: What is unit testing? (from 2.1.1 knots)

A: In my opinion, testing is an essential part of software, and unit testing I initially understand is to set up a test method for "one problem", that is, this method is suitable for you to enter various data, test compliance standards. I have been in Shenzhen, a foreign company "Yu Ke global" for one months of summer work, in which I am an operator. This company is to do computer hardware company, mainly to do the storage data of the disc (Western data), and operators also have a lot of different division of labor, an empty magnetic film to be unpacked, clean, run oil, grinding, ultraviolet irradiation, testing, packaging. Each link needs to learn the relevant knowledge of the operator, and I happen to be assigned to the test link, wherein the test is the most important part, which determines whether a magnetic disc can achieve normal indicators to packaging sales. Each operator will be eligible for action after one weeks of study. In the testing process is a machine in the test disc, the entire dust-free operation of almost 90% of the machine is in operation, of course, the machine is also a person to do, each machine has two computers, each incoming disc has to enter the physical test (Glad) and performance Testing (MAG), in line with the specified indicators to the factory. I think every machine is like a unit test. And I think the unit test of the software, although not so large machine, but the nature is similar.

On Baidu found the official definition is as follows:

Unit testing is a small piece of code written by a developer to verify that a small, well-defined function of the code being tested is correct. Typically, a unit test is used to determine the behavior of a particular function under a particular condition (or scenario). For example, you might put a large value in an ordered list, and then confirm that the value appears at the end of the list. Alternatively, you might remove characters from the string that match a pattern, and then confirm that the string does not actually contain the characters anymore.

Chapter III: The growth of software engineers

Ask the question: Do I have the ability to have a software engineer now? (from section 3.1)

A: Measuring their ability is a very important process of growth, people have to know well-known "the Enemy can victorious." Now if I like the book Twist Rubik's Cube example, I feel that I am still in the first layer, still in the foundation layer, now I am not very solid foundation, so to work harder to lay a good foundation for the future life of the road to pave the way. So, now I obviously do not have a software engineering ethics ability.

The fourth chapter: two people cooperation

Ask questions: How to improve work efficiency in two-person cooperation? (from section 4.6)

A: In practice II, I ended up with my little partner to program, and gained a lot. In the beginning, the two people should make their own views, respect each other's suggestions, write a preliminary plan (like the beginning of the book), and then in the process of writing code will appear differences of opinion, to control their own emotions, compare their views, or combine the opinions of two people to propose new ideas (like the book in the running-in phase). Finally, after the program has been knocked out will be tested, some code format specifications, vulnerability issues, or new idea, can be added in this phase (specification phase), the final completion of the program (creation phase). To do these four links, I believe that can effectively improve the efficiency of cooperation between the two people. In the process of cooperation between the two people, I enjoy the process, enjoying it. So, having a good attitude to do things is also good.

Fifth: Teams and processes

Ask questions: What is the model for Team software development? (from section 5.2)

A: There are many models available in the book, with Nest Bee mode, attending physician mode, star mode, community mode, amateur theater mode, Secret Team, spy team, Symphony mode, jazz mode, functional team mode, bureaucratic mode and so on. So many patterns make me very confused, how to choose the corresponding model to make the team development smoothly? How do they work together in different patterns?

PRACTISE3 read the law of construction 1-5 chapters