Software Development Life Cycle for Web

Application by using Traditional Methodology vs

2024 Ninth International Conference on Science Technology Engineering and Mathematics (ICONSTEM) | 979-8-3503-6509-2/24/$31.00 ©2024 IEEE | DOI: 10.1109/ICONSTEM60960.2024.10568596

Agile Methodology
V. Vamsi Krishna1 and G. Gopinath2
1
Research Scholar, School of Computer Science, Engineering & Applications, Bharathidasan University, Tiruchirappalli, India.
2
Professor, School of Computer Science, Engineering & Applications, Bharathidasan University, Tiruchirappalli, India

E-mail : [email protected], [email protected]

Abstract- Life cycle software development is concerned in Nissan being forced to recall more than a million vehicles
the software development process (SDP), which inspects the after a software bug in the airbag sensor detector. Or a
software development region. Life cycle of software software flaw that prevented the launch of a $1.2 billion
development (SDLC) is a technique that assures that the military satellite. 2 The data speaks for itself. In the
software abides by the recognized necessities. In this
methodologies, to create the method more effective and also
United States, software bugs cost the economy $1.1
conventional it applies numerous grades in the SDP. In this trillion in assets in 2016. Additionally, they affect 4.4
work, the heavy class methodology (traditional SDLC) and billion consumers. Although testing is expensive,
as well the Lightweight Methodology (Agile SDLC) are companies with effective testing techniques and quality
explicated and also conducted a correlation betwixt the assurance processes can save millions of dollars each year
policy of Method. in development and maintenance. Initial software testing
reveals problems before the product is launched. Early
Keywords: Life cycle of software development (SDLC), development teams get feedback on testing; sooner they
Techniques: traditional and agile. can fix issues like: • Architecture bug • Bad design
decision • Invalid or incorrect functionality • Security
I. INTRODUCTION vulnerability • Capability issues scalability as the tests
have enough room during development, the reliability of
The construction of laptop Application programs along the software increases and the high product programmers
with records designs is constantly dictated through have fewer bugs. A system that meets or even exceeds
specific development methods. A software program customer expectations can increase sales and market
improvement (SPI) methodology mentions the structure share.
that is utilized to manage, plan, and manipulates the
procedure of construction of a record system. Generally, a Requirement Analysis
SPI methodology is termed SDLC. This methodology is This section is mainly intended to recognize the actual
partitioned into some stages that contain 1) Requirement needs of clients and also to folder requirements
Analysis (RA), 2) Design, 3) Code, 4) Test, 5) Install, and appropriately. The importance of RA is to discover what
6) Maintenance are all steps in the software development is required as of the method. In SDLC, it is a significant
process. Software testing is a technique to determine if the level. Software Requirement Specification (SRS) is the
actual software product matches expectations and is free outcome of RA that affords a detailed explanation about
of bugs. It involves human or automated execution of the SP to be structured.
software/system components to evaluate one or more
attributes of interest. The goal of software testing is to Design
find bugs, holes or unmet requirements compared to the In SDLC, it is the highest creative segment. In this
written requirements. Some like to say that software segment, the requirement specification is rehabilitated
testing means white box and black box testing. In simple into a plan or else shape. It is a methodology of planning
terms, software testing means validation of the application together with trouble fixing for an SP solution. It involves
under test (AUT). This software testing course introduces SP builders along with designers to sketch out the plan
software testing to the general public and explains the intended for a solution. Software Design Document
importance of software testing. Few people dispute the (SDD) is the outcome of this segment.
need for quality control when creating software. A brand's
reputation can be damaged by late deliveries or software Coding
bugs, which can lead to anger and loss of customers. In In this segment, by utilizing certain programming
extreme cases, a bug or vulnerability can damage languages the SDD is changed into code. In SDLC, it is
connected systems or cause serious problems. Think of

Authorized licensed use limited to: Centre de Recherches et des Technologies des Eaux. Downloaded on July 31,2024 at 07:15:35 UTC from IEEE Xplore. Restrictions apply.
 the logical segment. Software code is the outcome of this Iterative Model
