Essay Collection 2011

Abstract:Software engineering as a relatively young branch has gone through an extraordinary evolution during the last couple of decades. The method of testing the software changed with the development of software engineering. Software testing gradually became more professional and automatic, as the systems in development were becoming more extensive and difficult and errors found late became more expensive. Nowadays, there are several approaches to software testing. In this essay, I am contemplating the current state of the testing and its future tendencies. Some well-known methods are mentioned, such as black-box and white-box testing, but also more modern approach including test driven development. It is also discussed when to use which method according to the project and phase of the development, which person from the team should be testing and how. I will conclude with my opinion on testing our own project for the subject Team project.

Abstract:Estimation of software project can greatly influence its planning process, its course, and its outcome. How the estimate affects the project, depends on its accuracy. Generally, the more accurate the estimate, the better. But how do we obtain an accurate estimate? Is it even possible? Creating a good estimate of a software project is costly and difficult. Is it beneficial for all projects to create estimates? If yes, how should they be created? I look for answers for these and other questions in my essay. I address several methods for estimating software projects, their performance and accuracy. I address the need for estimating various types of software projects and how should these projects be estimated. Finally, I discuss the issue of estimating in the light on our team project.

Abstract:Currently, we often experience the situation when the individual team members may be situated anywhere in the world during the entire cycle of software developing in team. This fact does not inhibit them any substantial way to carry out their role in the team. One of the problems that arise in the management of the project is how to check the status of the project and also overload on the team members. The aim of my essay is to point to the benefits of the support tools, which allow to monitor the status of the project whether the projects are managed by the agile or increment-iterative methodology. I weigh the techniques that could be possibly used by a combination of the imaging methods in both methodologies. I try to express my personal opinion on the issue based on my own past experience.

Abstract:When we create either smaller or bigger software projects, it is suitable to have more people to make it and create a team that works as good as possible. Sometimes, it may be very difficult to make such powerful team. It is not the best solution to include just specialists or experts in their sphere into the team. Personality trails of individuals are also very important aspect when making a team. The best way how to make a perfect team is to involve people with different types of personality to make the team more various. In this essay I briefly describe characters of personality according to very often used Myers-Briggs Type Indicator. I also describe suitability of people for concrete possitions in the team. I am concerned with conflicts, that can happen during the co-operation and also with the manner, how to prevent it. I think about the way how to make a team for smaller projects like team projects at universities. Whereas I am part of the team that works on a team project during the time I am writting this essay, I am trying to analyze our team, and I am estimating our efficiency according to results of the MBTI test.

Abstract:Small projects are often underestimated, therefore there is not much emphasis put on analysis and risk planning. This may cause complications for the project, complete failure in the worst cases. It has, for the most part, resulted in deliberate overlooking of the problems and carefree approach. A large part of these problems would not occur at all, or could be easily solved with the correct approach. The aim of this essay is to assess the most serious risks occurring in small projects, while drawing from my own experience. The next aim is to show the basic principles of prevention from these risks and assess the errors which are mostly made in software projects.

Abstract:One of the essential components of a software project success is the monitoring of project’s progress. The essay focuses on key elements of this process and tries to assess the effectiveness of various approaches to solving the problem. Emphasis is put on importance of acquiring a good overview of the project and choosing a properly defined approach to data analysis. It is suggested not to underestimate the importance of communication – both with team members and with the customer. A few methods of monitoring the project’s progress are discussed to provide some insight into the various approaches. Final part of the essay is devoted to describing the importance of manager’s personality for effectiveness of his work.

Abstract:Diversity and complexity of software is increasing day by day, therefore, must be provide software quality. Software quality is considered more attributes of quality, whether it's performance and usability for end-user or high stability and reuse. Emphasis on improving the quality of the software development system and avoids confusion in the actual implementation. Testing is compared to software quality assurance focused on "detection". When testing software quality reveals the shortcomings and errors developed by the software, therefore it is necessary to test the software, although it seems that it is not necessary. Currently, there are many different methods of how to properly test the software quality. The essay focuses on quality assurance and software convinces you that the development of controlled tests, saving valuable time and money by comparing with software testing after the completion of implementation.

