Essay Collection 2008

Abstract:Ever bigger boom of the Internet and Web Services brings some new principles of system development and implementation. One of the most frequently used method is the SOA (service-oriented architecture) principle. Fundamentals are well-known but uncertainties appear. We are going to develop a new system. We want to go with times so we decide to implement a system using SOA architecture. We know what this is in aid of. We want how the system is supposed to work. We know how we can design it. But a lot of questions come up. Among the most relevant issues fall questions about system quality. Will the system be fast enough? Will it be secure? Will it be easily testable? And what about extensibility? Possibility to interconnect with other systems? This and some other questions related to the quality of SOA systems will be answered in this paper.

Abstract:A project is usually deemed as successful, if it meets requirement is delivered on the time and delivered within budget. It’s goal of the software risk management, which is an approach that attempt to formalize risk oriented correlates of development success into a readily applicable set of principles and practices. Big part of the essay is devoted about four risks management’s parts. Very importing and interesting is a text about divided risks to different groups. At the end it is written about educational institutions and risks in them.

Abstract:Planning is one of the most important and the most critical part of the project. Small mistake, although irrelevant at the first sight, can create big problems in later phases of the project. Many theories and methodologies for proper planning of the project were created due to these reasons. These theories assume that the project team has the fixed time for working on the project. But the project team in student projects doesn’t have the fixed time for working on the project. Their time possibilities are very dynamic and create plan for student project is therefore very difficult.

Abstract:Large influence on quality of software has code testing. In this document are presented some characteristics of code testing. Testing is cost activity, so everybody wants to make testing effectively as is possible. Very effective technique is code inspection. However, testing of object-oriented software has its own special features, that testing of other software has not. Essay is concerned on some techniques to inspection object-oriented code. In next part of essay are presented different testing techniques, their advantages and disadvantages. Aim of essay is show some testing techniques and helps readers to make testing more effectively.

Abstract:In each small group where people are working together and want to achieve a goal you can find management. In process of creating software project you have a lot of different tasks to do. These tasks are made by not only one person, but whole team. According to developing of the World, increasing needs and quality of software project it has to be found support tools. This support tools, tracking issue programs can help us, as well. It helps us in cooperation, checking state of tasks etc. Using support tools make management in software engineering easier, but we have to choose right tool and we can use it in right way.

Abstract:Planning plays very important role in software development process. Development of each software product is unique process; that is why it is not enough to define the plan just as a sequence of steps. In the beginning phases of the project it is not possible to define all the steps due complexity of the software, moreover the world of software engineering is very dynamic and the plan should be flexible enough to cover all the changes. Essay focuses on plan definition on enterprise architecture level. Essay does not want to be a set of instructions, how to develop a perfect plan. Essay wants to present how to define the organization structure and its processes to fulfill the project aims on time and in sufficient quality.

Abstract:No one of managers from a big corporation nowadays wouldn’t argue against the planning needs. Level of the traditional planning process is, however, outdated and doesn’t reflect modern corporations needs. Classic planning based on direct model, fixed financial process, annual strategy and allocation of sources without the ability of flexible distributing the resources – this is status of today. It doesn’t bring new opportunities for companies and doesn’t increase product value. Improvement of this process means to be individual, not to designate absolutely objectives, but relatives – to be directly competition comparable. In other words, it means market-oriented planning strategy and to cover up not only workers of financial divisions, but also other company workers. Don’t allow theoreticians to plan, but people with praxis and with practical market skills. How to build a modern planning system – that’s the question, with the managers worry about.

Abstract:The very significant part of a software project management is controlling and monitoring of the actual status of the project. This activity could notice the project manager about incoming problem early enough to react and to do some corrective actions. The aim of my essay is to describe the monitoring of the project, to talk about a few ways how to do that, about what parameters are monitored and how they are analyzed. Based on the results of the analysis it is possible for the project manager to choose the appropriate action to minimalize the variance of project plan.

Abstract:There are many types of software project management support tools. Some of them are used for communication and coordination of team members, others for planning, responsibility allocation, version control or issue tracking. There are also many kinds of software projects, each of them is of different range and has different needs of tracking of some factors. These facts imply that every project manager needs to choose right combination of software tools so that all support their project needs would be satisfied. This leads us to several questions. Which factors should be tracked for each kind od software project? How to choose the right combination of support tools for each project? This essay tries to find answers to these questions. It envisages the identification of needs of management of different kinds of sofware projects and choosing combinations of supporting software tools to satisfy these needs.

Abstract:Software project is process. In project initialization a plan is made. It is needed to have some process to detect real state of project in real-time to meet requirements of this plan. By the fact that exactly one plan is made is assumed that this plan is the best known this far to achieve defined goals. That is the reason why we are attempting to eliminate any differences towards the plan. Keeping the plan accurate is made by managing project, and after some time and gained experiences, we can make it better and use it in project. Aimed monitoring of project is inevitable to get details needed in project management and work made evaluation. What do we understand in real state of project? In what measure are we able to specify this state? How can we avoid differences towards the plan? Is it necessary to make changes in project and/or corrections to plan in case of differences towards the plan? These are questions I am to speak about in this work.