Experiences of software quality assurance
First of all, the importance of software quality assurance is self-evident, the book says software quality in the following areas
- The visibility of the software development process
- Risk control software development process
- Internal software module, an intermediate stage of the project delivery quality factors of project management tools
- Software development cost control
- Completion of the internal quality indicators
Have a mature theory to measure various software engineering quality --CMMI (Capacity Maturity Model Integrateg), that is, the set of Capability Maturity Model.
At the same time to achieve a certain degree of software quality comes at a cost, to develop new features is important, but also must invest a certain cost to ensure the quality of the existing public to solve the problem. This is the team of people to various departments to do.
Whether QA (Quality Assurance) or Test is for the quality of software for security, we should not be too open to independent. A clear division of labor is certainly important, can improve the efficiency and quality of work, but I feel that " cooperation is the basis for the division of labor ," the book to illustrate the importance of using football division, said there is focus on the attack, have focused on defense. But regardless of offense or defense will always be a team as a whole, competitive sports even more so, in fact, you have the world's best striker, the best personal capacity, there may be a defensive formation get bruised and battered. Also, even if your personal ability to defend better, there may be several mass cut easily tear defense. Teamwork is the basis of division of labor , division of labor is not a good fit only added trouble for no reason, by more than a problem. Zou teacher has a few points I think that's very good in summary:
- In the initial stage (a new project, a new team to enter the field, who has just entered a new project), each team member should try to get through all aspects of multi responsible for all the things they get to know the culture generalists.
- When the project / industrial development to a certain stage (included in the trench warfare of the time), we should vigorously promote the division of labor, training professionals.
Only when you have an understanding of all the work processes in order to realize their own positions on the fundamental essence. QA (Quality Assurance) itself includes Test, so I think both of these two should not conflict itself is not completely independent.
If I were a QA project, I think my job responsibilities are:
I think a good QA must be able to understand the full range of projects from development to testing needs, people do not understand the development of QA is necessary to do well, but in fact, regardless of QA (Quality Assurance) or are for the Test quality software for security, should not be too open to independent. As long as the fundamental understanding of the development, master the development, in order to better quality assurance, the same should also know Dev test, two species itself two complementary positions in order to establish a clear division of labor in doing good and basis.
If I was a project manager, I think I have a project does not require an absolute full-time QA:
There is a saying in the article is particularly good:
Do not understand the development of the people must do well test. Just do not understand the development of R & D Manager R & D team as necessarily a bad tube. I feel more and Dev should do the test should be the most suitable candidate, it must be the future trend (because I have seen the progress of Chinese programmers, compared to 10 years ago, today's programmers have a very comprehensive , come back ten years, must prove my point right).
Yes, people just do not understand the development of QA should do well, on the basis of a project itself, those who do not understand what can go to maintain his quality as a QA developers do not have to be like Daniel, then it must be proficient have their own understanding, which is like the NBA is excellent, the legendary coach is not necessarily a good basketball player but he must have a deep understanding of themselves, have their own ideas. So I think that should not exist absolutely dedicated QA, QA, even if such work would not be able to integrate into the team, good coordination between the various departments. QA is to ensure the quality, but the quality is not tested out of control if you do not do a good job requirement analysis, software design, code implementation. We had plenty to talk about just what the test is found to ensure the BUG only. Questions about QA and Test above I have already mentioned the cooperation is the basis for the division of labor, regardless of QA (Quality Assurance) or Test are in as guarantee for the quality of software, should not be too open to independent. It also does not mean no one is responsible. Team is the need for the person in charge, the team's test itself is a cooperative, problem is the responsibility of the team, as head of the team must be held accountable, finishing the entire team to identify and resolve the problem.
2019-09-22 13:18:38