scholarly journals eXSRUP: Hybrid Software Development Model Integrating Extreme Programing, Scrum & Rational Unified Process

2015 ◽  
Vol 16 (2) ◽  
pp. 377
Author(s):  
Nidhi Sharma ◽  
Manoj Wadhwa
Keyword(s):  
Software Development ◽  
Large Scale ◽  
Management Practices ◽  
Poor Performance ◽  
Extreme Programming ◽  
Agile Development ◽  
Team Collaboration ◽  
Unified Process ◽  
Software Development Model ◽  
Engineering Practices

<p>Software industries are progressively adopting the agile development practices of customized models such as Extreme Programming (XP) or Scrum or Rational Unified Process (RUP). Scrum and Extreme Programming (XP) are frequently used agile models, whereas Rational Unified Process (RUP) is one popular classic plan driven software development methodology. Both agile and plan driven models have their own merits &amp; demerits such as XP has good engineering practices, team collaboration and on the other hand weak documentation, poor performance in medium &amp; large scale projects. Scrum is based on project management practices. RUP model has some limitations such as impractical for small and fast paced projects, tendency to be over budgeted, condemn rapid changes in requirements. This research paper based on proposes hybrid framework eXSRUP by combining strengths of Scrum, XP and RUP by suppressing their limitations to produce high quality software.</p>

Software Testing Under Agile, Scrum, and DevOps

2021 ◽  
pp. 114-131
Author(s):  
Kamalendu Pal ◽  
Bill Karakostas
Keyword(s):  
Software Development ◽  
Software Testing ◽  
Large Scale ◽  
Extreme Programming ◽  
Agile Development ◽  
Application Development ◽  
Software Application ◽  
Development Lifecycle ◽  
Software Development Lifecycle ◽  
Functional Teams

The adoption of agility at a large scale often requires the integration of agile and non-agile development practices into hybrid software development and delivery environment. This chapter addresses software testing related issues for Agile software application development. Currently, the umbrella of Agile methodologies (e.g. Scrum, Extreme Programming, Development and Operations – i.e., DevOps) have become the preferred tools for modern software development. These methodologies emphasize iterative and incremental development, where both the requirements and solutions evolve through the collaboration between cross-functional teams. The success of such practices relies on the quality result of each stage of development, obtained through rigorous testing. This chapter introduces the principles of software testing within the context of Scrum/DevOps based software development lifecycle.

Software Testing Under Agile, Scrum, and DevOps

2022 ◽  
pp. 1059-1076
Author(s):  
Kamalendu Pal ◽  
Bill Karakostas
Keyword(s):  
Software Development ◽  
Software Testing ◽  
Large Scale ◽  
Extreme Programming ◽  
Agile Development ◽  
Application Development ◽  
Software Application ◽  
Development Lifecycle ◽  
Software Development Lifecycle ◽  
Functional Teams

The adoption of agility at a large scale often requires the integration of agile and non-agile development practices into hybrid software development and delivery environment. This chapter addresses software testing related issues for Agile software application development. Currently, the umbrella of Agile methodologies (e.g. Scrum, Extreme Programming, Development and Operations – i.e., DevOps) have become the preferred tools for modern software development. These methodologies emphasize iterative and incremental development, where both the requirements and solutions evolve through the collaboration between cross-functional teams. The success of such practices relies on the quality result of each stage of development, obtained through rigorous testing. This chapter introduces the principles of software testing within the context of Scrum/DevOps based software development lifecycle.

scholarly journals Model Simulasi Rational Unified Process (RUP) Pada Pegembagan Perangkat Lunak

Repositor ◽  
2020 ◽  
Vol 2 (4) ◽  
pp. 485
Author(s):  
Tuti Tia ◽  
Ilyas Nuryasin ◽  
Maskur Maskur
Keyword(s):  
Software Development ◽  
Simulation Model ◽  
Large Scale ◽  
Simulation Models ◽  
Project Manager ◽  
Small Scale ◽  
Software Companies ◽  
Unified Process ◽  
Role Based ◽  
Engineering Projects