Abstract:Division of labor accompanied us for thousands of years, mainly due to different skills and abilities of each person. I tis still true in many different fields, including software engineering. To work on large team projects should be the focus of many different people – from across the emphaticanalyst programmerfair to responsible managers. The calculation of properties i tis clear that some people have greater moral prerequisites for a specific job. Essay points to the appropriateness of creating diverse teams, not only in terms of expertise but also the character page. Such a composition is preferable from the resulting negatives are more acceptable and easier solvable than with uniformly teams. The essay focuses particularly on the smaller working groups and the specifics of the creation and operation of school teams. Finally, analyze and evaluate student team, which I am a member.

Abstract:Software development is usually complicated and time-consuming process that is inextricably linked to each stage in use of different files or documents. Not all files are in final form, but they are a subject to further modification. Especially working in a team requires an option to modification shared files, where the changes do not always progress. Often, therefore, is needed to return back to the previous version. Versioning and change management deals with monitoring of software development from this perspective. The methods, by which it can proceed, are different. In this essay I give my opinion on various methods of version management, highlighting their advantages and disadvantages. I think about problems that may be by using different methods arise and what impact it may have on the overall software development. I believe, that we have to use versions, but which way is correct?

Abstract:Coordination and management of the development team demands from the project manager, information about the current status and distribution of tasks in the project. There is a wide range of support management tools to overview and administrate these activities. These tools play an important role in the software project. For large projects, these tools are necessity necessary, almost a inevitability of success. Their application is Reasonable in the commercial sphere, where the motivation for on-time fulfillment of assigned tasks is clear. Essay considers the case of using management tools in open-source projects to monitor and manage tasks. Discusses projects that are developed by community and a developers can become basically "anybody". Such motivation of developer is questionable and manager by managing such a team has to solve problems with human resources, such as load or duration of tasks, more often. The solutions are not always straightforward and problems often repeat.

Abstract:We have been imagining our future since our childhood, we have our dreams and targets. We need to create plans and follow them to achieve our targets. This is the same in software engineering. To reach our set targets we need to advance alongside well premeditated plans. This essay is dedicated to planning. At the beginning we point out what we understand by planning and introduce few means and methods used for composing plans. Just like in everyday life, even in the path of software development may occur some unforeseen occurrences which can slightly or completely change the original plan. I show several examples how to deal with the changing of plan, adding some examples from my own experiences, too.

Abstract:Cooperation of more then two people in software development is now common practice. An important prerequisite for the cooperation is communication between team members, with emphasis on its effectiveness. Communication can proceed in various ways, and it can be used also any support resources for communication, which largely contribute to the simplification and streamlining. An important factor in evaluating the effectiveness of communication is also understanding and correct interpretation of the content of communications by all. I observe existing forms of communication used in software teams and deal with the communication from the perspective of effectiveness and impact on successful project implementation, as well as any problems that are in team communication. Also I deal with the possibilities and advantages of using support communication tools in team communication and finally the team building activities as a way to streamline communication and increase the productivity of the team.

Abstract:Everyone has surely heard a quote “to err is human”. No wonder, because everyone must have experienced a number of mistakes of their own or other's. With an increasing complexity of the task at hand increases also the probability that something will go wrong. Software systems are continuously becoming more complicated – some of the new challenges are the need for distribution, extensibility, scale of the system and new areas of application. With an increasing complexity are coming new risks and it is once again human responsibility to mitigate them. On the other hand “human factor” is responsible for most of the incidents. Reasons for this are diverse, from the lower perception to the lack of knowledge or skill. There are also many kinds of solutions, some of them more suitable than other. That is why it is so important to contemplate on how to avoid human caused risks. It is a long time since Seneca said to err is human, but to persist in the mistake is diabolical, but it is still very true.