Software crowdsourcing is mediated by platforms that connect requesters (buyers) with online workers--the crowd. Thus, these platforms have emerged as an important stakeholder in software ...development. This article introduces them and groups them by development phase.
The development of high-quality software is an essential business activity in many organizations. Improving software quality requires the effective use of a software development process with ...well-defined phases of development and a metrics program to define and verify product and process quality. A key objective in software development is phase containment of defects. It is accepted knowledge that identifying and correcting defects as close to their source as possible produces higher quality software with enhanced development productivity. The essential goal is that a defect should not escape the phase in which it is introduced. This paper presents a formal model of phase containment metrics. We report on the implementation of phase containment metrics in a real software development project. Data tables and charts are proposed as effective means of collecting and reporting the metrics. We demonstrate how the phase containment metrics lead to software quality and process improvements. Future research directions are presented in the conclusion.
Software industries are continuously striving to achieve software quality through delivery of defect free software within time and within estimated budget. Most of the quality improvement strategies ...in software development focusses on optimizing a single response variable such as the defect count. But in reality, many responses contribute to the quality of software developed which requires to be studied simultaneously. This paper attempts to study the number of defects in software and the effort required in correcting these defects, simultaneously using desirability function and Taguchi method. Effort is defined as the time span from when the defect was logged into the system to the time when the defect was corrected and removed from the system and is measured in hours. The work has been executed on the issue tracking system of a large telecommunication organization. The organization manufactured consumer electronic devices having embedded software developed using agile development method. The input factors studied are Change Request Priority, software development phase and severity, which were selected from a total of 24 parameters using analytic hierarchy process. Significant factors and their optimal levels which optimized the defects captured and the effort taken to eliminate them, were obtained. Confirmation tests were performed using the optimal settings of the input factors on the data from the subsequent sprint which showed a 20% improvement in the overall desirability value.
Change effort estimation is needed not only in software maintenance phase, but also in the software development phase. Many techniques have been developed to estimate required change effort for a ...particular change request. One of these techniques is impact analysis. One main challenge of this technique from a software development perspective is that the existence of inconsistent states of some software artefacts, i.e. some classes have completely developed and some of them partially developed. Therefore, this research proposes a new change effort estimation model that overcomes this challenge using a combination of static and dynamic analysis techniques. The results of this research are two-fold: (i) a new change effort estimation model using static and dynamic analysis techniques for software development phase; and (ii) demonstration of significant achievements of the approach via extensive experimental validation using several case studies.
PDF
