Essays collection 2012
Home Home SK
Group 1
Baďura Filip

Abstract. Every day thousands of people work on development of thousands of software projects. To insure, that a reasonable cost and adequate time are spent on development of these projects, it is necessary to control this development. And it is part of management of project – monitoring, that serves to us, so that we don't waste a time and costs. Monitoring of project helps us to keep project on schedule and avoid unnecessary problems in its development. However, if we want to monitoring project, we need to determinate how to do it, what to look for and which metrics to use.


Bilevic Roman

Abstract. Reliability is one of the most important parameters of the software quality. Its evaluation is often underestimated and it is done in late phases of development. It is important to consider the influence of the software development method on its reliability. I describe the main tasks of reliability management this essay. I analyze test-driven development from the point of view of the reliability and I think about the advantages over the waterfall development. I describe the way it deals with the faults. Considering the assumptions of the reliability growth models I point out the extent of fulfillment by test-driven development. I assess the need of reliability modeling in this type of development.


Bimbo Miroslav

Abstract. Nowadays risk management is common part of software project management. It describes how to identify risks, on which risks to focus and what to do with them. Risk management is needed to be aplied on on every – even very small – project. Our team project is large enought to have risk management formalized. There is avaliable many methodologies for risk management in software projects. Which of them is most appropriate for our team project?


Bisták Andrej

Abstract. The planning of a software project is one of the most important parts of the whole process, because without a good plan it’s not possible to manage the project, identify necessary activities and resources effectively and thus gain the satisfactory result. But plans are not the same. According to older theories, the result of a project was understood as a concrete state, that if was achieved, the project was successful. This approach had proved not to be the most correct and the most appropriate for the software projects. Modern understanding of planning accepts as a successful project also the set of points that create a cube in a space. This approach is called a semi-quantitative reasoning. This is and effective method for planning and forecasting software project and in addition provides the flexibility and ability to cope with uncertainty and unforeseen situations during software development to project managers.


Blaho Tomáš

Abstract. The success of teamwork depends largely on the choice ofmeans of communication and therefore effective communication. Communication is the exchange ofinformation and it is important, but often happens that it is notgiven sufficient attention. In my practice I have met with many different types of communication that long periods of time, orhave been used. The question is when and with whom to communicate, and what form to choose. Properly selected, it is important for the success of the team. At work, pointing out the advantages and disadvantages of different instruments, but also personal communication, which I willpay particular attention. Also I will try to describe their views on the use of these forms of communication in agiledevelopment methods.


Fábik Pavol

Abstract. Quality is very familiar to us. We are in contact with it on everyday basis. It has strategic meaning for the software projects. There are several techniques how to achieve quality in software projects. I will analyze source code measuring techniques in this essay, which can developers use to increase quality of their projects. Measures can give developers exact number, which can help them in further coding and increasing quality. There are several quality factors which affect software quality and source code quality is one of the most crucial. Its meaning is very important during development and in maintenance


Holák Peter

Abstract. One of the broadest areas in software configuration management is version control systems. There has been rapid progress in this area, especially in the recent years. A relatively new trend are systems that use a distributed approach instead of a central repository. In these systems, each working copy can function as a full-fledged repository. In this essay, I look at the differences between various kinds of these systems – how they affect the work style and for what kinds of project they are suited for. I examine the effect the choice of a suitable tool has on the development process and other influences on the project. I am mostly drawing on my own experience with usage of various tools in various projects, but I am also trying to take something from the opinions of experts and people who undoubtedly have something to say about this topic.


Jurčák Ondrej

Abstract. Monitoring and controlling of project in every phase of development process is important task of management. For the best project control, planning and control its performance, provide sufficiency of resources, is important estimate size and required effort of project in early phases of development.

Use cases play important role in software development. They depend from software requirements and describe its functionality. Making points of Use Cases we can estimate size and effort needed for software development, what is sufficient amount of information to create main line of project. Use Case Points outgoing from Function points and was first presented by Gustav Karner at 1993. However this method is known quite long time, it’s using on different types of projects point on success usage of this method. So UseCase points have advantages and disadvantages. In the essay below is described disadvantages and advantages of using this method on different kind of projects.



Paššák Peter

Abstract. Quality and security of software are very important goals in its creation process. This is also a need from customers, who demand reliable and safe systems. Fault tree analysis method is one of the methods used for searching risk points in complex systems and for increase of security. This essay talks about the use of this method in variable phases of the life cycle of software, about forming and progress of this method, about the creation technique and parts which construct the fault three. This method is also applicable for communication with the customer, where it has some benefits, which is also addressed in this essay.


Sedláček Andrej

Abstract. The essence of each successful project is effective communication among the team memebers. There are several forms of communication and also tools to enable these forms. It is very important to use the right tools in every situation what helps to improve overall efficiency of the team. In this essay, I discuss individual communication tools, its specifications, advantages and disadvantages. I also deal with individual phases of the project from the view of software agile development and according to research, I introduce the best convenient techniques of communication for each of phases. At the close, I describe using of communication tools within team according to my own experience and I emphasise its selection in critical situations.


Šimko Ivan

Abstract. Software development in distributed global environment is increasingly used by many companies. It brings many advantages but also disadvantages as it is relatively new way of project management and introduces many problems that need to be addressed. Software configuration management and its tools have a lot of potential to help in solving many mentioned problems, but still do not have the functionality required by many projects. In this essay we will discuss some of the introduced problems that need to be addressed as well as the added value these solutions will have for project management. The last part of this essay is focused on the problem of slow development and deployment of new tools for real world environments. We will discuss some of the causes for this problem and try to talk about the next step in improving these tools to better help project management.


Sokol Pavol

Abstract. Working with people in general can be very exhausting. Quality of team collaboration is determined by personal sympathies, temperament, personal and collective goals and the way the goal is achieved. All these effects are potential sources of conflict. A team player is aware of diversity in human characters and can accept it. A team leader should motivate people and lead them to higher performance. He is responsible for beating barriers and building harmony. Categories of human nature are not the strict defined norm to accomplish team building. It’s only tool to help break barrier and create social understanding. Motivation and dealing with conflicts are important tasks in project management.


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