Quality control of software often still neglected
Fully functional and error-free in use - this is how today's software solution should be. However, the reality often looks different: The quality assurance of software often comes far too short, which leads to the fact that it only matures - if at all - at the customer. As a result, processes come to a standstill due to errors.
As soon as software manufacturers are under cost pressure, they would quickly cut back on quality assurance: This is the opinion of Oliver Huth, chief developer and technical head of quality assurance at Intervista AG, based in Potsdam, Germany. "Many forget: Simply trying out the software at the click of a mouse or checking it according to instructions is no substitute for an extensive check of its performance." Even for automated tests, those responsible need necessary programming skills in addition to technical know-how.
Technology checks technology
Quality control does not only come into play shortly before the completion of the software, but accompanies the entire lifecycle - from planning to development to delivery. "Even afterwards, control continues to be of great importance. It is a continuous process. Moreover, the trend is now clearly moving in the direction of 'software tests software'. That's why various innovative technologies are used in quality assurance," says Huth. The final quality of the developed solution goes hand in hand with the respective corporate philosophy. Intervista relies on a tester team of four people for implementation. "We do not see software development and quality assurance as two mutually exclusive processes. Because: quality assurance is software development - and one of the most important pieces of the puzzle of successful projects," clarifies the expert. Depending on requirements, the provision of automated test cases for the software is also an option, which companies can use and adapt in their test environment.
Both sides consider
According to ISO 9126, quality characteristics of software can be divided into six categories: Functionality, Reliability, Usability, Efficiency, Modifiability and Transferability. These requirements and criteria are taken into account in the tests performed. "We always look at quality assurance from two perspectives: that of the technicians and that of the users. It is therefore imperative that we know about both sides. The process runs across disciplines, so to speak," says Huth. "The challenge for quality assurers is to know the entire breadth of a project." Only in this way can the targeted level be achieved in software development. Therefore, the foundation of the software is of particular relevance. In the conceptual design, the strategic measures that stem from the strategy development are implemented in a targeted manner - in contrast to the conventional requirements analysis, this even goes far beyond the recording of technological demands and the user's point of view.
Further information under www.intervista-ag.de
