Journal articles: 'Agile Software Model'

1

Aoyama, Mikio. "Agile software process model." Computer Standards & Interfaces 21, no. 2 (1999): 177. http://dx.doi.org/10.1016/s0920-5489(99)92220-1.

Full text

APA, Harvard, Vancouver, ISO, and other styles

2

Masood Butt, Saad, Shahid Masood Butt, Azura Onn, Nadra Tabassam, and Mazlina Abdul Majid. "Usability Evaluation Techniques for Agile Software Model." Journal of Software 10, no. 1 (2015): 32–41. http://dx.doi.org/10.17706/jsw.10.1.32-41.

Full text

APA, Harvard, Vancouver, ISO, and other styles

3

Jain, Parita, Arun Sharma, and Laxmi Ahuja. "Software Maintainability Estimation in Agile Software Development." International Journal of Open Source Software and Processes 9, no. 4 (2018): 65–78. http://dx.doi.org/10.4018/ijossp.2018100104.

Full text

Abstract:

Agile methodologies have gained wide acceptance for developing high-quality products with a quick and flexible approach. However, until now, the quality of the agile process has not been validated quantitatively. Quality being important for the software system, there is a need for measurement. Estimating different quality factors will lead to a quality product. Also, agile software development does not provide any precise models to evaluate maintainability. Therefore, there is a need for an algorithmic approach that can serve as the basis for estimation of maintainability. The article proposes an adaptive neuro-fuzzy inference system (ANFIS) model for estimating agile maintainability. Maintainability is one of the prominent quality factors in the case of agile development. The proposed model has been verified and found to be effective for assessing the maintainability of agile software.

APA, Harvard, Vancouver, ISO, and other styles

4

Rawat, Shubham, Nupur Goyal, and Mangey Ram. "Software reliability growth modeling for agile software development." International Journal of Applied Mathematics and Computer Science 27, no. 4 (2017): 777–83. http://dx.doi.org/10.1515/amcs-2017-0054.

Full text

Abstract:

AbstractThe frequent incremental release of software in agile development impacts the overall reliability of the product. In this paper, we propose a generic software reliability model for the agile process, taking permanent and transient faults into consideration. The proposed model is implemented using the NHPP (non-homogenous Poisson process) and the Musa model. The comparison of the two implementations yields an effective, empirical and reliable model for agile software development.

APA, Harvard, Vancouver, ISO, and other styles

5

Zeba-Shahzeab, Z.I.Shaheen Sajjade. "Agile Process Model for Software Development." Journal of Advancement in Software Engineering and Testing 3, no. 3 (2020): 1–9. https://doi.org/10.5281/zenodo.4281979.

Full text

Abstract:

Software development is that the process of observing, requiring, designing, programming, documenting, testing and bug fixing involved in creating and preserving applications, maintaining frameworks or other software components. Software Development Life Cycle (SDLC) consists of an in depth plan which needs the way to develop, maintain and replace specific software. Several software development models followed by various organizations are referred to as Waterfall Model, V-Shaped Model, and Incremental Model. However Agile is adopted to be a winning choice for software development across all industries. The features like possibility of modifications as per requirements at any stage of software development and importance given to the business values delivered instead of confirmation to project plan makes Agile unique from traditional software development models. Industries are changing their software development choice as agile methodology.  It shows how the Agile is becoming an attractive choice for software development altogether industries across the world.

APA, Harvard, Vancouver, ISO, and other styles

6

Suresh, Kannan Duraisamy, Bass Bryce, and Mukkavilli Sai. "Embedding Performance Testing in Agile Software Model." International Journal of Software Engineering & Applications (IJSEA) 12, no. 6 (2021): 1–11. https://doi.org/10.5281/zenodo.5771628.

Full text

Abstract:

In the last couple of decades, the software development process has evolved drastically, starting from Big Bang to Waterfall to Agile. The primary driver for the evolution of the software was the “Speed of Delivery” of the Software Product which has significantly accelerated from months to less than weeks and days. For IT (Information Technology) Organizations to be successful, they inevitably need a strong technology presence to roll out new software and features as quickly as possible to their customer base. The current user generation tends to use technology to maximum potential and is always striving to keep up with the new trends. The main subject is for the organizations to be ready with their Speed of Delivery strategy adapting to all technology modernization initiatives like CICD (Continuous Integration and Continuous Deployment), Agile, DevOps, and Cloud so that there are negligible customer friction and no risks to their Market shares,. The aim of this paper is to compare the performance testing in every stage of the agile model to the traditional end testing. The results of the corresponding testing phases are presented in this paper.

APA, Harvard, Vancouver, ISO, and other styles

7

Mahmut, Ünver. "Software Process Models and Agile Method Applicability in Industry." International Journal of Trend in Scientific Research and Development 3, no. 1 (2018): 1285–89. https://doi.org/10.31142/ijtsrd20238.

Full text

Abstract:

Software process models have been developed since 1968. When software process models are implemented in the software sector, it is considered that more suitable projects will be developed in terms of customer satisfaction and cost. In this study, the use of Agile, which is a frequently used software process model, in industry is investigated. In the research, software process models are explained and industrial sectors using Agile method are examined. It has been observed that customer satisfaction, time saving, and project success increase in sectors where Agile method is applied. Likewise, the project has also increased efficiency and competence. Mahmut Ã&oelig;nver "Software Process Models and Agile Method Applicability in Industry" Published in International Journal of Trend in Scientific Research and Development (ijtsrd), ISSN: 2456-6470, Volume-3 | Issue-1 , December 2018, URL: https://www.ijtsrd.com/papers/ijtsrd20238.pdf

APA, Harvard, Vancouver, ISO, and other styles

8

Rathore, Manvender, and Deepa Jose. "Software Upgradation Model Based on Agile Methodology." Oriental journal of computer science and technology 10, no. 2 (2017): 352–58. http://dx.doi.org/10.13005/ojcst/10.02.14.

Full text

Abstract:

Agile software development work on twelve principle for software development which implies requirements and solutions evolved through the combined teamwork of disciplined and interdisciplinary teams. The objective of this paper is to connect agile methodology with Version Control System for more efficient and effective utilization of resources. In this proposed model based on agile methodology, the Version Control System plays a vital role to make work done faster as compared to SCRUM. This paper compares various existing agile methodologies. The efficiency of the proposed model is proved through comparative analysis with existing agile methods and using ANOVA mathematical model. Bitbucket as Version Control System is used as web based hosting service and the proposed model is compared by maintaining similar sprints in SCRUM and VSprint model. VCS and previous SRS documents are the important components of this proposed model which helps in increasing the work speed at different phases of software development which the existing models does not consider.

