1. In general, we spend more time reading software than writing software. Because it is easier to write software than to read software, the readability of the code is particularly important. So how do we avoid unnecessary, misleading comments when we write a program, and write a note that helps others understand the program?
2. The needs of people in today's world are varied, and a software team with a keen sense of smell can capture people's needs accurately and comprehensively, thus designing software that meets people's needs. How do inexperienced software teams like us, which have just been born, get to know the needs of market customers?
3. A team of members of the software team work together to collaborate, in the book specifically introduced the project manager--pm this role, and proposed that the PM is in addition to development and testing all things. However, the positioning of this role for me is still too vague, there are no classic PM work examples?
4. After the completion of a software design, the software should not be updated and maintained according to customer's requirements during the product use. When we write software design and code, how to avoid the major changes in the late stage of product development resulting in the chain reaction of other modules, improve the maintainability of the code?
5. We all know that an online game will be on the inside again beta, but also constantly encourage players to find and raise bugs. Testing after a software development is complete, debugging is essential. So how do we do efficient testing, not exhaustive, carpet-type testing?
6. A division of software team members collaborate. However, in the software development process, the work is often not at the same time. How we should fully coordinate the working relationship between members, so that members can learn as much as possible about the software development process, rather than just learn the part of the work they are responsible for the knowledge and experience.
Question: How do the words "Software" and "engineering" appear? 1958 Turkey is presented in the paper "The Teaching of Concrete mathematics". First seen in Richard R. carhart,1953. Software engineering, 1968 North Atlantic Treaty Organization meeting in the former Federal Republic of Germany presented.
#个人博客作业Week1-Six questions and software and software engineering proposed after viewing the textbook.