What's Not Working: The Traditional Tools for Controlling Quality

Sponsored Links:

So, now I have outlined a quantity of the problems associated with the ideas behind what is quality assurance. But how quality control tests and make effective in ensuring that products and services effective? To choose that answer, they must examine a quantity of the tools used by traditional people of quality assurance and see where there is room for improvement.What, then, is quality control? The British Standard 4778 defines quality control as "the operational techniques and activities used to meet quality requirements.They try to control quality and defects in the program through the establishment of control processes of design, coding, testing, delivery, and so on. The idea is that if they standardize the method by which something is done, they can establish in the method repeatability and uniformity of confidence in the product of the method. In addition, a standardized method can be automated, eliminating the need to have people participating in it at all. People are not uniform in nature. The method is a nice device to minimize the impact of (non-uniform) people on a project. But when all is said and done, the program is written by people for use by people. It is this fact that ultimately may be our salvation, although it is proving a challenge at this time of transition.Program development is a creative, innovative method. Quality assurance principles have been developed for manufacturing, which is based on the repeatability and seldom innovative. Principles of traditional quality assurance does not fit with the speedy paced needs of today's environment of program development.Principles of traditional quality assurance of all match quality with reliability. This definition is simple for today's market, which means that the priorities of traditional quality control are out of touch with the needs of the program development community.Manufacturing has not been excessively concerned with human factors. Manufacturing was founded in an environment where the most active era of machinery, repetitive mechanical processes that could be institutionalized management by decree, and where the role of the people were in the service of method.In enterprise program stores, the biggest asset is people and intellectual property they generate. Only a method that is accepted by the people doing the work to succeed. And only a method that treats people as assets will be accepted.

Traditional QA and Testing Tools Can't Keep Up:
The following are the traditional tools used by quality assurance and testers:

Records. Documentation that keeps track of events, answering questions when, where, who, how and why.
Activities. Comments, modify management, version control check.
Documents. Standards, quality plan, check plan, statements of method, politics.

These are mainly on paper in charge. Most quality assurance tools are based on traditional paper. It is virtually impossible to do a job that is more accurate than the tools used to generate the work. How can they ensure quality and check groups are expected to be more effective than their best tools?

The Paper Problem:
The main problem with the traditional quality control of RAD is that the productivity-enhancing tools used by application developers have alienated much the role that produce the tools used by quality control groups, measurement & groups documentation. The application product development at a pace that is faster by several orders of magnitude as the transfer of knowledge, composition, design & review of paper documentation. The result is a paper produced by groups not to continue with the pace of development.Paper is the most important hindrance to application quality today. Not coincidentally, the inspection of documents & comments are the most effective ways to have errors in our application. The inspections & tests proof on paper documents. Paper documentation is the single biggest mistake repository application development. Besides the number of design errors, my communications, ambiguities & fallacies that introduce & reinforce in our products, the number of errors introduced by the paper documentation is outdated or dissenting important quality problem. Furthermore, the creation & collection of paper documents is expensive & slow.In the time it takes to describe the problem of paper, which can make major changes in the functionality of a application implementation, recompile, & have it ready for testing. The paper documentation is out of date.The distribution of information through paper documents is expensive & slow. The paper documentation is usually at least a small out of date by the time you print. When they need to distribute information to more people, they make more copies of paper. When they must update information, they make copies to replace all existing previous versions & try to distribute these new paper copies to all who had a copy of the previous version. This is a manual method of version control. You can not hope to maintain all information distributed fresh.In general, development time to build a version, but managing modify takes days to approve the release & technicians need weeks to prove it. Meanwhile, the design changes daily, & documents basically can not keep up.

No comments: