Essay Collection 2008

Abstract:Nowadays, the computers are inseparable part of our lives. There is large amount of software utilities, which tries to simplify our everyday chores. In strong competition it's necessary, that the produced software reach as high quality as possible. Quality of final product is affected by several factors. One of these factors is planning, which in large degree depends on monitoring of software project. Information flow demand systematic analysis of data, either by using various tools, or by utilization of human sources. Diverse character of these data require specific forms of presentation, either graphical, verbal or written. Many changes that arise in project's production process are results of monitoring, and emerge from data analysis of project's current status. The ability to react to these changes soon enough is necessary condition of project success.

Abstract:Planning plays very important role especially in large software projects. That is because it is necessary to keep using and managing great amount of resources (financial, time and man-power resources). It is planning that yields techniques to use and manage these resources effectively. One of the main goals of this essay is to present an analysis of individual plans to reader and successively also the problem of creating some basic plans, which are used in solving of every software project. The essay describes the division of individual roles in team and monitors their fulfillment. The essay also describes the situations, where goals are not fulfilled or goals are overdue. In that case we demand from plans to be flexible, to be easily updateable.

Abstract:In the contemporary age there’s increase of using of informatics in our society. Using of software spread into all areas of our life. Lot of companies is becoming highly dependent on using of software products. For that reason the importance of software system quality is growing. The quality of software systems is a very discussed subject of many conversations and there’s a lots of procedures, models and methodologies for quality assurance management. Software projects are very different and each of them has got a different quality requirements. For that reason it’s very important to choose an appropriate system for quality management which is dependent on the nature of each project, on the … of team and other attributes. In this essay I will focus on quality assurance in small software projects which are similar to projects developed on our faculty.

Abstract:Development of software systems is difficult process. Demands on the system functionality and quality are growing every day. This is putting a tremendous weight over shoulders of people connected in software creation process. Many software projects have trouble to achieve their outcomes or fail completely. Software risk management is the approach which is able to revert these negative factors. This essay brings an overview of software risk management. It also presents a simple tool to quickly estimate the overall risk of software project.

Abstract:As well as in other areas, in the area of software development quality plays a major role in determining the competitive attribute of the final product. One of the basic tools for software quality increasment is its systematic testing and validation. With enormous development in area of software development testing become untrivial process spreading into all phases of software lifetime cycle. In this essay I will concern on process of software testing in a detail. I Introduce some of the well known models of testing as V-model of software development or Test Driven Development model. The main motivation is to focus on testing techniques concerning application for small teams.

Abstract:Problem of information overload, also called information pollution is interfering with whole areas of human activity. It is related to growing use of Internet in last twenty years and increase of communication tools numbers. This essay is dealing with usage of support tools for management of software projects, planning, management of human resources and their connection to information overload. It also offers view of support tools for management of software processes and methods of their use, that can minimize problems with information overload. Part of this view is a speculation on the impact of CASE tool usage on success rate, price and another aspects of software systems development. Particular attention is dedicated to differences emerging in smaller software development teams, where team members often change their roles as time goes on, such as team projects at universities.

Abstract:A project plan is an entity, that accompanies a project through it's whole lifecycle. For different parameters of the project, estimates are being used in the plan. This essay aims at the time, cost estimates and the project size estimate. During the duration of the project, the project plan has to be revised and updated. The most important parts of a project plan are mentioned in this essay and it focuses on the reasons, why the plan needs to be corrected. We try to uncover different factors which influence a project and its plan. We also lay out the relation between project parameter estimates and the project plan changes. There are several models mentioned in the essay, which are being used in the estimates and we try to predict their future advancement. This essay also deals with setting up student project's goals and possibilities of planning such a project.

Abstract:The document offers general information about project planning. Readers, who don't have experiences with project management and planning, would find planning as necessity to manage successful project. How to define aims, resource requirements, work requirements, how to make the plan which will keep the project running – answers to these questions can be found as basics of project planning. In the essay, there is also explained, which questions planner should answer during process of planning to make the project plan useable to reach specified aims. After reading this article reader would know the basic knowledge to plan the project of small range.

Abstract:It is hard to draw a picture of a manager managing software project (either using traditional methods such as tables or models, using software products or without using any support). Number of managing methods is still increasing and so is number of ways how to approach them. Common sign of all methods is reason why they were made – simplification of work while managing difficult (not only software) projects. This essay will explain potentiality of support tools, ways how to use them and will identify cons as results of wrong choice or use. First part is specifying content of correct management method (tool). Second part looks at use of methods in communication and tasks (planning, assigning responsibilities, successful finishing).

Abstract:Development of software products is a complicated process, which has to be planned precisely and then controlled. Even of all the effort to follow the plan, an unexpected event can occur. These critical situations can be predicted and controlled, however it depends on the applied method. Existing methods are different in their usage, reliability and period for predicting the risk. In this document we focus on to provide a short description of risk management cycle. Beginning from risk identification this paper takes us up to the usage of risk control. We describe the methods used in work experience and refer to pros & contras and possible application in software projects.

Abstract:According to increasing complexity a importance of software products, the phrase "Software quality" is becoming more important. However we are using this phrase more and more often, there are not many people which can fully understand meaning of this two abstract words. The Goal of this essay is to introduce various ways in which is quality of software perceived in present days. There will be also described pros and cons of this ways according to user's and programer's view. The will be part describing the measurment and matric used to measure quality of software.

Abstract:Nowadays, majority of software development is done by teams. Teams consists of many people who communicate and cooperate together for the purpose of solving problems. Software project management tools makes work easier, are conductive to better cooperation and last but not least they assists to keep better overview about actual project state and hels to make better view of project state. Therefore software management tools are important element of software project management. The focus of this essay is to approach the importance of these tools in present days. This thesis also describes basic properties that these tools should have since there are a lot of available tools and it is not easy to choose properly. In the article there are also described advantages of the tools and the main goal is to highlight the their significancy for project management.