The method of construction reading notes (i)

It has been 5 weeks since I studied software engineering, and through this five weeks of study, experimentation, and reading I have a certain understanding of the Software engineering course. Let's take a look at how I feel recently through the reading process of the book "Building Law".

Through the reading of spare time, "the construction of the law" This book I have read the first 4 chapters, through the four chapters of the reading, in addition to the basic concept of software engineering understanding, I think I harvest the most is the software engineer in the company's positioning and development has a great understanding. Software engineering is the process of applying a systematic, orderly, quantifiable approach to software development, operations, and maintenance. Software engineering includes software requirements analysis, software design, software components, software testing, and software maintenance. Software engineering also covers many other disciplines. This shows that software engineering is not what we usually learn about the fixed computer related knowledge, but a method, a method of application. It gives a detailed list of how a project is designed, what knowledge is used in the process of completing the project, and what methods are used. These are based on different projects have different detailed design, and what we are learning is to summarize these detailed design methods summarized things. Can be said to be a kind of thought, he is not invariable.

By studying the software engineering course and reading the law of construction, I am impressed by the following points:

The first is a new and more correct understanding of the concept of bugs. I used to think that the bug is a software vulnerability, failure, in the normal operation of the software will appear unknown error. In fact, this idea is not correct, the bug can not be defined as such. The software industry has such a famous joke: (BUG) This is not a flaw, this is a feature. The so-called bugs are different for different objects. Some people's requirements for a software or a feature are not very high, so when he brought a simple software to use, the software to meet his needs, then his experience of the software should be very good, but when the other time, he asked for a feature higher, But he did not know that the software does not support the functionality he envisioned, so when he uses the software is not a good experience, he may say that the software has a bug, then this software is really a bug? By the above, you can basically explain what the bug is.

Secondly, I have a clear understanding of the personal development process. Carnegie Mellon University designed a set of model--PSP (Personal software Process) for software engineers. The latest software engineer's Task List (PSP) is this:

Plan Estimate how long this task will take	Note
Development Analyze requirements Creating a design Document Design Review Code specification Specific design Specific code Code review Test
Elapsed time of recording
Test report
Computational effort
Summary afterwards
Propose Process Improvement Plan

Through the reading of this table, we can clearly understand the personal development process should be noted in the pen recorded things, these things can continue to improve the level of our design, and this is our study of promotion records and vouchers. So it's important to say these things. In addition, in the development process of development testing is a more important thing, do not do too much interpretation of the record, the following should be more detailed elaboration.

Let's take a look at how software engineers have grown:

1, accumulate software development related knowledge, improve technical skills. For example, the mastery of a development platform.

2. Accumulation of problem areas only and experience

3, the general software design ideas and the understanding of the engineering concept

4, improve professional skills, including: self-management ability, expression and communication skills, and the ability to work with people, according to the quality of the implementation of the task, these capabilities in all areas are very important

5, the actual results. Product display and market share and so on.

These aspects are important for a junior software engineer. In addition, the professional development of software engineers also have many models, but based on our current status of college students, only the grade of the road this model to a certain extent, more suitable for us. We can choose the right to say that there is a certain amount of gold qualification examination to test grade.

The fourth chapter is about the cooperation between two people, this chapter focuses on how the two people should cooperate, the relevant methods of cooperation between the two people and the stage that may go through. These for the present we still have a certain distance, of course, with the help of teachers, we have experienced a two-person cooperation experience. Through this experience, I do recognize the advantages of co-development, but I think these things are carried out on a certain basis. The basis is that we have a relatively deep personal development technology, only in this way, we will be in the development of cooperation can be harvested from the things that should be harvested, such as the experience of cooperation, the process of cooperation and so on. When our own development ability is relatively weak, the focus of our development process is not cooperation, but the respective mastery of the relevant technology, which is not contrary to our original idea, I think so for the moment, may be wrong, maybe I do not have a better understanding of cooperative development. Instead, in this chapter of the study, I harvest the most is the code, which is the basis for cooperative development. At the same time this code for a person is also a specification, a ability to improve, I think this training is in line with our current situation, because our code should be said to be no specification. Of course, the introduction of cooperative development is also very important, this is facing the graduation we are very good guidance, if not this part of the introduction, we will experience more difficulties after work, I am very fortunate to learn this knowledge.

Through these 5 weeks of study, I think I have gained a lot of things, and later on employment also have a clearer understanding of the past. Have a more definite goal for the development of the individual. These will reduce our tension and pressure on employment to a certain extent.

The method of construction reading notes (i)