A Quantitative Study of Waterfall and Agile Methodologies With the Perspective of Project Management

2022 ◽  
pp. 111-133
Author(s):  
Kenish Rajesh Halani ◽  
Kavita Jhajharia
Keyword(s):  
Software Engineering ◽  
Software Development ◽  
Extreme Programming ◽  
Prototype Model ◽  
Software Products ◽  
Customer Involvement ◽  
Waterfall Model ◽  
Almost All ◽  
Spiral Model ◽  
Agile Model

Software engineering is used in order to develop larger and complex software products. As software product is needed in almost all the industries, software engineering becomes really important. Software development can be done through various software development life cycle (SDLC) models like waterfall model, agile model, spiral model, prototype model, etc. SDLC is a framework that defines the tasks that to be performed at each step in the development process. Authors are mainly focusing on two models (i.e., waterfall and agile model). Waterfall model is a serial model which follows a strict sequence. Agile methodology can be divided into scrum methodology and extreme programming. Scrum methodology mainly focuses on how to manage tasks in a team-based environment. Scrum consists of three main roles. They are scrum master, product owner, and scrum team. While comparing both the models, the main difference obtained is waterfall does not allow any customer involvement while agile does allow it.

Project Implementation Decision Using Software Development Life Cycle Models: A Comparative Approach

2021 ◽  
Vol 28 (1) ◽  
Author(s):  
M.A. Adeagbo ◽  
J.E.T. Akinsola ◽  
A.A. Awoseyi ◽  
F. Kasali
Keyword(s):  
Life Cycle ◽  
Comparative Analysis ◽  
Software Development ◽  
Cost Estimation ◽  
Comparative Approach ◽  
Project Implementation ◽  
Development Life Cycle ◽  
Software Development Life Cycle ◽  
Waterfall Model ◽  
Spiral Model

Selection of a suitable Software Development Life Cycle (SDLC) model for project implementation is somewhat confusing as there are a lot of SDLC models with similar strengths and weaknesses. Also, the solutions proffered among the researchers so far have been the  qualitative comparative analysis of SDLC models. Hence, this paper proposes a comparative analysis of SDLC models using quantitative approach in relation to strengths and weaknesses of SDLC models. The study adapted comparative analysis and Software Development Life Cycle (SDLC) models features’ classification using ten characteristics such as project complexity, project size, project duration, project with risk, implementation/initial cost, error discovery, associated cost, risk analysis, maintenance and cost estimation. A quantitative measure that employs online survey using experts in software design and engineering, project management and system analysis was carried out for the evaluation of SDLC models. Purposeful Stratified Random Sampling (SRS) technique was used to gather the data for analysis using XLSTAT after pre-processing, taking into consideration both benefit and cost criteria. The overall performance evaluation showed that Spiral-Model is the best followed by V-Model and lastly Waterfall Model with comparative values of 38.63%, 35.76% and 25.61% respectively. As regards cost estimation, Waterfall Model is the most efficient with value of 41%, then V-Model with 31% and lastly Spiral Model with 28%. V-Model has great error recovery capability with value of 45% which is closely followed by Spiral Model with 37% and lastly Waterfall Model with 18%. The study revealed that, a model with efficient risk assurance does not guarantee efficient cost management. In the future work, more characteristics regarding SDLC models shall be considered.

Software Modeling Processes

2009 ◽  
pp. 169-178
Author(s):  
Roy Gelbard
Keyword(s):  
Software Development ◽  
System Analysis ◽  
Unified Modeling Language ◽  
Extreme Programming ◽  
Software Modeling ◽  
Application Development ◽  
Levels Of Abstraction ◽  
Model Driven ◽  
Waterfall Model ◽  
Future Direction

Applications require short development cycles and constant interaction with customers. Requirement gathering has become an ongoing process, reflecting continuous changes in technology and market demands. System analysis and modeling that are made at the initial project stages are quickly abandoned and become outmoded. Model driven architecture (MDA), rapid application development (RAD), adaptive development, extreme programming (XP), and others have resulted in a shift from the traditional waterfall model. These methodologies attempt to respond to the needs, but do they really fulfill their objectives, which are essential to the success of software development? Unified modeling language (UML) was created by the convergence of several well-known modeling methodologies. Despite its popularity and the investments that have been made in UML tools, UML is not yet translatable into running code. Some of the problems that have been discovered have to do with the absence of action semantics language and its size. This chapter reviews and evaluates the UML evolution (UML2, xUML), providing criteria and requirements to evaluate UML and the xUML potential to raise levels of abstraction, flexibility, and productivity enhancement. At the same time, it pinpoints its liabilities that keep it from completely fulfilling the vision of software development through a continuous exactable modeling process, considered to be the future direction for modeling and implementation.

Obstacles for the Integration of HCI Practices into Software Engineering Development Processes

2006 ◽  
pp. 422-428 ◽  
Author(s):  
Xavier Ferre ◽  
Natalia Juristo ◽  
Ana M. Moreno
Keyword(s):  
Software Engineering ◽  
Software Development ◽  
Computer Literacy ◽  
Software Process ◽  
Software Systems ◽  
Software Products ◽  
Software Market ◽  
Visible Part ◽  
Software Product ◽  
Development Processes

