Biroš Michal

Abstract. In solving of bigger software project, there are involved a lot of people, who work on different tasks. In order to manage this project successfully, it is necessary to managers and customers to know in what state is project at the moment and how much it meets the quality requirements. These data can be retrieved and interpreted in different ways. Nowadays, there is a lot of attention paid to agile methods which can provide a clear and understandable picture about the plan compliances. However, traditional monitoring can be still used very well. In this essay, I will compare earned value method as a member of agile methods an GQM (Goal Question Metric) as member of traditional monitoring.

Caban Tomáš

Abstract. Open-source software has achieved great success and today we encounter open-source software almost constantly. Open-source software has also spread to commercial area as companies had noted its undisputed benefits. However, open-source software has always been accused of lack of quality and reliability. Most used argument for this is that open-source development process does not use traditional quality assurance techniques and methods used in commercial development. This essay reviews quality assurance process in open-source development, methods, processes and techniques which provide quality of open-source software. This paper also aims to compare quality of open-source and commercial software and tries to answer question if open-source software really has less quality than commercial software. In the end this essay tries to think of possibilities of using open-source quality assurance in commercial development.

Agile software development impact on software quality

Calík Jakub

Abstract. Every software developer is trying to create software with best quality. Quality is not something that can be easily measured by the number of lines of code. There are several aspects that determine balance of the overall quality of software. Several methodologies and models for software development was made in order to create software product of good quality. However, not all of the methods and procedures of software development, place equal emphasis on all aspects of quality. While some aspects can have more weight in certain model, others could be put asside completly. Lately, become very popular agile development model. In this essay, I will try to explain how agile software development influence software quality aspects and how it can be improved.

Specifics of risk management for medical software

Gajdoš Jozef

Abstract. Nowadays, the Information Technology penetrates into all sectors of human society and even healtcare. In the medical softwarethere is the greatest a ubiquitous part of the medical devices with a very specific area of software systems. And even in terms of the actual software solution as well as in the development of risk management. In medical software is the greatest risk associated with patient deaths or irreversible health damage and therefore the risk management goes to extreme measures to eliminate these risks. In this essay, I compare the specific procedures to eliminate the risk of failure in the medical software with e-shop and the banking system. Are mutual applicability and meaning of these solutions in various industries.

The faces of communication problems in open source projects

Geier Martin

Abstract. The communication between people standing face-to-face is many times complicated and difficult, but we are improving in this sphere day by day. The success of every single man and society is based on communication, as well as their projects. But how can be the communication in project creation successful, when we are distant from each other hundreds of kilometers and dispense us different languages and traditions? In this essay I describe the choice of communicational tools suitable for communication in open software projects that make possible collaboration between foreign people without direct contact. In next part of essay I present a look on communication ways by designing a project. The biggest part of this essay is dedicated to communication about a source code, which is important factor in functioning of whole project. I do analyze the most frequented problems, which can appear in communication about a project and which really appear. Thereafter I suggest more or less effective ways to how the communication guide to the project or evade from those parts, which need the direction.

Improving code quality by using refactoring techniques

Greguš Peter

Abstract. It isn’t simple to make quality code. We can reach this goal in several ways, but when we will know, that we created the code in required quality? Answer to this question is given by the code metrics, which tells us the level of quality of our code. Than we can tell which of two codes is qualitatively better, given their metrics values. But when we want to tell if single code has good quality or not we must know the values of the metrics for quality code. The way how to reach quality code from inferior code is to use the refactoring techniques. By using this tool we can change code structure in a way, that we upgrading its internal structure (quality), but we don’t change its external behavior. Applying the refactoring rules changes the values of the metrics, which set the code quality and we shouldn’t bind ourselves to them, but use them as indicators, that we should change something in our code. Because of it we should use refactoring when the code metrics indicate bad values and not as engine to improve those values, because we can degrade our code in this way. So it’s necessary to know when to use refactoring in the correct way.

So many possibilities for risk management, which one is the best for my team?

Hlavenka Marián

Abstract. The worst kinds of problems that may occur during the course of a software project are the unexpected. Therefore, it is extremely important for the success of the whole project to choose the right approach to risk management right at the beginning of the project, to determine all the possible risks so we won’t be met with any unexpected problems. Selection of incorrect or improper approach for your team can result in unnecessary complications or even complete failure of risk management, which can lead to the failure of the whole project. How do I choose the right approach to risk management for the project? How does the structure of the team influence the selection of the right approach? Those were the issues that I addressed and looked for their answer. I chose four risk management approaches which I compared in their suitability for different structures of the team during all the different phases of the approaches. Every approach has its use in specific cases, but there are also weaknesses that are best eliminated by combining multiple approaches.

Monitoring in a small agile project

Hudák Miroslav

