Answer the questions you ask

Introduction to the first chapter, questions:

The book describes the detailed software engineering properties, we can know that the idea is that there is no perfect software, only more appropriate software. How can we truly judge the degree of perfection to a standard that can be published for this kind of software with different levels of perfection?

Answer: We should try to perfect what we can do to achieve the standard of release.

Chapter II Personal skills and processes, questions:

We know from the book content that our college students and professional software development engineers spend a great amount of time on the work of the ratio is very different, we generally think, how to complete the programming, and software engineers are more time spent on software requirements analysis and testing. What do we usually do to cultivate a level that is closer to the software engineer?

Answer: We can try to do more programming, increase proficiency, so that when programming only consider the idea, rather than spend a lot of time to figure out how to write code.

Chapter III Development of software engineers, problems:

The requirements of our programming are ordinary things to do--proficient! But in fact, we learn a lot of courses every year, and each subject has a lot of content, want to well consolidate the things that have been learned in the past is basically difficult to do, and my memory is very poor kind of-back an ancient poetry to about one months. I've been learning about almost 90% of what I've already forgotten. So how do you get a good grasp of programming this stuff with a lot of code?

Answer: Do more to be proficient.

The fourth chapter two people cooperation, the question:

The fourth chapter is the code specification and pair programming, for the pair programming, according to the mathematical point of view, the work efficiency of the two people is certainly higher than the individual, in fact, we are easy to know in the programming process, the two people's programming level and idiomatic code are not the same, So it takes two people to work together to complete a job that is actually much more than a person's workload, or even a poor result. This kind of programming may be necessary in the future of large software team design, but now we students start to do this really helpful to us?

Answer: The beginning of everything is difficult, a lot of trying to make two people better cooperation.

Fifth. Team and process, questions:

When we talk about teamwork, we have to look at the waterfall process, which is the focus of this chapter. We can discover all the things we need to be aware of in our team from this waterfall process. And every time you mention a leader, do our programmers not have to consider the problem of these team mode assignments, just write your own program?

Answer: It's better to have a good balance.

The fifth chapter team and process:

The fifth chapter has introduced to many patterns, the best team pattern should be Which?

Answer: is applicable to own group of ...

Sixth Agile Process:

Is agility a panacea? Obviously impossible, so, where is its inadequacy?

A: The shortcomings are negligible for their merits.

Chapter Seventh MSF:

MSF has not seen such a claim in previous studies, does it mean that this model is actually not very practical?

Answer: Maybe it's just a higher level of difficulty than it appears.

The eighth chapter (8.8): When it comes to drawing sectors, the goal we set at the outset is not to make much better, but to make smaller?

Answer: Start with something specific, and be more aware of the thrill of accomplishing your goal.

The Nineth chapter (9.4): PM's ability is very important, but always have "smart" in the same team, how should we get along with each other?

Answer: Deal with the people in the team is PM an important ability, the best PM ability is higher, have the ability to serve the audience.

The tenth chapter (10.2): How can we properly handle everyone's scheduling problems during the development phase?

Answer: It is necessary to work together. In particular, the front of the work, if dragged all the time will delay other people's work. So work needs to choose people with the right working time and ability to assign jobs.

13: Test performance data is a very deep field, the book also suggests that we need a painstaking effort to master, we students to grasp this is not a little oversupply?

Answer: For most people, the test performance data is really not a very simple question. But there is a need to deal with children's shoes that are interested in the computer industry.

14: How should QA and testing work be arranged for the team?

Answer: According to the actual staff's ability and free time to arrange it.

15: Can not achieve the expected function of the design, to be cut off, but if this is not to meet the work requirements?

Answer: The cut is only add-ons, the main function is to be implemented, otherwise it is not the completion of the design.

16: Our ability to grasp the code is not very high, for innovation, we should still belong to the unreliable it?

Answer: Actually we learned a lot of code. More will need their usual internet, the library continues to learn more deeply. Innovation is not something that is too far away.

17: For the team's contribution to the problem, may each have a different dispute, for the evaluation, there are efficiency, working time and other factors, how to achieve a truly impartial evaluation?

Answer: This need to be negotiated slowly, and according to the actual workload of each person to score

Answer the questions you ask