Decision-Tree Models for Predicting Time Performance in Software-Intensive Projects

Decision-Tree Models for Predicting Time Performance in Software-Intensive Projects

Nermin Sökmen, Ferhan Çebi
DOI: 10.4018/IJITPM.2017040105
OnDemand:
(Individual Articles)
Available
$37.50
No Current Special Offers
TOTAL SAVINGS: $37.50

Abstract

Initial requirements, new requirements and technical issues are the main factors that have a great effect over the software product development process. Difficulties resulting from incomprehensibility of initial requirements indicate two sub-factors: Deviations determined during analysis of initial requirements and deviations resulting from interpretation of requirements inaccurate and incomplete. New requirements being received from customers or end users during the development process affect the project performance. There can be problems during the implementation of product specifications, inaccurate formation of architectural design and technical solutions, incorrect coding of functions, or wrong realization of interfaces. The general technical problems cover the all problems arising from technical reasons and the negative situations they create on the project. During the design and implementation activities of software intensive projects, these tree main factors can be affected by other sub-factors. The aim of this study is to examine the factor classes which influence these three problem domains with CHAID (Chi-squared Automatic Interaction Detection) technique. Time deviations caused by initial requirements, new requirements and general technical problems are selected as target variables. In this research, 75 projects that develop software intensive products are studied to formalize the most accurate decision mechanism.
Article Preview
Top

1. Introduction

The quality of project planning affects the project success (Dvir and Lechler, 2004). According to Sarigiannidis and Chatzoglou (2014), the negative relationship exists between project quality and risk. Quantifying impact of risks has a positive association with the overall project schedule targets of new product development program (Oehmen et al., 2014). It is very important to identify risks and assess their likelihood and potential effect on project schedule before the project started.

Software development risks have been widely discussed in the literature (Barki et al., 1993; Jiang and Klein, 2000; Schmidt et al, 2001; Wallace and Keil, 2004; Wallace et al., 2004b; Han and Huang, 2007). Difficulties resulting from initial and new requirements and problems related to technical issues have always been important risk items in software development projects (Sökmen et al., 2014). Liu et al. (2011) indicate that the performance of software development process is affected by the requirements that are not defined completely, correctly and comprehensively. Incorrect, unclear, inadequate, ambiguous or unusable requirements increase problems or risks in software development projects (Wallace et al., 2004a). Goal changes that can be due to changes in requirements or lack of ability to meet existing requirements may cause change in project plans in order to meet the new requirements (Dvir and Lechler, 2004). Requirements instability negatively affects the project performance with extending the project time, causing remaking of the substantial part of work and affecting the other project features (Ferreira et. al., 2009).

Technical sub-system risks determined by uncertainty and technical complexity have strong impact on project management risks (Wallace et al., 2004b). In fact, functional development risk is directly associated with increase in system development risk (Na et al., 2007). According to Carvalho et al. (2015), project complexity has a significant effect on schedule variation. The inaccurate formation of architectures, interfaces and data structures, incorrect coding and environment uncertainty are some of the negative situations that affect the performance of the entire project unless they are managed well. These negative situations are evaluated together under a single factor called as “general technical problems”.

There are only few studies that examined the schedule performance of the sub-processes or tasks in development projects in the literature. In this study, the difficulties resulting from analysis of initial requirements are examined with the problems arising from new requirements and general technical difficulties. Sökmen et al. (2014) used multiple linear regression analysis to examine the effects of these three factors (or sub-processes) on project schedule in software-intensive projects. This study is expected to go one step further by analyzing the impact of sub-factors. The aim of this study is to find out the effect of the sub-factors influencing these three main factor classes. Schedule delays or time deviations in the project due to initial requirements, new requirements and general technical problems are the target variables. The study aims to build three predictive models to help reveal the most effective factors on the success of the software development processes.

In the study, the factors including the status of requirements, product innovation, project manager competency, team competency, preliminary preparation studies, reuse, customer support and product type are selected as the factors that could be effective on these destructive factors, namely, problems caused by initial requirements, problems caused by new requirements and general technical problems. Here, the most effective factors on the target variable are determined by using CHAID (Chi-squared Automatic Interaction Detection) algorithm. With the help of the hierarchical tree structure, the effects of the factors on the target variable are found out.

Complete Article List

Search this Journal:
Reset
Volume 15: 1 Issue (2024)
Volume 14: 1 Issue (2023)
Volume 13: 4 Issues (2022): 3 Released, 1 Forthcoming
Volume 12: 4 Issues (2021)
Volume 11: 4 Issues (2020)
Volume 10: 4 Issues (2019)
Volume 9: 4 Issues (2018)
Volume 8: 4 Issues (2017)
Volume 7: 4 Issues (2016)
Volume 6: 4 Issues (2015)
Volume 5: 4 Issues (2014)
Volume 4: 4 Issues (2013)
Volume 3: 4 Issues (2012)
Volume 2: 4 Issues (2011)
Volume 1: 4 Issues (2010)
View Complete Journal Contents Listing