Chapter I. Essays && Study Questions

The law of construction has already been handed, but has not yet begun to look, only to look at the first few pages, and the traditional teaching material is very different, there is no large space theory, than the textbook looks interesting. The first chapter also mentions the origin of the ' bug ', the first time I heard it, it feels very interesting.

The first week of class teacher asked what is software, students think software is a program, I think so. But why would he call the software instead of the program? For the program, the more common definition is: program = algorithm + data structure. But can the algorithm and data structure compose software? The answer is not enough. Therefore, in the introduction of software engineering, it is defined as a complete set of programs, data and related documents (software = program + data + documents). The program can not enter data, can not have documents, but the software does not. Software is to be based on the user's input requirements, the calculation, the results are fed back to the user, so the software to be composed of data. At the same time, the software needs to be maintained, if not documented, such software must not survive long. As the software becomes larger, the code becomes more and more, there is no document-assisted interpretation, and for the subsequent software engineers, it is difficult to understand the previous procedures, it is difficult to maintain the perfect. In the beginning of the law of construction, the definition of software is also given, which defines software as Software = program + Engineering. By comparing the two concepts, we can introduce a conclusion: Software engineering = data + documentation. If that's the case, then there's no difference between the two definitions. What about software engineering? The book also introduces, the core of software engineering is the construction of management, source code management, software design, project management and other related software development activities. Think about it as a combination of data and development documents, so the definition of software in the two books is virtually indistinguishable.

\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\ Split Line \\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\

On how to measure individual performance in a team

The first thought is certainly who does the part of many, difficult, who's cent high. But then there are a lot of questions.

1. How to define the workload or efficiency of each person

If you only use the working time and the number of lines of code as a measure, it will cause programmers to deliberately write the program complex and lengthy. Only 3 instructions can be done, in order to increase the length of the code can be increased to 10, 20, but this for the whole project is not only not good, but also bring harm. The shorter the better the code, then can we evaluate the work of the members according to whose code is short? This is also not possible, first of all, the group of each member of the task is not the same, a little task is more complex, a little more simple. Then the corresponding code must be different. And if you deliberately reduce the code, there are likely to be potential bugs. I think this part is not very well defined, so my strategy is not to consider this part.

2. About working hours

Obviously, working hours are not as long as possible. So my strategy is to stipulate the working hours of each member, to punish the absence and not to complete the task, to work longer than the individual's planned time, not to punish, and not to encourage, just finish the assignment on time.

3. About the difficulty of the work

Who solves the key problem, should get more score. However, the tasks assigned to everyone are different. If you want to get this part of the score, then everyone will be asked to do the hardest part, who to do the simple task? And not everyone can solve it. So, for this part, my idea is that each team member's results are the same, the leader according to the group project results than the members of a little more points.

Finally, my conclusion is: personal achievement = Group Score + Team leader plus points + unfinished task deduction

Chapter I. Essays && Study Questions