The first ~ the fourth chapter:
1, is not sure to understand the procedure, the procedure to understand the new members to read as soon as possible to understand the procedures of the design, then if the existing procedures are very large, very complex, do not understand its programming ideas, new members to read it is not to spend a lot of time? It takes energy to learn new things, isn't it a waste of time and energy? (chapter I P4)
A: If the team has a new addition of new members, for the existing procedures, to reduce the time and energy waste, you can write the program I give a general explanation of the new members, or if a team has been formed, it is best not to add new members, Or try to gauge the manpower needed by the team before the project starts, and don't change the number of members once they are formed.
2, how to write unit test? Does every program have to have unit testing? What are the methods for writing unit tests? If a program can have a lot of problems with its budget, is it not every possible mistake to write unit tests? If the unit test was written incorrectly, wouldn't this unit test be useless? (chapter II 2.1.2)
A: Unit test is divided into white box test and black box test. A unit of popular meaning is a function that implements simple functions. A unit test is a test function that uses only a specific set of inputs (test cases) to function properly and returns the correct output. White box testing is the core code of the program packaging, and placed in a new class, in the core code class in the unit test, select the function to test, verify that the test results are consistent with the expected, if not consistent, it may be a bug in the program; white-box testing to have a test coverage type (including statement overrides, Decision Overlay (also called branch coverage), conditional override, decision-conditional override, conditional combination test, PATH test) While black box testing is the fault tolerance of the program, such as input box input type is a number, if the input character should be prompted by the corresponding error, or input number range overflow and so on.
3. Is it a good software engineer to be a self-assessment every time? (chapter III 3.2.4)
Answer: Yes. To be in time to conduct self-assessment, improve the ability to identify problems and solve problems, and evaluate their own communication skills, such as product, design, and subordinate communication.
4, code specification is not required in the code to pay attention to the format, so that the code looks clear, good-looking, easy to understand, if there is only one statement, the curly brace is not writable, such as P58
if (condition)
DoSomething ();
Else
Dosomethingelse ();
, the Judgment statement if () after only one statement, without curly braces and curly braces, sometimes a different result, which is why? (chapter fourth 4.2.4)
A: It is best to write, write a guaranteed percentage yes, it is difficult to ensure that the problem is not written.
5. What is assertion? What is the use of assertions? How to use it? (P63 4.3.3 2nd)
A: When writing code, we always make assumptions that the assertion is used to capture these assumptions in code, that you can use assertions to create more stable, better quality, and error-prone code, and that you can use assertions when you need to break the current operation with a value of false. Unit tests must use assertions (JUNIT4).
6, what is called the package and efficiency? (P64 4th and 5th)
A: The idea is to take care of several aspects at the same time, so the combination of packaging and efficiency is to be able to take care of both package and efficiency, now look at this problem only to find that I understand the wrong words.
7, teamwork is the team members assigned to each of their own sections, design good after each person responsible for the process of building together, so there will be no confusion? Because a project is very large, the code is thousands of or even tens of thousands of lines, if everyone is working together, then each person completed a specific program, how to put the respective responsible program, everyone's programming ideas and ideas and styles are different, so that does not create confusion and difficult to find out the problem? (chapter Fifth)
A: Since the team is doing the project, it means that there is already a lot of experience, know how to do the project, how to piece together, so with experience, there will be no confusion.
9, name a variable must prefix name? What happens when you do not add? How to add?
Answer: This is not necessarily, see what language, each language has its own naming rules.
Chapter V-Seventh:
1, how to the various modules through manual or automated means, the executable system to build out? is the validation module included in the build? (P95 5.3.4)
A: To implement the workflow, the engineer implements the design of the previous output as planned, submits the developed components, together with the validation modules, to the system, and the engineers integrate the results generated by the individual developers and build the executable system.
2, in the configuration and change management, how to do parallel development and distributed development? (P95)
A: Create a complete, comprehensive configuration management infrastructure that effectively oversees all types of projects. This management infrastructure should not only include a sound management system and normative standards, but also include a software configuration management system for efficient implementation of the above management tools, as well as other related expansion areas, to lay a solid foundation for future long-term development.
3, the agile process is probably meant to supervise each other, learn from each other, and make common progress. (chapter sixth)
A: The agile process is a collection of values and methodologies, but it is also a member of the team to learn from each other and progress together.
4. Can MSF solve all the problems? What if there are problems that are difficult to solve? Is it possible to solve all the problems that may occur in the software? (chapter 7th)
A: This I do not know, I Baidu to find a bit did not search the corresponding answer.
Section 8~, Chapter 10th:
1, do the project to understand the user needs is the most important, but if the user himself can not describe what he wants, or the user just about the needs of their own, and the project personnel can not understand the real needs of users, how to do? (Chapter 8th 8.3)
A: Let a person with a strong understanding of customer requirements to communicate with customers.
2, if a team has been decided, then if the team can not find the right person to do the project manager, then still want to find a team in the project manager or to find another is suitable? (Chapter 9th 9.4)
Answer: Can not find the right to exercise their own ability.
3, analysis of user needs, whether you need to write a document to explain? Or is it just a verbal communication between people on the team? There is the team to do a project, need to prepare so many instructions? Both the specification, but also the function of the manual, that if the completion of these will not be time-consuming, is not as long as the team to do the project to follow this process? (chapter 10th)
A: I think it's best to write a document and write it before remembering the customer's needs. The best way for a team to do a project is to follow the process so it doesn't get messy.
11th-12th Chapter:
The 11th Chapter Question: The development stage also has the daily management, thus does not waste the team to do the project the time, does a project to do the sprint plan, but also the daily regular meeting, as well as the specification, the function instruction, the column typical user and the typical scene description and so on, when these completes, determines still has the time to make the project? (chapter 11th, section 11.2)
A: The team that developed the project has already done the project, has the certain experience and the ability, will not be very time-consuming.
The 12th question: the user experience and quality, sometimes do not do well at the same time, then the two of the one important point? Which one is to be sacrificed and which to take? (12 chapters 12.1.6)
A: Experience is a part of quality, depending on the characteristics of the project, see the situation.
13th-17th Chapter:
The 13th question: Software testing has so many tests, in case there is not enough time to complete all the tests, then which software testing is the most important, and the completion of a project will take a lot of time, really enough time to complete all the required software testing? (Chapter 13th 13.2)
A: This I do not know, for the software engineering I understand is not very thorough, is not very clear, but probably know some of the software engineering processes and methods and concepts, ideas and so on.
Question 14th: What is performance? What do you mean by optimizing role performance? (14th 14.2.2 Question III)
A: Performance is the result of a person's work in the team.
The 15th question: How to develop the user, industry, software development insight? (chapter 15th 15.1.1)
A: More practice, practical knowledge, a lot of things to do before you know the effect.
The 16th question: How to practice innovative tricks? (Chapter 16th 16.3)
A: You can refer to other people's innovative results, and then think more about themselves, more hands-on, more attempts.
The 17th question: Is there a fair and acceptable performance appraisal method that everyone is willing to accept? (Chapter 17th 17.3)
A: I think there should be no.
Software Engineering Questions and answers