Software Engineering--The Fifth Time blog assignment

The method of construction: Modern software Engineering--review

I am a student of software engineering, this semester we have studied the course of software science, the textbook is used by the Xin Zou teacher to write the method of construction of the book. After learning the contents of the inside, the feeling of their own learning is very helpful, so here are some after reading this book a little bit of experience and everyone to share, hope to be able to exchange together!

Before I read this book, the software engineer in my eyes was working quietly in the office knocking at the code. But after reading this book, only to find that my idea is really naïve, code writing in a project development is only the tip of the iceberg, the project development of the writing requirements, code writing specifications, code review, and after the completion of the test phase and test report, as well as after the project delivery, post-maintenance. These are a good project must be indispensable link, and no matter which part is sloppy, must be quality and quantity of the completion.

The construction method is really suitable for rookie advanced book, the content of the book is easy to understand, and with a lot of practical examples, which makes it easier for readers to understand, such as in the 17th chapter of the book-people, Performance and professional ethics, the use of pig, chicken and parrot story to explain the Rasci model, funny cartoon characters Makes it easy for me to understand the RASCI model:

R: That is responsible, responsible for the specific things done.

A: That is, accountable, responsible for the task, have the right to approve.

S: Supports, support for tasks, completion of auxiliary tasks.

C: Consulted, consulting, the role of having the information or ability to complete the project.

I: That is informed, the person who knows, should inform the role of the result in time afterwards.

In addition, there are a lot of other interesting examples to explain the points of knowledge, interested in you can go to see.

The 4,5,6,7 of this book introduces the teamwork that has given me a lot of feeling that it is impossible for a good project to be done by a single person. Even if you are a Daniel in this area, one's strength is always the enemy of a team. Of course, the team here refers to a good team, not just a few people to make a team. A good team should be able to follow the basic principles of MSF: to promote information sharing and communication, to work for a common vision, to be fully empowered and trusted, to be responsible for the project, to deliver incremental value, to remain agile, anticipate and adapt to change, to invest in quality, to learn all the experience, and to work with customers. Everyone on the team is doing what they need to do, and it's good to follow the MSF principles, so a team that makes a project must be quite perfect!

The above is I read the book after a little experience, finally I have a few small questions, I hope to share with you:

1. Question: In what way can we begin to develop our own development thinking and ability at this stage, to move towards the engineer?

2. Question: Is it important to require code coverage to reach 100% in unit testing?

3. Question: The importance of the team is highlighted in the book, so how do you choose the right people to form a good team?

4. Problem: When a team has a discordant voice, such as complaining about the uneven distribution of work, what should be done?

5. Question: What is the best way to improve the normative aspects of code writing?

Software Engineering--The Fifth Time blog assignment