| 1. |
- Afzal, Wasif, et al.
(författare)
-
Genetic programming for cross-release fault count predictions in large and complex software projects
- 2010
-
Ingår i: Evolutionary Computation and Optimization Algorithms in Software Engineering. - : IGI Global, Hershey, USA. - 9781615208098
-
Bokkapitel (refereegranskat)abstract
- Software fault prediction can play an important role in ensuring software quality through efficient resource allocation. This could, in turn, reduce the potentially high consequential costs due to faults. Predicting faults might be even more important with the emergence of short-timed and multiple software releases aimed at quick delivery of functionality. Previous research in software fault prediction has indicated that there is a need i) to improve the validity of results by having comparisons among number of data sets from a variety of software, ii) to use appropriate model evaluation measures and iii) to use statistical testing procedures. Moreover, cross-release prediction of faults has not yet achieved sufficient attention in the literature. In an attempt to address these concerns, this paper compares the quantitative and qualitative attributes of 7 traditional and machine-learning techniques for modeling the cross-release prediction of fault count data. The comparison is done using extensive data sets gathered from a total of 7 multi-release open-source and industrial software projects. These software projects together have several years of development and are from diverse application areas, ranging from a web browser to a robotic controller software. Our quantitative analysis suggests that genetic programming (GP) tends to have better consistency in terms of goodness of fit and accuracy across majority of data sets. It also has comparatively less model bias. Qualitatively, ease of configuration and complexity are less strong points for GP even though it shows generality and gives transparent models. Artificial neural networks did not perform as well as expected while linear regression gave average predictions in terms of goodness of fit and accuracy. Support vector machine regression and traditional software reliability growth models performed below average on most of the quantitative evaluation criteria while remained on average for most of the qualitative measures.
|
|
| 2. |
- Afzal, Wasif, et al.
(författare)
-
Resampling Methods in Software Quality Classification
- 2012
-
Ingår i: International Journal of Software Engineering and Knowledge Engineering. - Sweden : World Scientific. - 0218-1940. ; 22:2, s. 203-223
-
Tidskriftsartikel (refereegranskat)abstract
- In the presence of a number of algorithms for classification and prediction in software engineering, there is a need to have a systematic way of assessing their performances. The performance assessment is typically done by some form of partitioning or resampling of the original data to alleviate biased estimation. For predictive and classification studies in software engineering, there is a lack of a definitive advice on the most appropriate resampling method to use. This is seen as one of the contributing factors for not being able to draw general conclusions on what modeling technique or set of predictor variables are the most appropriate. Furthermore, the use of a variety of resampling methods make it impossible to perform any formal meta-analysis of the primary study results. Therefore, it is desirable to examine the influence of various resampling methods and to quantify possible differences. Objective and method: This study empirically compares five common resampling methods (hold-out validation, repeated random sub-sampling, 10-fold cross-validation, leave-one-out cross-validation and non-parametric bootstrapping) using 8 publicly available data sets with genetic programming (GP) and multiple linear regression (MLR) as software quality classification approaches. Location of (PF, PD) pairs in the ROC (receiver operating characteristics) space and area under an ROC curve (AUC) are used as accuracy indicators. Results: The results show that in terms of the location of (PF, PD) pairs in the ROC space, bootstrapping results are in the preferred region for 3 of the 8 data sets for GP and for 4 of the 8 data sets for MLR. Based on the AUC measure, there are no significant differences between the different resampling methods using GP and MLR. Conclusion: There can be certain data set properties responsible for insignificant differences between the resampling methods based on AUC. These include imbalanced data sets, insignificant predictor variables and high-dimensional data sets. With the current selection of data sets and classification techniques, bootstrapping is a preferred method based on the location of (PF, PD) pair data in the ROC space. Hold-out validation is not a good choice for comparatively smaller data sets, where leave-one-out cross-validation (LOOCV) performs better. For comparatively larger data sets, 10-fold cross-validation performs better than LOOCV.
|
|
| 3. |
- Afzal, Wasif, et al.
(författare)
-
Search-based prediction of fault-slip-through in large software projects
- 2010
-
Ingår i: Proceedings - 2nd International Symposium on Search Based Software Engineering, SSBSE 2010. - : IEEE. - 9780769541952 ; , s. 79-88
-
Konferensbidrag (refereegranskat)abstract
- A large percentage of the cost of rework can be avoided by finding more faults earlier in a software testing process. Therefore, determination of which software testing phases to focus improvements work on, has considerable industrial interest. This paper evaluates the use of five different techniques, namely particle swarm optimization based artificial neural networks (PSO-ANN), artificial immune recognition systems (AIRS), gene expression programming (GEP), genetic programming (GP) and multiple regression (MR), for predicting the number of faults slipping through unit, function, integration and system testing phases. The objective is to quantify improvement potential in different testing phases by striving towards finding the right faults in the right phase. We have conducted an empirical study of two large projects from a telecommunication company developing mobile platforms and wireless semiconductors. The results are compared using simple residuals, goodness of fit and absolute relative error measures. They indicate that the four search-based techniques (PSO-ANN, AIRS, GEP, GP) perform better than multiple regression for predicting the fault-slip-through for each of the four testing phases. At the unit and function testing phases, AIRS and PSO-ANN performed better while GP performed better at integration and system testing phases. The study concludes that a variety of search-based techniques are applicable for predicting the improvement potential in different testing phases with GP showing more consistent performance across two of the four test phases.
|
|
| 4. |
- Ahmad, E., et al.
(författare)
-
Assessment and support for software capstone projects at the undergraduate level: A survey and rubrics
- 2011
-
Ingår i: Frontiers of Information Technology (FIT), 2011, Islamabad, 19-21 Dec. 2011. - Islamabad. - 9780769546254 ; , s. 25 - 32
-
Konferensbidrag (refereegranskat)abstract
- Software engineering and computer science students conduct a capstone project during the final year of their degree programs. These projects are essential in validating that students have gained required knowledge and they can synthesize and use that knowledge to solve real world problems. However, the external requirements on educational programs often do not provide detailed guidelines for how to conduct or support these capstone projects, which may lead to variations among universities. This paper presents the results from a survey conducted at 19 different Pakistani universities of the current management practices and assessment criteria used for the capstone project courses at Undergraduate level. Based upon the results of this survey and similar work on Master Thesis capstone projects in Sweden, we present assessment rubrics for software-related undergraduate capstone projects. We also present recommendations for the continuous improvement of capstone projects.
|
|
| 5. |
- Alégroth, Emil, 1984, et al.
(författare)
-
Industrial application of visual GUI testing: Lessons learned
- 2014
-
Ingår i: Continuous software engineering. - Cham : Springer International Publishing. ; 9783319112831, s. 127-140
-
Bokkapitel (övrigt vetenskapligt/konstnärligt)abstract
- A large body of academic knowledge has been devoted to automated software testing in order to support the software market's demands for continuous software delivery. However, most of these automated techniques approach testing from lower levels of system abstraction, e.g., component level, which limit their applicability for high-level regression testing of, for instance, system and acceptance tests, thus forcing companies to perform these test activities manually, which is considered time consuming, tedious, and error prone. In this book chapter, we present visual GUI testing (VGT), a tool driven test technique that uses image recognition in order to interact and assert the correctness of a system under test (SUT) through the bitmap graphical user interface (GUI) that is shown to the user on the computer monitor. This approach makes VGT flexible and applicable to any SUT with a GUI but also allows VGT tools to emulate end-user behavior and therefore automate previously manual system and acceptance test cases. In addition to presenting the technique itself, this chapter will also present some VGT tools and empirically identified problems with the technique and how these problems can be mitigated in practice. Finally we will discuss how VGT can be used in the context of continuous software development in order to support market demands for quicker software delivery.
|
|
| 6. |
- Alégroth, Emil, 1984, et al.
(författare)
-
Transitioning manual system test suites to automated testing: An industrial case study
- 2013
-
Ingår i: Proceedings - IEEE 6th International Conference on Software Testing, Verification and Validation, ICST 2013. - : IEEE. - 9780769549682 ; , s. 56-65
-
Konferensbidrag (refereegranskat)abstract
- Visual GUI testing (VGT) is an emerging technique that provides software companies with the capability to automate previously time-consuming, tedious, and fault prone manual system and acceptance tests. Previous work on VGT has shown that the technique is industrially applicable, but has not addressed the real-world applicability of the technique when used by practitioners on industrial grade systems. This paper presents a case study performed during an industrial project with the goal to transition from manual to automated system testing using VGT. Results of the study show that the VGT transition was successful and that VGT could be applied in the industrial context when performed by practitioners but that there were several problems that first had to be solved, e.g. testing of a distributed system, tool volatility. These problems and solutions have been presented together with qualitative, and quantitative, data about the benefits of the technique compared to manual testing, e.g. greatly improved execution speed, feasible transition and maintenance costs, improved bug finding ability. The study thereby provides valuable, and previously missing, contributions about VGT to both practitioners and researchers. © 2013 IEEE.
|
|
| 7. |
- Alizadeh, Zeinab, et al.
(författare)
-
Alignment of requirements specification and testing: A systematic mapping study
- 2011
-
Ingår i: Proceedings of the ICST Workshop on Requirements and Validation, Verification and Testing (REVVERT'11).
-
Konferensbidrag (refereegranskat)abstract
- Requirements should specify expectations on a software system and testing should ensure these expectations are met. Thus, to enable high product quality and efficient development it is crucial that requirements and testing activities and information are aligned. A lot of research has been done in the respective fields of Requirements Engineering and Testing but there is a lack of summaries of the current state of the art on how to link the two. This study presents a systematic mapping of the alignment of specification and testing of functional or nonfunctional requirements in order to identify useful approaches and needs for future research. In particular we focus on results relevant for nonfunctional requirements but since only a few studies was found on alignment in total we also cover the ones on functional requirements. We summarize the 35 relevant papers found and discuss them within six major sub categories with model-based testing and traceability being the ones with most prior results.
|
|
| 8. |
- Baigent, Colin, et al.
(författare)
-
The effects of lowering LDL cholesterol with simvastatin plus ezetimibe in patients with chronic kidney disease (Study of Heart and Renal Protection) : a randomised placebo-controlled trial
- 2011
-
Ingår i: The Lancet. - 0140-6736 .- 1474-547X. ; 377:9784, s. 2181-2192
-
Tidskriftsartikel (refereegranskat)abstract
- Background Lowering LDL cholesterol with statin regimens reduces the risk of myocardial infarction, ischaemic stroke, and the need for coronary revascularisation in people without kidney disease, but its effects in people with moderate-to-severe kidney disease are uncertain. The SHARP trial aimed to assess the efficacy and safety of the combination of simvastatin plus ezetimibe in such patients. Methods This randomised double-blind trial included 9270 patients with chronic kidney disease (3023 on dialysis and 6247 not) with no known history of myocardial infarction or coronary revascularisation. Patients were randomly assigned to simvastatin 20 mg plus ezetimibe 10 mg daily versus matching placebo. The key prespecified outcome was first major atherosclerotic event (non-fatal myocardial infarction or coronary death, non-haemorrhagic stroke, or any arterial revascularisation procedure). All analyses were by intention to treat. This trial is registered at ClinicalTrials.gov, NCT00125593, and I SRCTN54137607. Findings 4650 patients were assigned to receive simvastatin plus ezetimibe and 4620 to placebo. Allocation to simvastatin plus ezetimibe yielded an average LDL cholesterol difference of 0.85 mmol/L (SE 0.02; with about two-thirds compliance) during a median follow-up of 4.9 years and produced a 17% proportional reduction in major atherosclerotic events (526 [11.3%] simvastatin plus ezetimibe vs 619 [13.4%] placebo; rate ratio [RR] 0.83, 95% CI 0.74-0.94; log-rank p=0.0021). Non-significantly fewer patients allocated to simvastatin plus ezetimibe had a non-fatal myocardial infarction or died from coronary heart disease (213 [4.6%] vs 230 [5.0%]; RR 0.92,95% CI 0.76-1.11; p=0.37) and there were significant reductions in non-haemorrhagic stroke (131 [2.8%] vs 174 [3.8%]; RR 0.75,95% CI 0.60-0.94; p=0.01) and arterial revascularisation procedures (284 [6.1%] vs 352 [7.6%]; RR 0.79, 95% CI 0.68-0.93; p=0.0036). After weighting for subgroup-specific reductions in LDL cholesterol, there was no good evidence that the proportional effects on major atherosclerotic events differed from the summary rate ratio in any subgroup examined, and, in particular, they were similar in patients on dialysis and those who were not. The excess risk of myopathy was only two per 10 000 patients per year of treatment with this combination (9 [0.2%] vs 5 [0.1%]). There was no evidence of excess risks of hepatitis (21 [0.5%] vs 18 [0.4%]), gallstones (106 [2.3%] vs 106 [2.3%]), or cancer (438 [9.4%] vs 439 [9.5%], p=0.89) and there was no significant excess of death from any non-vascular cause (668 [14.4%] vs 612 [13.2%], p=0.13). Interpretation Reduction of LDL cholesterol with simvastatin 20 mg plus ezetimibe 10 mg daily safely reduced the incidence of major atherosclerotic events in a wide range of patients with advanced chronic kidney disease.
|
|
| 9. |
- Berntsson Svensson, Richard, et al.
(författare)
-
Prioritization of quality requirements : State of practice in eleven companies
- 2011
-
Ingår i: 2011 IEEE 19th International Requirements Engineering Conference, RE 2011; Trento; 29 August 2011 through 2 September 2011. - Trento : IEEE. - 9781457709234 ; , s. 69-78, s. 69-78
-
Konferensbidrag (refereegranskat)abstract
- Requirements prioritization is recognized as an important but challenging activity in software product development. For a product to be successful, it is crucial to find the right balance among competing quality requirements. Although literature offers many methods for requirements prioritization, the research on prioritization of quality requirements is limited. This study identifies how quality requirements are prioritized in practice at 11 successful companies developing software intensive systems. We found that ad-hoc prioritization and priority grouping of requirements are the dominant methods for prioritizing quality requirements. The results also show that it is common to use customer input as criteria for prioritization but absence of any criteria was also common. The results suggests that quality requirements by default have a lower priority than functional requirements, and that they only get attention in the prioritizing process if decision-makers are dedicated to invest specific time and resources on QR prioritization. The results of this study may help future research on quality requirements to focus investigations on industry-relevant issues.
|
|
| 10. |
- Berntsson Svensson, Richard, et al.
(författare)
-
Quality Requirements in Industrial Practice – An Extended Interview Study at Eleven Companies
- 2012
-
Ingår i: IEEE Transactions on Software Engineering. - : IEEE. - 0098-5589 .- 1939-3520. ; 38:4, s. 923-935
-
Tidskriftsartikel (refereegranskat)abstract
- In order to create a successful software product and assure its quality, it is not enough to fulfill the functional requirements, it is also crucial to find the right balance among competing quality requirements (QR). An extended, previosluy piloted, interview study was performed to identify specific challenges associated with the selection, trade-off, and management of QR in industrial practice. Data was collected through semi-structured interviews with eleven product managers and eleven project leaders from eleven software companies. The contribution of this study is fourfold: First, it compares how QR are handled in two cases, companies working in business-to-business markets, and companies that are working in business-to-consumer markets. These two are also compared in terms of impact on the handling of QRs. Second, it compares the perceptions and priorities of QR by product and project management respectively. Third, it includes an examination of the interdependencies among quality requirements perceived as most important by the practitioners. Fourth, it characterizes the selection and management of QR in down-stream development activities.
|
|
