Panelists: Wangzhong Fei, Liu Rui, Xu Bao Bao, Zou Dongmei, Chen Zhiwei
QA team
In the process of software development it stands to reason that there should be a person responsible for the QA. QA responsibilities described in the CMMI system, QA should have the following responsibilities:
1, by monitoring the development process to ensure the quality of work product
2, to ensure that the products developed and development process in line with relevant standards and regulations
3, to ensure that products, processes exist does not meet the problems are addressed, if necessary, will issue to senior managers
4, to ensure that the project team to develop plans, standards and procedures in line with the project team needs, while meeting the needs assessment
5, provide feedback to developers
But given the size of our team, our only major QA project manager served as the main function, and then through daily meetings, close communication to ensure the quality of the software development process.
As we know, software engineering, software quality + quality = quality program,
The first aspect of program quality assurance:
Because we do this software functionality is relatively simple, so overall it is relatively simple to achieve, in the beginning to make the entire framework needs analysis and software architecture as well as the time, we have planned a few pages of one of the few function, as well as implementation, everyone is responsible for everyone to do their own part of the time, he met not the place, look up information can be solved, it will not function in our daily meetings the next day, when we mention out, brainstorming, all can be resolved. On software quality is better guaranteed.
Second, we have the assurance of software engineering:
A significant impact on the quality of software engineering by the quality of the final software. This time is mainly responsible by our project managers, project managers Agile development process in strict accordance with planning our daily workload, work tasks, daily legislature.
We are also in strict accordance with the project manager's plans are successful completion of their work.
Team of testing
Our test work on our project amount is made more rigorous, we require a daily amount of small task, but our strict quality requirements of daily work, and strive not rework, do not waste time. We daily meetings that they will emphasize our daily work without error. Then all of us after the completion of their projects and then test each function, and then we test again exchange items per person in turn test. After a summary of all projects per person, bug testing software. In order to ensure that software is not wrong. After all, is the type of password to test the software. Our security software or should value most.