Abstract Pada pengembangan perangkat lunak terdapat beberapa jenis metodologi yang dapat digunakan, salah satunya adalah Rational Unified Process (RUP). RUP merupakan salah satu jenis proses pengembangan perangkat lunak yang digunakan di berbagai perusahaan perangkat lunak. Terdapat berbagai jenis proyek pada pengembangan perangkat lunak RUP, yaitu proyek yang dibangun dari awal dan memiliki skala kecil, proyek yang memiliki skala besar dan proyek pengembangan dari sistem yang sudah dibangun sebelumnya. Setiap jenis proyek memiliki kebutuhan yang berbeda, terutama dalam penggunaan setiap peran. Pada RUP terdapat beberapa peran penting yang tidak dapat dilakukan oleh satu individu karena harus bekerja pada saat bersamaan. Pada dasarnya tujuan dari RUP adalah dapat menghasilkan perangkat lunak yang berkualitas tinggi. Hal tersebut tidak dapat tercapai apabila penggunaan peran yang kurang tepat. Penelitian ini mengusulkan jumlah peran yang dibutuhkan untuk pengembangan perangkat lunak menggunakan RUP dengan membuat model simulasi. Tujuan dari pembuatan model simulasi ini adalah untuk mengetahui peran yang sesuai berdasarkan setiap jenis proyek. Hasil dari model simulasi yaitu berupa persentase dari setiap peran yang dibutuhkan, project manager memiliki persentase terbesar dibandingkan dengan peran lainnya, yaitu sebesar 76% pada proyek skala kecil dan 60% pada proyek skala besar.AbstractIn software development there are several types of methodologies that can be used, one of which is Rational Unified Process (RUP). RUP is of software development process used in various software companies. There are various types of projects in RUP software development, small scale project, large-scale projects and re-engineering projects. Each type of project has different needs, especially in the use of each role. In RUP there are several important roles that cannot be done by an individual because they have to work at the same time. Basically the purpose of the RUP is to be able to produce high quality software. This cannot be achieved if the inappropriate role is used. This study proposes the number of roles needed for software development using RUP by creating simulation models. The purpose of simulation model is to determine the appropriate role based on each type of project. The results of the simulation model are in the form of a percentage of each role needed, the project manager has the largest percentage compared to other roles, which is 76% in small-scale projects and 60% in large-scale projects.

scholarly journals SIMULATION MODEL FOR RATIONAL UNIFIED PROCESS (RUP) SOFTWARE DEVELOPMENT LIFE CYCLE

SISTEMASI ◽  
2019 ◽  
Vol 8 (1) ◽  
pp. 176
Author(s):  
Tuti Karen Tia
Keyword(s):  
Software Development ◽  
Simulation Model ◽  
Large Scale ◽  
Simulation Models ◽  
Small Scale ◽  
Software Companies ◽  
Development Life Cycle ◽  
Unified Process ◽  
Role Based ◽  
Engineering Projects

In software development there are several types of methodologies that can be used, one of which is Rational Unified Process (RUP). RUP is of software development process used in various software companies. There are various types of projects in RUP software development, small scale project, large-scale projects and re-engineering projects. Each type of project has different needs, especially in the use of each role. In RUP there are several important roles that cannot be done by an individual because they have to work at the same time. Basically the purpose of the RUP is to be able to produce high quality software. This cannot be achieved if the inappropriate role is used. This study proposes the number of roles needed for software development using RUP by creating simulation models. The purpose of simulation model is to determine the appropriate role based on each type of project. The results of the simulation model are in the form of a percentage of each role needed, the project manager has the largest percentage compared to other roles, which is 70% in small-scale projects and 65% in large-scale projects.

Web Engineering in Small Jordanian Web Development Firms

2011 ◽  
pp. 1696-1707
Author(s):  
Haroon Altarawneh ◽  
Asim El-Shiekh
Keyword(s):  
Organizational Development ◽  
Process Model ◽  
Small Firms ◽  
Ad Hoc ◽  
Extreme Programming ◽  
Agile Development ◽  
Web Development ◽  
Web Engineering ◽  
Engineering Best Practices ◽  
Engineering Practices

