Quality life cycle of object oriented software development in extreme programming

Thesis (Master)--Izmir Institute of Technology, Computer Engineering, Izmir, 2008Includes bibliographical references (leaves: 53)Text in English; Abstract: Turkish and Englishviii, 53 leavesAlthough there are many teams using Extreme Programming, many people still think that applying its values, principles and practices will cause catastrophic results.However extreme programming is not only compatible with today.s software standards, technologies and most importantly with the changes at every phase of software development but also improves the quality of software. In my thesis I analyze its values, principles, and practices and how they increase the quality comparing to old software development methodologies

IT-enabled change into the structures of health information systems in Africa: A case study in Kenya

Agile software development methods have emerged in recent years and have become increasingly popular since the start of the century. While much research claims to study agile methods, the meaning of agility itself in software development is yet to be fully understood. Agility is viewed by some as the antithesis of plan, structure discipline and bureaucracy. This study aims to develop a better understanding of agility, using the key concepts of Complex Adaptive Systems as a theoretical lens. The study explores agility from several different angles, including autonomous team, stability and uncertainty, and team learning. A multiple case study research method was employed. The findings of the study emphasize that agility is manifested as stability and discipline, which are just as desirable as flexibility, and context sharing is of the same value and importance as knowledge sharing. In addition, the collective nature of learning is underlined

Omission of quality software development practices : a systematic literature review

Software deficiencies are minimized by utilizing recommended software development and quality assurance practices. However, these recommended practices (i.e., quality practices) become ineffective if software professionals purposefully ignore them. Conducting a systematic literature review (n = 4,838), we discovered that only a small number of previous studies, within software engineering and information systems literature, have investigated the omission of quality practices. These studies explain the omission of quality practices mainly as a result of organizational decisions and trade-offs made under resource constraints or market pressure. However, our study indicates that different aspects of this phenomenon deserve further research. In particular, future research must investigate the conditions triggering the omission of quality practices and the processes through which this phenomenon occurs. Especially, since software development is a human-centric phenomenon, the psychological and behavioral aspects of this process deserve in-depth empirical investigation. In addition, futures research must clarify the social, organizational, and economical consequences of ignoring quality practices. Gaining in-depth theoretically sound and empirically grounded understandings about different aspects of this phenomenon enables research and practice to suggest interventions to overcome this issue.fi=vertaisarvioitu|en=peerReviewed

Cost estimation in agile development projects

One of the key measures of the resilience of a project is its ability to reach completion on time and on budget, regardless of the turbulent and uncertain environment it may operate within. Cost estimation and tracking are therefore paramount when developing a system. Cost estimation has long been a difficult task in systems development, and although much research has focused on traditional methods, little is known about estimation in the agile method arena. This is ironic given that the reduction of cost and development time is the driving force behind the emergence of the agile method paradigm. This study investigates the applicability of current estimation techniques to more agile development approaches by focusing on four case studies of agile method use across different organisations. The study revealed that estimation inaccuracy was a less frequent occurrence for these companies. The frequency with which estimates are required on agile projects, typically at the beginning of each iteration, meant that the companies found estimation easier than when traditional approaches were used. The main estimation techniques used were expert knowledge and analogy to past projects. A number of recommendations can be drawn from the research: estimation models are not a necessary component of the process; fixed price budgets can prove beneficial for both developers and customers; and experience and past project data should be documented and used to aid the estimation of subsequent projects

Key Factors for Selecting an Agile Method: A Systematic Literature Review

Agile methods have become popular in recent years because the success rate of project development using Agile methods is better than structured design methods. Nevertheless, less than 50 percent of projects implemented using Agile methods are considered successful, and selecting the wrong Agile method is one of the reasons for project failure. Selecting the most appropriate Agile method is a challenging task because there are so many to choose from. In addition, potential adopters believe that migrating to an Agile method involves taking a drastic risk. Therefore, to assist project managers and other decision makers, this study aims to identify the key factors that should be considered when selecting an appropriate Agile method. A systematic literature review was performed to elicit these factors in an unbiased manner and then content analysis was used to analyze the resultant data. It was found that the nature of project, development team skills, project constraints, customer involvement and organizational culture are the key factors that should guide decision makers in the selection of an appropriate Agile method based on the value these factors have for different organizations and/or different projects

Are Delayed Issues Harder to Resolve? Revisiting Cost-to-Fix of Defects throughout the Lifecycle

