Study Bowen Software Quality Assurance
Software Quality word is widely used, has different meanings in different contexts. Here is the most recent definition of ISO:
"Capability of software product to satisfy stated and implied needs under specified conditions."
"The degree to which a software product meets established requirements; however, qualitydepends upon the degree to which those established requirements accurately
representstakeholder needs, wants, and
expectations.
Both definitions emphasize the software to meet the needs of users and stakeholders, there are several ways to analyze the quality of the software, academic papers in this regard a lot in this book, we know:
Software program = + Software Engineering
So, we can nest this formula:
Software Quality = + program quality software engineering quality
The quality of the program is reflected in the quality of the software outside the function. There are many features of the various functions needed to measure, for example, the site displays the speed of query results; booking sites capable of concurrent processing throughput operations; support the number of online users
the amount. There are other aspects of the program, such as the quality of the user experience, quality and safety of international quality.
Software development process has three characteristics: good, fast, cheap. Popular to say that "software function, cost and time in all three areas to meet the needs of stakeholders ."
I realized that the quality of software protection should be divided in many ways, not simply a way, it is controlled by many factors, after perusal of books, I realized that
The quality of software engineering in the following areas:
The visibility of the software development process
Risk control software development process
Internal software module, cut off the middle of the project delivery of quality, project management tool factors
Software development cost control
Completion of the internal quality indicators
Software quality looks very abstract, but in reality very specific. He needs not a particular aspect of perfection, but everything, because the software program is equal to plus Software Engineering
There are many aspects of the program structure, software engineering is not one aspect of the composition.
Software Quality Assurance (QA) and Software Testing (Test) is very different.
A programmer who works at Yahoo and Microsoft, have such a broken theory, most of the development team, does not need an independent testers.
First of all, there is division of labor is a good thing, the team should have an independent software testing role. Everyone can participate in the work of QA (Report Bug or something), but in the end there must be a role is responsible for QA it. Not only role to be alone
Legislation, and in the final software release, this role must be signed guarantee (Sign Of). Is the result of social division of labor and industry evolution, development and testing are actually two branches of software engineering, software 1 for different services,
The manner and extent of testing has the distinction. 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
In the familiar textbook, I found that internal QA team needs an independent role outside the team also needs an independent QA role. Therefore, the scope of work QA quality of fact, online, shipping a series of checks, both within the team or outside the team.
For testers point of view a lot of people have different views:
Since it was responsible, I would not be responsible for the
Blind trust in the role played by professionals
For his role to do performance optimization
Restricting division
No clear division of responsibilities
There are many successful people and successful companies known not necessary to set up an independent test role
For more than I do about the problem description, I think every company should set up an independent QA, QA each team not only can test this test work, you can also test the other teams testing work outside the team.
QA test and full-time are not the same
QA concerned about the product TESTER focus is on the outcome of software development inspection, control , however, test concerned SQA process focuses on the software development process supervision and control.
If there are problems, it can be made according to what aspects of the problem, to determine who is the problem. The code above fine differences can be delivered to the programmer to rectification, if the above is because the test error, it can determine this is a problem negligence testers appear caused.