Essay Collection 2011

Abstract:Every one of us is unique man with goals and desires after entire life. We usually lead up all our materially, mentally and human resources to achievement all of these goals. We are consciously or unconsciously managing a planning our life under the influence. From the point of view this plans can be compared to project planning. We plan more extensive operations to achievement our goals in advance and mostly alone, or with your family, our loved ones, team mates. Variousness of approaches to making plans is very frequent event nowadays. Effective using of visualisation tools which are full of functions isn´t any speciality. Current support planning tools offer to beginner many new function elements with which we can´t meet in ordinary planning.

Abstract:The software product is not usually creating by individual, but by a group of people, especially if it is the larger solution. Man is a unique being with unique properties. Therefore, connecting more people together, shouldn´t bring a right compositions. People in the team affect to each other either positively or negatively. In order to create well-functioning team of people, we must first know the individual's personality. Therefore, in the essay I will describe the various characteristics of personality typologies. Next I will discuss roles, that are appropriate for different types of personalities and look at, what is the best composition of people, according to most studies. Finally, think about the composition of our team.

Abstract:Nowadays web-based applications are an important part of software systems. They are needed by more and more companies to ensure business services. Web-based systems as constantly in development and as they are more complex, the assurance of their quality can cause major problems. Testing can require a high amount of time, so the expenses can grow to unexpected measures. In this essay I am going to be concerned of possibilities of cutting down expenses during the testing of web-based applications, with the possibilities of different methods of user-based tests and with the possibilities of automatic error detection. I am also going to study different ways of motivation users during user-based testing.

Abstract:Time spent on project or his financial costs are the primer sources for decision-making in project management. Often in small or middle-sized projects in order to minimize costs project leaders decide to economise wrong aspects of software development and management. The example could be monitoring of software and process of his development. Monitoring is one of the sources of information important in process of decision-making. Subject publications concerning on this problem tends to analyse monitoring in complex way, or deeply describe specific metrics or approaches. They don’t offer complex view to the problem of monitoring small and middle-sized projects. That are projects, in which is increased requirement of effective monitoring and monitoring in proper range. I provide in my essay recommendation for monitoring range, which minimize time spent on monitoring, but also maximize positive aspects of monitoring for successful software management.

Abstract:Collaboration is one of the most important part of team software development in all stages, from analysis to testing and greatly affects its success. Today used collaboration support tools are mostly oriented on certain concrete activity, though it would be convenient, if there was a complex collaborative system supporting all aspects of collaboration like communication, cooperation and coordination. Progress of such systems goes on two ways: tools using Web 2.0 technologies and collaborative development environments. In this essay I compare these two different approaches, investigate their pros and cons and evaluate some existing tools from point of view of their usability in team projects. Moreover I introduce some possible improvements which could lead to more effective team work and finally I present my opinion on future development in this filed.

Abstract:In the time of great boom in economy and computer technology at home or in the world, there is necessary to develop new, more interesting and more complex software programs. And it is a work on such projects where is very important to follow certain rules, to determine certain priority so the entire project had the most positive qualities and the possibility of some risks have been minimized. Control and risk management in software projects are considered to be one of the key tasks which determine whether the project will be successful or not. But isit even possible to manage the risks? I will try to answer on this as well as many other similar questions in this essay.

Abstract:Software project monitoring is an important part of the work on a project, which is preceded by an analysis and design of the monitoring method. In addition to the explicit monitoring, when the developers create information used in the monitoring, the implicit monitoring is used, which involves authomatic data collection, for example from the software repositories. A lot of monitoring methods have been proposed, mainly related to systems with a specific characteristics (for example component based systems) or they are bound to the specific development method (for example open source software). This work analyses the restrictions of the studied monitoring methods and brings some thoughts about their boundaries and the ability to find broader possibilities to use them. There is even an ability to search their intersections in some specific case. We can then determine, if a simple way of creating of an generalized (usable in the most common cases) method exists.

Abstract:There are many situations during project realization, when some key task is delayed. Then it is necessary to shorten next task to reach important milestones and deadlines. In project management, there are many schedule shortening methods. However they are not used often by project management. In essay, I will show existing methods and experiences of project manager during large projects. The result of essay is that is too hard to use existing methods for schedule shortening. It is because of many attributes, for every single task, are needed. In addition these attributes are also difficult to obtain. Methods for schedule shortening are not used often because of these reasons. I take a thing about how to use these methods effectively. I will also compare critical path methods with graph based methods in this essay. The result of this essay is that simpler methods take advantage against complicated graph methods because of their clumsiness in large project plans.