APA, Harvard, Vancouver, ISO, and other styles

9

Gürkan, Alpaslan, and Kalıpsız Oya. "Model Driven Web Application Development with Agile Practices." International Journal of Software Engineering & Applications (IJSEA) 7, no. 5 (2021): 1–11. https://doi.org/10.5281/zenodo.5513486.

Full text

Abstract:

Model driven development is an effective method due to its benefits such as code transformation, increasing productivity and reducing human based error possibilities. Meanwhile, agile software development increases the software flexibility and customer satisfaction by using iterative method. Can these two development approaches be combined to develop web applications efficiently? What are the challenges and what are the benefits of this approach? In this paper, we answer these two crucial problems; combining model driven development and agile software development results in not only fast development and easiness of the user interface design but also efficient job tracking. We also defined an agile model based approach for web applications whose implementation study has been carried out to support the answers we gave these two crucial problems.

APA, Harvard, Vancouver, ISO, and other styles

10

Russo, Daniel. "The Agile Success Model." ACM Transactions on Software Engineering and Methodology 30, no. 4 (2021): 1–46. http://dx.doi.org/10.1145/3464938.

Full text

Abstract:

Organizations are increasingly adopting Agile frameworks for their internal software development. Cost reduction, rapid deployment, requirements and mental model alignment are typical reasons for an Agile transformation. This article presents an in-depth field study of a large-scale Agile transformation in a mission-critical environment, where stakeholders’ commitment was a critical success factor. The goal of such a transformation was to implement mission-oriented features, reducing costs and time to operate in critical scenarios. The project lasted several years and involved over 40 professionals. We report how a hierarchical and plan-driven organization exploited Agile methods to develop a Command & Control (C2) system. Accordingly, we first abstract our experience, inducing a success model of general use for other comparable organizations by performing a post-mortem study. The goal of the inductive research process was to identify critical success factors and their relations. Finally, we validated and generalized our model through Partial Least Squares - Structural Equation Modelling, surveying 200 software engineers involved in similar projects. We conclude the article with data-driven recommendations concerning the management of Agile projects.

APA, Harvard, Vancouver, ISO, and other styles

11

Sandeep, Kaur*. "COMPARATIVE ANALYSIS OF SOFTWARE DEVELOPMENT MODELS." INTERNATIONAL JOURNAL OF ENGINEERING SCIENCES & RESEARCH TECHNOLOGY 6, no. 10 (2017): 611–17. https://doi.org/10.5281/zenodo.1036644.

Full text

Abstract:

No geek is unfamiliar with the concept of software development life cycle (SDLC). This research deals with the various SDLC models covering waterfall, spiral, and iterative, agile, V-shaped, prototype model. In the modern era, all the software systems are fallible as they can’t stand with certainty. So, it is tried to compare all aspects of the various models, their pros and cons so that it could be easy to choose a particular model at the time of need

APA, Harvard, Vancouver, ISO, and other styles

12

van Driel, Willem Dirk, Jan Willem Bikker, Matthijs Tijink, and Alessandro Di Bucchianico. "Software Reliability for Agile Testing." Mathematics 8, no. 5 (2020): 791. http://dx.doi.org/10.3390/math8050791.

Full text

Abstract:

It is known that quantitative measures for the reliability of software systems can be derived from software reliability models, and, as such, support the product development process. Over the past four decades, research activities in this area have been performed. As a result, many software reliability models have been proposed. It was shown that, once these models reach a certain level of convergence, it can enable the developer to release the software and stop software testing accordingly. Criteria to determine the optimal testing time include the number of remaining errors, failure rate, reliability requirements, or total system cost. In this paper, we present our results in predicting the reliability of software for agile testing environments. We seek to model this way of working by extending the Jelinski–Moranda model to a “stack” of feature-specific models, assuming that the bugs are labeled with the features they belong to. In order to demonstrate the extended model, two use cases are presented. The questions to be answered in these two cases are: how many software bugs remain in the software and should one decide to stop testing the software?

APA, Harvard, Vancouver, ISO, and other styles

13

Bose, Bijoya, Nishat Tasnim Khan, Sumaiya Ashreen, Faishal Ahmed Shuvo, Md. Mazid-Ul-Haque, and Abhijit Bhowmik. "Hybrid Scrum-XP: A Proposed Model based on Effectiveness of Agile Model on Varieties of Software Companies in Bangladesh." AIUB Journal of Science and Engineering (AJSE) 22, no. 1 (2023): 35–44. http://dx.doi.org/10.53799/ajse.v22i1.353.

Full text

Abstract:

The Agile Methodology is a term which refers to a method of software development that is incremental and iterative in nature and is used to manage and incorporate constantly changing needs. This entails decomposing the entire development process cycle into a series of tasks. The process is further divided into a number of sub-tasks, each function is independently. The Agile Development technique, which is a popular and growth-oriented strategy, provides not only speedy project delivery, but also software responsiveness, which leads to total corporate growth and agility. The organization's project management capabilities and performance are improved through the adoption of Agile practices. In their business, the companies employ Agile methods. As a result, the goal of this study is to see how effective agile approaches are in Bangladeshi software organizations. A survey of established software companies in Bangladesh is being conducted to accomplish the objective. The Scrum and XP agile technique is the most widely used according to the findings. It is proposed that Scrum and the XP model be combined to achieve maximum effectiveness and overcome their respective limits.

APA, Harvard, Vancouver, ISO, and other styles

14

Duraisamy, Suresh Kannan, Bryce Bass, and Sai Mukkavilli. "Embedding Performance Testing in Agile Software Model." International Journal of Software Engineering & Applications 12, no. 06 (2021): 1–11. http://dx.doi.org/10.5121/ijsea.2021.12601.

Full text

Abstract:

In the last couple of decades, the software development process has evolved drastically, starting from Big Bang to Waterfall to Agile. The primary driver for the evolution of the software was the “Speed of Delivery” of the Software Product which has significantly accelerated from months to less than weeks and days. For IT (Information Technology) Organizations to be successful, they inevitably need a strong technology presence to roll out new software and features as quickly as possible to their customer base. The current user generation tends to use technology to maximum potential and is always striving to keep up with the new trends. The main subject is for the organizations to be ready with their Speed of Delivery strategy adapting to all technology modernization initiatives like CICD (Continuous Integration and Continuous Deployment), Agile, DevOps, and Cloud so that there are negligible customer friction and no risks to their Market shares,. The aim of this paper is to compare the performance testing in every stage of the agile model to the traditional end testing. The results of the corresponding testing phases are presented in this paper.

APA, Harvard, Vancouver, ISO, and other styles

15

Afshari, Mahnaz, and Taghi Javdani Gandomani. "Quality of agile adoption in global software development: An assessment model." Indonesian Journal of Electrical Engineering and Computer Science 21, no. 1 (2021): 367–76. https://doi.org/10.11591/ijeecs.v21.i1.pp367-376.

Full text

Abstract:

Over the last decade, software development has faced two approaches to Agile and global software development (GSD). While Agile development is focused on the reduction of software development overhead by reducing the distance between individuals and face-to-face communications, in global software development, the use of human power in various sites is considered. Despite their inherent differences, the combination of these two approaches has received considerable attention from researchers and software professionals. Meanwhile, the lack of a model or tool capable of assessing teams' adaptation to Agile methods seems to be a research gap. The current research aims to solve this challenge by proposing a model in this regard. Considering the major related factors and weighting them, this model allows software teams to assess the rate of their adaptation and success in global software development

APA, Harvard, Vancouver, ISO, and other styles

16

Huss, Moe, Daniel R. Herber, and John M. Borky. "Comparing Measured Agile Software Development Metrics Using an Agile Model-Based Software Engineering Approach versus Scrum Only." Software 2, no. 3 (2023): 310–31. http://dx.doi.org/10.3390/software2030015.

Full text

Abstract:

This study compares the reliability of estimation, productivity, and defect rate metrics for sprints driven by a specific instance of the agile approach (i.e., scrum) and an agile model-Bbased software engineering (MBSE) approach called the integrated Scrum Model-Based System Architecture Process (sMBSAP) when developing a software system. The quasi-experimental study conducted ten sprints using each approach. The approaches were then evaluated based on their effectiveness in helping the product development team estimate the backlog items that they could build during a time-boxed sprint and deliver more product backlog items (PBI) with fewer defects. The commitment reliability (CR) was calculated to compare the reliability of estimation with a measured average scrum-driven value of 0.81 versus a statistically different average sMBSAP-driven value of 0.94. Similarly, the average sprint velocity (SV) for the scrum-driven sprints was 26.8 versus 31.8 for the MBSAP-driven sprints. The average defect density (DD) for the scrum-driven sprints was 0.91, while that of the sMBSAP-driven sprints was 0.63. The average defect leakage (DL) for the scrum-driven sprints was 0.20, while that of the sMBSAP-driven sprints was 0.15. The t-test analysis concluded that the sMBSAP-driven sprints were associated with a statistically significant larger mean CR, SV, DD, and DL than that of the scrum-driven sprints. The overall results demonstrate formal quantitative benefits of an agile MBSE approach compared to an agile alone, thereby strengthening the case for considering agile MBSE methods within the software development community. Future work might include comparing agile and agile MBSE methods using alternative research designs and further software development objectives, techniques, and metrics.

APA, Harvard, Vancouver, ISO, and other styles

17

Lamsellak, Hajar, and Mohammed Ghaouth Belkasmi. "Global software development agile planning model: challenges and current trends." Indonesian Journal of Electrical Engineering and Computer Science 32, no. 3 (2023): 1774. http://dx.doi.org/10.11591/ijeecs.v32.i3.pp1774-1784.

Full text

Abstract:

Agile planning offers a number of benefits that make the customers active members of the team throughout the project. In global software development (GSD), geographic separations demand special attention to harness these benefits. Our paper conducted a systematic mapping study (SMS) to analyze GSD-specific agile planning challenges followed by a systematic literature review (SLR) for efficient solutions. These studies led to a model for agile planning in global software development supporting GSD practitioners during this process.

APA, Harvard, Vancouver, ISO, and other styles

18

Jain, Parita, Arun Sharma, and Laxmi Ahuja. "A Customized Quality Model for Software Quality Assurance in Agile Environment." International Journal of Information Technology and Web Engineering 14, no. 3 (2019): 64–77. http://dx.doi.org/10.4018/ijitwe.2019070104.

Full text

Abstract:

The agile approach grew dramatically over traditional approaches. The methodology focuses more on rapid development, quick evaluation, quantifiable progress and continuous delivery satisfying the customer desire. In view of this, there is a need for measurement of the agile development process. In this respect, the present research work investigates the inter-relationships and inter-dependencies between the identified quality factors (QF), thereby outlining which of these QF have high driving power and dependence power, working indirectly towards the success of agile development process. This paper proposes a new agile quality model, utilizing an interpretive structural modeling (ISM) approach and the identified factors are classifies using Matriced' Impacts Croise's Multiplication Applique´e a UN Classement (MICMAC) approach. The research findings can significantly impact agile development process by understanding how these QF related to each other and how they can be adopted.

APA, Harvard, Vancouver, ISO, and other styles

19

Zhang, Fuye, Nur Atiqah Sia Abdullah, and Marshima Mohd Rosli. "Analysis of Critical Success Factors of Agile Software Projects based on the Fuzzy Delphi Method." Engineering, Technology & Applied Science Research 15, no. 1 (2025): 19424–33. https://doi.org/10.48084/etasr.9151.

Full text

Abstract:

Agile software development initiatives have gained widespread recognition both domestically and internationally, particularly in the Chinese software industry. However, traditional enterprises often face challenges, such as inadequate project management and lower success rates, which can be attributed to a limited understanding of agile methodologies and effective implementation of agile practices. To address these challenges and identify the Critical Success Factors (CSFs) in agile software projects, an extensive literature review was conducted. As a result, a CSFs model for agile projects in China was constructed. The aim of this study is to evaluate the CSFs model using the Fuzzy Delphi Method (FDM). The research involved 30 authoritative experts from the Chinese agile software development industry and academia, each with more than 10 years of relevant industry knowledge and experience. The FDM was applied to collect data through questionnaires and verify theoretical success factors and dimensions in three rounds of the survey. Finally, a total of 28 factors were analyzed and ranked to develop an optimized CSFs model that has a significant impact on agile software development in China. The research findings provide a feasible set of CSFs for the effective implementation of agile software projects in China. This CSFs model also offers valuable insights for the broader adoption of agile practices in China, with the potential to greatly improve the success rate of agile software development and implementation.