segment. It is a technique that offers a novel scheme to the
developing models that could provide speedy outputs,
Testing require fewer details, and offer higher flexibility. In this
Following the coding segment, the testing is executed to phase, the model is separated into small sections. This lets
establish the application‟s final output. It is performed to the development team to display the outcomes in advance
discover the original output along with the forecasted together with that attain valuable comment from clients.
outcome. It is a significant and as well powerful segment. Usually, emphasis is a mini-waterfall procedure with the
High graded SP products, reduced maintenance cost and response as of a segment offering significant facts for the
also perfect in addition to dependable outcomes are making of the following phase. In this method, the
provided by this testing segment. system is evolved and also enhanced via several steps and
hence the risks are predicted in advance. Hence the
Maintenance defects‟ downward movement is averted. In this, the
It is the final segment of SDLC, in which the SP being feedback of the responsible person is provided.
developed is sent to clients who utilize it for the
appropriate processes. Incremental Model
This model partitions the components, wherein the
SDLC Models mission phases are produced and inspected individually.
There are different SPI methods illustrated and also This method probably detects the errors. Like the
structured that might be utilized via SPI methodology; lifecycle models, the requirements of the last method are
those methods are also termed as "SDP Models". Every approved initially in the incremental phase. In this,
single method pursues a particular lifestyle series to reserved requirements are allotted to iteration; together
obtain specific achievements in the method of SPI. with every consecutive (internal) commenced needs are
handled in anticipation of the final (external) launch
Traditional Model fulfills all needs [2].
It is the typical version of SP manufacturing [1] moreover
its miles are termed as a linear-sequential lifestyles Prototyping Model
iterative version. It describes a little prime function that is It is a running model that is comparable to the product. [4]
completed in series: a) necessities definition, b) It is a usable device that is developed rapidly with
architecture layout, c) special layout, d) implementation, reduced cost, and also intended to alter or modify it via a
e) thing verification, f) integration verification and g) full-scale and as well completely functional system. [5] It
necessities validation. In this method, every single allows the clients to comprise a communication by means
segment should be completed prior to the start of the later of the design that allows offering higher feedback along
segments. At the completion of every single segment, an with specifications.
assessment is conducted to make a decision whether the
task is on the correct path and also whether to persist or V-Shaped Model
else remove the task. And this method provides a a This model performs successively. Every single phase
starting point for a variety of lifecycle strategies [1][2]. should be ended prior to the start of the following phase.
Before the execution of the coding, the process of testing
Spiral Model evolved, during every phase‟s previous execution. The
It is an incremental method, by means of a greater accent needs of this model are equivalent to the waterfall model.
positioned on risk evaluation. It has 4 stages, namely Risk Prior to the evolvement, the test plan is produced. The
Analysis, Planning, Evaluation along with Engineering, assessment plan‟s focus is to fulfill the specifications
An SP mission goes by those steps in iterations (called pointed out in the necessities collected. The high-level
Spirals on this version). Beginning with the development design concentrates on the models' design together with
stage, the requirement is collected as well as risk is architecture. Nevertheless, the low-level design phase
analyzed in the base spiral. Each spiral makes at the base appears where the original SP is structured, and as well
spiral. Necessities are gathered throughout the unit tests are also produced in this stage. [1]
development segment. In the portion of hazard evaluation,
a method is executed to detect hazards along with varied RAD Model
solutions. In the last part of the risk evaluation section, a It's a common incremental model. In this, additives else
model is being developed. In the engineering phase, the competence enhanced simultaneously as it was provided
software is created and at the conclusion, testing is with small-projects. The traits are obtained along with
performed. The project‟s outcome is evaluated by the that are arranged into an operating prototype. This can
client in analysis to update prior to the work begins to the rapidly provide the client with somewhat to peer besides
following spiral [3]. utilize to offer response regarding the transmission
together with their supplies.

Authorized licensed use limited to: Centre de Recherches et des Technologies des Eaux. Downloaded on July 31,2024 at 07:15:35 UTC from IEEE Xplore. Restrictions apply.
 Traditional SDLC (Heavyweight Methodology) which is primarily centered on that belief. The assets of
