Bielik Pavol

Abstract. Despite the high awareness of the importance of risk management and theoretical basis in this area, studies show problems in its practical implementation. This fact is reflected by high number of companies and student teams not using any risk management techniques, even though, they are well aware of the appropriateness of their use. What are causes of the current state and how can we change it for better? One possible approach is using games, which brings an innovative approach to software engineering, helping students apply theoretical knowledge to real life situations. But is it effective and if so, where do games fit in the current scheme of education? These are the questions we discuss and answer in this essay.

Burger Roman

Abstract. It is not easy to do something we haven’t done yet. It is not easy to learn something new. And especially, it is not easy to determine if we are doing it the right way. Therefore we should be extra careful and diligent to understand the core of things. In this essay I will discuss my own experience in software development in newly assembled team. I will show which processes in software planning are hard at first even if you consider yourself skilled and I will also show which processes could be done easier with the appropriate approach.

Can captain steer the ship without a compass?

Chylik Michal

Abstract. It is a generally known fact that the basic preconditions for a successful project lie in precise but reasonable designation of the target and in a detailed plan of steps that lead to the target. Project management is dealing with these issues and defines a vast number of theories that should help the manager to effectively make use of the resources, to create a project plan, and to determine and avoid potential risks. Effectively, it helps bring the project to a successful conclusion. Project management nowadays provides a large variety of supporting tools that make the tasks of the development team easier. This essay is predominately dealing with supporting tools of project planning and issues related with the utilization of these tools. Why doesn't everybody use these tools if their benefits are obvious and analyzed in a number of works by renowned experts in the field? What discourages the managers from using these tools? Is it just the ignorance of the existence of such tools or the lack of belief in their benefits? Is the utilization of support tools suitable for smaller companies with fewer development team members as well?

Will SCRUM based planning guarantee the success of project?

Ivanec Peter

Abstract. Planning is important and integral part of every project, not only that software oriented. Using agile methodology - Scrum - is planning more intensive and critical than in other types of software development. In individual few-weeks-long sprint is necessity to plan and meet short term goals specified for that-which sprint. If the project wants to end successfully, it has to be well planned and all specified deadlines have to be met. But what is the successful project and who decide, if concrete project is successful or not? Planning deadlines of projects alone is not enough. There are known certain agile programming factors, which connections with successful Scrum project were proven. Therefore is planning in this essay described as a tool, which gives the project potential of success? Is it everything that is needed to guarantee success? Is setting a project plan only really enough? What planning needs to include, so project based on this plan will be successful?

Estimation that counts on everything?

Krátky Peter

Abstract. This essay discusses the process of creating accurate time estimations of the project plan. In the beginning I concentrate on the necessity of the accurate time estimations and issues resulting in the overrun of the estimation. Next I introduce wide-spread technique to get a detailed look of the project as a basis of the time estimations creation. I acquaint the reader with the cardinal groups of the methods to create time estimations and I compare them particularly in the point of view how they are influenced by presence resp. absence of the human factor. In connection with this I underline the importance of liability and fairness in creating estimations. Finally I answer the question of which method is the best choice in the time estimation process with respect to character and environment of the project.

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.

Let me work! I’ll fix the bug later...

Mitrík Štefan

Abstract. In the software development process, bugs generally cannot be avoided. While the time available for software development often decreases rapidly, the quality requirements remain the same. Teams of programmers, who do not systematically fix bugs, lower the quality of the software and increase the time needed for development. For a team, it is important to know when and who is responsible for fixing each bug. The productivity of a programmer who is being disturbed while working on his task lowers along with the quality of his work. That is why a successful team needs clearly defined responsibilities and procedures for debugging. In my essay, I focus on debugging techniques used specifically in the Scrum process.

Support tools for version control: suitable choice for our team?

Nagy Balász

Abstract. Software development today is a process that usually takes months, but sometimes several years. Such projects do not need only sufficient human resources, but also support tools to facilitate employees to co-operate and work effectively during working time. One of these tools is the version control system, which is responsible for cooperation, in particular with the source code. Choose from these funds is not as easy as it may seem, because there is a lot of systems like that. In this essay are mentioned the advantages and disadvantages, and some own experiences with this systems. The essay also deals with a suitable choice and with the way of the selection versioning systems. The reader should read the following to get a basic overview of this field and issues.

Monitoring, success in student environment

Polakovič Patrik

Abstract. Academic environment is always taken with reserve. Students make up their own duties as to be able to achieve the desired goal. And so even promising and well-developed student projects often end unsuccessfully or incomplete. One of the reasons is the weak scheduling tasks figuring in poor self-control, or control by the other members of the project team. In practice, this problem of software projects solves monitoring management, which oversees the process of project creation. In student environment is sometimes problem to integrate the monitoring management from time-management reasons, or lack of human resources. This essay will attempt to discover whether it is possible to create a monitoring management in student team. What should be noted during realization of methods for monitoring the project and what problems to expect in the integration of specific methods of monitoring into the student project team environment.

Will SCRUM lead to us killing each other?

Šalmík Jakub

Abstract. Communication is a key attribute in any the creation of any project. But only establishing effective communication channels is does not make communication successful as a whole. By defining a communication culture or form, we can prevent conflicts and other problems. Despite this, there are conflicts, communication through channels fails or is ineffective- all of which are signs of something being wrong. This essay will summarize how to distinguish and solve problems in a team and furthermore will look at how these approaches can be used in a team which uses the SCRUM method, a method specified by stress situations and high demands for every member. In SCRUM, communication is an important element, because the given rate when developing a software project can be very fast, making effective communication key.

Tools that shaped the open source software

Šoka Milan

Abstract. The Version Control systems have experienced significant increase over the last few years. It was thanks to open source, why Version Control systems has become more developed. And it was thanks to the Version Control systems, why open source can get to where it is today. So we can say that the Version Control systems shaped the development of open source in highly significant manner.

Supporting tools for control quality as core of software quality

Szórád Anton

Abstract. In the software development process is quality important. 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. This essay provides a basic explanation of these tools. There are many tools, but not every support tool is suitable to the circumstances such as time or type of organization. Essay discusses the possibility of using support tools for small organizations to maintain the quality of the development process, their advantages and disadvantages and offers recommendations how to use these support tools.

Why Open Source Has Failed to Change the World

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.