1. insights on the protection of software quality
1.1 Software Quality
1.1.1 What is Software Quality
Generally speaking , the quality of the software is " software requirements explicitly and implicitly defined the extent consistent " . More specifically, software and software quality are expressly recited function and performance requirements, development standards document explicitly described as well as any professional development of software product should have features consistent with the implied degree.
Simply summarized a formula can be used:
Software Quality = program quality + Software Engineering Quality
1.1.2 Quality Program
About the quality of the program, which is mainly reflected in the quality of the software outside the function . For example, tickets for a website, it's the quality of the program mainly as follows: the site can handle the throughput of concurrent services to support the number of users simultaneously online (when tens of millions of users online, whether there will be bounced off the site case), the speed of web pages open on tickets and so on. Of course, the quality of the program there will be reflected in other areas, such as the quality of the user experience, international quality, safety, quality, the NPS values and so on.
1.1.3 Quality Software Engineering
The quality of the program is mainly reflected in the function, the quality of software engineering mainly in software development cost and time, mainly in the following areas:
v visibility into the software development process
v Risk control the software development process
v internal software module, an intermediate stage of the project delivery quality factors of project management tools
v software development costs of control
v the completion of the internal quality indicators
1.2 How to measure software quality and security
Practice has shown that, CMMI level can be a good measure of the quality of software. Effective implementation of CMMI can improve the management level, reduce business costs.
Software security needs with quality in all aspects, from programmer to software designers, to project managers, the company owner, each layer should be strictly in accordance with the relevant provisions of the standards for software development.
The following points summarize Software Quality Assurance key measures :
( 1 ) Application of good art method
Software developers should choose the right software development environment, relying on appropriate technological, high quality and high standard of design development software.
( 2 ) Test software
Software can be found in most of the potential errors in software testing, try to avoid increasing the cost of ongoing maintenance, and improve software quality.
( 3 ) formal technical reviews
At the end of each phase of software development, we should organize a formal technical review . In accordance with the specification and design of software product of a rigorous review by the technical staff to review. In most cases, the review can effectively find software defects and errors. National standards development units must be SQA review, document review, design review, audit and testing specific means to control quality.
( 4 ) Embodiment standard
Users can, with reference to national standards, international standards or industry standards, the development of norms of software engineering implementation. Once the software quality standard form, it is necessary to ensure compliance with them. During technical review should assess whether the software is consistent with the standards set.
2. If you are a project of QA , then what is the scope of your responsibilities?
Can not do without a good software QA efforts of staff, which also requires QA personnel with high professional competence, and QA responsibilities of personnel in the software development process is mainly to act as watchdogs, so if I, as a project QA staff, I feel duty the following aspects:
- Timely follow up on the process of project development, the ability to detect problems in software development or testing process, the analytical report
- To develop a reasonable software development process to ensure that research and development team, by definition, a good plan
- Have some programming ability, can participate in the software development process
- According to the project development needs, set up software testing framework, writing test cases and test data
- Complete integration testing and system testing of the project and do a detailed test performance and other aspects of the software
- Analysis and report writing software defects
- For user requirements and functional performance expected to achieve, the software periodically review
3. If you are a project manager, a full-time do you think your project needs to QA it? There are still only Test to? If problems arise, how do you define who should bear responsibility?
If I was a project manager, I think my QA staff definitely need a full-time project. Software quality assurance is a project development will not be the missing link, and the premise of software quality assurance is to have professional staff to implement it. In the moment, many companies because of the lack of effective project scheduling and project management, lead and did not leave enough time to do system testing, and finally makes the listing to spend more time and money to do the maintenance of late. Moreover, if the requirements change too much, this time not yet complete requirements document, then the tester can only be tested on their own imagination, not only increases the cost of time, can lead to a test to do is not complete.
If there is a problem, who should be responsible? This should analyze specific issues, first of all we have to understand that there is a problem in which link, then go to the relevant person in charge, and asked the reason, but not all the problems can be attributed to a person who, after all, is a software development project , that we need to complete together, we should monitor with each other, but since there is a problem, the most important is to solve the problem, we should not be eager to find out who was wrong or eager to punish, but should face the problem with the entire team , to solve the problem, the most important project is completed first.