Process Models of SDLCs

2009 ◽  
pp. 76-89 ◽  
Author(s):  
Laura C. Rodriguez ◽  
Manuel Mora ◽  
Miguel Vargas Martin ◽  
Rory O’Connor ◽  
Francisco Alvarez
Keyword(s):  
Software Process ◽  
Systems Development ◽  
Life Cycles ◽  
Process Models ◽  
Software Systems ◽  
Engineering Discipline ◽  
Development Teams ◽  
The Common ◽  
Research Questions ◽  
Conceptual Research

The software engineering discipline has developed the concept of software process to guide development teams towards a high-quality end product to be delivered on-time and within the planned budget. Consequently,several software-systems development life-cycles (PM-SDLCs) have been theoretically formulated and empirically tested over the years. In this chapter, a conceptual research methodology is used to review the state of the art on the main PM-SDLCs formulated for software-intensive systems, with the aim to answer the following research questions: (a) What are the main characteristics that describe the PM-SDLCs?, (b) What are the common and unique characteristics of such PM-SDLCs?, and (c) What are the main benefits and limitations of PM-SDLCs from a viewpoint of a conceptual analysis? This research is motivated by a gap in the literature on comprehensive studies that describe and compare the main PMSDLCs and organizes a view of the large variety of PM-SDLCs.

The Incremental Commitment Spiral Model for Service-Intensive Projects

2013 ◽  
pp. 94-115
Author(s):  
Supannika Koolmanojwong ◽  
Barry Boehm ◽  
Jo Ann Lane
Keyword(s):  
Web Services ◽  
Process Model ◽  
Software Process ◽  
Business Environment ◽  
Process Models ◽  
Software Systems ◽  
Generation Process ◽  
Software Process Models ◽  
Commercial Off The Shelf ◽  
Spiral Model

To provide better service to customers and remain competitive in the business environment, a wide variety of ready-to-use software and technologies are available for one to “grab and go” in order to build up software systems at a rapid pace. Currently, a wide variety of Web services are available and ready to use for this purpose. Current software process models also support commercial-off-the-shelf (COTS)-based development processes. However, although COTS and Web Services are similar, they are different in many perspectives. On one hand, there are various software process models that support Web services development. Yet there is no process model that supports the project that uses services provided by others. This chapter introduces the Incremental Commitment Spiral Model (ICSM), a new generation process model that provides development guidelines, from exploring a Web service alternative to deployment and maintenance with case studies.

The Incremental Commitment Spiral Model for Service-Intensive Projects

2014 ◽  
pp. 2142-2162 ◽  
Author(s):  
Supannika Koolmanojwong ◽  
Barry Boehm ◽  
Jo Ann Lane
Keyword(s):  
Web Services ◽  
Process Model ◽  
Software Process ◽  
Business Environment ◽  
Process Models ◽  
Software Systems ◽  
Generation Process ◽  
Software Process Models ◽  
Commercial Off The Shelf ◽  
Spiral Model

To provide better service to customers and remain competitive in the business environment, a wide variety of ready-to-use software and technologies are available for one to “grab and go” in order to build up software systems at a rapid pace. Currently, a wide variety of Web services are available and ready to use for this purpose. Current software process models also support commercial-off-the-shelf (COTS)-based development processes. However, although COTS and Web Services are similar, they are different in many perspectives. On one hand, there are various software process models that support Web services development. Yet there is no process model that supports the project that uses services provided by others. This chapter introduces the Incremental Commitment Spiral Model (ICSM), a new generation process model that provides development guidelines, from exploring a Web service alternative to deployment and maintenance with case studies.

Evolution and Maintenance of Web Sites

2011 ◽  
pp. 255-271
Author(s):  
Rafael Capilla ◽  
Juan C. Duenas
Keyword(s):  
Web Sites ◽  
Systems Development ◽  
Product Line ◽  
Software Systems ◽  
Software Products ◽  
Software Companies ◽  
Software Engineers ◽  
The Common ◽  
Common Architecture ◽  
The Web