These methodologies are planed wherein paintings start versions may be identified along with handled in the
evolved with the evocation and additionally course of the enhancement existence cycle. The
documentation of the complete set of necessities, conventional SPI existence cycle is very process-centric
analogized to the buttress of utilising architectural and as in summary.
properly high-level format development together with the
examination. [6] This method is termed as a heavyweight, Agile SDLC (Lightweight Methodology)
as a consequence of these heavy factors. These A compilation of SPI techniques which might be
methodologies are centred on certain steps such as answer frequently targeted on iterative together with incremental
building, trying out, definition, and also deployment. development is called Agile Software Development, in
Initially, the needs are stated as well as documented in which necessities and solutions expand thru collaboration
these Heavyweight methodologies. Software models like among self-organizing, centered teams [8]. Quick and
the Waterfall approach, V-Model, together with RUP flexible responses to varying requirements are enabled by
have been termed as traditional SPI methodologies along the approach together with it supports evolutionary
that these are organized into heavyweight methodologies. development, adaptive planning, and also delivery along
It will be liable to remodel a huge portion of the SP with a “time-boxed” emphasis approach [11]. Foreseen
methodology in the first-rate element for an expanded interactions are promoted by a conceptual framework
period. This methodology pursues an engineering field during the enhancement cycle. A complicated method is
wherein the enhancement is expected and also repeatable. software advent if it isn‟t performed accurately.
A huge level of significance is occurred on the model Communication, flexibility, along with proper analysis is
concentrating on the system‟s requirement efficiently. A the key to a successful SP task [12] in order that the agile
significant model in heavyweight models is the huge technique is followed for SP enhancement. It possesses
layout upfront (BDUF) method, wherein a perception that the capability of evolving while matters change. A
it is probable to the buildup of the client‟s necessities conceptual framework for projecting any SP engineering
before coding. And this method is successful in projects is called the agile improvement technique [13].
engineering fields that make it engaging the SP Agile methodology is a technique that encourages
production. continuous testing and development throughout the
software development lifecycle of a project. Unlike
Characteristic of Traditional Methodology Waterfall method, Agile model for software testing
The conventional SPI approach‟s feature is mostly involves concurrent development and testing. One of the
centered on „4‟ steps. Installing the requirements for the simplest and most effective methods for turning visions of
undertaking is the initial step. It determines the period business needs into software solutions is agile software
taken for enforcing the different levels of enhancement development. The term "agile" is used to describe
while expecting any problems that arise with the software development methodologies that involve
undertaking. The movement into the layout together with planning, continuous learning and improvement,
the architectural planning segment is the succeeding step teamwork, evolutionary development, and early delivery.
wherein a technological infrastructure is generated inside It promotes adaptive responses to change. When written
the shape of diagrams or else designs. The mission moves in 2001, the Agile Software Development Manifesto
into the enhancement segment after the group is happy offered a revolutionary way of thinking about delivering
regarding the architectural and layout plan where the code value and interacting with customers. The four core
is generated until the specific dreams are attained. For values of Agile are: 1) People and interactions rather than
making sure whether the issues are discussed early on, the processes and equipment 2) Usable software rather than
checking out segment is often overlapped with the complete documentation 3) Customer involvement in
enhancement segment. The purchaser becomes a part of contract negotiation 4) Adapting to change rather than
the checking out together with comments cycle after the exploring a plan Agile Framework So what is Agile
purchaser satisfies it and the finishing touch is approached project management? It is a project management method
by the mission and the builders are close to the assembly that involves continuous communication and iterative
of the mission necessities [7]. The crucial nature of the development. These principles and frameworks for
conventional SPI existence cycle is as: Apprehending the putting them into practice, such as Scrum, Kanban,
users' requirements, crafting a strong layout, developing Extreme Programming (XP), and the Adaptive Project
SP perfectly, and putting a helpful gadget that fulfills Framework, are now known as agile (APF).
person necessities are the dreams. For addressing risks,
there exists a heavy emphasis on making plans. Such a Extreme Programming (XP)
technique presumes that troubles are adequately It is an agile technique, concentrates SPI methodology
explained. Via widespread and up-the-front making plans, along with handling the analysis, [30] enhancement, and
an optimum answer might have arrived. The approaches also testing with novel processes motivated in making a
are predictable and might be optimized along with huge distinction to the end product. [14]
repeated. The approaches might be accurately estimated

