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.