A comparison of stepwise and fuzzy multiple regression analysis techniques for managing software project risks: Analysis phase
Risk is not always avoidable, but it is controllable. The aim of this study is to identify whether those techniques are effective in reducing software failure. This motivates the authors to continue the effort to enrich the managing software project risks with consider mining and quantitative approa...
Saved in:
Main Authors: | , |
---|---|
Format: | Article |
Language: | English |
Published: |
Science Publications
2014
|
Subjects: | |
Online Access: | http://eprints.utem.edu.my/id/eprint/12251/1/A_COMPARISON_OF_STEPWISE_AND_FUZZY_MULTIPLE_JCS.pdf http://eprints.utem.edu.my/id/eprint/12251/ https://thescipub.com/abstract/10.3844/jcssp.2014.1725.1742 https://doi.org/10.3844/jcssp.2014.1725.1742 |
Tags: |
Add Tag
No Tags, Be the first to tag this record!
|
Institution: | Universiti Teknikal Malaysia Melaka |
Language: | English |
Summary: | Risk is not always avoidable, but it is controllable. The aim of this study is to identify whether those techniques are effective in reducing software failure. This motivates the authors to continue the effort to enrich the managing software project risks with consider mining and quantitative approach with large data set. In this study, two new techniques are introduced namely stepwise multiple regression analysis and fuzzy multiple regression to manage the software risks. Two evaluation procedures such as MMRE and Pred (25) is used to compare the accuracy of techniques. The model’s accuracy slightly improves in stepwise multiple regression rather than fuzzy multiple regression. This study will guide software managers to apply software risk management practices with real world software development organizations and verify the effectiveness of the new techniques and approaches on a software project. The study has been conducted on a group of software project using survey questionnaire. It is hope that this will enable software managers improve their decision to increase the probability of software project success. |
---|