Essays collection 2012
Home Home SK
Group 6
Cádrik Michal

Abstract. Documentation can be found everywhere around us and in every process of human activity. The process of software making is not an exception. It is a necessity which is very important for the process because of its complexity Writed type of documentation was enriched by graphical elements in the way of UML diagrams which are more suitable for reading and understanding of program's processes. UML could be a replacement for the textual documentation. If it is possible is the point of this essay. The one pro is part of UML called executable UML (xUML), which is the basis of model driven architecture, is very strong argument for graphical documentation, because developer does not need think about implementation details of specific language.


Červeňák Matej

Abstract. The essay focuses on the monitoring of software projects. It raises issues associated with software development and its proposed solution. It highlights the need for monitoring software to enhance the quality of the development and indicates the possibility of specific methods of monitoring, by means of software agents. It discusses the quality of this technique and presents the advantages and disadvantages of its use. The main point of the essay is a comparison of software agents with human beings. This is a comparison of their properties and then their reasoning, justify a situation where it is advantageous to use software agents and how to manage these agents. On the other hand, it talks about the opposite satiation, ant the disadvantages of software agents, which favors a major player in person.


Čorej Tomáš

Abstract. Electronic software distribution is changing our lifestyle because it has become a part of our lives. Integration and success of those platform makes Internet payments and software distribution easy. Nowadays, when we may anytime buy with one click software for fun or business, we should ask ourselves how is this everything changing our look at the pirating software.


Detko Martin

Abstract. In this paper I try to find the causes of low quality of student projects and possibilities to improve their quality. One way to improve quality, described in this paper is to test projects with acceptance tests. I discuss the possibility of publication the acceptance tests for students and subsequent methods of evaluation. In addition, I try to distinguish the situation of small tasks, which need only implement a simple algorithm and larger projects where you need to make design. Another way to improve quality is to change the way of development. Especially, I analyze the test-driven development. In this case, I describe the reasons why it is good to use this type of development compared to traditional approaches and to find potential problems with its use. In conclusion, I try to summarize if it is better to provide complete tests to students or trying to force them to make their own ones.


Kvitkovič Matej

Abstract. This essay covers comparison of version control systems. There are two main architectures these systems implement – centralis ed and distributed architecture. For each of them, there are many mature tools with different attributes and features. Essay compares features of tools of both architectures, covers history of their development and usage and their current state. The two tools used for reference are Subversion and Git. Essay considers the usage of those tools in a software project. It arguments the use of a distributed tool for Team project - Digital Theatre. After considering the needs of our team, it marks the flexibility od development process which is offered by distributed tools as the most significant feature. It saves time and with that all the other resources required.


Lezo Andrej

Abstract. In the next chapters I analyze broader look on Riskit method and reason, based on case studies and avaible materials if it can help in risk management. Its main properties are structural process and complexity. It contains many same steps, which couldn’t bring us to the desirable result. Of course, it’s important to choose correct and appropriate way of usage for this method. Main reason why its usage is applicable and only large companies benefit of it is that too much effort devoted to every step is required.


Mačuga Peter

Abstract. Essay provides a subjective view of the estimation techniques or project planning- earned value analysis with use case points. Technology itself is outlined only in broad outlines. Negative author’s view dominates the essay, this view is supported by facts, personal experience and subjective opinion. Essay analyzes and gradually disproves, or finds alternatives all of the positive aspects of this technique. It proves that always depend on people, their feelings and experiences in software planning (monitoring), it is impossible to replace them with mathematical formulas or procedures.


Mihalik Matej

Abstract. Critical path method is currently a very wide-spread and popular method used in planning of software and many other types of projects. A reader who does not have a complex understanding in the field of project planning can often stuble in the dark when it comes to the choice of which method to use in planning of a specific project. This paper is aimed exactly at such readers, since we will take a closer look at the critical path method planning, its usage in the real life projects, and we will try to answer the question of why should we consider using this method, and when is it most beneficial for our goals. We will present the method's various characteristics, and afterwards the method's pros and cons. In the end we will discuss the method's appropriateness for various kinds of projects, considering their size, as well as the development model used.


Neslušanová Lenka

Abstract. Common people can imagine planning like a notepad where they can write important dates or like a phone reminders, which beeps in an important moment. The same concept also includes complex processes which keeps order and control of the huge IT companies all over the world. Maybe not everyone gets in the organization of that size in his life, but planning is an important element of any company and in some way we use it daily in real life. The main idea of the essay is focused on selected factors influencing the planning and their different involvement in agile development and the the waterfall model. I would like to show what are the advantages of one approach over the other in dealing with these factors, or which should be focused in each approach more or less.


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.


Ševcech Jakub

Abstract. A large part of the success of each project is the approach to the communication with people. In order to have product that people use, it is necessary to attract them and convince them that yours project is the right one. In the open-source projects, the communication with users have also another dimension. We try to create a community around our project which would not only enjoyed our product but would also contribute to it and would try to improve it. This essay describes means to establish a "relationship" with users and maintain the community as well as instructions on how to use these means for motivating people to participate in the project.


Slotík Igor

Abstract. When creating a software product, especially at the beginning of its life cycle is a great need for communication. Implementation would not even really begun, if every developer did not know what has developed into components which can interfere with where and how to save changes to the developed product, who are his superiors. Lack of communication and organization will return in the form of conflict intervention in the source code, changes in technology, failure to meet inspection deadlines, or total failure of software development. Need for communication is particularly appreciable for distributed development. If you have distributed teams since the beginning of the problem to agree on important issues, software product development is threatened. In the essay, I want to think about when and even whether it is worthwhile to distribute the work and if so, what methods and approaches to solve the communication problem of distributed development.


Žilinčík Michal

Abstract. The essay clarifies principle of conflict, its possible consequences and the most frequent and the most important reasons for its occurrence. In this context the essay discusses the impulse of trying to fulfill one’s needs and the fears of losing one’s safety. Even though conflict is neither bad, nor good in its nature, the essay focuses on options of anticipating it. When it comes to causes of confrontation it emphases the importance of proper communication and active listening. That helps to eliminate uncertainty and fear rising from it. In essay I accentuate possibilities of precaution in avoiding conflictful atmosphere in teams. Besides clear phrasing and active listening, we can include lots of managerial and organizational actions. The essay describes e.g. keeping subordinates informed about current goals and heading of the company or the tea and creation and updating written methodologies.


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