Authorized licensed use limited to: Centre de Recherches et des Technologies des Eaux. Downloaded on July 31,2024 at 07:15:35 UTC from IEEE Xplore. Restrictions apply.
 Crystal Methods  Adaptive
It has been evolved to manage a number of circumstances  Empirical Process.
together with the particular traits of the issue [16].  People-oriented.
Crystal's circle light-weight SDLC methodology is the  Team Competence
beginning of Alistair Cockburn [10]. It is made of above 1  Small Self-organizing teams. [8]
method as a consequence of Cockburn‟s perception that  Conformance to Actual.
various challenge sorts need differing methodologies [15].  Collaboration.
Project sorts are classified as the range of humans at the
 Balancing Flexibility and Planning. [34]
enhancement group along with the total risk. These
 Decentralized Approach. [35]
methodologies are partitioned into hues coded bands [31].
“Clear” Crystal is the tiniest in addition to lightest.  Simplicity.
“Yellow”, “Orange”, “Red”, “Maroon”, “Blue”, together
with “Violet” comply by means of to be utilized with Agile methodologies are the subset of iterative along with
huge organizations the utilization of highly complicated evolutionary methodologies. Iterations are little to offer
methodologies [9]. additional well-timed feedbacks to the business enterprise
group [23]. Extreme Programming is mainly centred on 4
Scrum values along with 12 particular software improvement
It is basically a lightweight methodology possessing huge applications. Crystal's circle of related methodologies is
applicability intend for handling along with managing mainly centred on the features of the project and also the
repetitive as well as incremental schemes of the complete group [36]. Scrum specifically provides venture
sorts [17]. It became famous within the SP network on administration values. The model permits the group
account of its ease and also definite productivity [18]. liberty to select its certain advancement practices [24]. It
This methodology focuses on a particular way to control has the utmost evaluation together with layout practices
challenges within a group mainly centred on completely [10].
enhanced circumstances [19].
Traditional Vs Agile Technique
Feature-Driven Development (FDD) Even though the agile methodology is centred upon
It is a short-generation SPI method [32]. This iterative development, there are certain key differences
methodology started by setting up a widespread model betwixt the agile and conventional methods [25].
pattern [9]. This is conducted by a series of “layout Traditional methodologies utilize development plans as
through feature, construct through feature” iterations [20]. their administration system, whilst agile methodologies
It contains 5 sequential phases such as plan through utilize the comments from the clients as the prime
feature, increases a universal version, layout through management mechanism. [26] The agile technique is also
feature, construct a functions list, and construct through termed a people-centric approach [37]. The agile model
feature [33]. Initially, the first 3 phases are performed can offer an operating model associated with standard
[21]. The final stages are the method‟s iterative phase methodologies so that the client can understand a number
which aids the agile methodology with detailed of the advantages [27]. In contrast with other standard
diversifications to past modifications in requirements methodologies, the agile method‟s testing time is low
along with enterprise wants [6]. [38]. Several conventional methodologies are extremely
nonflexible when analogized to the agile technique [28].
Characteristics of Agile Technique On account of these benefits, agile is employed above the
The taking after are the prime errand of the dexterous other conventional models [29].
demonstrate that varies from the overwhelming weighted
strategy [22].
Table 1.0 Agile approach vs Traditional approach
Characteristics Agile approach Traditional approach
Organizational structure Iterative Linear
Scale of projects Small along with medium scale Large-scale
User requirements Interactive input Completely explicated before execution
Involvement of clients High Low
Development model Evolutionary delivery Life cycle
Customer involvement Customers included as of the time Customers are included initially in the project but
work is being executed not after the execution has begun
Escalation management When issues occur, the whole team Escalation to managers when an issue occurs
functions together to solve it
Model preference Adaption is supported by agile Expectancy is supported by the traditional model
model

Authorized licensed use limited to: Centre de Recherches et des Technologies des Eaux. Downloaded on July 31,2024 at 07:15:35 UTC from IEEE Xplore. Restrictions apply.
 Product or process Less focus on formal as well as It is more serious concerning processes when