APA, Harvard, Vancouver, ISO, and other styles

20

B, Prakash, and Viswanathan V. "Distributed Cat Modeling Based Agile Framework for Software Development." International Journal of Engineering Education 2, no. 1 (2020): 20–32. http://dx.doi.org/10.14710/ijee.2.1.20-32.

Full text

Abstract:

Software development is a hectic process that requires keen understanding and effective model such that the developed software inherits good quality, reliability, and achieves customer satisfaction towards achieving the goals effectively. The effective operation of the software is enabled by modifying the operating modules of the software through a model, like agile. In this paper, the catastrophic and distributed computing models are integrated into the software development step. The proposed model is termed as Distributed Cat model that is developed with the aim to handle the risk factors engaged in various developing stages of the agile model. The risk factors that affect the communication, planning, release, design, coding and testing modules of the agile modules are deeply learned and executed such that the risk factors are tackled by various modules present in the proposed Distributed Cat model. The effectiveness of the proposed model is analyzed based on the performance metrics, such as Index of Integration (IoI) and Usability Goals Achievement Metric (UGAM), for which five products including the hotel management system, Customer relationship Management system (CRM), Rainfall prediction system, Temperature monitoring system, and meta-search system, are employed and analyzed. The analysis is progressed using the parameters, like mean difference, variance, standard devaiation, correlation. The analysis proves that the proposed model offered a great deviation after applying the proposed model contributing a high degree of performance in software development.

APA, Harvard, Vancouver, ISO, and other styles

21

Wijesinghe, Uthpala, Vidara Mapitiyage, Chathurya Wickramarathne, Chamoda Wickramage, Krishantha Wisenthige, and Chathuni Aluthwala. "Does management support drive sustained agile usage? a serial mediation model and cIPMA perspective." PLOS ONE 20, no. 2 (2025): e0316538. https://doi.org/10.1371/journal.pone.0316538.

Full text

Abstract:

Agile software development is immensely popular in the industry, but most teams struggle to sustain its use. Human factors like management support, agile training, agile mindset, and team resilience are often neglected, hindering long-term success. However, research has not explored their underlying mechanisms in depth. Therefore, this study examines if management support impacts the sustained usage of agile methodologies within software development teams. It subsequently investigates the individual and serial mediating effects of agile training, the agile mindset, and team resilience on this relationship. Additionally, it compares the importance and performance of management support, agile training, the agile mindset, and team resilience in infusing agile practices. Finally, it determines these antecedents’ necessity for the enduring success of agile application. Data collected from 391 agile software development professionals using a structured questionnaire. Partial-least-squares structural equation modelling, importance-performance map analysis and necessary condition analysis were used to investigate relationships. The findings underscore the pivotal role of management support in infusing agile practices. Agile training, mindset, and team resilience emerge as critical mediators, with a strong serial mediation effect. While management support is paramount, its practical implementation falls short within teams. All four antecedents are found to be necessary for optimal agile sustainment. Thus, this study significantly advances theoretical understanding by introducing a serial mediation model that elucidates their mechanisms in impacting agile infusion. It extends prior organisational-level findings to the team-level. The study’s quantitative verification of qualitative findings strengthens their generalisability to a broader spectrum of teams. It pioneers in expounding the constructs’ relative importance, performance and necessity, to offer actionable insights for agile practitioners. Finally, it provides methodological guidance to apply importance performance map analysis and necessary condition analysis in agile software development research.

APA, Harvard, Vancouver, ISO, and other styles

22

Silas, Faki Agebee, Musa Yusuf, and Anah Hassan Bijik. "Hybridization of Class Responsibility Collaborators Model (HCRCM) with Function Point to enhance Project Estimation Cost in Agile Software Development." Circulation in Computer Science 2, no. 6 (2017): 20–24. http://dx.doi.org/10.22632/ccs-2017-252-32.

Full text

Abstract:

Estimating software cost in an agile system in terms of effort is very challenging. This is because the traditional models of software cost estimation do not completely fit in the agile development process. This paper presents a methodology to enhance the cost of project estimation in agile development. The hybridization adopts Class Responsibility Collaborators models with function point thereby boosting the agile software development estimation process. The study found out that adopting the Hybridized Class Responsibility Collaborator with function point has great improvement on cost estimation in agile software development.

APA, Harvard, Vancouver, ISO, and other styles

23

Norzariyah, Yahya, and Sarah Maidin Siti. "Hybrid agile development phases: the practice in software projects as performed by software engineering team." Hybrid agile development phases: the practice in software projects as performed by software engineering team 29, no. 3 (2023): 1738–49. https://doi.org/10.5281/zenodo.7797397.

Full text

Abstract:

The combination of scrum and waterfall is one of the software engineering teams that preferred hybrid agile models. The purpose of combining the two models is to leverage the advantages of each also to tailor the hybrid agile model to the needs of the project. However, to what extent are the phases, stages, and features of scrum and waterfall implemented in a software project remains unclear. Additionally, which phase will employ scrum, and when will waterfall be deemed optimal is also the arising question. Thisresearch adopted a qualitative study, and interviews are used as a data collection instrument. The interview is conducted based on an interview protocol, and thematic analysis is utilized to extract the themes from the interviews. This study investigates how the scrum and waterfall models are utilized in a software project, and three themes were identified in answering the research question. The findings indicate five development phases in a hybrid agile project and that waterfall is the preferable model in planning, while development is on scrum, and project testing and deployment could be either waterfall or scrum.

APA, Harvard, Vancouver, ISO, and other styles

24

Hashmi, Amber Sarwar, Yaser Hafeez, Muhammad Jamal, Sadia Ali, and Naila Iqbal. "Role of Situational Agile Distributed Model to Support Modern Software Development Teams." July 2019 38, no. 3 (2019): 655–66. http://dx.doi.org/10.22581/muet1982.1903.11.

Full text

Abstract:

ADSD (Agile Distributed Software Development) is a growing trend for software development organizations to develop quality software with limited cost and time. However, it gives rise to additional situational challenges. Situational variations result in unstable agile architecture which gets highly affected. Although the present literature focuses on agile architecture but effect of situational variation on the agile architecture still needs consideration. One possible solution is development of conceptual model and incorporation of multiple situational factors. This research study aims to identify the most relevant situations and propose situational ADSD approach for the development of situation-based software architecture framework for agile distributed projects. The study focuses on agile methods, rendering identified situational variations. The approach is developed through analyzing data from literature and their associated work documents. Comprehensive survey helps to bridge the gaps from conceptual to architecture model. The experimental results are acquired through both practical and statistical analysis. The results support Conway’s law, e.g. correlation that maps architecture with the communication and coordination needs. Correlation results show that architecture has major contribution in ADSD and validate the relationship among conceptual model and architecture model. The results also suggest that stable architecture in ADSD can positively affect the product.

APA, Harvard, Vancouver, ISO, and other styles

25

Kukreja, Vinay, Sachin Ahuja, and Amitoj Singh. "Measurement and structural model of agile software development critical success factors." International Journal of Engineering & Technology 7, no. 3 (2018): 1236. http://dx.doi.org/10.14419/ijet.v7i3.12776.

Full text

Abstract:

Purpose: Agile methodologies have emerged as an innovative and successful business changing way for software development companies since the success rate for completing the software projects on time and budget is better than conventional methodologies. This study proposes a theoretical framework of success factors for agile software development and validates the proposed framework using structural equation modeling.Design Methodology: A survey based random sampling was performed for data collection from 201 respondents identified from the pool of agile practitioners in software companies. Structural Equation Modeling performed on the collected data to validate measurement model as well as the structural model.Findings: The theoretical model was confirmed with modifications and the results showed that required level of fitness indexes have been achieved for the measurement model and structural model. The validation of the factors has also been done.Originality/Value: This study will guide the agile practitioners, academicians and project managers to focus more on the particular success factors which have high weight towards project success.

APA, Harvard, Vancouver, ISO, and other styles

26

Kumar Nath, Udit, Satyasundara Mahapatra, Prasant Kumar Pattnaik, and Alok Kumar Jagadev. "Issues of lean-agile software development environment." International Journal of Engineering & Technology 7, no. 3.3 (2018): 432. http://dx.doi.org/10.14419/ijet.v7i2.33.14204.

Full text

Abstract:

The popular waterfall model is widely accepted approach for project management paradigm; however lean based agile model is the recent revolution to reduce work in progress items and makes transformation to better process by identifying and eliminating non-value-add activities and increase productivity with quality of deliverables. This paper includes the issues that involved in lean- agile process.

APA, Harvard, Vancouver, ISO, and other styles

27

Khalid, Ayesha, Shariq Aziz Butt, Tauseef Jamal, and Saikat Gochhait. "Agile Scrum Issues at Large-Scale Distributed Projects." International Journal of Software Innovation 8, no. 2 (2020): 85–94. http://dx.doi.org/10.4018/ijsi.2020040106.

Full text

Abstract:

The agile model is a very vast and popular model in use in the software industry currently. It changes the way software is developed. It was introduced in 2001 to overcome deficiencies of software development in a workshop arranged by researchers and practitioners who were involved with the agile concept. They introduced the complete agile manifesto. The agile model has main components that make it more viable for use in well-organized software development. One of these is scrum methodology. The reason for the agile-scrum popularity is its use for small-scale projects, making small teams and allows change requests at any stage of a project from the client. It works for client satisfaction. Instead of so much popularity and distinctive features, agile-scrum also has some limitations when used for large scale projects development that makes it less efficient for development. This article discusses the agile-scrum methodology and its limitations when using for large-scale project organization.

APA, Harvard, Vancouver, ISO, and other styles

28

Janus, André. "Towards a common agile software development model (ASDM)." ACM SIGSOFT Software Engineering Notes 37, no. 4 (2012): 1–8. http://dx.doi.org/10.1145/2237796.2237803.

Full text

APA, Harvard, Vancouver, ISO, and other styles

29

Sanpote, Davit, and Worrakit Sanpote. "Software Engineering Learning Model Framework using Agile Techniques." International Journal of Engineering Trends and Technology 71, no. 12 (2023): 90–97. http://dx.doi.org/10.14445/22315381/ijett-v71i12p210.

Full text

APA, Harvard, Vancouver, ISO, and other styles

30

Fotariya, Mr Anuj, and Mr Omprakash Mandge. "Systematic Review of Agile Methodologies for Software Development." International Journal for Research in Applied Science and Engineering Technology 10, no. 6 (2022): 1771–74. http://dx.doi.org/10.22214/ijraset.2022.44143.

Full text

Abstract:

Abstract: With the increase in complexity and innovation in IT products and services, developing them, that to by the shared efforts of team members brings in the need of some standardized development model or approach. Due to several advantages of agile methodologies over the traditional waterfall based models, it is the preferred choice. Many a times, a single agile method is also not enough to meet the current scenario of product development. We therefore propose a Competitor Driven Development (CDD) model, a hybrid agile process model for IT product development by abstracting practices from Extreme Programming (XP) and Feature Driven Reuse Development (FDRD) agile methods. This model is based on self-realizing requirements generation for Product development by keeping an eye watch on competitor’s upcoming launch of the product and market response to it rather than customer explicitly specifying the requirements. This development model can be generally used by the organizations who intend to develop IT product for mass targeted customers rather than an individual or an organization.

APA, Harvard, Vancouver, ISO, and other styles

31

Afshari, Mahnaz, and Taghi Javdani Gandomani. "Quality of agile adoption in global software development: An assessment model." Indonesian Journal of Electrical Engineering and Computer Science 21, no. 1 (2021): 367. http://dx.doi.org/10.11591/ijeecs.v21.i1.pp367-376.

Full text

Abstract:

Over the last decade, software development has faced two approaches to Agile and global software development (GSD). While Agile development is focused on the reduction of software development overhead by reducing the distance between individuals and face-to-face communications, in global software development, the use of human power in various sites is considered. Despite their inherent differences, the combination of these two approaches has received considerable attention from researchers and software professionals. Meanwhile, the lack of a model or tool capable of assessing teams' adaptation to Agile methods seems to be a research gap. The current research aims to solve this challenge by proposing a model in this regard. Considering the major related factors and weighting them, this model allows software teams to assess the rate of their adaptation and success in global software development.

APA, Harvard, Vancouver, ISO, and other styles

32

