scholarly journals Using the Fuzzy Linguistic Preference Relation Approach for Assessing the Importance of Risk Factors in a Software Development Project

2013 ◽  
Vol 2013 ◽  
pp. 1-9 ◽  
Author(s):  
Shih-Tong Lu ◽  
Shih-Heng Yu ◽  
Dong-Shang Chang ◽  
Shih-Chang Su
Keyword(s):  
Risk Factors ◽  
Software Development ◽  
Preference Relation ◽  
Development Project ◽  
Software Development Project ◽  
Linguistic Preference Relation ◽  
System Risk ◽  
Risk Dimensions ◽  
Fuzzy Linguistic ◽  
Information Collecting

This study employs fuzzy linguistic preference relation (Fuzzy LinPreRa) approach to assess the relative degree of impact of risk factors in software development project for two expert groups working in technology enterprises and software development companies. For the identified risk dimensions, the results show the same rankings for these two groups. “Organization function risk” is considered the most important dimension influencing the software development project performance, with the others, in order, being “developing technology risk,” “resources integration risk,” “personnel system risk” and “system requirement risk.” The proposed approach not only facilitates the information collecting for making pairwise comparisons, but it also eliminates the inconsistencies in the collected information.

scholarly journals Most severe risk factors in software development projects in Kuwait

2021 ◽  
Vol 21 (1) ◽  
pp. 591
Author(s):  
Abdullah J. Al-Shehab ◽  
Thalaya Alfozan ◽  
Hesham Gadelrab
Keyword(s):  
Risk Factors ◽  
Software Development ◽  
Quantitative Methods ◽  
Developed Countries ◽  
Development Project ◽  
High Rate ◽  
Development Projects ◽  
Face To Face ◽  
Software Development Project ◽  
Private Organizations

<p><span>Software development projects are famous of high rate failure, this made an encouragement for researcher to investigate reasons of failure. However, literature covering under developed countries is uncommon. This research investigates the most severe risk factors in software development project in the country of Kuwait. A face-to-face questionnaire with 109 IT practitioners in Kuwait from government and private organizations was conducted. The findings reveal and identify risk factors that have a high impact on the budget, quality, and schedule. The aim of this study is to validate risk factor taxonomy through quantitative methods by experts in the field of IT. Another purpose of this research is to provide a comprehensive and updated review of risk factors from Kuwait to be presented for IT practitioners and researchers.</span></p>

Software Development Project Risk

2012 ◽  
Vol 3 (4) ◽  
pp. 41-55 ◽  
Author(s):  
Sam Thomas ◽  
M. Bhasi
Keyword(s):  
Software Development ◽  
Factor Model ◽  
Developed Countries ◽  
Development Project ◽  
Project Planning ◽  
Software Project ◽  
Project Risk ◽  
Software Development Project ◽  
External Risk ◽  
Risk Dimensions

Software development risk points to an aspect of a development task, process or environment which, if ignored, tends to adversely affect the project performance. Observations from literature show that while many studies on software project risk construct have been done in developed countries, there is scarcity of literature from Asian countries, especially India. Hence, this research was formulated with an objective of studying software development project risk in the Indian context. Data related to the presence of risk items was collected from 527 software development projects in India. This data was factor analyzed to identify five major risk dimensions namely Team risk, Project planning and Execution Risk, External risk, User risk and Project complexity risk. The resulting factor structure was validated through Confirmatory Factor Analysis. Software project risk was seen to be best represented by a second order factor model with five first order factors.

scholarly journals Suppliers’ software development project start-up practices

2017 ◽  
Vol 10 (4) ◽  
pp. 880-896
Author(s):  
Helena Merikoski ◽  
Paula Savolainen ◽  
Jarmo J. Ahonen
Keyword(s):  
Life Cycle ◽  
Software Development ◽  
Development Project ◽  
Cycle Phase ◽  
Development Projects ◽  
Content Type ◽  
Business Context ◽  
Software Development Project ◽  
Business Goals ◽  
Start Up

Purpose The purpose of this paper is to present a life cycle phase of a software development project which is substantial for the success of the project. This paper visualizes the project start-up phase from suppliers’ perspective. Design/methodology/approach The method is a theory building from case studies. The data were collected from three software supplier firms by conducting process modeling separately in each firm. Findings The study resulted in a model of a supplier’s software project start-up which includes start-up practices and involved roles. The results indicate that project start-up is an integral and structured phase of project life cycle, which influences the execution of a software development project, especially from the supplier’s perspective in the project business context. Research limitations/implications The study focuses on the start-up phase of software development projects delivered to external customers. Therefore, developed project start-up model is applicable as such in software supplier firms. Practical implications The project start-up model presented in this paper indicates that project start-up is a complex and multi-dimensional activity in a supplier firm. This study suggests that if the project start-up phase is clearly defined, planned and followed in a supplier firm, it reduces confusion and miscommunication among the people involved in the project and helps to achieve the business goals of a project. Originality/value This study emphasizes that it is necessary to make a distinction between the perspectives of the customer and the supplier when studying projects in the project business context. The findings contribute the new knowledge for managing outsourced software development projects.

Knowledge Management and Quality Control in Software Outsourcing Projects

2017 ◽  
Vol 13 (4) ◽  
pp. 31-55 ◽  
Author(s):  
Rajorshi Sen Gupta
Keyword(s):  
Quality Control ◽  
Knowledge Management ◽  
Intellectual Property ◽  
Software Development ◽  
Service Providers ◽  
Economic Incentives ◽  
Development Project ◽  
Apparent Paradox ◽  
Software Development Project ◽  
Lump Sum

This article describes how entrepreneurs face critical risks in terms of quality control and knowledge management while outsourcing software development to independent service providers. First, it is recommended that lump-sum payment contracts should be avoided since software development project involves uncertainty. Instead, a variable payment contingent on observed quality can induce the service provider to exert optimal effort on the project. Second, entrepreneurs must not overlook the importance of providing economic incentives. They can protect their intellectual property by withholding critical knowledge and paying information rents in terms of higher than market wages to the service providers. Third, a startling result is that a low wage nation is not necessarily the optimal location to outsource software development projects. Thus, high wage-strong IPR nations might be chosen instead of low wage-weak IPR nations. Finally, the article explains the apparent paradox that software projects are often outsourced to locations that are characterized by weak intellectual property rights regime and high propensity of imitation.

scholarly journals Towards a methodology to estimate cost of object-oriented software development projects

2004 ◽  
Vol 1 (2) ◽  
pp. 173-194 ◽  
Author(s):  
Radoslav Rakovic
Keyword(s):  
Software Development ◽  
Development Process ◽  
A Priori ◽  
Unified Modeling Language ◽  
Object Oriented ◽  
Subsequent Development ◽  
Development Project ◽  
Software Project ◽  
Software Development Project ◽  
Early Estimate

Successful management of a software project, besides a well-defined project development process, requires an early estimate of project complexity. In a prevailing practice, software development costs usually have been determined a posteriori i.e. after software project implementation. It is essential however, to know this estimate a priori, i.e., before commencement of works. This paper presents an attempt to construct a methodology that would enable an early estimate of software development cost and its refinements during subsequent development phases. The methodology assumes an object-oriented approach based on the Unified Modeling Language (UML) and Unified Software Development Process (USDP). It outlines an Use Case Driven Architecture-Centric, Iterative and Incremental estimate process that could significantly improve and simplify early cost estimates. The presented methodology is illustrated on example of the POST software development project.

Sign in / Sign up

Export Citation Format

Share Document