Comparative Analysis of Software Process Models in Software Development

2021 ◽  
Vol 10 (3) ◽  
pp. 2593-2599
Keyword(s):  
Comparative Analysis ◽  
Software Development ◽  
Software Process ◽  
Process Models ◽  
Software Process Models

A Brief Overview of Software Process Models

2014 ◽  
pp. 258-271
Author(s):  
Sanjay Misra ◽  
Martha Omorodion ◽  
Luis Fernández-Sanz ◽  
Carmen Pages
Keyword(s):  
Comparative Analysis ◽  
Software Engineering ◽  
Software Development ◽  
Process Development ◽  
Software Process ◽  
Process Models ◽  
Future Research ◽  
Development Models ◽  
Software Process Models ◽  
To Come

Software process development in software engineering does not seem to offer a solid view of what they have in reality. Although many models have already been developed, recommended, or even used in the industry, these proposals have still not been able to come to terms with what is available. This chapter evaluates the benefits and limitations of some of the software development models while offering a comparative analysis and data on their real usage. In particular, an attempt has been made to evaluate the problems and strengths of a good variety of software process models and methodologies. Some conclusions and lines of future research are presented.

A Brief Overview of Software Process Models

2017 ◽  
pp. 1-14
Author(s):  
Sanjay Misra ◽  
Martha Omorodion ◽  
Luis Fernández-Sanz ◽  
Carmen Pages
Keyword(s):  
Comparative Analysis ◽  
Software Engineering ◽  
Software Development ◽  
Process Development ◽  
Software Process ◽  
Process Models ◽  
Future Research ◽  
Development Models ◽  
Software Process Models ◽  
To Come

Software process development in software engineering does not seem to offer a solid view of what they have in reality. Although many models have already been developed, recommended, or even used in the industry, these proposals have still not been able to come to terms with what is available. This chapter evaluates the benefits and limitations of some of the software development models while offering a comparative analysis and data on their real usage. In particular, an attempt has been made to evaluate the problems and strengths of a good variety of software process models and methodologies. Some conclusions and lines of future research are presented.

scholarly journals Software process models: a review and analysis

2018 ◽  
Vol 7 (2.29) ◽  
pp. 325
Author(s):  
Ramzi A. Haraty ◽  
Gongzhu Hu
Keyword(s):  
Software Development ◽  
Development Process ◽  
Software Process ◽  
Process Models ◽  
Complex Nature ◽  
Software Development Process ◽  
The Past ◽  
Management Quality ◽  
Human Management ◽  
Software Process Models

Modeling of software process has been a very challenging problem and constantly debated in the software development community in the past 30+ years, largely due to the complex nature of the software development process that involves not only the technical knowledge and skills but also many other factors, such as human, management, quality assessment, and cost. Although the situations of creating software differ greatly from one case to another, there are some common themes shared by many of the situations, and hence various software process models have been emerged to address these common themes. In this paper, we present a review of the software process models commonly used in practice, from traditional to agile, and assessment of these models with metrics and case studies.

scholarly journals Tarpinio programų kūrimo proceso modelio reikalavimai

2011 ◽  
Vol 56 ◽  
pp. 138-145
Author(s):  
Stasys Peldžius ◽  
Saulius Ragaišis
Keyword(s):  
Software Development ◽  
Process Model ◽  
Software Process ◽  
Process Models ◽  
Capability Maturity ◽  
Software Product ◽  
Software Process Models ◽  
Software Development Methodologies ◽  
Software Crisis

