Essay Collection 2009

Abstract:Every skilled master starts his job with preparing all necessary tools. Even during the work he tries to improve these tools, changes them to better ones until he is satisfied with his work. Instruments such as support tools extend our talent. They will become like an extension of our hands if we learn to use them correctly. This paper generally describes the main tools in monitoring tasks in software project development, but particularly in terms of their impact on usage, in essence, it describes team management for their use. However, it contains some handful tools that do not relate directly to them, but there is the basis for most project teams. The aim of this essay is to offer a view from the other side, the side of the scheduled task. So how these tools effects task evolution and whether they will actually speed up task, as would be expected. Article offers several my interesting experience in working with instruments of that kind as well.

Abstract:Creation of software project is affected by many factors. If they are human factors or not, each one can cause unsuccessfulness of project or contribute for it. If project managers want success of their projects, they need to give beams with risks of their projects. It is necessary to perceive that in many causes also little time delay can cause big economic fall. Risk management is a collection of techniques, which help managers to identify particulars risks, prevent them respectively prepare for them and down the fall. In these pages I will describe most known and most often identified risks which exist in development of software project. Thereafter I will describe some approaches how to anticipate them.

Abstract:Software project monitoring is very important process during project development. Practical realization may vary and depends on different factors. Size of the project is very important as well as team structure. Within small projects, monitoring is usually provided by team members, but larger projects certainly need manager or managers. It’s also interesting to watch differences between school and business projects. Each of them has different motivation of the team and because of this, monitoring is also different. With wrong approach chosen, things may become very complicated and can result to bad consequences such as wasting human and financial resources, project overrun or even project collapse.

Abstract:A well-defined plan can become a good starting point in order to achieve a successful project that results in meeting the needs of a customer. This essay gives a detailed guide for project planning. I have concentrated on planning in small teams and have described the fundamental principles of management planning for those uninterested in the field. I have tried to focus on the importance of a plan and the advantages associated with it. A well-made plan can become a means to simplificate the development process of a software product with the emphasis on saving resources, money and the overall improvement of team work and effectivity at work on a project. The document rivets upon the iterative life-cycle model and mentions its elementary behavior compared to the waterfall model. The plan of a project accentuates the assessment of time setting, budget and dead-line observance. The document also mentions risks that occur in the majority of projects.

Abstract:The development of projects, small or big, software or of other types may also mean a creation of errors. The programmers create a code, but also errors which simply cannot be avoided. Testing serves to reveal and minimize the unwanted and unpredicted application failures, or to evaluate the project state. There are a lot of ways and plans how to perform testing effectively and qualitatively. However, the plans are not always performed successfully. It is often demanding to provide a skilled staff, or there is not enough time to carry out the testing plans. Testing plans may also fail easily if the used methods or tools are inappropriate. How to choose the appropriate way of testing? What techniques to combine? When to involve testing in the project? I will try to look at these questions more closely and reveal some erroneous decisions and practices that may occur in testing, as well as situations when testing can be ineffective and cause delays of the project development.

Abstract:Projects in software engineering are mostly concern of team work. Therefore is essential put together efficient teams that would solve these projects qualitatively. Following MBTI personality test we can determine personality types of team members. According these profiles we could know what we can expect from team members and what tasks we should give them. Author of this essay describes how should be optimally delegated roles in team in which belongs himself as well. This delegation should be done according to personality type of each member. Further describes how to solve conflicts between individual personality types and how to improve collaboration between team members. According to this information and solutions should performance of team increase.

Abstract:In software development team are meeting different types of professionals, which should be during the certain period of time cooperating on the same purpose. In the process of creating such a team is important to consider not only professional skills of participants, but also their personal characteristics. This essay describes metrics used to analyze personality styles, and how to exploit the results for improving existing team, assigning workers to positions or creating a new one.

Abstract:Planning plays very important role especially in large software projects. In software engineering exists many ideas and approaches to planning project. One of this approaches is iteration planning or otherwise said iteration development software. One of the mail golas this essay is explain reader definition iteration, purpose, necessity, reasons creation and usage iteration in software project. The part of this essay is short description, advantage, disadvantage and suitability usage other princip of planning, which from historical aspect forewent iteration planning. In not least stage essay deals with explain princip agil methods and their exploitation in iteration planning concrete exploitation extrem programming.

Abstract:The typical production environment has certain characteristics which may negatively affect software quality. The developers have widely varying level of skill. Customers have poorly defined but often complex objectives and are usually interested only in the software output. Also the frequent changes of the people in the team contribute to the decrease of software quality. Quality assurance as a process involves all activities aimed to assure software quality. That means careful attention to the specification of the requirements to be satisfied, to ensure they accurately capture what is wanted or intended, and the formulation of the test cases that can be used to demonstrate their eventual satisfaction in code. Testing lowers the probability that the created software won`t work in some cases as desired. It cannot guarantee us flawless software though. A lot of money is spent on testing during the software development. It is crucial to choose the proper testing method and reserve the adequate amount of time in each phase of the development process. In this paper I would like to introduce some of the approaches to testing and quality assurance.

Abstract:Nowadays a lot of software projects are rising, but only small part of them are successful. One of the major reason of failure is insufficient management and absence of support tools. Managing of difficult and extensive projects is time-consuming process and requires considerable a number of resources. With right choice of support tools we earn a lot of extra time, which we can utilize in more effective ways. Support tools are playing the prime role in control and management of resources, tasks, plans and communications inside the team. There are available a lot of support tools in the market, which are different in many aspects of usage and convenience for given project too. Aim of this assay is provide to reader the base overview of available tools and methods, describe their utilization in process of control and evaluation theirs applicability for given type of software project.

Abstract:The goal of Team Project is to prepare students for working in a smaller team. Inside the team different roles are assigned to individual students and most often the project traverses through all development phases. Thus, in Team Project management conventional methods used in practice for other projects can be applied. However, to most students it is just another school subject. Also the requirements for operating procedure and final product, including documentation, differ from those in the projects run by large companies where the main goal is to satisfy the customer. The author tries to present an objective view on risks occurring in Team Project and introduces his own opinion on how these risks can be reduced by increasing the team’s morale.