Skip to main content

Tangibility of Fuzzy Approach Risk Assessment in Distributed Software Development Projects

  • Conference paper
  • First Online:
Artificial Intelligence and Applied Mathematics in Engineering Problems (ICAIAME 2019)

Abstract

Software is a product or a service or a project whose requirements are captured; specification document is prepared by requirements analysis; in/out architecture is designed; related source codes, variables, methods, classes, modules and relationships among these are written; necessary test and integration operations are done; when needed, maintenance, repair and update operations are executed by software or computer engineers and also that has its own documentation jobs and user manual, and has numeric and textual data, and also multimedia tools in its memory. Software development projects have a large financial burden and need to invest in high volumes. When looked at costs based on the international tangible data on computer software; it was $150 billion in 1985, it was $2 trillion in 2010 and it passed over $5 trillion after 2015. Also, in the year of 2018, the giro of Apple Store is about $250 million. Despite the costs, expenses and investments that are exponentially increasing every year, the rate of successful development of the software projects is not very high. Based on the “CHAOS” report (international size) prepared in 2016 only 17% of the software projects developed were completed in a timely manner, in the allocated budget and in accordance with the requirements. 53% of the projects were completed over time and/or over budget and/or also without fulfilling the requirements exactly. 30% of the software projects cannot have been completed in the development phase and were cancelled. For that software development projects with such high expenses and low success rate can have a better quality structure, a risk assessment approach has to be determined for the risk assessment methodology. So, some problems which may form software risks can be recognized and determined on time before causing trouble and endangering for software development projects. In this paper, some software risk assessment approaches underlying software risk management were introduced and explained in detail in addition to “fuzzy approach”. In addition, that this fuzzy technique is more useful and more effective for software risk evaluation in comparison with the others was showed and expressed by giving linguistic rules in this article. This paper tried to explain the terms from the general to the specific.

This is a preview of subscription content, log in via an institution to check access.

Access this chapter

Chapter
USD 29.95
Price excludes VAT (USA)
  • Available as PDF
  • Read on any device
  • Instant download
  • Own it forever
eBook
USD 129.00
Price excludes VAT (USA)
  • Available as EPUB and PDF
  • Read on any device
  • Instant download
  • Own it forever
Softcover Book
USD 169.99
Price excludes VAT (USA)
  • Compact, lightweight edition
  • Dispatched in 3 to 5 business days
  • Free shipping worldwide - see info

Tax calculation will be finalised at checkout

Purchases are for personal use only

Institutional subscriptions

References

  1. Roger, S.: Pressman and Bruce Maxim: Software Engineering: A Practitioner’s Approach, 8th edn. McGraw-Hill Higher Education, New York (2015)

    Google Scholar 

  2. Sommerville, I.: Software Engineering, 10th edn. Pearson Education Limited, England (2016)

    MATH  Google Scholar 

  3. Dey, P.K., Kinch, J., Ogunlana, S.O.: Managing risk in software development projects: a case study. Ind. Manag. Data Syst. 107(2), 284–303 (2007)

    Article  Google Scholar 

  4. OmarElgabry’s Blog, A general introduction to software engineering. https://medium.com/omarelgabrys-blog/software-engineering-introduction-part-1-b79238ec97ee. Accessed 6 May 2019

  5. Tutorialspoint, Software Project Management. https://www.tutorialspoint.com/software_engineering/software_project_management.htm. Accessed 7 May 2019

  6. National Research Council: The Owner’s Role in Project Risk Management. The National Academies Press, Washington (2005)

    Google Scholar 

  7. Sadiq, M., Rahmani, Md.K.I., Ahmad, M.W., Jung, S.: Software risk assessment and evaluation process (SRAEP) using model based approach. In: International Conference on Networking and Information Technology. IEEE (2010)

    Google Scholar 

  8. Mohamud, S.A., Basri, S.: Software risk assessment: a review on small and medium software projects. In: Software Engineering and Computer Systems, ICSECS, pp. 214–224 (2011)

    Google Scholar 

  9. Quality Progress. http://asq.org/quality-progress/2002/03/problem-solving/what-is-a-fault-tree-analysis.html. Accessed 7 May 2019

  10. Weibull. https://www.weibull.com/basics/fault-tree/index.htm. Accessed 7 May 2019

  11. Medium Home Page, Decision Trees Algorithms. https://medium.com/deep-math-machine-learning-ai/chapter-4-decision-trees-algorithms-b93975f7a1f1. Accessed 7 May 2019

  12. U.S. NRC, Probabilistic Risk Assessment (PRA). https://www.nrc.gov/about-nrc/regulatory/risk-informed/pra.html. Accessed 7 May 2019

  13. Rausand, M.: Event Tree Analysis (2005). https://hkarms.org/ASUS_Server/myftp_web_resources/2005_Conference_Presentation/Sys_Any_Event_Tree_Anly.pdf. Accessed 7 May 2019

  14. NPD solutions, Failure Modes Effects Analysis. http://www.npd-solutions.com/fmea.html. Accessed 7 May 2019

  15. HACCP Principles & Application Guidelines. https://www.fda.gov/food/hazard-analysis-critical-control-point-haccp/haccp-principles-application-guidelines. Accessed 7 May 2019

  16. Leaf. http://www.leafexcellenceinauditingforum.com/2018/09/28/root-cause-analysis/. Accessed 7 May 2019

  17. Manufacturing Technology Committee – Risk Management Working Group, Risk Ranking and Filtering. http://pqri.org/wp-content/uploads/2015/08/pdf/Risk_Rank_Filter_Training_Guide.pdf. Accessed 7 May 2019

  18. Haimes, Y.Y., Lambert, J., Li, D., Schooff, R., Tulsiani, V.: Hierarchical holographic modeling for risk identification in complex systems. In: International Conference on Systems, Man and Cybernetics. IEEE (1995)

    Google Scholar 

  19. Garcia-Diaz, N., Lopez-Martin, C., Chavoya, A.: A comparative study of two fuzzy logic models for software development effort estimation. In: Iberoamerican Conference on Electronics Engineering and Computer Science (2013)

    Google Scholar 

  20. Garrido, A., Yuste, P.: Looking for oriental fundamentals fuzzy logic. Brain 4(1–4), 121–125 (2013)

    Google Scholar 

  21. Lamersdorf, A., Münch, J., del Viso Torre, A.F., Sánchez, C.R., Heinz, M., Rombach, D.: A rule-based model for customized risk identification in distributed software development projects. In: Proceedings of the International Conference on Global Software Engineering. IEEE (2010)

    Google Scholar 

Download references

Author information

Authors and Affiliations

Authors

Corresponding author

Correspondence to Mustafa Batar .

Editor information

Editors and Affiliations

Rights and permissions

Reprints and permissions

Copyright information

© 2020 Springer Nature Switzerland AG

About this paper

Check for updates. Verify currency and authenticity via CrossMark

Cite this paper

Birant, K.U., Işık, A.H., Batar, M. (2020). Tangibility of Fuzzy Approach Risk Assessment in Distributed Software Development Projects. In: Hemanth, D., Kose, U. (eds) Artificial Intelligence and Applied Mathematics in Engineering Problems. ICAIAME 2019. Lecture Notes on Data Engineering and Communications Technologies, vol 43. Springer, Cham. https://doi.org/10.1007/978-3-030-36178-5_56

Download citation

Publish with us

Policies and ethics