Essay Collection 2009

Abstract:On every product, which has been formed till now, man or group of people was sharing in to a great size. But everyone is unique and in forming of this team is necessary to reflect several factors. Between most important belong collective co-operation and preventing conflicts between members of team. For choosing the correct team is necessary to look not only at skills of single member, but also at his personality character. Choosing the best decomposition of people is not easy, but there are several methods used in practice life. This document is for people who can make a good team.

Abstract:Plans have been used for a very long time in all spheres of human activities and also in software projects. When talking about software we speak about plan-controlled development. However, is it appropriate to use such approach in this case? It is difficult to create an exact plan, considering potential changes. Especially in a software which is to a large extent nonvisualizable. Various methods are used to solve problems with correct estimation of the time period necessary for the project and to create a plan consisting of the individual suitably decomposed tasks. In this essay we will get acquainted with them and we will evaluate their strong points and weaknesses. We will compare the selected methods and we will try to find the right one for creating plans in software engineering.

Abstract:Nowadays, we do not know the way, how to assure absolute perfection of software products. However, there is big amount of methods, which improves quality of produced software. In spite of it, these methods are not utilized, especially in small companies. The consequences are complications with testing and the insufficient product quality, when products contain lot of errors. That is why the inventing of new better methods of testing and improving of quality is big challenge for whole computer society, as well as the finding of way how to bring this progress in the use. We can develop more quality software using more quality tools, because the tools are exactly the things, which give the power to humans in different areas and improve their abilities.

Abstract:People participating in software projects usually take advantage of some form of task tracking and management, whether it is using stickies, MS Outlook, or software designed for this purpose. Usage of such software tools can significantly simplify the work of management; however, it can sometimes introduce new hazards. This essay deals with the importance of these tools, as well as the requirements on them. Furthermore the essay analyses the problems relating to the use of support tools of project management and considers options for avoiding these problems by using agile methods of development.

Abstract:Every phase of software project has its importance in complex process of system development. In this work, I try to explain some aspects of monitoring small software projects. Often project managers ask questions like “How much work have we done and how much of work is still to do”. We need to get very concrete answer on questions like this. There are some methods and techniques such as EVA, which managers can use to keep good orientation in project costs and schedule. In academic software projects such as Team Project, this methods need to be modified. In this paper, I show the way, how EVA can be used properly in non-commercial project. Other idea of this work is considered about the influence of monitoring the project on project realization. Does project monitoring make realization of project faster, or it causes too much pointless work to be done? More questions like this are discussed in this paper.

Abstract:Today, when every second of time is important and client wants to see the results immediately, there is no place for mistakes anymore. There is a pressure from every side, bringing risks which endanger the project. Risk is often seen as a danger of some kind of loss. Risk management as well as the preparation of adequate safety solutions is a complex problem. Analysis and risk management helps to prevent or at least minimise situations which could endanger the time schedule, or worse so the software project itself. The paper deals with risk occasions' elimination or at least minimisation of their negative impact on the software project. Moreover, different mistakes and risks' sources which most frequently cause a project failure are analyzed and divided into groups, e.g. foreseeable and controllable or the uncontrollable on the other side as well is what the meaning of a risk itself. Finally, different approved models of software development are mentioned.

Abstract:During the entire period of the life cycle of the solved software project increases together with its increasing complexity also the relevance of the question how to manage this project. Each project is linked to a limited number of resources that improper use can be significantly expensive. In order to solve this problem a number of supporting tools was created to help managers in the way of their effective management. The ambition of this essay is therefore to familiarize the reader with some of them concentrating in particular on supporting tools intended for tracking tasks and allocating human resources. Paper also deals with the appropriateness of their use in small teams, solving the task of the scope of the team project at FIIT STU.

Abstract:Planning is an important part of the life cycle of every - not only software - project. Nevertheless it is often underestimated, or even completely ignored. It is particularly true for smaller projects, where people assume, that if the project is smaller, it must be also simple. So what is planning for such project good for? The planning process will take more time than the execution! This may not always be true. And often it is not. In fact, also a simple-looking job can show as complicated and vague. People are often forced to literally throw away a lot of work and return to the beginning. Finally one spends more time on the project than one wishes and the result do not necessarily correspond to the expectations. In this paper I will point at the fact, that it is well worth to plan also a smaller project and that planning is not for lengthen the project, but on the contrary, to simplify it and prevent unclear situations.

Abstract:Formation of a team is usually given to workers themselves. There is a method which determines the personality type of each person. The creation of a team is based on the results of this method. The personality type can be determined using various tests. The most known is the Myers-Briggs test, which determines the personality type based on a yes-no test. In this paper I will write about the impact of various personality types on a software project. I will find out the personality types of my team colleagues from Team project class, test if we are a good team and assign functions to every team member.