In this chapter we describe the product line models, and show how to apply them for developing and evolving Web products. A product line captures the common and variable aspects of software systems as key assets under a common architecture. Software companies are increasingly adopting this approach in order to accelerate the development of families of similar software products. In certain domains, such as the Web systems, development and maintenance operations are required more often. New techniques to engineer Web sites are needed in order to reduce the time to market for the Web products and to maintain the systems afterward. The authors believe that understanding the notion of lightweight product line and the role that the architecture plays will help software engineers in the construction of software products, and they will be able to manage the evolution effectively against future changes.

Influential Agile Software Parameters

2011 ◽  
pp. 1938-1943
Author(s):  
Subhas C. Misra ◽  
Vinod Kumar ◽  
Uma Kumar
Keyword(s):  
Project Management ◽  
Software Process ◽  
Systems Development ◽  
The Other ◽  
Software Systems ◽  
Software Projects ◽  
Optimal Cost ◽  
Management Processes ◽  
Agile Software ◽  
Refining Processes

Successful software systems development is a delicate balance among several distinct factors (Jalote, 2002) such as enabling people to grow professionally; documenting processes representing the gained experiences and knowledge of the organization members; using know how to apply the suitable processes to similar circumstances; and refining processes based on achieved experience. Software projects have two main dimensions: engineering and project management. The engineering dimension concerns the construction of a system, and focuses mainly on issues such as how to build a system. The project management dimension is in charge with properly planning and controlling the engineering activities to meet project goals for optimal cost, schedule, and quality. For a project, the engineering processes specify how to perform activities such as requirement specification, design, testing, and so on. The project management processes, on the other hand, specify how to set milestones, organize personnel, manage risks, monitor progress, and so on (Jalote, 2002). A software process may be defined as “a set of activities, methods, practices, and transformations that people use to develop and maintain software, and the associated products and artifacts.”1 This is pictorially depicted in Figure 1 (Donaldson & Siegel, 2000).

Software Process Paradigms and Crowdsourced Software Development

Crowdsourcing ◽  
2019 ◽  
pp. 1551-1568
Author(s):  
Nitasha Hasteer ◽  
Abhay Bansal ◽  
B. K. Murthy
Keyword(s):  
Software Development ◽  
Development Strategy ◽  
Software Process ◽  
Process Models ◽  
Development Methodology ◽  
Develop Software ◽  
The Common ◽  
Traditional Process ◽  
Use Of Social Media ◽  
The Right

Production of quality software requires selecting the right development strategy. The process and development strategies for creating software have evolved over the years to cope with the changing paradigms. Cloud computing models have made provisioning of the computing capabilities and access to configurable pooled resources as convenient as having access to the common utilities. With the recent advancements in the use of social media and advent of software development through crowdsourcing, the need to comprehend and analyze the traditional process models of software development, with regard to the changed paradigm have become ever more necessary. The changes in the way software are being created and the continuous evolution in the processes of development and deployment has created a need to understand the development process models. This chapter provides an insight on the transition from the conventional process models of software development to the software development methodology being used to develop software through crowdsourcing.

Software Process Paradigms and Crowdsourced Software Development

2016 ◽  
pp. 229-246
Author(s):  
Nitasha Hasteer ◽  
Abhay Bansal ◽  
B. K. Murthy
Keyword(s):  
Software Development ◽  
Development Strategy ◽  
Software Process ◽  
Process Models ◽  
Development Methodology ◽  
Develop Software ◽  
The Common ◽  
Traditional Process ◽  
Use Of Social Media ◽  
The Right

Production of quality software requires selecting the right development strategy. The process and development strategies for creating software have evolved over the years to cope with the changing paradigms. Cloud computing models have made provisioning of the computing capabilities and access to configurable pooled resources as convenient as having access to the common utilities. With the recent advancements in the use of social media and advent of software development through crowdsourcing, the need to comprehend and analyze the traditional process models of software development, with regard to the changed paradigm have become ever more necessary. The changes in the way software are being created and the continuous evolution in the processes of development and deployment has created a need to understand the development process models. This chapter provides an insight on the transition from the conventional process models of software development to the software development methodology being used to develop software through crowdsourcing.

Software Process Paradigms and Crowdsourced Software Development

