The method of construction read Note 06

This was the time to read the remainder of the law on construction.

The 14th chapter is to undertake the software testing of the former, and to talk about the work of software quality assurance. The author first introduced the software quality measurement can use CMMI, but also said that the quality of the cost of protection (prevention, evaluation, internal failure, external failure), software testing and quality assurance is different. Software quality assurance includes testing.

The 15th chapter-the stability and release phase, the author of the code issued when the issue may be encountered in the list, but also on the timely release of the tricks DCR, ZBB, the final project summary and review. It can be seen that software engineering is not just the completion of code, as a project, its life cycle has not ended.

16th Chapter--it Industry Innovation, innovation is the hot words, every day can hear see, seize the opportunity of innovation is very important, and innovation is constrained by many factors.

The 17th chapter-People, Performance and professional ethics. There are 3 kinds of people in the software team, pigs, chickens and parrots. The pig threw himself into the work, while the chickens were only part of the energy, and the parrot was moving mouth skin. In fact, most people in life work want to be a parrot, but just want to get something for nothing is wrong, in school can rely on friends, but the future work without strength, work may not have. We hope that our team can do their best to make the program. The cooperation stage of software team has sprout, running-in, norm, creation and so on. All industries have their own professional ethics, software engineers are no exception.

Read the "Construction of the Law" on the software engineering has a deeper understanding, Xin Zou Teacher This book, written not as rigid as the general textbook, lifting and more extracurricular examples and software engineering knowledge combined. The contents of the book from the introduction of "SOFTWARE = program + Engineering" began, first individual programming to two people and team cooperation. We also talk about all aspects of software engineering, such as requirements analysis, design implementation, testing, and so on. The process of software development can not be separated from people, programmers and users are important participants in the process.

Finally, in my reading plan, I asked the following questions: Http://www.cnblogs.com/a1397240667/p/5247236.html

1. How to determine if a software is "good enough" and can be released?

Obviously, the software release is subject to all aspects, not the programmer feel technically perfect can be called "good enough", the actual need to consider the duration, budget and customer needs. In order to meet the most important needs of customers, but also in keeping with the changeable market. There will be some, we can only complete the relatively good software.

2. Personal software development process the PSP relies on the engineers to collect data for analysis, so this process ensures the authenticity of the data?

As far as I'm concerned, it's hard to keep going. Therefore, the implementation process of self-consciousness is very important.

3. There are multiple modes of teamwork, how do you determine the appropriate model for your team?

The manager of the team needs to have a clear understanding of the characteristics of the players and explore in the process of cooperation.

4. The modern software engineering methodology can be broadly divided into the two major camps of heavy methodology and agile methodology, how to choose the appropriate software engineering methodology?

The emphasis on methodology emphasizes upfront design and design for the future, while the agile methodology emphasizes that it is designed only for the present and reconstructs it in the future, and that the most essential difference is the basis for the right choice based on the actual characteristics of the project. The requirement analyst should be based on the understanding of the business area, correctly judge the characteristics of the project, for the development team to choose the appropriate software engineering methodology to make recommendations. and Xin Zou's blog also gave advice on how to determine http://www.cnblogs.com/xinz/p/3852390.html

5.MSF fit for the team inside the university?

As the course learns, I think MSF is a good model, but it's not easy to implement in a team. The current students ' attitude towards learning is mostly "coping", and when programming, most of them are programmed by one person, others are watching.

The method of construction read Note 06