Small firms do not have the managerial experience, the financial resources and the methodological know-how to manage web-based applications projects the way large firms do. Many small firms are unaware of existing software process assessment models and standards. There’s often the assumption that assessments conformant to these models and standards can be expensive and time consuming, and therefore difficult to perform in small companies. This chapter proposes a theoretical model for small Web project development and its special features in the context small Web firms, which are capable of being “tailor able” to the particular stage of organizational development of small Web firms . The process model derived form Web engineering best practices, real case studies from Jordanian Web firms and agile development methodologies (extreme programming) . This chapter also contains results from tow surveys: a questionnaire to Web developers and interview with Web mangers in Jordan.The results reflect the Web industry situation in small Jordanian firms, and the major problems they face. Most of small Web projects in Jordan run over time and budget, due to the ad hoc development and the weakness of Web project management. The results showed that there is a weakness in applying Web engineering practices in small Jordanian Web development firms.

scholarly journals Coordinating Knowledge Work in Multiteam Programs

2018 ◽  
Vol 49 (6) ◽  
pp. 64-77 ◽  
Author(s):  
Torgeir Dingsøyr ◽  
Nils Brede Moe ◽  
Eva Amdahl Seim
Keyword(s):  
Software Development ◽  
Large Scale ◽  
Development Program ◽  
Knowledge Work ◽  
Agile Development ◽  
Development Projects ◽  
Development Programs ◽  
Knowledge Based ◽  
Over Time

Software development projects have undergone remarkable changes with the arrival of agile development approaches. Although intended for small, self-managing teams, these approaches are used today for large development programs. A major challenge of such programs is coordinating many teams. This case study describes the coordination of knowledge work in a large-scale agile development program with 12 teams. The findings highlight coordination modes based on feedback, the use of a number of mechanisms, and how coordination practices change over time. The findings can improve the outcomes of large knowledge-based development programs by tailoring coordination practices to needs over time.

scholarly journals Practices of Motivators in Adopting Agile Software Development at Large Scale Development Team from Management Perspective

Electronics ◽  
2021 ◽  
Vol 10 (19) ◽  
pp. 2341
Author(s):  
Rashid Ali Khan ◽  
Muhammad Faisal Abrar ◽  
Samad Baseer ◽  
Muhammad Faran Majeed ◽  
Muhammad Usman ◽  
...  
Keyword(s):  
Scale Development ◽  
Software Development ◽  
User Satisfaction ◽  
Large Scale ◽  
Low Cost ◽  
Rapid Development ◽  
Agile Software Development ◽  
Agile Development ◽  
Small Scale ◽  
Agile Software

Agile software development methodologies have become the most popular software development methods in the last few years. These methodologies facilitate rapid development. The low cost and prioritized user satisfaction make these methodologies more attractive. These methodologies were also intended for small scale developmental teams. Therefore, challenges were encountered when these methodologies were used in large-scale development teams. This study was based on the identification of factors which were discovered in our previous study. Some of the factors included “leadership strong commitment and team autonomy”, “cooperative organizational culture”, and “team competency—agile development expertise”. A total of 147 practices were identified in this study via a systematic literature review. These practices will help practitioners and project managers to adopt agile software methodologies and encourage them to the enhance them.

scholarly journals Learning from the Case Studies, How Global Software Development Process is executed in an Agile Method Environment

2010 ◽  
Vol 1 (2) ◽  
Author(s):  
Ridi Ferdiana ◽  
Lukito Edi Nugroho ◽  
Paulus Insap Santoso ◽  
Ahmad Ashari
Keyword(s):  
Software Development ◽  
Extreme Programming ◽  
Global Software Development ◽  
Agile Methods ◽  
Analysis Method ◽  
Agile Method ◽  
Development Lifecycle ◽  
Software Development Lifecycle ◽  
Unified Process

