Software Maintenance – Complex or Neglected?

Fejes Máté

Abstract. The main point of this essay is a reflection on the causes and possible solutions to the complexity of software maintenance. Work includes subjective opinions on the general approach to the development. Errors in ways of solving of individual tasks are searched. The idea of a fictitious future support instrument is discussed. The content of this text is the result of research and personal experiences of the author.

Are source code comments really necessary?

Gelányi Ľuboš

Abstract. This essay is dealing with source code comments necessity according to creating software documentation. Author evaluates different methods concerning approaches for generating source code documentation. Main issues are dealing with standard source code generators or advanced methods describing this process such as code analysis based on information retrieval or pattern matching and Web 2.0 perspective for software documentation. Whole problem is issuing through code comments which are disputed whether to use them or not.

Way for a successful project solution is communication

Hula Igor

Abstract. Communication plays an important role in software development. This essay deals with the methods of communication between participants in agile development of software called Scrum. There are evaluated the advantages and disadvantages of communication methods. The essay recommends a particular communication channels between the different actors of the software development. There is highlighted the importance of archiving of communication and creating knowledge base in software development process.

How to help in project monitoring?

Jaroszewicz Kazimír

Abstract. This paper tries to solve problems in software projects monitoring. I described processes in software control system, I have pointed on problems in these processes and offered some solutions.

Support of change request process – automatic or manual?

Kontúr Radoslav

Abstract. Process of change request is one of the most important and most expensive processes in software development life cycle. This essay discusses the means of support to this process. This work critically compares the approach based on supporting this process by using a tool for automatic routing of change requests with approach based on organization changes in this process. The work is enriched by the author's practical experience with the support of this process.

Effective time planning

Kuka Radovan

Abstract. Planning is undoubtedly very important. I tis said that i tis better to have a bad plan, as have no plan. This applies not only for managers, but also for developers. They should plan work on theyr tasks. This essay provides a way, how to efficiently create personal plans. It also suggests a method to simplify time estimation.

Necessary methods of software monitoring and problems comings with them

Mäsiar Juraj

Abstract. Project monitoring should be important and integral part of each project development. Any project development cannot end successfully without it. But on the other hand there are many problems that have influence on monitoring. If we solve those problems, we can make monitoring much better. This paper discusses different monitoring methods, features and problems. Into this work I have included my suggestions of solving some monitoring problems.

Type and intensity of communication in debug process

Masný Ľuboš

Abstract. The whole essay is about communication. It’s about advantages and disadvantages of personal and computer mediated communication. What type of communication is better for development team and what kind of communication for customer. At the beginning are mentioned important facts, which can decide type of communication. When it’s too much complicated, there is a suggestion about having system. System is tracking all the fact and making decisions about next step in communication.

How on pampered customers

Mihalik Adam

Abstract. The essay points out, that despite the advanced development of information technologies we are not able to meet all project risks. At the same time it provides insight into the risks to the customer as one of the most dangerous risks of the project. We determine the percentage of most frequently used methods of the risk elimination and we upgrade them for a finding the specific issues related to customer requirements. We analyze the success of the most common methods of identifying risks and compared with the success of applying decomposition method to the same problem. Using the decomposition method we determine the riskiness of specific project areas, thus we can predict the formation and changes in customer requirements.

Estimation techniques of software projects planning

Pszota Dávid

Abstract. This paper describes some estimation techniques, which are used in software project planning and scheduling. It also provides comparison and information about advantages and lacks of the described techniques. Here are given some recommendations for better estimation, including the historical data analysis. There is defined the need of discussion between planning management and the members of the developer team.

Distributed team as a way to effective communication?

Sopko Pavol

Abstract. The authors look at the field of communication in a distributed team environment. Current problems and main points of criticism of managing a distributed team are discussed while comparing them to those of a traditional team. In the end, a proposal for a fresh and alternative view on the aforementioned issues is presented with some conditions on the structure of the team and their software support infrastracture.