Essays collection 2012
Home Home SK
"plan"
Belanji Juraj

Abstract. When a man stands in front of a problem, the first instinctive thing that occurs to him is to create a plan to solve that problem. Although that plan is not formally written, each person creates a plan in his mind. For creating a software product, a plan is also needed. The plan is the cornerstone of creating a good software product. As each person is a unique individual, so must any new plan be unique. But is this really true? Is it possible to create a plan, which would be a blueprint for creating new plans? This essay identifies errors that occur while creating a plan. The essay offers a different view on universal planning, and shows that sometimes a universally created plan yields better results than a newly created one.


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.


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.


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.


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