Software quality assurance and refactoring

Jendrej Maroš

Abstract. In an essay dealing with the quality software of systems. I point to resource by which software can ensure software quality. The main resource for quality assurance is testing. I show here to the importance of phases before the start of testing. Quality assurance is not merely testing the software project, but also to prepare the criteria and requirements to be met by specified levels. One of the other resources for the better the quality of the software project is refactoring. Refactoring is changing architecture of the software without having to change his behavior, while increasing its quality. Applying refactoring in the project, but does not improve quality. There are various indicators by which detects whether the refactoring is appropriate and as possible is applicable.

How to effectively improve the quality in student projects?

Lajčin Tomáš

Abstract. The introduction of this essay deals with definition of quality in software projects. It is not easy to define quality in student software projects. In fact, it is a demanding process. The main idea of this essay is to think about ways to improve the quality of student software projects. Improving the quality of student projects is problematic, because the environment is different and traditional large commercial software projects rules for quality are not applicable here. Using standards for ensure the quality in student project is not as easy as it seems. Student projects have smaller range and they are affected by lot of new factors. This essay is also talking about measurable quality in software projects and the standards are appearing here again. The end of the essay deals with the impact of software projects testing on its quality.

Golden mean

Meliško Peter

Abstract. Testing is an important part in the process od software development. Any underestimation or bad testing of product will affect the final quality and may have a direct impact on marketability of the product, which in turn may affect the relationship between producer and customer. Testing can be classified by several criteria. This essay is focused on the subdivision by human intervention: manual and automated testing. Both methods have advantages and disadvantages, where one of the methods seems to be stronger, there the second seems to be weaker. At first sight manual and automated tests seem to be counterparts, but a deeper analysis shows, that they overlap in many cases and they are complementary. Using both methods give the best precodition for achieving quality results, knowing that we make every effort for positive assessment of the product to customers.

Everyone makes mistakes…that’s what testers are for

Pomothy Adam

Abstract. Nowadays, testers are usually considered to be temporary one-shot employees. They are given only test scripts and rules, how to report found errors and they are supposed to do their jobs. However, testers are equivalent to a development team. They have the same goal – to deliver a high quality product to a customer. The communication is crucial for these two teams. However, if new testers are hired for every project, they have no relationship to developers and they are also in brand new environment. As a result, their communication is too formal and inefficient. That is the reason, why it is important to have a static team of testers as it is in case of developers. Good relationships or friendships result in much better cooperation. To achieve as effective communication as possible, it is also important to choose team leaders of both teams (it is common in case of developers, but not in case of testers). Team leaders coordinate other members of team, they are aware of current tasks and they communicate with external world in the name of whole team.

Does test-driven development influence software quality?

Račev Marek

Abstract. With advancement in information technologies and increasing amount of requirements it is more and more difficult to develop high-quality software. Many development teams are adopting agile methods of software development in order to ensure quality. In this essay I discuss one of the core extreme programming practices – the test-driven development. The fundamental principle of this approach is automated tests writing prior to developing of functional code in small, rapid iterations. The main question that I am trying to answer is whether test-driven development has an impact on software quality in terms of delivered software quality and internal code quality. A special focus is given to pros and cons of this approach and the suitability of its use depending on type of project.