Abstrak. Belajar dari Studi Kasus, Bagaimana Proses Pengembangan Perangkat Lunak Global Dieksekusi Pada Lingkungan Metode Agile. Tantangan terbesar dalam Software Development Global (GSD) adalah efisiensi waktu untuk mengembangkan. GSD menyediakan panduan untuk menggunakan proses bersama dengan muka seperti proses metode analisis terpadu atau metode air terjun. Meskipun, itu memberikan manfaat melalui dokumentasi yang komprehensif dan kejelasan, ia memberikan menghambat organisasi yang ingin menggunakan GSD tetapi dalam terburu-buru. Metode Agile mengklaim efisien dan pendekatan yang efektif untuk pengembangan perangkat lunak. Makalah ini laporan tentang bagaimana organisasi menggabungkan proses GSD dengan metode tangkas seperti eXtreme Programming (XP), Scrum, Agile Unified Process (UP Agile), Pengembangan Fitur Driven (FDD), dan Microsoft Solusi Kerangka Agile (MSF Agile). Makalah ini menggunakan studi kasus untuk mendapatkan pengalaman organisasi dan menjelaskan praktek yang berguna untuk organisasi yang ingin menerapkan GSD dengan metode tangkas. Kata Kunci: Siklus Hidup Pengembangan Perangkat Lunak, Agile, GSD Abstract. The biggest challenge in Global Software Development (GSD) is the efficiency of time to develop. GSD provides a guidance to use the process along with up-front analysis method like unified process or waterfall method. Although, it gives a benefit through comprehensive documentation and its clearness, it gives inhibits the organization which wants use GSD but in a rush. Agile methods claim an efficient and the effective approach to software development. This paper reports on how organizations combine the GSD process with agile methods like eXtreme Programming (XP), Scrum, Agile Unified Process (Agile UP), Feature Driven Development (FDD), and Microsoft Solution Framework Agile (MSF Agile). The paper uses case study to get organization experiences and describe useful practices for the organization that want to implement GSD with an agile method. Keywords: Software Development Lifecycle, Agile, GSD

scholarly journals Requirement Engineering Challenges in Agile Software Development

2021 ◽  
Vol 2021 ◽  
pp. 1-18
Author(s):  
Aqsa Rasheed ◽  
Bushra Zafar ◽  
Tehmina Shehryar ◽  
Naila Aiman Aslam ◽  
Muhammad Sajid ◽  
...  
Keyword(s):  
Software Development ◽  
Large Scale ◽  
Development Process ◽  
Requirement Engineering ◽  
Agile Software Development ◽  
Vital Role ◽  
Agile Development ◽  
Comprehensive Overview ◽  
Development Life Cycle ◽  
Agile Software

Agile software development has large success rate due to its benefits and promising nature but natively where the size of the project is small. Requirement engineering (RE) is crucial as in each software development life cycle, “Requirements” play a vital role. Though agile provides values to customer’s business needs, changing requirement, and interaction, we also have to face impediments in agile, many of which are related to requirement challenges. This article aims to find out the challenges being faced during requirement engineering of agile projects. Many research studies have been conducted on requirement challenges which are somehow biased, no suggestions are given to improve the agile development process, and the research does not highlight large-scale agile development challenges. Hence, this article covers all the challenges discussed above and presents a comprehensive overview of agile models from requirement engineering perspective. The findings and results can be very helpful for software industry to improve development process as well as for researchers who want to work further in this direction.

Web Engineering in Small Jordanian Web Development Firms

2009 ◽  
pp. 130-141
Author(s):  
Haroon Altarawneh ◽  
Asim El-Sheikh
Keyword(s):  
Organizational Development ◽  
Process Model ◽  
Small Firms ◽  
Ad Hoc ◽  
Extreme Programming ◽  
Agile Development ◽  
Web Development ◽  
Web Engineering ◽  
Engineering Best Practices ◽  
Engineering Practices

Small firms do not have the managerial experience, the financial resources and the methodological know-how to manage web-based applications projects the way large firms do. Many small firms are unaware of existing software process assessment models and standards. There’s often the assumption that assessments conformant to these models and standards can be expensive and time consuming, and therefore difficult to perform in small companies. This chapter proposes a theoretical model for small Web project development and its special features in the context small Web firms, which are capable of being “tailor able” to the particular stage of organizational development of small Web firms . The process model derived form Web engineering best practices, real case studies from Jordanian Web firms and agile development methodologies (extreme programming) . This chapter also contains results tow surveys: a questionnaire to Web developers and interview with Web mangers in Jordan.The results reflect the Web industry situation in small Jordanian firms, and the major problems they face. Most of small Web projects in Jordan run over time and budget, due to the ad hoc development and the weakness of Web project management. The results showed that there is a weakness in applying Web engineering practices in small Jordanian Web development firms.

Sign in / Sign up

Export Citation Format

Share Document