Abstract. Monitoring is an important part of software project management. The aim of this activity is to identify the problem early and take steps to minimize possible damage. A frequent cause of project failure is a bad time estimate and associated project overcharge. Therefore, it is important to obtain relevant information about the status of the project in order to apply change management. In this essay I will discuss one of the most used methods for monitoring the project - Earned Value Analysis, its use in agile software development, and propose a simple method to use this technique in a small project such as a student team project.

Ethical hacking

Kunka Tomáš

Abstract. Despite at least two decades of software risk management research, including some extensive research programs, software project failure is frequent. Resources for software risk management remain limited despite its importance in software projects. Essay discusses ethical hacking as one technique of risk management, lesser known in our country. It points out risks of ethical hacking and suggests solutions for these risks by proper education in school. These suggestions are universal and can be used in many other areas of education. It also brings critical view of ethical hackers and searches for right spot for them in risk management process.

How to write user friendly documentation

Lekeň Tomáš

Abstract. Documentation of all kinds is part of every software product. Regular user, who is not technically proficient, most coming in contact with user manuals. It should therefore be placed the highest demands on its readability and clarity. New forms of documentation, such as video tutorials, contribute greatly for clarity. That make it easy to perform using of selected features. The essay focuses on the issue of readability and simplicity of created documentation.

How to not plan your end

Martinkovič Milan

Abstract. In process of creating of software product, the planning and creating of schedule is often lacking attention despite of the fact that by good planning we can ensure smooth running of whole process. What is more, because of planning we can identify some key properties in our project in sufficient advance. Some of these properties are for example necessary resources, which can be people, material and immaterial resources and so on. Based on the identification of these entities, we can then derive the structural features of the project such as the required budget and so on. Despite these undeniable advantages, it is common that due to negligence of honest planning such an organization unconsciously plans its own end. In order to reduce the risk of potential errors, we must find the factor, which can in advance tell us about how good our plan can be. One of such factors is for example experience with planning, which significantly affects the final version of the plan.

Why is not appropriate to combine several methods of time estimating

Šinský Peter

Abstract. One of the most important tasks in developing the plan is to estimate the time. Estimation is part of the planning process and aims to establish an estimate that says about the time needed to perform tasks. Based on this estimated time, we can create a plan, which we can follow through the project development. However, there are several ways to build forecasting. In the essay I am providing an overview of selected methods for estimating time. On that basis, I came up with an example, how these techniques could by combined to create a perfect guess. As at first glance, combining everything and trying to use only the best, not necessarily win. It is necessary to think about what the consequences of such an approach can bring. Will it take all too long? Will it be clear about how much time we actually estimate? Do we have the motivation to do so?

Version Control System – Centralized or Distributed?

Sivák Peter

Abstract. Using version control system in any project is necessary. In the past there were only centralized types of systems but distributed approaches were developed later – you have to choose one of them. Distributed systems become more popular today but it does not mean that you automatically choose them. The goal of my essay is to show you that both principles have advantages and disadvantages and only after proper analysis you can responsibly choose one of them, which will better suit to your project. I analyze here various aspects which can have impact on the final decision. I illustrate here repository access problem, which are pros and cons of distributing, how large teams cooperate on the project and which solution is better for them. Later I describe potential risks resulting from irregular committing of versions to server and to the end of this essay I talk about the transition between the version control systems and what are the benefits and costs of it. You also have to realize, which aspect has for the team more priority and include also that to the final decision.

Correct choice of communication methods for local and distributed team

Staňo Filip

Abstract. Communication is a base of every human coexistence and cooperation. In software development, correct choice of communication method is critical. This is the reason, why I will try to analyse and describe all common forms of communication used in software engineering. Main subject of this essay is local and distributed communication and their appeal on team performance. I claim that local communication is always an advantage. Subsequently I describe formality as a phenomenon in team cooperation and its appeal on motivation and oppositely on chaos in communication. Last but not least is analysis of synchronnous and asynchronnous communication method following with recommendation how to use them properly and in correct situation. In this essay I will describe all afore mentioned methods of communication in detail and also their final outcome on project results. Later I will identify usability of all this methods in certain situations as well as consequences of their incorrect use. In this essay I compare suitability of all methods based on number of people in team and also based on software development process phase we are currently in.

The disadvantages of Software Configuration

Szilva Bálint

Abstract. Software systems are day-by-day bigger and more complex and every day thousands of people are working on these systems to keep them up to date. To reach the best performance of software systems they had to be configured in the right way. Sometimes the best way is to allow for users configure their software system alone for themselves. Essay opens a few questions about configurations and contains ideas about possibilities in software configuration. When and why should we allow users to configure software systems and why we shouldn´t? Which level of the software is the best to configure our software?

Support tools for control quality as core of software quality

Szórád Anton

Abstract. In the software development process is important its quality. The essay discusses this concept not only in general but also as regards the quality of software development. To be able to measure software quality and maintain high level, support tools are needed. At present, there are support tools that are based on other support tools. This essay provides a basic overview of these tools.Essay discusses the possibility of using support to maintain the quality of the development process, their advantages and disadvantages and offers recommendations how to use these support tools.