Santosh, Kumar Vududala. "The Impact of Agile Methodology in Modern Software Development." International Journal of Innovative Research in Engineering & Multidisciplinary Physical Sciences 7, no. 1 (2019): 1–5. https://doi.org/10.5281/zenodo.14881067.

Full text

Abstract:

In today’s world software development is a complex process which requires requirements gathering, analysis, development, testing, delivery and maintenance.  Over the last few years, there are different Software development methodologies in the IT industry like Waterfall, Incremental, Prototype, V-Model, Agile etc. In this competition world, companies do not need aSDLC model which consumes a lot of time and effort to develop a software. More time taken to develop the software will lead increased cost, competition and delayed time to market.Most of the projects have failed because they arenot able to respond to the changing user needs. This has encouraged the software engineers to propose flexible and effective techniques that help to develop quality software. The methodology impacts software development because it results in quality products. To mitigate these problems Agile methodology is a modern approach in software development. Agile methodology aims to meet the customer requirements with the deployment changes in the rapidly developing environments.  Agile principles and innovative setup rules and protocols helps developers to overcome the challenges faced in the traditional waterfall model.The benefits of Agile include flexibility to change the requirements, enhanced product quality, cost effective, customer interaction, and continuous testing.This paper explains various ways in which agile methodology impacts software development. Italso describes benefits and limitations of agile methodology. This paper helpssoftware development companies to adopt thismethodology in order to develop software that meet their changing needs.

APA, Harvard, Vancouver, ISO, and other styles

33

Wang, Hua, Xian Yu Li, Xue Ning Wang, and Li Zhang. "The Practice and Analysis of Software Agile Development of Information System." Applied Mechanics and Materials 380-384 (August 2013): 2125–28. http://dx.doi.org/10.4028/www.scientific.net/amm.380-384.2125.

Full text

Abstract:

Based upon the synopsis of software agile development, this paper describes the basic contents of agile development, and then puts forward Revised XP Model outline development flow and phase product. Meanwhile, development policies and further works are presented. This will benefit the software agile development of information system.

APA, Harvard, Vancouver, ISO, and other styles

34

Sunda, Neelam, and Ripu Ranjan Sinha. "A Review: Effort Estimation Model for Scrum Projects using Supervised Learning." International Journal on Recent and Innovation Trends in Computing and Communication 11, no. 11s (2023): 302–8. http://dx.doi.org/10.17762/ijritcc.v11i11s.8102.

Full text

Abstract:

Effort estimation practice in Agile is a critical component of the methodology to help cross-functional teams to plan and prioritize their work. Agile approaches have emerged in recent years as a more adaptable means of creating software projects because they consistently produce a workable end product that is developed progressively, preventing projects from failing entirely. Agile software development enables teams to collaborate directly with clients and swiftly adjust to changing requirements. This produces a result that is distinct, gradual, and targeted. It has been noted that the present Scrum estimate approach heavily relies on historical data from previous projects and expert opinion, while existing agile estimation methods like analogy and planning poker become unpredictable in the absence of historical data and experts. User Stories are used to estimate effort in the Agile approach, which has been adopted by 60–70% of the software businesses. This study's goal is to review a variety of strategies and techniques that will be used to gauge and forecast effort. Additionally, the supervised machine learning method most suited for predictive analysis is reviewed in this paper.

APA, Harvard, Vancouver, ISO, and other styles

35

S., Chandramouli, and G. Rajesh Kumar Dr. "HR MANAGEMENT BEST PRACTICES IN IT ORGANIZATIONS WITH SPECIAL REFERENCE TO AGILE - SCRUM PROJECTS." International Journal of Human Resource & Industrial Research 3, no. 2 (2016): 16–26. https://doi.org/10.5281/zenodo.10699714.

Full text

Abstract:

Agile is an iterative and incremental (evolutionary) approach to software development which is performed in a highly collaborative manner with "just enough" ceremony that produces high quality software which meets the changing needs of its stakeholders in particular delivering quick value to the Customer. In Agile less focus given on tracking individual performance, more on overall team performance (Chandramouli S & Dr. Rajesh Kumar, 2013 b).  According to Invancevich and Glueck, “HRM is concerned with the most effective use of people to achieve organizational and individual goals. It is a way of managing people at work, so that they give their best to the organization.”  Agile manifesto states that - Individual and interactions (organizations) over Process and tools.  Author tries to combine both the definitions together and tried to find out how HR Management practices (Effective use of People) helps the project and program managers to execute agile projects in particular scrum methodology based projects. Agile concepts and HR Management are tightly coupled together. This paper is aimed to study the human resource management practices of agile scrum methodology with respect to SCRUM TEA Model in detail. Key Words: Agile, HR Management, HRM, SCRUM TEA Model

APA, Harvard, Vancouver, ISO, and other styles

36

Yong, Ding. "Design and Practice of Software Architecture in Agile Development." Journal of Physics: Conference Series 2074, no. 1 (2021): 012008. http://dx.doi.org/10.1088/1742-6596/2074/1/012008.

Full text

Abstract:

Abstract Software architecture design is a very critical part of the software development process. In order to be able to respond to changes in user requirements in software development in a timely manner, a convenient and lightweight development model should be adopted. Agile development adopts a human-oriented, step-by-step development process that can quickly respond to changes in software requirements, adjust the design of software architecture in a timely manner and adapt to software development in a dynamic environment. Based on the analysis and comparison of traditional development process and agile development process, this paper analyzes the key technologies in agile architecture design and proposes a software architecture design method based on agile development mode.

APA, Harvard, Vancouver, ISO, and other styles

37

Shivarudra, Ashwini. "Implementing Agile Testing Methodologies in Banking Software Project." Journal for Research in Applied Sciences and Biotechnology 1, no. 4 (2022): 215–25. http://dx.doi.org/10.55544/jrasb.1.4.32.

Full text

Abstract:

Agile software development has been increasingly popular in a number of sectors in recent years. Financial businesses are used to this tendency since it requires them to respond to changes in their business environments more swiftly. Agile approaches have emerged to address the limitations of old ones. In response to the ever-changing and dynamic nature of the business environment, software development businesses are increasingly implementing agile methodologies. The word "Agile" originally arose in the disciplines of software development and project management around thirty years ago. It is used to research with wide-ranging implications, and it is utilized at different levels and in different circumstances. Scrum, kanban, large-scale scrum (LeSS), spotify model, continuous integration, Scaled Agile Lean Development (SCALeD), and many more variations of the agile methodology have emerged. Initially implemented at the individual software development and team level, agile has developed into projects, programs, solutions, and portfolios over time, ultimately reaching full-service growth into an enterprise level framework. In order to examine agile methodologies, models, and practices in a less researched area of the banking and financial services industry—from software development and modelling to large-scale case study organization levels—a unique methodology to surveying the literature has been presented in this paper. The study's conclusion outlines the contributing variables, best practices, advantages, and lessons that professionals in the banking and financial services industries may apply to create a simplified, agile deployment.