Usability has become a critical quality factor in software systems, and it has been receiving increasing attention over the last few years in the SE (software engineering) field. HCI techniques aim to increase the usability level of the final software product, but they are applied sparingly in mainstream software development, because there is very little knowledge about their existence and about how they can contribute to the activities already performed in the development process. There is a perception in the software development community that these usability-related techniques are to be applied only for the development of the visible part of the UI (user interface) after the most important part of the software system (the internals) has been designed and implemented. Nevertheless, the different paths taken by HCI and SE regarding software development have recently started to converge. First, we have noted that HCI methods are being described more formally in the direction of SE software process descriptions. Second, usability is becoming an important issue on the SE agenda, since the software products user base is ever increasing and the degree of user computer literacy is decreasing, leading to a greater demand for usability improvements in the software market. However, the convergence of HCI and SE has uncovered the need for an integration of the practices of both disciplines. This integration is a must for the development of highly usable systems. In the next two sections, we will look at how the SE field has viewed usability. Following upon this, we address the existing approaches to integration. We will then detail the pending issues that stand in the way of successful integration efforts, concluding with the presentation of an approach that might be successful in the integration endeavor.

scholarly journals Reuse Alternatives based on the Sources of Software Assets

2021 ◽  
Vol 10 (1) ◽  
Author(s):  
Anas AL-Badareen
Keyword(s):  
Software Engineering ◽  
Software Development ◽  
Software Reuse ◽  
Development Process ◽  
Software Systems ◽  
Software Development Process ◽  
Software Products ◽  
Engineering Discipline

    Abstract— Since the idea of software reuse appeared in 1968, software reuse has become a software engineering discipline. Software reuse is one of the main techniques used to enhance the productivity of software development, which it helps reducing the time, effort, and cost of developing software systems, and enhances the quality of software products. However, software reuse requires understanding, modifying, adapting and testing processes in order to be performed correctly and efficiently. This study aims to analyze and discuss the process of software reuse, identify its elements, sources and usages. The alternatives of acquiring and using software assets either normal or reusable assets are discussed. As a result of this study, four main methods are proposed in order to use the concept of reuse in the software development process. These methods are proposed based on the source of software assets regardless the types of software assets and their usages.

scholarly journals Product development models in the IT sector-From Waterfall to Agile Project Management Model s in the case of AVIRA SOFT S.R.L

2018 ◽  
Vol 12 (1) ◽  
pp. 568-578 ◽  
Author(s):  
Maria Alexandra Maassen
Keyword(s):  
Product Development ◽  
Business Models ◽  
Business Environment ◽  
Customer Requirements ◽  
Development Models ◽  
Political Processes ◽  
Customer Involvement ◽  
Waterfall Model ◽  
Agile Model

Abstract The digitalization process of the business activities has increased tremendously in the last fifty years, revolutionizing several fields of activity, such as communication, medicine, production, transport, as well as all aspects of the daily social, economic and political processes. Furthermore, the IT field has developed new ways of innovating, including new management models in the production field, that allow management of IT companies to become more customer-oriented in a dynamic competitive field. As technological progress is becoming present in every aspect of everyday life, the pressure for innovation and customer involvement represent the two main challenges of producing successful prototypes and final products for the IT market. The purpose of the present paper is to analyze two of the main product development business model trends in the IT field, namely Waterfall model and Agile model, the latest being an adapting strategy to increased customer requirements and the changing business environment. In order to ensure a practical approach the case study was based on the analysis of their implementation within the company Avira Soft S.R.L. The results of the study emphasized the benefits of using the Agile model at Avira Soft S.R.L starting with 2011 in comparison to the previous model of Waterfall product development. The relevance of the paper consists in the fact that the two models indicate how the IT product development business models are evolving depending on environmental factors and the need for continuous adaptation and innovation due to increased competition. The Agile model brought improvements of the Waterfall model, but also new challenges regarding the organizational culture, communication between members of the company and more pressure for continuous improvement. However these two models are an example of how the IT product development business models are evolving and they form a basis for future product development strategies.

scholarly journals Development of Medical Record With Extreme Programming SDLC

2018 ◽  
Vol 5 (1) ◽  
pp. 47-53 ◽  
Author(s):  
I Gusti Ngurah Suryantara ◽  
Johanes Fernandes Andry
Keyword(s):  
Software Development ◽  
System Design ◽  
Medical Record ◽  
Programming Model ◽  
Extreme Programming ◽  
Application Development ◽  
Time Of Application ◽  
Waterfall Model ◽  
The Right ◽  
Selection Of

