Essay Collection 2009

Abstract:In this paper I describe how to create a team of software experts in which there is a low possibility of creation of conflicts. Also there is a simple list of types of personalities and their influence to a team. Significant part of documents describes various combinations of personality types, whose are interesting in the context of team. There are described effects in the group of people such as submission, motivation, leadership, conformity, social power and others.

Abstract:In this paper, I focus on the subject of a software project tracking problem. There are described some tools for software project like a task manager and a version control system. I focus on using it on a project in small team. A part o document is about pros and cons of these tools. This paper also talks about subject of planning with emphasis on human resources. How can be automatic planning useful for project manager and how not. A different approach to task managing and planning has system ISTAR. It’s based on a contract model. Requirements in company are organized to a contract model. A contract contains a task specification, a contractor and a client.

Abstract:Management of risk in software's system originate in last century. People got know by software development, that it is necessary to analyze troubles which can begin. This branch goes through development as another branch. A new methods and a ways are added up on analyze and planning of risk. Today nobody has doubts about important of this work and a few projects exist without analyses of risk and without plans of solution. Planning and identification are not shot-time processes. It is executing in many of stages during whole cycle of project. I will try to give answers on three basic questions by my essay: Why are important identification, classification and planning problems in software's system. How to do management of risk for saving money in the project, for saving resources and for saving the work of people. Where we can use management of risk in creating of team project.

Abstract:In the last few years the software products are more extensive and more complex. During development of software products, complexity has critical and strategic importance. In this case of discussing sizes and complexity of products, the question of quality becomes the key question. The question is how to create the software product of highest quality in limited time with limited sources. Software products are integrated into services of big companies. These companies are involved in critical areas as health and atomic energy, where possible error can cause death of many people. Because we have to assure the quality of software products it is necessary to follow nowadays defined norms. These norms contain only recommendations how go through development process but not how to create software. In this essay I would shortly describe some problems, which are solving, discussing on Workshop on Software Quality (WoSQ). The aim of the work is to describe process of controlling, assuring quality and testing during development of software product.

Abstract:The success of software projects depends on the ability of a human planner to understand the relationships of tasks and their temporal uncertainty an hence the visualization thereof. In software engineering are many methods which are eliminating the task uncertainty. Projects which use these methods are considered as robust and more efficient. In this essay I am describing planning methods, comparing to each other and trying to find its advantages and disadvantages. I am comparing them from several perspectives. For example, one perspective is effort which is needed to read important information from these methods.

Abstract:In today’s world is created many concepts how to help managing oraganization, in spite of this there is barely cover non-stoping growth of the requirements on support of information systems. Creating suitable models for solving a specific task, for instance processing project, help in looking for common and fast adaptable approaches. But why is not it enough and thare are appearing problems during managing and planning project? Why are not the projects on time? In this essay is analyzing exactly this problem and useable methods in solving it in team projects within monitoring, managing and gaining solutions effectively.

Abstract:Successful project management involves a lot of important factors, which need to be monitored, managed, modified and deliberated through the whole duration of project. The basic ones are task management, schedule monitoring, good information about the actual state of project for all team members, good statistics, communication and sharing of common sources. For successful and effective accomplishment of these requirements it is very useful and often essential to use some sort of tool made or this purpose. Lot of options are available, but I will concentrate only on the web based ones in this document. Their main advantage is connection from everywhere, where the internet connection is available, without special type of client or terminal required and high level of interactivity between team members. This choice is also very good for smaller team, such like in a subject Team project.

Abstract:Software quality can be divided into internal and external. External quality is implied by customers’ requirements on product. Key activity in external quality assurance is testing. However testing stage has a serious drawback: it may be hard to predict its duration and efficiency. This can be tightly related with low internal software quality. Unclean, complex and coupled source code makes testing harder. It also causes low maintainability especially low analyzability. This may be the source of program defects and errors. In this essay author deals with relationship between internal and external software quality. Author also aims at possible reasons of low software quality and it’s improvement in different stages of software development cycle.

Abstract:An information system development is process where many people are co-working. They formed team (teams), work together, communicate, divide jobs… As in every group of people, also in working team has a personality of each member a big influence upon work effectiveness, solidarity among team and relationships between people. The bigger the team is, the influences are smaller. Of course, the most important are abilities, skills and knowledge. But unsuitable character can be a big problem in cooperating with others. In my work I will try to deal with this problem.