Many practitioners and academics believe in a delayed issue effect (DIE); i.e. the longer an issue lingers in the system, the more effort it requires to resolve. This belief is often used to justify major investments in new development processes that promise to retire more issues sooner. This paper tests for the delayed issue effect in 171 software projects conducted around the world in the period from 2006--2014. To the best of our knowledge, this is the largest study yet published on this effect. We found no evidence for the delayed issue effect; i.e. the effort to resolve issues in a later phase was not consistently or substantially greater than when issues were resolved soon after their introduction. This paper documents the above study and explores reasons for this mismatch between this common rule of thumb and empirical data. In summary, DIE is not some constant across all projects. Rather, DIE might be an historical relic that occurs intermittently only in certain kinds of projects. This is a significant result since it predicts that new development processes that promise to faster retire more issues will not have a guaranteed return on investment (depending on the context where applied), and that a long-held truth in software engineering should not be considered a global truism.Comment: 31 pages. Accepted with minor revisions to Journal of Empirical Software Engineering. Keywords: software economics, phase delay, cost to fi

Best Practices for Implementing Agile Methods: A Guide for Department of Defense Software Developers

Traditional plan-driven software development has been widely used in the government because it\u27s considered to be less risky, more consistent, and structured. But there has been a shift from this approach to Agile methods which are more flexible, resulting in fast releases by working in an incremental fashion to adapt to the reality of the changing or unclear requirements. This report describes the Agile software development philosophy, methods, and best practices in launching software design projects using the Agile approach. It is targeted to Defense Department software developers because they face broad challenges in creating enterprise-wide information systems, where Agile methods could be used most effectively. Though not a panacea, agile methods offer a solution to an important class of problems faced by organizations today. Technology and E-Government

Using wireless sensors and networks program for chemical particle propagation mapping and chemical source localization

Chemical source localization is a challenge for most of researchers. It has extensive applications, such as anti-terrorist military, Gas and oil industry, and environment engineering. This dissertation used wireless sensor and sensor networks to get chemical particle propagation mapping and chemical source localization. First, the chemical particle propagation mapping is built using interpolation and extrapolation methods. The interpolation method get the chemical particle path through the sensors, and the extrapolation method get the chemical particle beyond the sensors. Both of them compose of the mapping in the whole considered area. Second, the algorithm of sensor fusion is proposed. It smooths the chemical particle paths through integration of more sensors\u27 value and updating the parameters. The updated parameters are associated with including sensor fusion among chemical sensors and wind sensors at same positions and sensor fusion among sensors at different positions. This algorithm improves the accuracy and efficiency of chemical particle mapping. Last, the reasoning system is implemented aiming to detect the chemical source in the considered region where the chemical particle propagation mapping has been finished. This control scheme dynamically analyzes the data from the sensors and guide us to find the goal. In this dissertation, the novel algorithm of modelling chemical propagation is programmed using Matlab. Comparing the results from computational fluid dynamics (CFD) software COMSOL, this algorithm have the same level of accuracy. However, it saves more computational times and memories. The simulation and experiment of detecting chemical source in an indoor environment and outdoor environment are finished in this dissertation --Abstract, page iii

Mittareiden käytön syyt ja seuraukset ketterissä tiimeissä teollisuudessa - Systemaattinen kirjallisuuskatsaus

Ketterät ohjelmistokehitysmenetelmät ovat lisänneet suosiotaan, mutta tutkimuksia, joissa tutkittaisiin syitä mittareiden käytölle ja niiden vaikutuksille, on varsin rajallisesti teollisen ketterän kehityksen osalta. Tämä tutkimus esittää tuloksia systemaattisesta kirjallisuuskatsauksesta. Perustuen tähän tutkimukseen, tulokset esittävät, että syyt mittarien käytölle keskittyy seuraaviin alueisiin: suunnittelu, etenemisen seuranta, laadun ymmärtäminen ja parantaminen, ja ongelmien tunnistaminen. Lisäksi, mittareiden vaikutukset keskittyvät seuraaviin alueisiin: suunnittelutoimet, reaktiiviset toimet, ihmisten motivointi ja parannusideoiden luominen. Tämä tutkimus myös listaa tärkeitä mittareita, jotka tunnistettiin kuvauksien sekä esiintymismäärien avulla. Tuloksia verrataan ketterän kehityksen periaatteisiin ja näyttää siltä, että mittareiden käyttö tukee ketteriä periaatteita lukuuottamatta muutamia poikkeuksia. Lisäksi, tämä tutkimus osoittaa, että suunnittelu- ja seurantamittareiden käytöstä on paljon näyttöä. Tutkimus tunnistaa myös tilannesidoksisia mittareita, joita käytetään yleensä ongelmien korjaamiseksi. Lopuksi, mittareiden käytön negatiiviset vaikutukset voi olla mielenkiintoinen tulevaisuuden tutkimusalue