Answer your questions.

Answer your questions.

Chapter I.

question : Having and mastering a lot of expertise is not a qualified software engineer, so what should a qualified software engineer have?

my answer is: first, good programming ability. Programming ability directly determines the efficiency of project development.  This requires a software engineer to be proficient in at least one programming language, familiar with its basic syntax, technical features, and APIs (application interfaces). Second, self-conscious normative consciousness and team spirit. As software projects become more and more large, relying solely on personal power has not been able to complete the work, therefore, modern software companies pay more and more attention to team spirit. Generally speaking, software enterprises in the programmer can be divided into two, one is "guerrillas", they may be very familiar with programming tools, strong ability, the program is concise and efficient, but lacks the concept of standardization and cooperation, the other programmer's personal ability is not necessarily very strong, but the procedures are more normative, cooperative awareness is good. The second kind of person is more suitable for the modern software enterprise development trend.  For basic software engineers, their role in the enterprise determines that they must have a good sense of discipline and team spirit. Third, the ability to recognize and apply the database. Information is data-centric, so interaction with the database is essential, understanding the operation and programming of the database is one of the basic qualities required by software engineers.

Chapter II

problem: in the past, the teacher assigned to the homework, all the students are finished directly to the teacher, and did not follow the PSP table to count their time in this experiment, then we have to form a PSP from now on the habit of the table? What's the best thing about this habit for us?

my answer: according to the PSP protocol, the steps to improve the software process first need to identify the quality objectives, that is, the software will meet the functional and performance requirements and user potential needs. Then is the measurement of product quality, with the goal is not enough, the goal is only a matter of principle, is not easy to operate and judge, therefore, the target must be decomposed and measured, so that software quality can be "measured." Then it is understanding the current process, finding the problem, and adjusting the process. Finally, apply the adjusted process, measure the result of practice, compare the result with the target, find out the gap, analyze the reason, and make continuous improvement to the software process.

Chapter III

question: We have a theory of all aspects of our profession, but we have not practiced it, so how do we practice it? Which is the best way to practice?

My answer: we can take part in some of the school's software-related activities to practice the knowledge we have learned. This is also the best way.

Fourth Chapter

problem: Pairing programming This pattern has been in practice before, but it's not as if the two-person program spends a lot less time than one person, so how can we improve the efficiency of programming?

my Answer:1, write unit tests, improve efficiency, 2, training their own programming skills, 3, read more code and technical information.

Fifth Chapter

Question: This chapter focuses on the various patterns of teamwork and the development process of the team, and choosing the right team model is of course practical to consider and analyze, but what does a good team depend on?

my answer: good team, first of all must have a good leader, have the courage and perseverance, visionary, leading the whole team to progress. Then there will be a few elite in various fields, not too much, but must be "fine", such a person can top 10 ordinary people. Also, the team can have ordinary people, but must not have sinister designs, such people will certainly let the whole team back to shame. Finally, continue to strengthen their tacit understanding, see each person's merits and shortcomings, but also better cooperation.

Sixth chapter

Question: We now practice is 2 people pair programming, is not a team, the book said the team is weak can not force the agile set up, in order to avoid the emergence of this problem, we will create a strong team in the future? Can a strong technician get together and build a strong team?  

my answer: The most critical point is self, including your own heart, the attitude of the people. ways to handle problems. Ability to co-venture with others

。 Second, carefully select team members. Germany is the first in the choice of virtue. Entrepreneurship is hard. If team members are unable to face the difficulties in their own business, they will avoid and shirk. Or suspicion of each other, hostile words, must be finished. Therefore, the choice of members, to distinguish between the relationship, the most core members, must be the relationship between each other more harmonious. The character is better. Once again, in the creation, it is necessary to distinguish the responsibilities of the team, who should do, should not do what should be said clearly. Must have a final decision of the person. If you're going to lead the team yourself, pay more attention to this. It's hard to imagine a successful team without a clear mandate. Finally, in absorbing the team, it is best to consider the individual background, the same or similar background of people to work together more smoothly.

