International Journal of

ADVANCED AND APPLIED SCIENCES

EISSN: 2313-3724, Print ISSN: 2313-626X

Frequency: 12
line decor
  
line decor

 Volume 7, Issue 3 (March 2020), Pages: 1-8

----------------------------------------------

 Original research Paper

 Title: Accurate cost estimation for software with volatile requirements

 Author(s): Ibrahim Hassan 1, *, Ayub Latif 1, Khalid Khan 1, Fadzil Hassan 2, Muhammad Saeed 3

 Affiliation(s):

 1Department of Computer and Information Sciences, PAF KIET University, Karachi, Pakistan
 2Department of Computer and Information Sciences, Universiti Teknologi PETRONAS, Seri Iskandar, Malaysia
 3Department of Computer and Information Sciences, University of Karachi, Karachi, Pakistan

  Full Text - PDF          XML

 * Corresponding Author. 

  Corresponding author's ORCID profile: https://orcid.org/0000-0003-4757-6800

 Digital Object Identifier: 

 https://doi.org/10.21833/ijaas.2020.03.001

 Abstract:

Requirements volatility in the software development lifecycle is considered to be one of the biggest risks during development. Countering this is mandatory in order to achieve success in a software project. Such requirements if they exist and not handled at an appropriate time can also result in a huge amount of error in estimation, whether it relates to cost or time. This paper first provides a clear understanding of requirements volatility along with its major contributors. The paper then mentions some widely-used techniques to achieve maximum accuracy in software costing. In section 4, the paper highlights how costing accuracy can be achieved if the software has volatile requirements by measuring an existing survey’s result costing impact on the project. Finally, the paper concludes that volatile requirements cannot be eliminated but can be minimized using the approaches mentioned in the paper. 

 © 2020 The Authors. Published by IASE.

 This is an open access article under the CC BY-NC-ND license (http://creativecommons.org/licenses/by-nc-nd/4.0/).

 Keywords: Volatile requirements, Software costing, Software estimation, Accuracy

 Article History: Received 11 July 2019, Received in revised form 20 December 2019, Accepted 22 December 2019

 Acknowledgment:

No Acknowledgment.

 Compliance with ethical standards

 Conflict of interest: The authors declare that they have no conflict of interest.

 Citation:

 Hassan I, Latif A, and Khan K et al. (2020). Accurate cost estimation for software with volatile requirements. International Journal of Advanced and Applied Sciences, 7(3): 1-8

 Permanent Link to this page

 Figures

 Fig. 1

 Tables

 Table 1 Table 2 Table 3 Table 4

----------------------------------------------

 References (25) 

  1. Abd Elwahab K, Abd El Latif M, and Kholeif S (2016). Identify and manage the software requirements volatility proposed framework and casestudy. International Journal of Advanced Computer Science and Applications, 7(5): 64-71. https://doi.org/10.14569/IJACSA.2016.070510   [Google Scholar]
  2. Al-Saiyd NA (2016). A multistep approach for managing the risks of software requirements volatility. Computer and Information Science, 9(1): 101-112. https://doi.org/10.5539/cis.v9n1p101   [Google Scholar]
  3. Al-Saiyd NA and Zriqat IA (2015). Analyzing the impact of requirement changing on software design. European Journal of Scientific Research, 136(1): 62-73.   [Google Scholar]
  4. Boehm BW, Madachy R, and Steece B (2000). Software cost estimation with Cocomo II. Prentice-Hall, New York, USA.   [Google Scholar]
  5. Chari K and Agrawal M (2018). Impact of incorrect and new requirements on waterfall software project outcomes. Empirical Software Engineering, 23(1): 165-185. https://doi.org/10.1007/s10664-017-9506-4   [Google Scholar]
  6. Fairley RE (1992). Recent advances in software estimation techniques. In the 14th International Conference on Software Engineering, Association for Computing Machinery, New York, USA: 382-391. https://doi.org/10.1145/143062.143155   [Google Scholar]
  7. Galorath DD and Evans MW (2006). Software sizing, estimation, and risk management: When performance is measured performance improves. Auerbach Publications, Boca Raton, USA. https://doi.org/10.1201/9781420013122   [Google Scholar]
  8. Harker SD, Eason KD, and Dobson JE (1993). The change and evolution of requirements as a challenge to the practice of software engineering. In the IEEE International Symposium on Requirements Engineering, IEEE, San Diego, USA: 266-272. https://doi.org/10.1109/ISRE.1993.324847   [Google Scholar]
  9. Javed T and Durrani QS (2004). A study to investigate the impact of requirements instability on software defects. ACM SIGSOFT Software Engineering Notes, 29(3): 1-7. https://doi.org/10.1145/986710.986727   [Google Scholar]
  10. kalbani AA and Nguyen K (2010). Designing flexible business information system for modern-day business requirement changes. In the 2nd International Conference on Software Technology and Engineering, IEEE, San Juan, USA, 2: V2-112. https://doi.org/10.1109/ICSTE.2010.5608774   [Google Scholar]
  11. Latif MA, Khan MY, and Bashir K (2018). Practices for achieving accuracy in software costing and estimation. In the 2nd International Conference on Computing and Information Sciences, At Karachi, Pakistan.   [Google Scholar]
  12. Madachy RJ and Khoshnevis B (1994). A software project dynamics model for process cost, schedule and risk assessment. Ph.D. Dissertation, University of Southern California, Los Angeles, USA.   [Google Scholar]
  13. Morehouse RE (1994). Beginning qualitative research: A philosophic and practical guide. Psychology Press, UK.   [Google Scholar]
  14. Nurmuliani N, Zowghi D, and Powell S (2004). Analysis of requirements volatility during software development life cycle. In the Australian Software Engineering Conference, IEEE, Melbourne, Australia: 28-37. https://doi.org/10.1109/ASWEC.2004.1290455   [Google Scholar]
  15. Peña M and Valerdi R (2015). Characterizing the impact of requirements volatility on systems engineering effort. Systems Engineering, 18(1): 59-70. https://doi.org/10.1111/sys.21288   [Google Scholar]
  16. Putnam LH and Myers W (2013). Five core metrics: The intelligence behind successful software management. Pearson Education, London, UK.   [Google Scholar]
  17. Rubin HA (1983). Macro estimation of software development parameters: The ESTIMACS system. In the SOFTFAIR Conference on Software Development Tools, Techniques and Alternatives, IEEE, Arlington, USA: 109-118.   [Google Scholar]
  18. Shah US and Jinwala DC (2015). Resolving ambiguities in natural language software requirements: A comprehensive survey. ACM SIGSOFT Software Engineering Notes, 40(5): 1-7. https://doi.org/10.1145/2815021.2815032   [Google Scholar]
  19. Shekhar S and Kumar U (2016). Review of various software cost estimation techniques. International Journal of Computer Applications, 141(11): 31-34. https://doi.org/10.5120/ijca2016909867   [Google Scholar]
  20. Sheta A, Rine D, and Kassaymeh S (2015). Software effort and function points estimation models based radial basis function and feedforward artificial neural networks. International Journal of Next-Generation Computing, 6(3): 192-205.   [Google Scholar]
  21. Sudhakar M (2005). Managing the impact of requirements volatility. M.Sc. Thesis, Umeå University, Umeå, Sweden.   [Google Scholar]
  22. Thakurta R and Ahlemann F (2010). Understanding requirements volatility in software projects-an empirical investigation of volatility awareness, management approaches and their applicability. In the 43rd Hawaii International Conference on System Sciences, IEEE, Honolulu, USA: 1-10. https://doi.org/10.1109/HICSS.2010.420   [Google Scholar]
  23. Urbieta M, Rossi G, Distante D, and Schwinger W (2013). Managing volatile requirements in web applications. In the 15th IEEE International Symposium on Web Systems Evolution, IEEE, Eindhoven, Netherlands: 77-82. https://doi.org/10.1109/WSE.2013.6642420   [Google Scholar]
  24. Zowghi D and Nurmuliani N (2002). A study of the impact of requirements volatility on software project performance. In the 9th Asia-Pacific Software Engineering Conference, IEEE, Gold Coast, Australia: 3-11. https://doi.org/10.1109/APSEC.2002.1182970   [Google Scholar]
  25. Zowghi D, Offen R, and Nurmuliani N (2000). Impact of requirements volatility on the software development lifecycle. In the 16th IFIP World Computer Conference: Software Theory and Practice, Publishing House of Electronics Industry, Beijing, China: 19-27.   [Google Scholar]