Resource Optimization-Based Software Risk Reduction Model for Large-Scale Application Development

Muhammad Shoaib,Ahsanullah Abro,Muhammad Imran,Basit Shahzad,Fazal Amin

doi:10.3390/su13052602

Muhammad Shoaib, Ahsanullah Abro + Show 3 more

Open Access

https://doi.org/10.3390/su13052602

Copy DOI

Abstract

Software risks are a common phenomenon in the software development lifecycle, and risks emerge into larger problems if they are not dealt with on time. Software risk management is a strategy that focuses on the identification, management, and mitigation of the risk factors in the software development lifecycle. The management itself depends on the nature, size, and skill of the project under consideration. This paper proposes a model that deals with identifying and dealing with the risk factors by introducing different observatory and participatory project factors. It is assumed that most of the risk factors can be dealt with by doing effective business processing that in response deals with the orientation of risks and elimination or reduction of those risk factors that emerge over time. The model proposes different combinations of resource allocation that can help us conclude a software project with an extended amount of acceptability. This paper presents a Risk Reduction Model, which effectively handles the application development risks. The model can synchronize its working with medium to large-scale software projects. The reduction in software failures positively affects the software development environment, and the software failures shall reduce consequently.

Highlights

Software development consists of several phases with a clear definition of tasks to be performed in each phase
It is important that the signal identification mechanism is in place that can determine that the risks are present in the software development lifecycle
The risk reduction model has been introduced in this study, where risks are handled based on the priority of handling and the resource of the projects under consideration

Summary

Introduction

Software development consists of several phases with a clear definition of tasks to be performed in each phase. Phase-wise distribution of software development decreases the amount of burden that can be put on one specific development activity. We gather and analyze the requirements, while in the design phase, the system design is generated. Software is developed based on the system’s design, and later it is tested to identify any possible errors. Testing software is done by using several methods to decrease or eliminate all the possible errors. If all these phases are done according to the schedule, the software can meet success, but this is usually not the case due to the diversity in the development activity

Objectives

Findings

Discussion

Conclusion