Seventh Chapter

Issue: This chapter focuses on the MSF (Microsoft Solution Framework) approach to the Microsoft Solution Framework. The great advantages of the MSF Agile Development Model are presented in section 7.5, and the software quality is high, but the next 7.6 sections say that the MSF CMMI Development model is better than the MSF development model, is the MSF CMMI more appropriate for today's development?

my answer: No. This is to take into account the results of their own team and the ability to choose a comprehensive factor to develop the model.

8th Chapter

question:8.7 divide and conquer, we all know that each person's ability is different, the attitude to the same project is different, or the team is not willing to stand up to carry, then what to do?

my answer: at this time to play their own leadership ability, if they have the ability, they stand out Luo, leaderless team is not a big deal.

9th Chapter

question: can there be more than one PM in a team?

my answer: yes.

10th Chapter

question: After we understand the user's needs, but we think and make the software will be biased with the user's needs, such as style, interface and so on, so how can our programmers get their ideas closer to the user's idea? Is it a situation?

my answer: It's a good way to set up a situation. We can also spend more time with the user to communicate, so that our ideas will be more and more close to the user.

11th Chapter

question: We are now at this stage is doing arithmetic app, if follow the steps of this chapter go down, every day to make progress update, and daily meeting also have daily build, will not quite accord with our present situation? After all, we can't just serve one course of time, and spend a lot of time on other courses.

my answer: It is clear that my view of the problem is not so, and there is no such time to torture, until we really pour into the company will do so.

12th Chapter

question: in a real project, we don't know which stage to start designing the user experience, so how can we be sure?

My answer: This I also very clear, need the teacher's help to answer. I think it's time to start designing the user experience when your team feels like you're doing it.

13th Chapter

problem: This chapter mainly discusses software testing, and introduces the function and function of various kinds of tests. and software testing is to make the software we make more perfect and more competitive. How do we quickly find bugs in the software we do?

My answer: generally do not meet the needs of users, or in the use of the process of causing inconvenience to users, think it is a bug. The words are a bit extreme, but the reality is that. Then for the new software testing novice quickly find out the bug in the software: 1, as soon as possible familiar with the company's product business, such as your company to do ERP software, you must be quickly familiar with the EPR business process; For example, your company is a court software, so you must be familiar with the court trial process, Only when you are familiar with the business process of the product can you quickly identify some of the important flaws in the software, and the software flaws you find are valuable. Otherwise, even if you can find some software defects, it is pure software defects, the value is not big.

The 14th chapter:

problem: This chapter mainly introduces the main content of QA, as well as the difference between QA and testing. In the cost control, tell us to control your own software development costs, time and money. If we are a new team, the first time to do software development, do not know the time and cost control at what limits, for this problem, how do we solve it?

my answer: I think we should look at other teams to do similar projects spent time and development costs, and then combined with the overall situation of their team to determine.

15th Chapter

Question: This chapter describes the software project's consultation and project summary, review and the software on time release of the various tricks, in the design change request, for the cut off the function of the trick, because there is a module can not be implemented, and we are now doing an app (arithmetic) , our characteristic function is that the user can enter the game mode after correct answer all the questions, but enter the game this function we can not realize, the demonstration is fast, we also adopt this kind of cut the trick, or replace the other function?

my answer: It should not be good to cut off. We can try to replace this feature with other features. If you cut it down, it will reduce the competitiveness of our app in the market.

16th Chapter

Question: This chapter focuses on innovation in the IT industry, and in the current era, it is almost impossible for us to come up with an innovative idea for ordinary people like ourselves. The book says, the key to innovation is the technology and to become an expert in the field, in order to innovate, only in this way can innovation be too high?

my answer: I think this is different from each other, some of the ideas are inadvertently thought of it?

17th Chapter

question: in the professional ethics, if our team has a programming technology first-class, is the core of the team, but his professional ethics, how should we deal with it?

my answer: first to confess with him, tell him to change it, really not. We also have two methods, one is to continue to endure, another option to leave the team, looking for new direction development.

Answer your questions.