directive processes contrasted to the product
Test documentation Comprehensive test planning Tests are planned one sprint at a time
Effort estimation Scrum master assists along with the The project manager estimates and attains approval
calculation are done by the team. as of PO aimed at the whole project.
Reviews and approvals Reviews are performed after every Excessive reviews along with approvals by leaders.
single iteration

II.CONCLUSION integration." In Agile Conference, 2009. AGILE'09., pp. 369-

374. IEEE, 2009.
[14] Agile Marketing Documentation. Last Accessed 2020. www
SDLC is a model that manages the whole development .agilesherpas .com/blog/state-of-agile-marketing-2020
system. In this research, The Traditional model offers the [15] Matharu, G. S., Mishra, A., Singh, H., & Upadhyay, P. (2015).
"Empirical study of agile software development methodologies:
basis for numerous developmental processes. Modern A comparative analysis". ACM SIGSOFT Software
SDLC is partitioned into 2 types: traditional SDLC along Engineering Notes, 40(1), 1-
with agile SDLC. In this study, the outline and the 6.https://doi.org/10.1145/2693208.2693233
features of the traditional along with agile SPI model are [16] Jammalamadaka, K., & Krishna, V. R. (2013). "Agile software
development and challenges". International Journal of Emerging
provided. In addition, 4 methodologies like crystal, XP, Technology and Advanced Engineering, 3(6).
FDD, together with Scrum are overviewed. Hence, the [17] Rodríguez, P., Mäntylä, M., Oivo, M., Lwakatare, L. E.,
evaluation betwixt the agile along with the conventional Seppänen, P., & Kuvaja, P. (2018). "Advances in Using Agile
methodologies is proved. and Lean Processes for Software Development". Advances in
Computers(Vol. 113, pp. 135-224). Elsevier.
[18] Erickson, J., Lyytinen, K., & Siau, K. (2005). "Agile modeling,
REFERENCES agile software development, and extreme programming: the
state of research". Journal of Database Management (JDM),
[1] L. Rising and N. S. Janoff, The Scrum software development 16(4), 88-100.https://doi.org/10.4018/jdm.20051001
process for small teams, IEEE Software, Issue 17, pp. 26-32, [19] Abrahamsson, P., Salo, O., Ronkainen, J., & Warsta, J.
2000. (2017)."Agile software development methods: Review and
[2] K. Schwaber and M. Beedle, Agile Software Development with analysis". arXiv preprint arXiv:1709.08439.[19]Schmidt, C.
Scrum, Upper Saddle River, NJ, Prentice-Hall, 1st Edition, Oct (2016).
2001. [20] Agile software development teams. Springer International
[3] Julian, Brendan, James Noble, and Craig Anslow. "Agile Publishing.
Practices in Practice: Towards a Theory of Agile Adoption and [21] Khurana gourav and s gupta(2012) “ Study & Comparison of
Process Evolution." International Conference on Agile Software Software Development Life Cycle Models” IJREAS, Vol. 2(2),
Development. Springer, Cham, 2019. 1514-1515.
[4] Puleio, Michael. "How not to do agile testing." In Agile [22] Wallin Christina and Land R. “Software development Life
Conference, 2006, pp. 7-pp. IEEE, 2006. Cycle models the basic type”, 2.
[5] Abrahamsson, Pekka, et al. "Agile software development [23] Nabil Mohammed Ali Munassar Ali and Govardhan A (2010)
methods: Review and analysis." arXiv preprint “A Comparison between Five Models of Software Engineering”
arXiv:1709.08439 (2017). International Journal of Computer Science, Vol. 7(5), 98-100.
[6] Pawlak, Michał, and Aneta Poniszewska-Marańda. "Software [24] Tuteja Maneela and Dubey G.(2012) "A Research Study on
Testing Management Process for Agile Approach Projects." Importance of Testing and Quality Assurance in Software
Data-Centric Business and Applications. Springer, Cham, 2020. development life cycle (SDLC)Models" International Journal of
63-84. Soft Computing and Engineering, Vol. 2(3), 251-252.
[7] Padmini, K.V.J. & Kankanamge, P.S. & Bandara, Dilum & [25] http://www.iscanotes.com(2011), 5-6 (accessed 11th July 2013)
Perera, Indika. (2018). Challenges Faced by Agile Testers: A [26] Awad M.A. “A Comparison between and Traditional Software
Case Study. 431-436. 10.1109/MERCon.2018.8421968. Development Methodology” 1-7
[8] Rajasekhar, P. & Yadav, Dr. (2013). Critical Issues in Software [27] Yu Beng Leau, Loo W.K., and Wai Yip Tham.(2012) "SDLC
Testing During Agile Development. Agile vs Traditional Approach", International Conference on
[9] Al-Zewairi, Malek, et al. "Agile software development Information and Network Technology, vol. 37, 162-165.
methodologies: a survey of surveys." Journal of Computer and [28] Harish Rohil and Syan Manisha(2012) "Analysis of Agile and
Communications 5.05 (2017): 74. Traditional Approach for Software development", International
[10] Stolberg, Sean. "Enabling agile testing through continuous Journal of Latest Trends in Engineering and Technology, Vol.
integration." In Agile Conference, 2009. AGILE'09., pp. 369- 1(4),1-3
374. IEEE, 2009. [29] T Bhuvaneswari and Prabaharan S.(2013) “A Survey on
[11] Rajput, Barkha. "Software Quality Assurance Using Agile Software development life cycle model”, Journal of Computer
Software Methodology in Education Assessment Industry." Science and Information Technology, Vol2 (5), 263-265.
(2016). Authorized licensed use is limited to NUST School of [30] Laurie Williams (2007) “A survey of Agile development
Electrical Engineering and Computer Science (SEECS). Methodologies”,215-218.
Downloaded on February 12, 2021, at 07:10:50 UTC from IEEE [31] Schwaber, K., & Beedle, M. (2002). Agile software
Xplore. Restrictions apply. 2020 14th International Conference development with Scrum (Vol. 1). Up-per Saddle River:
on Open Source Systems and Technologies (ICOSST) 978-1- Prentice Hall.
7281-9050-1/20/$31.00 ©2020 IEEE [32] Williams, L. (2010). "Agile software development
[12] Collins, Eliane, Arilo Dias-Neto, and Vicente F. de Lucena Jr. methodologies and practices". Advances in Computers (Vol. 80,
"Strategies for agile software testing automation: An industrial pp.1-44). Elsevier.
experience." 2012 IEEE 36th Annual Computer Software and [33] Chopade, M. R. M., & Dhavase, N. S. (2017). "Agile software
Applications Conference Workshops. IEEE, 2012. development: Positive and negative user stories". 2nd
[13] Stolberg, Sean. "Enabling agile testing through continuous International Conference for Convergence in Technology

