Software Process Improvement for Web-Based Projects Comparative View

Software Process Improvement for Web-Based Projects Comparative View

Thamer Al-Rousan (Isra University, Pakistan)
Copyright: © 2018 |Pages: 14
DOI: 10.4018/978-1-5225-2255-3.ch657
OnDemand PDF Download:
$30.00
List Price: $37.50

Abstract

Software process improvement has been the main targets by many Web application development organizations. Despite the importance of software process improvement, there is enough evidence that the majority of Web-based software organizations are reluctant to adapt existing software process improvement models and standards as they perceive them as being oriented towards traditional software organizations. It has been observed that Improvement efforts Web-based software development organizations based on process improvement frameworks which are designed for traditional software organizations fails most of the time. This study attempts to make a review of different software process improvement models, and check the suitability of these models to meet the special characteristics and requirements for the Web-based projects. The findings of this study can be helpful for the Web-based software development organizations in assessing and improving software processes.
Chapter Preview
Top

Introduction

In the last two decades, there have been a significant increase on the expectations and demand of Web-based application due to the influence of the World Wide Web on our modern economy (Pressman, 2004). At the same time, the development, deployment and maintenance processes of the web-based systems which have become more and more complex and difficult to manage, have not progressed at a sufficient rate to meet these demand and expectations (Cardoso, 2007).

Many developers of web-based projects do not take into concern the unique requirements and characteristics of Web applications. They fail to realize that characteristics and requirements of web-based systems considerably different from that of traditional software, and so does their development (Alrifai, 2008). Hence, many developers conduct web applications in an ad hoc manner, and fail to adopt sound design methodologies, resulting in poor quality web systems and applications. A survey by the Cutter Consortium (2006) shows that failure to meet business needs (84%), project schedule delays (79%), and budget overruns (63%), lack of functionality (53%) and poor quality of deliverables (52%) are the main problems cited by the stakeholders of such applications.

In finding solutions to the problems of web-based application development, there has been an increasing pressure on the Web-based application industry. The search for solutions to improve Web-based software development has continued for many years and Web-based applications organizations are now realizing that one of their fundamental problems is the inability to effectively manage the Web-based applications development process (Sulayman & Mendes, 2011). Software Process Improvement (SPI) has been recognized as an efficient and effective way for organizations to improve their quality of the software they develop and the productivity with which they work with. For this, SPI is an essential tool for improving Web-based applications development process (Sulayman & Mendes, 2011).

Process improvement in Web-based software projects is of growing concern for many reasons such as reducing cost and time, producing high quality software, and improving productivity (Smite et al., 2011). Despite the importance of SPI implementation, there is evidence that the vast majority of Web-based software development organizations are reluctant to adapt SPI models and standard because of their complexity (Abdel-Hamid & Abdel-Kader, 2011). It has been detected that improvement efforts in Web-based software projects based on process improvement frameworks which are designed for traditional software projects fails most of the time (Sulayman & Mendes, 2011).

In the absence of theoretical or empirical work examining the suitability of the traditional SPI standards and models for Web-based projects development, we believe that it is important to examine the suitability of the existing SPI standards and models for Web-based projects development process. The motivation for this study was to fill the gaps in the field of software process improvement. The main contributions of this study are:

  • 1.

    Examine the suitability of the existing software process improvement models and standards for Web-based projects.

  • 2.

    Increasing awareness on the importance of software process improvement in Web-based projects.

We believe that achieving these goals will lead to enrich the SPI in Web-based projects with new properties that leads to enhance the SPI projects implementation.

Key Terms in this Chapter

CMMI: A model that supports evaluating and improving an organization’s processes using a best-practice model.

ISO/IEC: An international standard for evaluating and improving an organization’s software processes.

Model-Based on SPI: Model-based on SPI approaches compare the current processes and practices of a development organization against a reference model or a benchmark.

Process Model: Representation of a real-world process that focuses only on specific features of the real-world process and does not capture all details.

QIP: The Quality Improvement Paradigm (QIP) is a six-step procedure for structuring software development and improvement activities.

Process Improvement (SPI): SPI means understanding existing processes and changing these processes to increase product quality and/or reduce costs and development time.

Software Process Model: A software process model is a model of a software process.

Model: An abstract and simplifying representation of an object or phenomenon of the real world.

Complete Chapter List

Search this Book:
Reset