Essay Collection 2011

Abstract:Software development has it’s specifics. No industry such a low unsuccessful project rate (studies state that the number of unsuccessful projects over 50%) and only a small portion of projects are finish on time and budget. The figures could improve by using issue tracking systems. They support better status updates on development progress, support capacity planning and make plan re-scheduling easier. I’m focusing on comparing the formal task management using issue tracking systems and informal task using text annotations in source code. I analyzed the relationship between formal and informal task tracking

Abstract:During the development and maintaince of a software product it is important to maintain software revisions, which store state of source codes, documentation, and test data in different project stages. This accelerates the whole process of software developement. In my essay i mainly discuss questions why it is so important to create revisions of system, how can it be possible, and which revision control systems are the best choice in my opinion. I describe the main advateges and disadvanteges of centralized and distributed revision control systems.

Abstract:As the time goes, the mankind is still facing a new and new issues, which complexicity is still increasing. The solution of these issues is beign taught not only by a single person but usually by a group of people, a team. Work in team can be effective only when proper information exchange is being used. But how to organize the communication in team? What are possibilities for the team in the area of communication. What are advantages and disadvatages of different types of communication means? When the form is suitable not only for work but also for the education of team members? Finding answers to these questions is goal of this essay.

Abstract:Software testing is not performed until source code has been programmed. With the rise of agile software development methods called Extreme Programming testing is moved from the last phases of software development to the “heart” of development. Software testing has received additional responsibilities in terms of determining the characteristics of the source code and directions of development of small pieces of code. The main question that I try to answer the essay is the extent to which it is appropriate to use the test-driven development in a team project. Large part of knowledge comes from surveys which were implemented at American universities and thus at least partially meet the conditions that we have at our university. The theoretical part of this essay focuses on the description of the tests driven development method.

Abstract:How to collect and distribute the best tasks in a team? How much human personality influences the distribution of human personality themes? While building a team it is good to consider not only the expertise of individual members but also take into account their personality traits. Each individual has his/her own personality- which can result in positive but also in a negative light. Human personality plays an important role- not only from the actual staffing of the team but also in the distribution of tasks within the team. I discuss about the results of the Myers-Briggs Type Indicator (MBTI) for our team and try to guess which tasks are the best suited for who according to his/her personality. I also analyze which tasks are not recommended to be assigned to whom.

Abstract:Software project failure is also today when the projects are precisely planned into smallest details, surprisingly normal thing. Surprise or an unexpected event can stop a project immediatelly or even completely cancel it. One word - a risk. Risks are one of the main problems in software development, therefore they should be identified in the earliest stages of development, when in fact we still do not cause any problems. In the first phase, which is to identify risks, play a crucial role specialized software for simulating risk, risk factors in project and their impact on the progress of development and success of the project itself. Are the supporting software tools able to identify more complex? Is the whole simulation useless waste of time?

Abstract:Is it possible to group a dream team of individuals based on personality testing who will collaborate effectively and who will be failproof? Many people would benefit from this finding. It will be helpful to find a way to predict project risks and success. These days, development of software is not only programming an application. It is important to communicate and collaborate. Personality testing could help improve grouping people to effective teams, but how? In this essay, we discuss the Meyers-Briggs Type Indicator method (MBTI). I focused on the results of personality testing, I had tested my own team and I conducted the chances of team based on the whole group of people and also based on role to person distribution. I conducted the results of finding.

Abstract:The risk will always pose uncertainty and it still does not bring success. Risk-taking in process of creating software product does not pay and in some cases result in catastrophic consequences. Main role of risk management is to minimize loss. Each project is endangered by risks from process of product creating. Firstly, these potential risks are identified and with this approach is possible to avoid problems and ensure creation of product with full functionality before deadline. Because of this, multiple procedures have designed and they are used for risk management. Can we manage risk effective? What affect has risk to project outcome? We try to answer these questions. There are only few ways, how to solve management problems in projects and risk management is one possible option.

Abstract:“What a work such a payment.“ It was true in past and it is valid nowadays. Mentioned statement can be applicable for software engineering even twice, as there are high quality and quality management requirements. No matter how elegant the methods used to test the final product are, how complete documentation is, how structured the methodology is applied , the development plans are detailed, the project reviews, walkthroughs, … all will mean to nothing and the project fail if the quality management system is not effective. ISO 9000 is the most frequently used norm nowadays, which is used for implementing effective quality system. We are focusing on several questions. We ask ourselves and we are going to answer them in the end of this work. The main question is what contribution brings ISO to companies, i.e. if it is full-value improvement of quality system or if ISO is only mark without which you would not be accepted as an equal partner.

Abstract:This essay is about bug-tracking systems and methods of writing bugs reports. Imagine this situation: Someone is writing a bug report. If that person writes this report too long the appropriate developer would spend too much time of understanding of report. On the other side if the bug report would be too short the developer wouldn't find what he was looking for. We ask ourself these questions: What exactly are bugs? How to write bug reports? These are the main questions asked in this essay. If we use some methods and principles of writing bug queries we will lower the amount of time spent on understanding on side of developer. This time is in most cases longer because the developer must ask additional questions. Using these principles and methods we spent less time in dealing with one bug.

Abstract:For success of any software project it is very important, it is well planned. Effective planning requires knowledge of its parts and their resource requirements. The most important resource in the most of the software projects are qualified workers and therefore all the parts of the project must be well assigned to them. For this purpose it is very important to be able to estimate time required to solve the problem with available resources not only in the beginning, but also during the entire project. In the present there are several methods, based on which it is possible to make these estimations. What are there advantages and disadvantages? When is it appropriate to use them? In this essay I want to take a look at several different approaches, which can be used to estimate required effort and I will try to evaluate their asset for project planning.