APA, Harvard, Vancouver, ISO, and other styles

38

Gray, Jeff, and Bernhard Rumpe. "Agile model-based system development." Software & Systems Modeling 17, no. 4 (2018): 1053–54. http://dx.doi.org/10.1007/s10270-018-0694-1.

Full text

APA, Harvard, Vancouver, ISO, and other styles

39

Dzulaiha Aryanee Putri Zainal, Rozilawati Razali, and Zulkefli Mansor. "Team Formation for Agile Software Development - Crowdsourcing-based Empirical Study." Journal of Advanced Research in Applied Sciences and Engineering Technology 34, no. 2 (2023): 133–43. http://dx.doi.org/10.37934/araset.34.2.133143.

Full text

Abstract:

Agile Software Development (ASD) is gradually substituting the plan-driven Waterfall development process. The nature of ASD requires that Agile development teams be more effective than any other development team in that Agile development is incremental, rapid, and responds well to changes. Therefore, team formation should be done properly in order for effective teamwork which leads to great performance and project success. To date, there is limited guidance, model, or frameworks that can assist in achieving optimum team formation. Currently, team formation is done based on heuristics and instincts which seemingly results in bias and incorrectness. This study aims to validate the Agile team formation conceptual model. This paper reports the initial empirical study that was done using a crowdsourcing-based method due to pandemic restrictions on close contact. The study was done in an Agile professional network group platform on the internet. The data collected is then analysed using contents analysis. The respondents validated that the team formation characteristics in the conceptual model were applicable with an emphasis on continuous learning and having a growth mindset. Future plan would be to determine the optimized team formation by using elements of Artificial Intelligence algorithms such as Genetic Algorithm.

APA, Harvard, Vancouver, ISO, and other styles

40

Wang, Yun Sheng, Bo Wang, Jun Guo, Bin Zhang, and Ji Na Wang. "An Agile Process Model Based on the Third-Party Testing Agencies." Advanced Materials Research 433-440 (January 2012): 4698–703. http://dx.doi.org/10.4028/www.scientific.net/amr.433-440.4698.

Full text

Abstract:

This paper has analyzed the entire testing task sets of the third-party software testing agencies. And for how to set these tasks to the process of projects’ research and development, proposed a new Software Process Model, which is an evolution of the helix structure. The model was based on the ideas of agile. It may become the first one that assigns the testing task sets to the whole process of software development in an independent third party perspective. The agile process model in this paper is major for the heavyweight projects’ research and development. Currently, this agile process model which is based on the independent third party has been adopted in practice projects, and achieved good results.

APA, Harvard, Vancouver, ISO, and other styles

41

Ambler, S. W. "Agile model driven development is good enough." IEEE Software 20, no. 5 (2003): 71–73. http://dx.doi.org/10.1109/ms.2003.1231156.

Full text

APA, Harvard, Vancouver, ISO, and other styles

42

Gidroets, M. O., and L. I. Grishanova. "SOFTWARE DEVELOPMENT METHODOLOGY." System analysis and logistics 4, no. 26 (2020): 45–53. http://dx.doi.org/10.31799/2007-5687-2020-4-45-53.

Full text

Abstract:

This article discusses the main methodologies for developing software products. The most common cascading and flexible methodologies are characterized. Considered the pros and cons of each methodology. The situations of expedient application of cascade and flexible approaches to software product development are determined. Key words: development methodologies, waterfall model, agile model, project management, planning, software product development.

APA, Harvard, Vancouver, ISO, and other styles

43

Bonner, Nancy A., Nisha Kulangara, Sridhar Nerur, and James T. C. Teng. "An Empirical Investigation of the Perceived Benefits of Agile Methodologies Using an Innovation-Theoretical model." Journal of Database Management 27, no. 3 (2016): 38–63. http://dx.doi.org/10.4018/jdm.2016070103.

Full text

Abstract:

There is little doubt that agile software development (ASD) methods have gained widespread acceptance in industry. Despite the attention these methods have received, there is little empirical affirmation of the benefits that accrue to those who use agile methodologies. Grounded in the conceptual foundations of innovation diffusion and agile philosophy of development, the authors' study validates a model to assess the perceived advantage of an iterative approach to software development. Consistent with their predictions, the results suggest that evolutionary development - the cornerstone of agile development – is perceived to be less complex and more compatible with the work habits of developers. Further, the findings support the hitherto unsubstantiated claim that iterative development yields benefits to software developers. However, process flexibility, yet another important characteristic of agile development, had no significant impact on complexity, compatibility, and relative advantage. The implications of the study for academics and practitioners, and directions for future research are discussed.

APA, Harvard, Vancouver, ISO, and other styles

44

Aziz, Nik Sakinah Nik Ab, and Rusli Abdullah. "An Ontological Model of Experience-Based Knowledge Management in Agile Software Development Environment." Lecture Notes on Software Engineering 3, no. 1 (2015): 26–30. http://dx.doi.org/10.7763/lnse.2015.v3.159.

Full text

APA, Harvard, Vancouver, ISO, and other styles

45

Zakrzewski, Pawel, Janusz Narkiewicz, and Darren Brenchley. "Safety Critical Software Development Methodologies in Avionics." Transactions on Aerospace Research 2020, no. 2 (2020): 59–71. http://dx.doi.org/10.2478/tar-2020-0011.

Full text

Abstract:

AbstractThis article summarizes avionics safety-critical software development methodologies and implications of the DO-178C standard from an Agile application perspective. We explain the safety-critical software categorization. It also outlines the main differences and advantages of different approaches to the development process, from Waterfall through the V-model to Iterative and Incremental. Agile principles are explained as well as a Scrum – which is a popular framework in the non-safety-critical software industry. The application of Agile, for safety-critical software considerations, is based on the practical knowledge of the authors, and looks at the potential solution from a DO-178C standard, size of the project, scalability, and organizational culture points of view. Definition of the Agile type of framework, consistent with the certification process and existing standards, has been highlighted as a potential game-changer for the avionics industry.