Įmonės, siekdamos sėkmingai įgyvendinti programų kūrimo projektus – pateikti rezultatus laiku, neviršydamos biudžeto, ir kad klientai būtų patenkinti jų kokybe, renkasi programų kūrimo proceso modelius, pagal kuriuos gali įvertinti savo programų kūrimo procesą ir jį gerinti. Šiuo metu pasaulyje populiariausi programų kūrimo proceso modeliai yra ISO/IEC 15504 ir CMMI. Įmonėms prasminga turėti įvertinimus pagal abu šiuos proceso modelius, bet kiekvienas įmonės vertinimas brangus tiek finansiniu, tiek laiko požiūriu, todėl būtų naudinga gauti įvertinimus pagal skirtingus modelius, atliekant tik vieną vertinimą. Norėdamos apibrėžti ir (ar) pagerinti savo programų kūrimo procesą, įmonės renkasi įvairius programų sistemų inžinerijos metodus, pavyzdžiui, XP, Scrum, DSDM, RUP. Įmonei svarbu žinoti, ką pasirinktas metodas jai gali duoti: kokį proceso gebėjimą ir (ar) brandą jis gali užtikrinti. Šias aktualias problemas išspręstų tarpinis programų kūrimo proceso modelis, kuris leistų įmonėms atlikti įvertinimą pagal vieną proceso modelį ir gauti rezultatus pagal kelis modelius, taip pat žinoti, kokį proceso gebėjimą ir (ar) brandą gali užtikrinti pasirinktas programų sistemų inžinerijos metodas. Straipsnyje pateikiamas pirmasistokio modelio kūrimo žingsnis – apibrėžiami tokio modelio reikalavimai.Requirements of Transitional Software Process ModelStasys Peldžius, Saulius Ragaišis SummaryMost of the software development projects face the following problems: projects are delayed; they overrun the budget; customers are dissatisfied with the quality of the software delivered. This phenomenon is so widespread that it is even called a software crisis. It has been understood that software process maturity is closely related to project success and the quality of a software product, so various software process models have been introduced. Organizations want to get all the advantages of the different process models that stimulate their harmonization and the investigation of process improvement in multimodel environments. Organizations seek to get their capability/maturity assessment according to several process models by conducting only a single assessment. This could be achieved by the transitional software process model. Organizations employ different software development methodologies, but they are unable to assess how they affect their process without implementation. The transitional model helps to assess the capability/maturity according to ISO/IEC 15504 and CMMI which could be ensured by agile or other software development methodologies. Similar ideas have been introduced in the unified SEPRM model. A detailed review of the deficiencies that led to its unpopularity is made. The paper presents the requirements for the transitional software process model.

scholarly journals Software process models: a review and analysis

2018 ◽  
Vol 7 (2.28) ◽  
pp. 390
Author(s):  
Ramzi A. Haraty ◽  
Gongzhu Hu
Keyword(s):  
Software Development ◽  
Development Process ◽  
Software Process ◽  
Process Models ◽  
Complex Nature ◽  
Software Development Process ◽  
The Past ◽  
Management Quality ◽  
Human Management ◽  
Software Process Models

Modeling of software process has been a very challenging problem and constantly debated in the software development community in the past 30+ years, largely due to the complex nature of the software development process that involves not only the technical knowledge and skills but also many other factors, such as human, management, quality assessment, and cost. Although the situations of creating software differ greatly from one case to another, there are some common themes shared by many of the situations, and hence various software process models have been emerged to address these common themes. In this paper, we present a review of the software process models commonly used in practice, from traditional to agile, and assessment of these models with metrics and case studies.

scholarly journals Is it Safe to Adopt the Scrum Process Model?

2011 ◽  
Vol 14 (3) ◽  
Author(s):  
Julio Ariel Hurtado Alegría ◽  
María Cecilia Bastarrica ◽  
Alexandre Bergel
Keyword(s):  
Software Development ◽  
Process Model ◽  
Software Process ◽  
Process Models ◽  
Process Definition ◽  
The Public ◽  
Software Companies ◽  
The World ◽  
Software Process Models ◽  
Agile Software

Scrum is a widely known agile software process model specifically designed for guiding non- technical activities in software development. This process has been formally defined in EPF and adopted by several software companies around the world. But having a process definition does not necessarily mean that it is well specified. We have developed AVISPA, a tool for localizing error patterns in software process models specified with EPF. In this paper, we analyze the public community specification of Scrum using AVISPA and we report our findings.

SOFTWARE PROCESS MONITORING MECHANISMS IN OIKOS

1994 ◽  
Vol 04 (04) ◽  
pp. 481-499 ◽  
Author(s):  
C. MONTANGERO ◽  
F. SCARSELLI
Keyword(s):  
Process Monitoring ◽  
Software Process ◽  
Process Quality ◽  
Process Models ◽  
Software Process Models

Collecting information about the performance of a software process is a necessary step for the assessment of the process quality. Oikos is an environment for the definition and the enactment of software process models. This paper presents the Oikos approach to history recording. We define the events that compose the histories and explain how the events to be monitored can be selected. Finally, we discuss the implementation of the recording mechanism.

Sign in / Sign up

Export Citation Format

Share Document