Essays collection 2012
Home Home SK
"quality"
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.


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.


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.


Tomlein Michal

Abstract. Open-source software can be found almost everywhere, including on most of the world’s servers and the computers of millions of users. However, the most successful open-source projects are the ones that produce software without a graphical user interface or software whose intended audience are administrators and developers. What the open-source movement has failed to give the world so far is a major breakthrough in the way we use and interact with computers, a major advancement in usability or any other innovation that would forever change the way we look at technology. These are characteristics we generally associate with closed software supported by strong leadership with a clear vision of how a change for the better could be accomplished. This kind of software also requires an enormous amount of design work, which open-source projects are generally not known for. In this essay, I ponder the question to what extent open-source software has pushed information technology forward, conclude where it falls short and try to identify the reasons behind this problem.


Left Separator
monitoring software project metrics function points plan planning software product risk management test driven development error effective communication sofware metrics software development team problems development software quality development support management extreme programming pair programming Scrum communication relations control progress subversion git critical path method project planning estimation agile development risks motivation requirement collection testing use case points support tools support tools outsourcing team size estimation version management quality cooperation risk documentation project software versioning conflict