Kuzmík Ondrej

Abstract. Test or not to test? If so, when, what and how? I use this opportunity to write an eassy to describe my opinion on the matter or at least a part of it. I describe my view on the connection between testing and quality. When testing is worthwhile and when it is not. Tests are usually made to reveal bugs in code and testing the requirements and functionality is often neglected. I try to bring my point on this issue, along with how good testing can make software better or oustanding. I also focus on who should be responsible for testing and the importantance of this person for the team.

Quality Aspects and Management of Selected Types of Applications

Lipták Martin

Abstract. Software quality consists of functional aspects, that are visible to the customer, and structural aspects, that are visible only in cases of their insufficiency. Quality must be built into product in each development phase including specification. Incorrectly specified product is a bad-quality product, since it is of no value for the customer. On the other hand, product built with quility in mind in each one of its development phases, leads to customer satisfaction. Quality must be constantly improved in the development process. Essay compares aspects of quality of web, mobile and desktop applications.

Waterfall or agile methods – where to quality?

Nagy František

Abstract. Quality is immensely important when developing any product. That holds even for development of software. In this essay, we will take a look on two different approaches to process of development, waterfall model and agile methods and compare how they assure quality. We will especially evaluate, which offers more controll over quality of final product to both developer and customer.

Does it make sense to test software manually?

Sucháč Filip

Abstract. Every software company wants to develop a quality product. Specific part of processes that are dealing with achieving software quality is testing. There are lots of approaches to testing. In many companies exists a position called tester that is occupied by people who are testing product under development manually and reporting detected bugs. In this essay I am dealing with pros and cons of manual testing, describing what characteristics should good manual tester have and what approaches to testing are good to be chosen.

Can be 2 > 1+1?

Zboja Tomáš

Abstract. Pair programming, known from extreme programming, was researched in various fields. This essay aims to look at pair programming how it relates to the quality of developed product. It identifies fields of quality of software, and later focuses on them. These are primarily standards during software development, the consequent quality from them, which should be part of requirements. A large part is dedicated to product errors – errors created during the implementation phase. Some sources of investigation indicate that pair programming has a negative impact on software's quality. The majority thinks the opposite, though. The essay contains a reflection, whether the measurment that indicates the negative impact is correct. Althought, generally, the acceptable result is, that this kind of programming is appropriate in terms of quality, there's a reflection on which kinds of software are the most suitable to be created with pair programming. It also states the conditions that would help to achieve the measured result - improved quality.