Authorized licensed use limited to: Centre de Recherches et des Technologies des Eaux. Downloaded on July 31,2024 at 07:15:35 UTC from IEEE Xplore. Restrictions apply.
 (I2CT) (pp. 297-299). [37] Samar Al-Saqqa, Samer Sawalha, Hiba Abdel-Nabi. Agile
IEEE.https://doi.org/10.1109/i2ct.2017.8226139. Software Development: Methodologies and Trends Article in
[34] Cohen, D., Lindvall, M., & Costa, P. (2003). Agile software International Journal of Interactive Mobile Technologies (iJIM)
development. DACS SOAR Report, 11, 2003. · July 2020..
[35] Franková, P., Drahošová, M., & Balco, P. (2016). "Agile project
management approach and its use in big data management".
Procedia Computer Science, 83, 576-
583.https://doi.org/10.1016/j.procs.2016.04.27
[36] Rijwan Khan, Akhilesh Kumar Srivastava, Dilkeshwar Pandey.
Proceedings of the SMART -2016, IEEE Conference ID: 39669
5th International Conference on System Modeling &
Advancement in Research Trends, 25th_27'h November 2016
College of Computing Sciences & Information Technology,
Teerthanker Mahaveer University, Moradabad, India Agile
Approach for Software Testing Process.

Authorized licensed use limited to: Centre de Recherches et des Technologies des Eaux. Downloaded on July 31,2024 at 07:15:35 UTC from IEEE Xplore. Restrictions apply.