Multi-Head CNN based Software Development Risk Classification

Agile methodology for software development has been in vogue for a few decades, notably among small and medium enterprises. The omission of an explicit risk identification approach turns a blind eye to a range of perilous risks, thus dumping the management into strenuous situations and precipitating dreadful issues at the crucial stages of the project. To overcome this drawback a novel Agile Software Risk Identification using Deep learning (ASRI-DL) approach has been proposed that uses a deep learning technique along with the closed fishbowl strategy, thus assisting the team in finding the risks by molding them to think from diverse perspectives, enhancing wider areas of risk coverage. The proposed technique uses a multi-head Convolutional Neural Network (Multihead-CNN) method for classifying the risk into 11 classes such as over-doing, under-doing, mistakes, concept risks, changes, differences, difficulties, dependency, conflicts, issues, and challenges in terms of producing a higher number of risks concerning score, criticality, and uniqueness of the risk ideas. The descriptive statistics further demonstrate that the participation and risk coverage of the individuals in the proposed methodology exceeded the other two as a result of applying the closed fishbowl strategy and making use of the risk identification aid. The proposed method has been compared with existing techniques such as Support Vector Machine (SVM), Multi-Layer Perceptron (MLP), Generalized Linear Models (GLM), and CNN using specific parameters such as accuracy, specificity, and sensitivity. Experimental findings show that the proposed ASRI-DL technique achieves a classification accuracy of 99.16% with a small error rate with 50 training epochs respectively

The impact of Software Process Maturity on Software Project Performance: The Contingent Role of Software Development Risk

Despite growing efforts to improve software development processes, recurring concerns about software project performance remain largely present. The rate of software development project failure rate has been routinely documented in information systems (IS) research (Wallace, 2004; El-Masry and Rivard, 2010). The management of software development projects is often marked by inadequate planning, a poor grasp of the overall development process, and no clear management framework, even as the focus in software development shifts from a technology perspective to a more process-centric view (Slaughter, 2006). To address such concerns few CMM-based studies have examined the benefits and direct impact of software process maturity on software project performance but with mixed results. The present paper attempts to systematically examine the contingent role of software development risk on the impact of software process maturity level on software project performance. Guided by risk-based perspective in Software Engineering and CMM-based framework, an exploratory model was developed and tested. The premise of this paper is that software development risk plays a contingent role in the relationship between software process maturity and software project performance. Drawing on a sample of 107 organizations that have undergone official CMM appraisals, the results of partial least squares analysis of the data reveal initial evidence that (1) a positive effect of software process maturity level on software project performance while underscoring the negative effect of software development risk on software project performance, and (2) more importantly, the findings show that software development risk plays a contingent role software process maturity level on software project performance. For researchers, the integration of software development risk can provide a much needed linkage in the three fundamental constructs of CMM. From a managerial perspective, in order to foster a better software project performance, IS project leaders and managers should strongly emphasize devising effective software development risk assessment since a variation of this construct’s level may strengthen or weaken the relationship between software development process maturity and software project performance

Stochastically Simulating the Effects of Requirements Creep on Software Development Risk Management

One of the major chronic problems in software development is the fact that application requirements are almost never stable and fixed. Creeping user requirements have been troublesome since the software industry began. Several empirical studies have reported that volatile requirements are a challenging factor in most information systems development projects. Software process simulation modeling has increasingly been used for a variety of issues during software development. The management of software development risks is one of them. This study presents an approach for simulating and analyzing the effect of Requirements Creep on certain software development risk management activities. The proposed algorithm is based on stochastic simulation and has been implemented using C

Offshore-Outsourced Software Development Risk Management Model

Offshore-outsourced software development is gaining popularity because companies are continuously forced to reduce production costs while keeping sustainable competitive strength. However, this trend of software development increases projects’ complexity and brings up risks to the overall project environment. Therefore, risks of offshore software development require to be managed as early as possible for a successful project. This paper considers a risk management model from a holistic perspective to manage offshore software development risk, integrated into early stages of development. The approach effectively identifies and specifies the goals of a project and the related risk factors. This is done at the basis of selected software development components within the running project. We show how to trace and control these risks already during early requirements engineering activities. The model at hand is implemented into an ongoing offshore software development project to (1) identify goals and risk factors from the local context and finally (2) to determine its applicability of the approach in offshore software development projects from a vendor’s perspective

Strategies for successful software development risk management

