The third software engineering jobs - Preliminary Software Quality Assurance Bowen

 

1) After reading textbooks and reference materials about software quality assurance What is your experience is?

As a matter of principle ① QA personnel should have, when the view is inconsistent with the team, to fight each other on the basis of compliance with the fundamental principles of

Compromise, can not say how the project went with what. Can not hang conventions, may be achieved in the case where the same effect, simplify the process,

This requires master "degree."

② Software Test (Test) and software quality assurance (QA) is very different

      Software quality assurance work (Quality Assurance): software team to make the software meet the quality standards defined in advance and

All activities, including testing.

       Software Test (Test): the use of certain processes and tools, the software enables verification functions and features pre-designed work

Processes are generally and quantifiable results.

③ quality management core idea is to prevent, is expected to take the initiative to communicate with their team when they could possibly go wrong, do not wait for a problem and we have to intervene,

QA CMMI is a product not to be seen more and more now CMMI, agile aspects of the transition to the mainstream, so the QA must adapt to the trend,

Try to grasp the agile coaching skills.

④ QA is the role of service-oriented, and when you ask questions to each other, how do how to project, whose heart will be uncomfortable, natural

There exclusion heart. And because the issues raised basic QA process specifications are mandatory execution, so the two often conflict, which is

Normal,

   (2) If you are a QA project, what do you think your job responsibilities?

① the initiative to understand all aspects of knowledge, we want others to accept, first let itself become stronger than the other. It does not require mastery of knowledge,

But to have a basic understanding of, for example, you do not understand the code, but the code can understand the static checking, code review and other aspects of knowledge.

② Communicate, communicate in order to achieve mutual understanding, so that project team members understand the meaning of QA work, but also to understand the QA team members

The true role and responsibilities in the project group.

③ guidance and training, although usually not in the guidance range of responsibilities in QA, but in fact almost every QA afford to be part of this party

Work surface. Training project implementation process, guidance mainly some targeted work to explain the process to follow which refers to training activities

Use south files, etc., is intended to help project team members to master the skills and methods of work as soon as possible, improve quality, speed up the progress.

④ supervision, audit and supervision of QA is the "original" work, you need to pay attention to the problem is found in audit oversight is to be timely feedback to the project by

Li, requires project managers to solve problems, not only do not directly manage the project team members, do not have to be reported to senior managers

⑤ consultant, if a company just over CMM certification, QA that will certainly dealing with consultants. There are consultants, appraisers

Existence, QA it has a dual identity, on the one hand, consultants, QA is carried out on behalf of the company CMM; on the other hand, for the company,

QA is a consultant interface, pass on their opinions, cloud and requirements.

(3) If you are a project manager, a full-time QA do you think that your project needs it? Or you can just have a Test? If problems arise, how do you define who should bear responsibility?

① I think it needs a full-time QA, my personal view is that in a complete project must clear division of labor. It is the result of social division of labor and industry evolution.

Development and testing are actually two branches of software engineering. If full-time QA and developers to cooperate with each other, can greatly improve the efficiency of development projects,

Useful role in some large-scale projects. So I think it needs a full-time QA.

② large to each department, small to everyone. Should have its own division, after a meticulous division of labor, each person is responsible for a small piece of something. Once there

Problem, the problem who appeared in charge of who bears responsibility.

 

Guess you like

Origin www.cnblogs.com/changheng/p/11567251.html