The XP (eXtreme Programming) model is best suited for the development of information systems projects that require rapid adaptation to changes that occur during application development compared to the SDLC Waterfall model. XP is also suitable for fewer team members and is in the same location in software development of medical record. Software development should be well planned, so that the software obtained quality and in accordance with the needs of users. The selection of the right framework will determine the success of software development, thus avoiding patchwork in application development. Step by step of research methods for medical record software are Planning, design, coding, testing and software increment. Studies conducted in this study include: library study, interviews, observation, document examination. Next do an analysis of the aplications made, and check the document to get a picture of the system created. This is done as an analysis and system design conducted by researchers. Selection of the right framework at the time of application development to bridge between the developer side and the user side, so that the developed application can be completed on time. In this research use eXtreme Prorgamming framework which focused on development of medical record, because eXtreme Programming more emphasis on software development and system design with CRC (Class Responsibility Collaborator). XP framework that every step always involves users, programmers, and parts of testing so that the applications created can be completed in a timely manner and in accordance with the needs of users

scholarly journals Scrum: An Agile Process Reengineering in Software Engineering

2020 ◽  
Vol 9 (3) ◽  
pp. 840-848 ◽  
Keyword(s):  
Software Engineering ◽  
Software Development ◽  
Control Theory ◽  
Engineering Management ◽  
Vital Role ◽  
Team Members ◽  
Software Products ◽  
Development Organizations ◽  
Organizational Mechanism ◽  
Agile Process

BPR (Business Process Re-engineering) is an organizational mechanism leading organization towards change management as and when it is required. In the form BPR, Agile practices have had a remarkable impact on Software Engineering Management (SEM) in software development organizations across the world. It has enhanced collaboration and productivity of Software Engineering (SE) teams and improved the level of quality of software products. Nowadays Scrum has been trending into software development organizations as a standard SDLC approach. Scrum is the framework of the Agile methodology, built on empiricism control theory, asserts that experience brings knowledge and increases decision making capabilities. The empiricism control theory is built on three pillars: Adaptation, Inspection and Transparency. This research study presents Scrum as a trending SDLC framework using empirical analysis. We have analyzed literature reviews, case studies, and research surveys; and implemented Scrum in our software development unit and carried out the reasons, why Scrum is trending in software development organizations. How the scrum artifacts, events and values play a vital role in upholding the Scrum pillars and strengthen the capabilities of Scrum team members to address the software engineering management challenges; compared to traditional software development approaches.

scholarly journals Runtime metric meets developer - Building better cloud applications using feedback

2015 ◽  
Author(s):  
Jürgen Cito ◽  
Philipp Leitner ◽  
Harald C. Gall ◽  
Aryan Dadashi ◽  
Anne Keller ◽  
...  
Keyword(s):  
Software Engineering ◽  
Software Development ◽  
Feedback Loops ◽  
Runtime Monitoring ◽  
Code Optimization ◽  
Proof Of Concept ◽  
Software Products ◽  
Code Changes ◽  
Cost Implications ◽  
Cloud Applications

A unifying theme of many ongoing trends in software engineering is a blurring of the boundaries between building and operating software products. In this paper, we explore what we consider to be the logical next step in this succession: integrating runtime monitoring data from production deployments of the software into the tools developers utilize in their daily workflows (i.e., IDEs) to enable tighter feedback loops. We refer to this notion as feedback-driven development (FDD). This more abstract FDD concept can be instantiated in various ways, ranging from IDE plugins that implement feedback-driven refactoring and code optimization to plugins that predict performance and cost implications of code changes prior to even deploying the new version of the software. We demonstrate existing proof-of-concept realizations of these ideas and illustrate our vision of the future of FDD and cloud-based software development in general. Further, we discuss the major challenges that need to be solved before FDD can achieve mainstream adoption.

scholarly journals Dynamic Agile Distributed Development Method

Mathematics ◽  
2019 ◽  
Vol 7 (10) ◽  
pp. 963 ◽  
Author(s):  
Muhammad Asgher Nadeem ◽  
Scott Uk-Jin Lee
Keyword(s):  
Software Engineering ◽  
Software Development ◽  
Rapid Development ◽  
Agile Development ◽  
Engineering Model ◽  
Team Members ◽  
Development Method ◽  
Distributed Development ◽  
Distributed Models ◽  
Agile Model

“Agile” is an effective software engineering model with a high trust and acceptance rate among its users. The term agility comes from the concept of rapid development and working in a team for better results and a faster competition rate when compared with any other software engineering model. In this study, an assessment of the different patterns, frameworks, and application program interfaces available for distributed development in an agile model is given. After analyzing the state-of-the-art distributed models, a novel framework of a dynamic agile distributed development method (DADDM) is introduced in this paper. Many researchers have worked on global software development using the agile approach; however, we are presenting the idea of incorporating the agile benefits with dynamic distributed software development. The applicability of the proposed model is checked via two selected parameters: a feasibility study and a business study. The complete DADDM development life cycle is presented in the methodology section. The techniques used in DADDM and team members’ roles and responsibilities in DADDM are defined in this study. This study reflects all pillars of planning, controlling, organizing, and management of leadership. The use of DADDM in distributed agile development encourages future researchers to use this proposed framework for comparison and testing of their models and to check the effectiveness through a comparison with DADDM.

Sign in / Sign up

Export Citation Format

Share Document