Panel members: Ge Xiang Fang Wei Yiming Zhou Yang Yunzhen Zhouyou Hui
How the team should arrange QA
After this semester we know that software programs = = Software Engineering Software Quality = program quality = Software Engineering Quality
QA (quality assurance software work): All active software team to make the software meet the quality standards defined in advance and carried out, including testing.
- Ensure visibility in 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
- Prevention (Prevention): In order to prevent accidents, the software team to invest in software process improvement, quality testing infrastructure and tools, in order to prevent the team due to changes in personnel caused no one can understand the old program, the software team to be in training invest some time, auditing and other activities.
- Review (Appraisal): Team to put human and material resources to do the review, as well as software testing, sometimes also evaluate the quality of software modules outside the company submitted.
- Internal fault (Internal Failure): All the problems found in the review process, need to be addressed, these processes will take time to process.
- External fault (External Failure): software distribution to the hands of users, more or less there will be all kinds of problems, the process of dealing with these issues are also costs.
- Process Analysis diverted via (Process Enhancement): After a project milestone, team members to analyze the advantages and disadvantages of the various stages of the past, and to suggest improvements. After a suitable team to discuss the implementation of improvements.
- Improve their professional skills (EnhanceProfessionalSkills)
- Technology Investment (Invest in Technology): the development, purchase, customize and improve the tools used for software development and software project management and learn the tools, play tools for maximum performance. Self-study or attend training, communication, learning new skills, such as a new language, framework, new developments in artificial intelligence.
How the team should arrange for testing
Software Test (Test): the use of certain processes and tools, verify that the software can realize the functions and features pre-designed work processes and results are usually quantifiable. Because of the process and the results are clearly defined, quantifiable, so a lot of testing can be automated.
A team must have a role in independent tests. First, a clear division of labor is a good team, the team should have an independent software testing role. Everyone can participate in the QA work, but in the end there must be a role is responsible for QA it. Not only to the role of independent, but in the final software release, this role must be signed guarantee. Is the result of social division of labor and industry evolution, development and testing are actually two branches of software engineering, the difference between two different software / test, mode and extent of testing there. The role of independent testing to verify the quality of products starting from the user's point of view. Independent professional test equivalent to the product certification on behalf of clients.