The method of construction read Note 05

The 15th chapter of the Law of construction gives us a brief introduction to the stability and release stages. As the book says, the final stage of the software life cycle is often the most Test team, not only Test team project management level, resilience, but also test the team's "blood type." The planned software release time is coming, but the software still has a variety of problems, what should we do? First of all, we should be able to recognize the shortcomings of their own software, can not be any software will be flawed as an excuse to deceive ourselves. Then we should form a group of consultants to diagnose the various bugs in our software and discuss the corresponding solutions. After the release of our software, I think the hindsight meeting is essential for summarizing the meeting. When all things are done, looking back at what we have done, it is not difficult to find ourselves and the team's shortcomings, we should make a timely summary, so as to benefit the team and personal progress.

The 16th chapter of the Law of construction tells us about innovation in the IT industry. Indeed, today's society, where all the need for innovative talent, our IT industry is no exception, in my opinion, only innovation can promote development. First of all we have to seize the opportunity of innovation, not when innovation will work. Our innovation should be to push the software to higher quality and better market, so innovation is not blind innovation, we need the purpose. In my opinion, we do not need to deliberately innovate, everyone has their own different views on everything, in fact, this is a form of innovation for everyone, but some of the innovative good and some useless. We should find innovative inspiration in our hands-on practice, and incorporate it into the software development process, which may have unexpected gains in our software development.

The main content of the 17th chapter of the Law of construction is people, performance and professional ethics. First of all, it's a matter of being a man. People can be divided into two kinds, the people who do things, the people who do not do things. And the people who do things can be divided into a lot of things, serious people, do fake things, pretend to do things people. Different people will have different performance, and so, there is what we call the work ethic. Performance, from the management point of view, is the result of organizational expectations, is the organization to achieve its objectives to show at different levels of effective output, it includes individual performance and organizational performance two aspects. Only those who do things seriously can have good performance, that is to say, we can guarantee the quality of our software. But also because there are those who pretend to do things and do fake things, there is a professional ethics so. I personally understand from the simplest point of view, I think our software engineer's professional ethics, is actually responsible for our software.

In the past, I can say is a relatively lazy people, so do not like the trouble, such as things done well and not good at summing up, the lack of innovative ideas feel trouble. Now I think that this is not only a bad influence on my personal growth, it is possible to find a job in the future have difficulties. The so-called software engineers have their own professional ethics, we do software engineering students, but also to have their own as a student of consciousness, right, anyway, we should be able to make themselves better in the direction of progress.

The method of construction read Note 05