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.

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.

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.

Software Process Models are Software Too

2002 ◽  
pp. 284-292
Author(s):  
Daniel Turk ◽  
Vijay Vaishnavi
Keyword(s):  
Process Modeling ◽  
Process Model ◽  
Software Process ◽  
Full Range ◽  
Process Models ◽  
Class Model ◽  
Organizational Goals ◽  
Software Process Modeling ◽  
Modeling Systems ◽  
Software Process Models

A software process model describes a set of partially-ordered sequences of activities that are carried out in order to accomplish certain goals. While numerous process modeling approaches have been proposed over the years, it seems that none of them have yet addressed the full range of concepts described in this definition. Most focus on activities and activity ordering; few, if any, focus on representing organizational goals and process improvement. Most provide concrete implementation approaches; few, if any, describe the general model(s) upon which these implementations are built. This paper suggests a new approach for developing software process modeling systems. If “Software Processes are Software Too,” as suggested by Osterweil (1987), then so are software process models, and hence there may be processes and models that are used in regular software development that may be useful in the process modeling domain as well. The paper focuses on the domain class model as an example of one type of model that might be produced if an approach such as the Unified Process were used in the process modeling domain. Such a process, and the set of models produced by it, if used, may be helpful in moving the process modeling field forward. While identifying the conceptual needs of process modeling systems, these models leave totally open the choice of how to formalize and implement actual solutions. A domain class model for process models is developed as an example of one of these models.

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.

Human Resource Related Problems in Agile and Traditional Software Project Process Models

2012 ◽  
pp. 1-13 ◽  
Author(s):  
Stefan Koch ◽  
Gerhard Turk
Keyword(s):  
Human Resource ◽  
Process Model ◽  
Software Process ◽  
Research Question ◽  
Process Models ◽  
Software Project ◽  
Main Research ◽  
Quality Aspects ◽  
Software Process Models ◽  
Project Participants

This paper explores the impacts associated with different software process models on the staff. The main research question addressed is whether any process model leads to a higher satisfaction of staff, and less human resource related problems, including staff turnover or increased stress levels. This issue is empirically investigated using a set of projects from 15 different software developing companies. Agile-oriented models are not necessarily limited to small projects, but both groups showed nearly identical distributions for team size and duration. Interestingly, rigid-type models tend to exhibit higher effort estimations, and lower correctness in these estimations. Also customer satisfaction is slightly lower. With regard to human resource issues, the differences are not major overall, but there are some noticeable exceptions. In general, satisfaction and acceptance are higher at lower stress and overtime levels for agile-type project participants, but, interestingly and contrary to theory, people wish for more responsibility. Agile-type projects also enjoy some advantages in information sharing and communication, and in some quality aspects. Rigid-type projects show considerable higher abilities to cope with absence of personnel.

Human Resource Related Problems in Agile and Traditional Software Project Process Models

2012 ◽  
pp. 304-316
Author(s):  
Stefan Koch ◽  
Gerhard Turk
Keyword(s):  
Human Resource ◽  
Process Model ◽  
Software Process ◽  
Research Question ◽  
Process Models ◽  
Software Project ◽  
Main Research ◽  
Quality Aspects ◽  
Software Process Models ◽  
Project Participants

This paper explores the impacts associated with different software process models on the staff. The main research question addressed is whether any process model leads to a higher satisfaction of staff, and less human resource related problems, including staff turnover or increased stress levels. This issue is empirically investigated using a set of projects from 15 different software developing companies. Agile-oriented models are not necessarily limited to small projects, but both groups showed nearly identical distributions for team size and duration. Interestingly, rigid-type models tend to exhibit higher effort estimations, and lower correctness in these estimations. Also customer satisfaction is slightly lower. With regard to human resource issues, the differences are not major overall, but there are some noticeable exceptions. In general, satisfaction and acceptance are higher at lower stress and overtime levels for agile-type project participants, but, interestingly and contrary to theory, people wish for more responsibility. Agile-type projects also enjoy some advantages in information sharing and communication, and in some quality aspects. Rigid-type projects show considerable higher abilities to cope with absence of personnel.

scholarly journals SOFTWARE PROCESS MODELS : A SURVEY

2020 ◽  
pp. 1-2
Author(s):  
Megha V. Polishwala ◽  
Pravin H. Bhathawala* ◽  
Viral Polishwala
Keyword(s):  
Software Engineering ◽  
Process Model ◽  
Software Process ◽  
Process Models ◽  
Software Product ◽  
Software Process Models ◽  
Paper Review ◽  
Systematic Development ◽  
Large Software

A eld of software engineering which is related to development of software product, needs systematic development for large software. This paper specify study of various process models from which systematic development of large software can be developed. Study of various paper and paper review of software process model is explained.

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.

Sign in / Sign up

Export Citation Format

Share Document