Abstract:Each developed system requires the implementation of certain means, such as time and money to its successful implementation. During the life of the development of the system may be the moment we are unable to tell the status of the system is. This can cause considerable problems, such as failure to meet the time schedule and the worse case is the failure of functional requirements. That as soon as possible, such weaknesses revealed, it is necessary to monitor the state in which the system is. Monitoring can be achieved by reducing the surplus funds for the development of the system as well as to identify the possible inaccuracies in respect of the requirements, which has developed a system to meet. In this essay I will try to explain why it should be monitored the developed system, show the ways what can be system monitored and what should be monitored for the development of more and which can give less attention.

Abstract:As the title says nothing ventured, nothing gained. This applies as well to software projects. It’s really important to have all risks under the control. Otherwise project will end prematurely and makes deficit instead of profit. According to miscellaneous researches unsuccessful projects occurs to many times in software development. Because of that, companies try to minimize risks as it’s possible. Risk management is used for assessment and risk planning in software projects. Risk management by convenient techniques identifies, analyze and control risks in software project. Thanks to it project manager increase probability of successful project conclusion, without time delay or cost overruns. This essay concerns lack of using risk management during software project development. Next thing that I’m concerned with are methods used to analyze risks, estimate risk exposure and methods used for mitigating identified risks.

Abstract:This question niggled my mind because of my practice. To be specific what practice, it is my short-term occupation in a test team. You could oppose that my short-term, approximately two months long practice does not give me the right to express doubts and give judgements. However, quite the contrary may authorize me to this, if I see the imperfection so soon afterwards. I will summarize them. Test team is an odd expression for something that can not be called a team. After all, a team is mainly about co-operation, which leads to bigger utility than amount of utilities of individuals. I do not see this in the test team. Outcomes of one member of the team are not used and if they are used, they are used only in limited way. Every member of the team works only for himself, he tests manually or he writes automatic tests for requirements assigned to him. It means that cohesion of the test team is low and that is a problem. If every tester tests his own group of requirements, would not be better to subjoin him to the developer team that implements the same requirements? Is it not better for him to be closer to the source and to the potential changes of the production code? Nevertheless, there are two sides of the same coin. I will try to summarize pros and cons of an individual test team.

Abstract:Area of informatics is rapidly developing. In the same way are developed also management theories of software projects. Every day are announced new theories around best way how to guide software projects. Nowadays, project supporting software is unsplittable part of the whole process of managing a software project. This article guides you through todays trends, and helps you find the best solution for your needs.

Abstract:A key to successful project is planning. Creating a plan of the project is the first step we should do when starting a project. We often rush into the the project before we do a proper project planning. Many people do not fully understand the value of planning in the form of saved time, money and possible future problems. This essay points out the meaning and the importance of software project planning and suggests a simple and practical approach to a software project plan.

Abstract:Project manager or person responsible for leading a team project, even of smaller extent, should be ready to face a crisis that may arise during project development or after its start-up, to cope with problems like unmet deadlines, overrun budget, system functionality differing from projected design etc. Such issues are not rare. Solution is to foresee unwanted situations and plan a risk. In my essay I shortly write about common known types of risk at lesser projects, about sources of the risk and also about particular methods of management and risk analysis. I would like to demonstrate on examples, I have experienced, possible solutions of risk management application which would lead to a successful progress and completion of project.

Abstract:Development of time and resources demanding large-scale software systems requires integration of several people into project by creating working teams. To build a productive and effective team is far from being an easy task. Besides the professional qualities of potential team members, their personality characteristics need to be also considered. These characteristics determine how well they will be able to cope with upcoming problems, that will influence whole team’s performance at the end. In the process of creating team and identifying team roles the application of personality analysis method may be very helpful. Currently used methodics define which role particular personality type fits the best, considering its behavioral traits, to make the biggest possible contribution to the team. This essay tries to answer the question whether the role, which one’s personality traits determines for, should be hold just because of the biggest expected contribution.

Abstract:Currently, a growing requirement for software creation and also process of software development becomes more complex and management of project is more difficult. An important role in the process of software development has monitoring. Monitoring helps in detecting deviations of the current state of the project against the initial plan. However, in order to be able to monitor the project must be clearly defined rules by which to evaluate the current status of the project. One of the options to monitor and supervise of the project is the integration of software functional size metric, COCOMO II and Earned Value Analysis in the process recommended by PMBOK (Project Management Body of Knowledge’s). This essay will focus on the clarification of these procedures.

Abstract:Fast evolution in software’s world changes character of internet from small amount of Web pages into big complex of Web applications, they provide services of various kinds and they are equivalent alternative to traditional software products, these days. Incremental complexity of Web applications results to need of new testing methods of development this kind of software, it’s not satisfied yet. Web applications are still testing with traditional methods, they are ineffective and expensive in many cases. Aim of this essay gives an author’s view to problems of software quality assurance. It deals with vulnerableness of low-quality software and reasons of their origin. It wants to point out ineffective testing techniques of nowadays. It thinks about possibilities of Web applications testing as interactive, multi-platform, dynamic system. At the end it tries to give a solution to improve efficiency of testing.