APA, Harvard, Vancouver, ISO, and other styles

46

Karlsen, Jan Terje, Anders Aaraas Pedersen, Max Paul Trautwein, and Hans Solli-Sæther. "Understanding Agile Software Development Team Adaptation Processes." International Journal of Risk and Contingency Management 11, no. 1 (2022): 1–25. http://dx.doi.org/10.4018/ijrcm.290059.

Full text

Abstract:

This study is about team adaptation from a continuous change perspective. The purpose was to investigate how agile software development teams in a Nordic financial institution adapt to task-based triggers. A single case study was conducted of three software development teams in a product unit reporting that they worked in agile ways. One of the main findings is that the agile software development teams sought to define tasks to be worked on individually. The adaptation triggers occurring during taskwork mainly prompt task-related interaction. In addition, the findings support that these adaptation triggers can either prompt small adjustments to taskwork or be more severe and move the focus to evaluation and planning activities before taskwork can be continued. We propose a model describing how agile software development teams adapt to task-based triggers based on the findings.

APA, Harvard, Vancouver, ISO, and other styles

47

Kamthan, Pankaj. "On the Nature of Collaborations in Agile Software Engineering Course Projects." International Journal of Quality Assurance in Engineering and Technology Education 5, no. 2 (2016): 42–59. http://dx.doi.org/10.4018/ijqaete.2016040104.

Full text

Abstract:

If there is a constant in software development, then it is that its ecosystem is a variable. The agile methodologies are part of a relatively recent shift from predictive to adaptive approach towards software development. This change has had a notable impact on software engineering education (SEE). In this article, a glimpse into the state-of-the-art of incorporating agile methodologies in software engineering courses is presented. In doing so, the reasons for including a project component in software engineering courses, and for committing to agile methodologies in software engineering projects in those courses, are given. The significance of collaboration in the execution of agile methodologies, in general, is underscored, and the pivotal role of collaboration in agile course projects, in particular, is emphasized. To lend an understanding to the notion of collaboration in agile methodologies, a conceptual model for collaboration is proposed and elaborated. The types of collaborations that can occur in agile course projects are classified and discussed. The use technological means for facilitating collaboration, including the Social Web and especially the Wiki, is highlighted.

APA, Harvard, Vancouver, ISO, and other styles

48

Misra, Subhas C., and Virender Singh. "Conceptualizing open agile software development life cycle (OASDLC) model." International Journal of Quality & Reliability Management 32, no. 3 (2015): 214–35. http://dx.doi.org/10.1108/ijqrm-08-2013-0127.

Full text

Abstract:

Purpose – Software development life cycle (SDLC) has always been the core methodology for any software engineer that depicts the entire development process which an organization is bound to utilize to achieve successful software. The purpose of this paper is to bring forth a conceptual model after analysing the best practices in SDLC, and extracting the best out of agile methodologies and the open source software, thereby bringing forward an optimised structure. Design/methodology/approach – The OASDLC is hypothesized specifically for “Brihaspati” project and is formulated keeping in mind the gaps and limitations posed by existing SDLC models. OASDLC is further put to test for achieving lower costs and efforts involved. The tests are further substantiated by means of hypothesis validation through execution of a survey based research. Findings – It has been observed that the present conceptual model further optimizes the efforts involved while adopting such a practice. Originality/value – This paper proposes a novel SDLC model so as to achieve a best practice for a software project. On analysing the issues involved such as tight budget and timelines, it led the authors to formulate a newer concept “Open Agile Software Development Life Cycle model” (OASDLC).

APA, Harvard, Vancouver, ISO, and other styles

49

Işık, Gürkan, and Mert Can Çifci. "A Model Proposal for Scaling the Productivity Increase in Agile Project Management Methodology." International Journal of Pioneering Technology and Engineering 2, no. 02 (2023): 147–64. http://dx.doi.org/10.56158/jpte.2023.48.2.02.

Full text

Abstract:

Project management in the software industry is the process of successfully planning, managing, and completing software development projects. Software projects can often be complex, constantly changing, and full of uncertainties, so project management is of particular importance in the software industry. There are two basic approaches to the execution of software projects. In the waterfall model, the project stages are operated in the determined order and after each stage is completed, the next stage is passed, while in the agile approach, the project is divided into small and priority parts, and the work processes are repeated at regular intervals and improvements are made depending on the feedback received. Recently, there has been a trend towards managing software projects with agile methodologies, as it provides flexibility and adaptability. However, there is no quantitative evaluation of the benefits of agile structuring both in the literature and in the sector, and this benefit is expressed with verbal expressions referring to the formation of a dynamic culture. For this reason, the productivity increase brought by the agile project approach cannot be measured and the benefit it provides cannot be scaled. In this study, a model that takes linguistic uncertainty into account is proposed to quantitatively scale the productivity increase provided by agile project structuring. The proposed model has been applied in a business where enterprise resource planning solutions have been developed and the effect of the transition from waterfall model to agile methodology on the productivity of the project has been investigated. Within the framework of the procedure proposed by the model, expert evaluations were taken in line with the determined quantitative and qualitative criteria, these criteria were listed with the fuzzy SWARA method, and the productivity increase provided by agile methodology was calculated using this information. The findings also allowed us to get an idea of the point of scaling the increase in productivity across the industry.

APA, Harvard, Vancouver, ISO, and other styles

50

White, A. S. "An Agile Project System Dynamics Simulation Model." International Journal of Information Technologies and Systems Approach 7, no. 1 (2014): 55–79. http://dx.doi.org/10.4018/ijitsa.2014010104.

Full text

Abstract:

This paper compares established Systems Dynamics (SD) models of software projects with models of agile development. A new minimal SIMULINK™ agile project model was created and compared to a Waterfall model of a NASA project. Results are presented to enable project managers to predict the performance of future agile project processes. The model includes the time to generate the requirements and a function to provide requirements volatility. These models show that for the same productivity and fraction of errors that are satisfactory, the overall development staff costs are similar for agile and waterfall projects and the undiscovered rework is less for the agile project. This model generally supports empirical observations that shorter time-box iterations yield a shorter overall project completion.

APA, Harvard, Vancouver, ISO, and other styles

Journal articles on the topic 'Agile Software Model'

Create a spot-on reference in APA, MLA, Chicago, Harvard, and other styles