Essay Collection 2009

Abstract:The need for planning in the software project almost any scale is indisputable. The project with no plan will almost certainly fail. The problem is that for different types of projects are appropriate different means of planning, the same we can tell about the scope of the project and the area in which the project is planned. In this essey I would like to make the introduction of, and to compare these funds. This article does not have the ambition to be a guide to planning tools to support the planning process, wants to on basis of this comparison to present the idea of a tool that would be appropriate for each project or at least most of the projects, whether it is possible to create such an instrument at all, and if not, what is it most today is close to or what idea or concept is the closest in today's conditions.

Abstract:Risks of the project development represent threat to the successful development and final deployment of the product. Experiences clearly show the need of risk management, so the project target may be achieved. Students, taking their study on the universities, are given role of the management, so they need to face risks endangering their project. This essay classifies risks as they are seen in the practice, categorizes them according to their importance and level of control. Gives picture of the risk planning management. Essay shows student experience with risks, risk planning management and risk avoidance from the university environment.

Abstract:Over the entire life cycle of software project, it is essential that each member of the team knows what his role is and what is decided. This contributes to efficient use of human resources, facilitating the control system to better the quality of their contribution to the resulting product. For these reasons, it is appropriate to create a so-called project manager. responsibility matrix, which describes the assignment of roles and responsibilities. Seldom are at the beginning of the role of stable and people that we have available. The creation of the matrix is a dynamic process that may end up with the completion of the project, which is produced. Essay describes the reaction to the continuous changes of tasks and people concerned with the added value of the matrix of responsibilities and difficulties in its development, describes the method of its formation by means of selective support measures and its impact on team cooperation.

Abstract:In creating a software product, the development team seeks to create quality software. Quality has become the main criterion when assessing software. However, to create a quality product at the very beginning it is extremely difficult, even almost unrealistic. Therefore, to maximize the quality testing is used. Testing reveal errors, which if deployed in service could cause problems, and their removal would be very costly, but also are testing to determine the possible objections or observations by the customer. The aim of this essay is to briefly bring the reader to the attributes of quality evaluation, the importance of testing, and in particular to highlight and explain the methods that are best suited for use in a team project.

Abstract:Monitoring the project and the adaptation of management and planning on the basis of the results is an important part of the project and its neglect or ignoring could have painful consequences for the finished product of the project. The result of proper monitoring is to identify the shortcomings of unforeseen and unexpected deviations from plans and thus prevent improper development while applying the precautionary measures. The aim of this work is to highlight the correct analysis of the results of monitoring, search for their causes and options for their removal. Another objective of this work is to show the potential risks in the event of ignoring or monitoring of its results, eventually the incorrect interpretations and the impact of this omission for the entire project and that project is carried out. The resulting work would bring a coherent view on this issue, which is increasingly in the development of large-scale projects, more important, because its main advantage is the reduction of costs for the production of the project.

Abstract:One many times neglect and very important part of management software project is the monitoring. Monitoring serves on early identification of possible problems, whereby gives an opportunity to rectification for relative low cost. One of the abhorred situations in the development of a software product is the frequency and amount of change. Therefore, project manager should continuously observe the potential changes between plan and real state. Through this essay, I would like to mention the value of the information obtained by the monitoring of the project planning and project management. How should managers respond to this information to avoid the possible problems, respectively deviations from the selected plan.

Abstract:One of the firsts task for the project manager is to create a plan and distribute task between team members. The choose of appropriate methods and correct progress monitoring with following actualization of working plans has significant impact on the success of the all project. It is thereof necessary that manager is familiar with the benefits and drawbacks of individual method and technique. The purpose of this document is to compare individual project planning and task distribution methods attributes, and select those, which would be beneficial for a small team working on a strictly time-bound project. The main attributes for choosing the most appropriate task are effective plan creation, plan correctness and early delay detection.

Abstract:We can find risks in some part of almost all projects. Risks can bring a new problems or show us a new solutions. That is the reason, why is risk management still more and more important in IT. Risk management search for a positive and negative parts of risk. Risk management show us how to identify risks, how to analyse it and find optimal solutions. Objective of a risk management is to minimalism problems of existing risks or prevent them. In my essay I will try to show you how it works. I will show how to identify and analyse risks and how to solve them. I will also compare different methods of solutions. In last part of my essay I will apply all my studies to my team project.