2019 ◽  
pp. 703-720
Author(s):  
Nitasha Hasteer ◽  
Abhay Bansal ◽  
B. K. Murthy
Keyword(s):  
Software Development ◽  
Development Strategy ◽  
Software Process ◽  
Process Models ◽  
Development Methodology ◽  
Develop Software ◽  
The Common ◽  
Traditional Process ◽  
Use Of Social Media ◽  
The Right

Production of quality software requires selecting the right development strategy. The process and development strategies for creating software have evolved over the years to cope with the changing paradigms. Cloud computing models have made provisioning of the computing capabilities and access to configurable pooled resources as convenient as having access to the common utilities. With the recent advancements in the use of social media and advent of software development through crowdsourcing, the need to comprehend and analyze the traditional process models of software development, with regard to the changed paradigm have become ever more necessary. The changes in the way software are being created and the continuous evolution in the processes of development and deployment has created a need to understand the development process models. This chapter provides an insight on the transition from the conventional process models of software development to the software development methodology being used to develop software through crowdsourcing.

A PROCESS MODEL APPLICABLE TO SOFTWARE ENGINEERING AND KNOWLEDGE ENGINEERING

1999 ◽  
Vol 09 (05) ◽  
pp. 663-687 ◽  
Author(s):  
SILVIA T. ACUÑA ◽  
MARTA LOPEZ ◽  
NATALIA JURISTO ◽  
ANA MORENO
Keyword(s):  
Software Engineering ◽  
Process Model ◽  
Knowledge Engineering ◽  
Software Process ◽  
Process Models ◽  
Software Systems ◽  
Conceptual Tool ◽  
Knowledge Based ◽  
Develop Software ◽  
Conventional Systems

Software engineering (SE) and knowledge engineering (KE) develop software systems using different construction process models. Because of the growing complexity of the problems to be solved by computers, the conventional systems (CS) and knowledge-based systems (KBS) software process is at present passing through a period of integration. In this paper, we propose a software process model applicable to both CS and KBS. The model designed is declarative, that is, it indicates what is done to build a software system. Its goal is to provide software and knowledge engineers with a techno-conceptual tool to develop systems comprising both traditional and knowledge-based software.

MUSTER

2010 ◽  
pp. 146-165
Author(s):  
Chad Coulin ◽  
Didar Zowghi ◽  
Abd-El-Kader Sahraoui
Keyword(s):  
Systems Development ◽  
Primary Objective ◽  
Requirements Elicitation ◽  
Software Systems ◽  
Method Engineering ◽  
Group Support System ◽  
Computer Aided ◽  
Elicitation Process ◽  
The Common ◽  
Computer Aided Software Engineering

In this chapter they present a collaborative and situational tool called MUSTER, that has been specifically designed and developed for requirements elicitation workshops, and which utilizes, extends, and demonstrates a successful application of intelligent technologies for Computer Aided Software Engineering and Computer Aided Method Engineering. The primary objective of this tool is to improve the effectiveness and efficiency of the requirements elicitation process for software systems development, whilst addressing some of the common issues often encountered in practice through the integration of intelligent technologies. The tool also offers an example of how a group support system, coupled with artificial intelligence, can be applied to very practical activities and situations within the software development process.

MUSTER

2012 ◽  
pp. 620-638
Author(s):  
Chad Coulin ◽  
Didar Zowghi ◽  
Abd-El-Kader Sahraoui
Keyword(s):  
Systems Development ◽  
Primary Objective ◽  
Requirements Elicitation ◽  
Software Systems ◽  
Method Engineering ◽  
Group Support System ◽  
Computer Aided ◽  
Elicitation Process ◽  
The Common ◽  
Computer Aided Software Engineering

In this chapter they present a collaborative and situational tool called MUSTER, that has been specifically designed and developed for requirements elicitation workshops, and which utilizes, extends, and demonstrates a successful application of intelligent technologies for Computer Aided Software Engineering and Computer Aided Method Engineering. The primary objective of this tool is to improve the effectiveness and efficiency of the requirements elicitation process for software systems development, whilst addressing some of the common issues often encountered in practice through the integration of intelligent technologies. The tool also offers an example of how a group support system, coupled with artificial intelligence, can be applied to very practical activities and situations within the software development process.

Sign in / Sign up

Export Citation Format

Share Document