Software Process Paradigms and Crowdsourced Software Development

Crowdsourcing ◽  
2019 ◽  
pp. 1551-1568
Author(s):  
Nitasha Hasteer ◽  
Abhay Bansal ◽  
B. K. Murthy

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.

Author(s):  
Nitasha Hasteer ◽  
Abhay Bansal ◽  
B. K. Murthy

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.


2019 ◽  
pp. 703-720
Author(s):  
Nitasha Hasteer ◽  
Abhay Bansal ◽  
B. K. Murthy

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.


Author(s):  
Tony Polgar ◽  
Jana Polgar

Software development methodology refers to a standardised, documented methodology which has been used before on similar projects or one which is used habitually within an choice of software development method, and applying the right method for the job. From this perspective, the portlet development encounters new circumstances which affect the chosen method. A portal development manager must be aware of the technological properties and constraints, because there development and deployment processes. These issues are not well defined yet; there is no proven methodology for driving portal projects. This article provides discussion of practical approaches to the resolution of development issues and risks in portal environment. The discussed topics include implementation of portals in enterprise environment, portlet applications’ high availability, portlet disaster recovery, and cost of portlet deployment. An attempt is made to forecast future trends in portlet technology at the end of the article, as well as suggest the directions for the flexible selection of methodologies and managerial experience suited to the portal development.


Author(s):  
Barbara Dellen ◽  
Frank Maurer ◽  
Jürgen Münch ◽  
Martin Verlage

Representations of activities dealing with the development or maintenance of software are called software process models. Process models allow for communication, reasoning, guidance, improvement, and automation. Two approaches for modeling processes and instantiating and managing the process models, namely CoMo-Kit and MVP-E, are combined to build a more powerful one. CoMo-Kit is based on AI/KE technology; it is a support tool system for general complex design processes, and was not been developed specifically with software development processes in mind. MVP-E is a process-sensitive software engineering environment for modeling and analyzing software development processes, and guides software developers. Additionally, it provides services to establish and run measurement programmes in software organizations. Because both approaches were developed independently from one another, major integration efforts had to be made to combine both their advantages. This article concentrates on the resulting language concepts, and their operationalization necessary for building automated process support.


Author(s):  
Chitrak Vimalbhai Dave

Abstract: Software Process Models from its inception instill standardization and creates a generic culture of developing software for various IT industries. A great paradigm shift has been observed in terms of embracing Agile Development methodology as a viable development methodology in cross key business units. There is a buffet of agile methodologies comes under the umbrella of ASD, out of which Scrum got the highest popularity and acceptability index. Agile based software development is the need of immediate environment. There is an increasing demand for significant changes to software systems to meet ever-changing user requirements and specifications. As Agile is volatile, so effort estimation is challenging and still striving for perfection to decide size, effort, cost, duration and schedule of projects with minimum error. This cause sensitizes potential researchers all across the globe to start working on addressing the issue of inaccurate predication of efforts. The gap between estimated and actual effort is because of limited or no inclusion of various estimation factors like people and project related factors, inappropriate use of size metric and cost drivers, ignorance of testing effort, team member’s inability to understand user story size and complexity etc. This paper attempts to bridge the gap of estimated and actual effort by the use of soft computing techniques thus taking the research to advance frontier area in terms ofestimation. Keywords: Cost Estimation, Effort Estimation, Scrum, Machine Learning, Agile Software Development


2018 ◽  
Vol 7 (2.29) ◽  
pp. 325
Author(s):  
Ramzi A. Haraty ◽  
Gongzhu Hu

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.


Author(s):  
Laura C. Rodriguez ◽  
Manuel Mora ◽  
Miguel Vargas Martin ◽  
Rory O’Connor ◽  
Francisco Alvarez

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.


2015 ◽  
Vol 3 (2) ◽  
pp. 30-33
Author(s):  
Иванов ◽  
A. Ivanov ◽  
Иванова ◽  
O. Ivanova

The paper considers issues related to the choice of more cost-effective methodologies of developing software needed for implementation of ITprojects. Also described are the most conventional methodologies of IT-projects development, along with their main features, specifics and terms of use. Factors, allowing to opt for the “waterfall” software development methodology or for the agile development methodology are identified.


2011 ◽  
Vol 56 ◽  
pp. 138-145
Author(s):  
Stasys Peldžius ◽  
Saulius Ragaišis

Į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.


Sign in / Sign up

Export Citation Format

Share Document