Nowadays, software is becoming a major part of enterprise business. Software development is activity connected with advanced technology and high level of knowledge. Risks on software development projects must be successfully mitigated to produce successful software systems. Lack of a defined approach to risk management is one of the common causes for project failures. To improve project chances for success, this work investigates common risk impact areas to perceive a foundation that can be used to define a common approach to software risk management. Based on typical risk impact areas on software development projects, we propose three risk management strategies suitable for a broad area of enterprises and software development projects with different amounts of connected risks. Proposed strategies define activities that should be performed for successful risk management, the one that will enable software development projects to perceive risks as soon as possible and to solve problems connected with risk materialization. We also propose a risk-based approach to software development planning and risk management as attempts to address and retire the highest impact risks as early as possible in the development process. Proposed strategies should improve risk management on software development projects and help create a successful software solution

Software Development Risk Management Model – A Goal Driven Approach

Software development project is often faced with unanticipated problems which pose any potential risks within the development environment. Controlling these risks arises from both the technical and non-technical development components already from the early stages of the development is crucial to arrive at a successful project. Therefore, software development risk management is becoming recognized as a best practice in the software industry for reducing these risks before they occur. This thesis contributes for a goal-driven software development risk management model to assess and manage software development risk within requirement engineering phase

The Impact of Software Process Maturity and Software Development Risk on the Performance of Software Development Projects

Despite the increasing efforts of organizations to improve the development processes of their software projects, there remain few empirical and generalizable findings when it comes to key questions regarding software process improvement initiatives. Rarely there was any empirical examination in an integrative model on how process improvement efforts affect key organizational concerns such as software project performance and the threat of risks in today’s dynamic and complex business environment. In addressing this knowledge gap, we propose and test a research model that allows for an empirical examination of the relationships between software process maturity and the performance of software development projects while assessing the impact of risk on software project performance. Data were collected from officially CMM-appraised organizations to test developed hypotheses using proven metrics identified in the literature. Our findings support our theoretical framework in providing evidence of the positive impact of software development process maturity on the performance of software projects while underscoring the negative effect of risk on software project performance. Key results and a discussion of the findings are also provided

Towards a Framework for Offshore Outsource Software Development Risk Management Model

Due to high demands on cost savings in software development projects, offshore outsource software development is becoming increasingly popular. Offshore outsourcing takes advantages of large labor pool in lowwage countries, round-the-clock development, and easy access to additional resources, in addition to the development cost savings. However, there are risks associated to this trend, as it brings new challenges into the development process, where some may even jeopardise the cost savings. The geographical and cultural distance is one part of the problem, inexperienced developers and lack of communication and a common cultural basis are other challenges. We therefore advocate the use of risk management (RM) to control risks in offshore outsource development. Here we present a RM framework tailored for such development contexts. The model; Goal-driven Software Development Risk Management modelling (GSRM) framework, assesses and manages risk during the early development phases, where risks can easier be tackled at a reasonable cost. The framework is comprised of four layers that together identify and link project goals, risks and treatments together in a goal-risk causal relationship model. The goal model makes use of an extended subset of the KAOS goal modelling language. We report on a study project focusing on the efficiency of the GSRM process model

Exploring aspects of agile software development risk – results from a MLR

Agile software development methods are widely used by software organisations, focusing on short developmental life cycles and customer satisfaction through the iterative and incremental development of software products. Despite their popularity, these methods present risks that may be underappreciated. This paper examines certain risks attributed to agile software development, with a focus on the lack of documentation, scope creep, technical debt and job satisfaction. Through the application of a multivocal literature review, we find that agile software development can greatly benefit projects. However, when agile methods are implemented inappropriately or sub-optimally, projects risk over-spending, delayed or defective software, employee turnover, and overall decreased productivity. Understanding the risks associated with agile software development can help practitioners to achieve higher efficiency and success in their software development projects

A Software Safety Risk Taxonomy for Use in Retrospective Safety Cases

Safety standards contain technical and process-oriented safely requirements. The best time to include these requirements is early in the development lifecycle of the system. When software safety requirements are levied on a legacy system after the fact, a retrospective safety case will need to be constructed for the software in the system. This can be a difficult task because there may be few to no art facts available to show compliance to the software safely requirements. The risks associated with not meeting safely requirements in a legacy safely-critical computer system must be addressed to give confidence for reuse. This paper introduces a proposal for a software safely risk taxonomy for legacy safely-critical computer systems, by specializing the Software Engineering Institute's 'Software Development Risk Taxonomy' with safely elements and attributes