Abstract:High importance is being assigned to the quality in software project over the last decades. Apart from simple testing, the importance is put mostly on solid and effective testing plan and improving the product quality during each stage of its development. One of the most used procedures is called the software quality assurance. It can be defined as a systematic process providing that developed product will meet the expected requirements after its completion. The objective of this paper is to explain the procedure of software quality assurance in small software company (with less than 30 employees). I will introduce the quality assurance during product development stages, their connection to other used methods and procedures and I will attempt to define the effectivity of the quality assurance implementation.

Abstract:Everybody is unique. There is something positive as well as negative in each of us. Everyone has his/her own character. S/he is a personality. For each member of a team working on a project, it is important to know the characteristics, habits and favourite activities of the colleagues. This can help to utilize the time used for the creation of the project effectively and also avoid conflicts. If we learn the abilities of the individuals and give them work they enjoy, we will not improve only the product of the work, but also the relationships between the colleagues can become more pleasant and less stressful. Our team consists of six members, whereby every member has specific qualities, which ought to be utilized for the team’s own benefit. Every individual should know virtues, move them into the team and choose the role, which satisfies him. In this specialistic essay I want to point out the various personalities based on Meyers-Briggs Type Indicator (MBTI). Subsequently, I’ll try to divide these personalities in the team in the right position, whereby MBTI designates the individual types for the specific working position. I would like to apply this in our team to prevent potential conflicts in it, and to utilize the virtues of the individuals in the most affective way.

Abstract:The project continues and we want to make sure the course of the development project is in line with the proposed plan. However well requirements are calculated, the majority of projects are in the course of his creation different from the plan. Monitoring progress in the development of software project gives us the opportunity to find out the current status of the project. In the event that the current status differs from the planned, we should take the action, which will attempt to return the project back into balance with the plan. In the essay I will focus on the importance of monitoring and how respond to changes and deviations from the plan during the life of the project development. Highlight what results from the failure to plan and how the changes affect the team.

Abstract:People work on software projects with one objectivity – to order customer`s needs. But before we can consider group of people to be a team, they need to coordinate and cooperate each other. How should we control their behavior most efficient? How can we predict their productivity, estimate time for solving particular tasks, distribute people resources between parallel processes of development? There are many tools to help solve this problems. But we will not discuss, how to use them. Instead, we will try to find the motivations, that stands behind this techniques. We will take a look on the contribution, that is hiding inside them, and relations, that may be interesting. We will try to convince the reader, that planning is not a doctrine, but some kind of intellect`s apparatus, which should serve to formulate own opinions and principles.

Abstract:We have discussed the MBTI typology and the preferences of the single types. There were also mentioned several concrete examples from reality. One software team built from students was introduced and analyzed. We have spoken about the metodology of testing and results of the team individuals. After comparison with previous examples we have estimated the success of the students team in their two term team project.

Abstract:Using of support facilities is nowadays helpful in almost every (managerial) activity. It's very important in such responsible activity as managing of project. There are many user-friendly facilities, which impact on effectiveness is surprisingly big. Many studies have already been devoted to the irretrivability of these facilities, but almost none deals with comparison of two companies, one using and another not using these facilities. This essay deals with this problem. Its goal is to show size of impact that has management of software project without using support facilities for management.

Abstract:The risk is an integral part of everyday life as well as the software projects. It is therefore necessary process of risk management in the software projects which identifies such risks, analyze and provides ways to solve such a risk. Otherwise it might have a negative impact on the timetable for the creation of a product, reducing the quality of output and thus also cause economic damage. The objective of risk management is early identification risks, which makes it possible to avoid completely or at least minimize the consequences that flow from them. Risk management is an essential part of a team project, which is solved by students at the faculty. For this reason, my work will deal with just such projects, which because of its size and composition of the team requires a special approach to the planning, analysis and proper solution of the potential risks. The goal of my work is to provide an overview of the potential risks and how to deal with them at the team's project.

Abstract:Complexity of software systems is rising and so is the difficulty to keep their good quality. One of the most important parts of software quality is its correctness, which is usually verified through testing. Testing is an area, which has large range containing specific, but also more general problems, which need to be solved by every project. In general when developing software, we want to be as effective as possible and because of that, we should concentrate on making the testing process more effective. That is where test automation might help. In this essay I am addressing problems and questions about test automation, what are its requirements, advantages or disadvantages and why is it in my opinion important thing on which we should never forget when creating new software.