Abstract:New technologies, growing requirements, fast work rate. It’s just a small group of risks that affect the work on a software project. Many times, underestimating the risks may have great influence on the further software project development process. So it is necessary, to be concerned about these risks, to identify them and try to select the best solution in case of their occurrence, or to prevent them completely, which will minimize the influence on the final product. The aim of this document is to provide the view on the most frequent risks, compare the methods of risk elimination from the view of the software engineering and extreme programming and also compare their applicability on specific software projects or teams.

Abstract:Planning results in an efficient completion of many activities, whether in a daily life, business, or software project creation. In comparison to a rush progression with no efficient strategy, the exact analysis enables a huge asset. This paper deals with most common problems which arise during planning, barriers which have to be overcome by the means of plans. It describes possible approaches to the project planning and which aspects share to the projects' bad success. Business and IT are directly connected. Therefore, it is necessary to plan business resources so that they were not endangered by dissipation before the project is even finishes. Customer orientation may lead to slowdown or even stagnancy of other projects. Beside the team project, students solve other projects within classes and therefore, it is necessary to prioritize and set the time schedule, the more the team work efficiency may be influenced. Therefore, planning in this area is very dynamic.

Abstract:To be a manager of successful finished software project is necessary to make amount of effort to monitoring project. Through this mechanism we can provide progress of software project according to plan. Frequently, during the software development lead to costs overrun, time delay, or functionality does not meet the requirements of clients. Monitoring is mechanism that allows project manager to give sufficient information about actual project state. With correct analysis and evaluation of information they can make estimate changes and measures in order to avoid unwanted project status. This essay deals with the topic of monitoring software project and influence on the planning and manage project on the basis of through analysis of information obtained during monitoring project.

Abstract:In my essay I would like tell us importance science Software engineering in the world. At the beginning I describe situation from history, because in this time programming was other than today. Later I describe actual situation, which I divide on two epochs. In the first epoch I explain waterfall model living cycle. This one I have experience, because this method is using at school. As the second epoch agility programming I explain extreme programming, which I will suppose become the best method in the future. Seeing that software engineering is only theory, so next part I explain it from praxes. I will focus on separately element of team. Everybody has own task in team and everybody bring other risk on the project.

Abstract:Distributed artificial intelligence, (DAI), which is a subdomain of artificial intelligence, (AI), works with independent systems that communicate and influence each other and by doing so solve defined problems. Because of the breadth of problems these systems are being used to solve, a question of verification and testing of these systems arise. In this thesis we will explain the DMAS testing method, specifically the testing of unwelcomed emergent behavior. Also we will discuss usability issues and the weak points of this method used in testing DMAS systems.

Abstract:Planning of development processes can be nowadays considered as necessity, at least in larger software products. Without a good plan, the development tends to become chaotic what results in reduced efficiency and increased time requirements. Creation of good plan is difficult matter which requires experiences and skills. Even the best plan cannot assure successful development. Unpredictable occasions may radically affect development process. This document aims to show the need of planning and adaptation of plans, according to unexpected circumstances.

Abstract:There are many ways of software development depending on complexity, inner structure, generally on software as it is. But in the process of developing the software, idea of software is only one of actor, that we have to observe. Besides, there is also human factor: it follows the software from idea in the brain of customer, melts to request specification in the hands of architect, it is transformed into the specific models in the hands of analytic, to be shaped into concrete prototype with the help of programmators, then it needs testers to test it, to be at last provided to users for using. And equally as wrong approach to the software, also wrong approach to the concerned people can lead to degradation of quality, so it is in our concern to look also to these aspects.

Abstract:Business is becoming more and more dependant on information technologies and products built on these technologies. Behind development of these products stand software teams consisting of developers, analysts, designers, but also of people responsible for project management. Project management is difficult activity, which demands a lot of focus during the whole life cycle of the project. There is a lot of tools for supporting these activities. Content of this paper is usage of tools like these, tools for project tracking, tools supporting collaboration and communication of team members. Paper deals with tools supporting project planning, tracking this plan and also deals with competency matrix as tool for evaluating team members and their work on project.

Abstract:The purpose of this essay is to inform reader why is it so necessary to make effort and give finances on monitoring of software project. Reader can understand the problematic of software monitoring and also gain knowledge about problems and troubles which appears during monitoring. Essay also discusses the tasks of software manager, who is a member of the team and is in charge of software monitoring and control. It describes in detail why factors as money, time and functionality are the key factors in software monitoring and which techniques and methods are used in monitoring. Real world associations are used in the article to allow better comprehension also to people who have just a little knowledge about software engineering.