Evolution of V-Agile Software Development

Life Cycle
Combination of agile and V-Model for Enhancement of Projects
Muhammad Waseem Ghulam Ali (Student) Ifrasaeab Afzal (Supervisor)
(Student) BSEM-F15-255 Department of Software
BSEM-F15-261 Department of Software Engineering
Department of Software Engineering Superior College University
Engineering Superior College University Campus
Superior College University Campus Lahore, Pakistan
Campus Lahore, Pakistan [email protected]
Lahore, Pakistan [email protected]
[email protected]

Abstract— The Software Engineering field has

numerous new models which are familiarizing
day with a day to improve the productivity 1. INTRODUCTION
and viability of the programming
advancement. Because of dynamic condition, There are many ambiguities which are in the
associations are every now and again trading mind of a software engineer, software developer,
their product limitation to meet their customer, and management also. In short, all
destinations. The basic purpose of this stakeholders who interact with the system which
research work is controlling the individual are going to the new build system have some
problems and drawbacks of both Agile uncertainties in mind. Certain complaints exist
Software Development Model and traditional against either excess or fewer of schedule details
V-Model processes in software engineering. given by the management, details are more which
Agile methodology has own unique features cause of over budget of the software, the software
but V-model is also playing a vital role in big didn’t meet the customer’s requirements, more
projects. These both models agile and V-model changing in project cause of the delay of the
used for small and large projects respectively. project, requirements are not fulfilled on the time,
This research tells us, the combination of both etc.
models will be effective, time-consuming,
iterative, user beneficial, and customer There are the diverse kind and distinctive
beneficial. The V-Agile software development scholarly dimension of partners that have
life cycle is providing more convenient, easy distinctive responsiveness, exercises, and
and flexible features to enhance the maturity perspectives as for the given requirements.
level of the projects. Embedded in Agile and V-model (V-Agile)
approach is suitable for this type of stakeholders.
Keywords-component: Software Development This approach is centralized and advance
Life Cycle model (SDLC-model), Agile Model, V- approach to controlling the failure points of the
Model, V-Agile Model, Software Development project. The software failure chances are almost
Project (SDP) too negative if stakeholders fulfill the
requirements according to the proposed V-Agile
SDLC model [1]. For introducing inventive and
crisp programming improvement procedure, it is
expecting that it will upgrade the effectiveness
and efficiency of programming fashioners,
analyzers, and in short whole programming team. represent the agile structure; Arranging,
Programming creation can be clarified as the fundamentals investigation, outline, coding, unit
extent of profitability made by programming testing, and acknowledgment testing.
group and resources utilized by them. The experts
defined profitability questions are: Is
programming group execution most significant as
it considered? Are group members in restriction?
Is exertion being fruitful? The answer to all
software related or management related question
is V-Agile approach which is fulfilling the
important queries associated with the system.
This approach is useful for producing a well-
defined document of the software by software
development and testing team and that document
plays a vital part to produce a profitable product
for stakeholders of the project. Through the
proposed approach, the coordination between the
different teams is increases and reusability of the
code is occur and every company wants to
achieve this technique to controlling the wasting
of time.

Most organizations are using an agile approach 1.2. Agile SDLC Principles
due to the flexibility of time and plan. Agile
development methodology believes in more There are agile SDLC standards which are
interaction with the user rather than detail following by the organization to producing a
processes [2]. For this approach, more experienced product or software for the end user;
persons of every filed those interact with the new
build system is required. The maturity of this  Welcome to developing necessities, even
approach is to enhance the maintenance, in late improvement.
assurance, cooperation, and proficiencies of the  Close each day support among
software by the development team for the businesspeople and architects.
software company [3]. The difficulty increases in  Undertakings are worked around induced
using this approach, when the customer’s demand individuals, who should be trusted.
for the software doesn’t understand by the  Up close and personal talk is the best sort
stakeholders. This cause may be produced the of correspondence.
failure of the product. The feature of agile is  Client satisfaction by in front of
more flexible which generates problem during the timetable and reliable transport of
integration of the software components [4]. Agile significant programming.
methodology is to making software is iterative
and incremental. The small part of the project is
completed then interacts with the customer and 1.3. V-Model SDLC
moves to next step [5].
There are many SDLC models which are used to
1.1. Agile Software Development resolve the problems which occur during the
Approach software project development. Some names of
these are; Water Fall, V-Model, Incremental,
Generally, the agile model believes to break the Agile, spiral, etc. The V-model pronounces
assignment into subtasks and arrange them. This Verification & Validation Model. It is the
is not arranging the whole assignments subtasks, extension of a waterfall model with a test phase
unfortunately. There are some steps which property of each phase and the next phase will be
started when the first phase is completed  Cross-referencing between requirements
successfully. This approach has verification part and testing to check the feasibility of the
of each phase on one side and validation part on software.
another side [6].

2. V-AGILE SDLC MODEL

Agile has more advantages over the V-Model.
The V-Agile SDLC proposed after emerging both
functionalities and resolves both problems. They
give the answer to the software related issue
when we use in programming.

1.4. V-Model SDLC Principles

There are V-Model SDLC standards, which are

following by the organization which are working
on large scale projects to producing a fine Requirement Analysis:
product or software for the end user [7]; The requirements gathering team gets the
requirement from the customer and analyzes
 This approach is refining the raw those problems.
information from large data. System Design:
 Data and processes of the project are The system analyst gives the proposed solution
integrated to accomplish the defined plan. by providing features of the software. They
 The V-Model has the scalability of the provide the general design of the software.
project. Review System Design & Requirement
 They have tangible documentation of the Analysis:
project. This is the advancement feature in V-Model.
Sometimes, requirements are missing,
requirements didn’t relate with system design or
vice versa. All modification or changing in investigation to the subsequent grid and huge
requirements write in this phase. relationship results prescribed for iterative and
Updated System Design: steady improvement.
The new information, getting from both user and
company stakeholders and make an updated Distinctive understood fifteen components
version of the requirements. undertaking frames invalid examination
Review Architecture & System Design: lightweight testing engineering and course of
In this phase, compare the general system design action conventional noticeable quality insistence
and architecture design to resolve the ambiguity program morals unimportant necessities iterative
and problems of the system in which the and gradual improvement and correspondence
company is going to build. process database preparing correspondence
Updated Architecture Design: practice and nimble practices declaration
After the team meetings, the stakeholders meet correspondence group program thought and audit
with each other to making a complete version of adjustment were dissected [7].
the software and this information apply on text
phase of the project. Software is a gathering of programs and related
Other Phase: facts and figures that provides the guidelines to
The other phases are working same like v-model. articulate a computer what to do and how to do
this and how it could be performed [8]. The
3. LITERATURE REVIEW collection of programs and information construct
the structure of software. Any update is called a
This is a proposed solution for both SDLC change or modification in the structure of
models. In this model, the agile technique is software. Dynamic changes occur in a system
embedding in V-Model processes. As we know without any disturbance upgrades any running
that, the agile model less accept documentation, system, is a type of software development.
but if we think in these days documentation of
each process is necessary to do solve the The Agility Profiler a matrix that initiatives
problems, manage the information, to satisfy the struggle for occasionally radical renovations to
customer, to make a record of the software which stand and expand their effectiveness. Below
is building process. present unclear and unsettled situations in several
The second point is that the V-Model is working competitive situations, agility is frequently
with its own characteristics but the features are required and considered a feasible strategy.
adding in it is to adopt the changing. e.g.; a Agility requirements are well known in what way
customer wanted a software in 6 months of time. its existing competencies can be enhanced and
They give all the information about the software difficulties can be minimized [9]. The profiler
with his agreement. After a month, he wants supports company fined motorist aims resources
more features in the software, then what we do? and obstacles to refining agility. There is no that
We are not adding more information and features type of thing which are bad or good a profile as a
because we are using v-model. To solve this type profile it specifies the strategy of organizations.
of problem, the research work shows the
advancement of the V-model with the emerging In light-footed (Agile Model) programming
agile model. advancement limited thought is engaged in
beginning the theoretical establishments.
Different Agile methodologies close around fifty- Subsequently, between the odds and
eight practices connected to check their viability. preliminaries that lie ahead for agents is to
Very nearly fifteen variables thought about and separate irregularity over the exploratory works
[10].
related to their practices accomplishment of the V model distinguishes for its adjusted testing
undertaking. These components join with the types like measured, testing and reconciliation,
improvement routine with regards to the spry testing.
procedure. They connected Correlations among There exist a relationship between Confirmation
the dug highlights were expected for the and Authentication arranges being developed
procedure. On the off chance that there is the of practices that consider quick modifications
nearness of a few blunders through improvement organizing the present thing improvement needs
[15]
because of the inadequacy of different stages than despite the way that the estimation of the spry
on inverse contiguous of the resultant stage is methods of insight is all around shown for lithe.
rehashed [11]. The purpose behind picking the v Updates are seen on the quality and on the
model amid medicinal gadget, programming customer impression of the completed thing,
advancement is fit with firm prerequisites as it while light-footed systems consider essential
controls the organization to make fundamental changes even late in the endeavor. Meanwhile,
arrivals of programming to test the tyrant building better correspondence and collaboration
conformance. in the gathering because of taking after the light-
footed practices, results in updated relations
The effects of agile methodologies in business among associates and to upgraded agent
advancements and endeavor to decide in what satisfaction estimations.
sort of conditions this is profitable to put on such
methodologies [12]. 4. Characteristics of V-Agile SDLC model:
 Project Risk Reduction: The reason
Despite the fact that the significant spotlight progression or advancement of the model
progresses toward becoming on the evolvement upgrades the ease of the undertaking and
of the light-footed relationship with their adventure control by deciding solid
accomplishment. The significant results watched techniques and spreading out the ensuing
for utilization of coordinated methodologies were outcomes and capable parts.
relevant the capacity to needs for the executives  Quality Needs: As the procedure model
of changes and for essential advancement system uses a set of institutionalized procedures
quality, client satisfaction and fulfillment for that guarantee the discoveries to be given
venture reflectivity. are finished and having wanted quality.
 Cost Reduction: By selecting a fitting
The development has a fringe definition and model for every improvement stage
thinks about that Agile Maturity Model could expense of the venture diminished.
wind up supportive helpful for the associations.  Project Scalability: It is the limit of the
Development tended to with the structure mutt (half) procedure model to be
determined component of groups. That checks the flexible in term of endeavor measure. It
connected pertinence of the results available here works commendably for little to mega
[13]
. Moreover, the connected pertinence of results assessed adventures.
is approved in new readings that consider Agile  Requirement Gathering Model: The
Maturity Models supporting the prerequisite for a heads and gathering of the item designs
new imaginative strategy to expand development have their very own commitments that
in coordinated. By correcting the v-model in are designated before the incitation of the
separating technique, recognizability can be sure undertaking. There are steps to follow the
of exertion parcels. Through that technique organization on the incitation time of the
limitation related exertion partition is having a requirements gathering;
place with least single undertaking thing and o Requirements are orchestrated
individual test classification work article [14]. into sets by separating them.
Configuration related work cut to littlest than one o The management assigns the
part and test class thing. At any rate portion sort particular undertakings among
work thing is connected to single test improvement group.
classification of thing. o The Development bunch (Team)
correspondence about the
Conventional programming headway methods are problem with the customers to
inflexible and disregard to respond on get the point by point
commanding customer requests. Strangely, swift prerequisites.
programming rationalities give a course of action
 o Deliver the total endeavor with [3]
Inayat, I., Siti.S. S., Sabrina S.and MayaD.”
its documentation to troughs. Agile requirements engineering practices and
challenges” Journal of Computers in Human
5. CONCLUSION
Behavior. 51(1): 915929, 2015.
To complete this Research 20 questions were [4]
made by dissecting the past history of the agile Agrawal, A., Atiq, M.A”. and MauryaL.S.” A
and V model to check the quality characteristics Current Study on the Limitations of Agile
as plan determination and prerequisite detail. Methods in Industry Using Secure Google
Diverse programming houses were visited and Forms”Procedia Computer Science, 78, 291-297,
they responded to the overview question.
The respondents of the overview included as 2016.
under programming frameworks engineer, IT [5]
chiefs, programming architects and programming Babar, M., NyugenV., CukI.R. Kamphuis,
designers. The appropriate responses gathered Bongaerts, M and Z. Hanzelka.”The rise of AGILE
from the distinctive foundation having demand response: Enabler and foundation for
respondents, they give various perspectives and change” Journal of Renewable and Sustainable
investigation and how reuse incorporates handy
Energy Reviews. 56(1): 686-693, 2016.
and non-specialized perspectives. About half of
the respondents (28 donors) engaged accomplish [6]
accomplishment in programming plans owed to
reuse of the product which is an extraordinary https://www.tutorialspoint.com/sdlc/sdlc_v_mo
favorable position. del.htm
[7]
89.8% male and 10.2% female respondents https://www.geeksforgeeks.org/software-
experienced from all out 50 respondents. Sort of engineering-sdlc-v-model/principles
designers was for the most part programming
architects and 98 % reactions about their [8]
Abbas, N., Gravell A.M. and WillsG.B.” Using
experience. factor analysis to generate clus-ters of agile
practices – a guide for agile process
6. REFERENCES improvement” In: Agile Conference. pp. 11–20,
2010.
[1]
Ahmad, A., GoranssonM., KollaS.J., ShahzadA.,
[9]
Arfeen Q. and ArshadZ. Requirements Lai, R., GargM., Kapur P.K. and ShaoyingL.” A
Development Life Cycle with Respect to study of when to release a Software Product
Geographically Distributed Stakeholders: The" V" from the perspective of Software Reliability
Model. In: Information Technology”New Models” Journal of Software. 6(4):651-661, 2011.
Generations Eighth International Conference. pp: [10]
Dingsoyr, T., NerurS., Balijepally V. and
1076-1077, 2011.
MoeN.B.,”Decade of agile methodologies:
[2]
Chuang, S.N., Tainyi L. and towards explaining agile software
TainyiP.“Assessment of institutions, scholars, development”Journal of System and
and contributions on agile software Engineering. 85(1):1213-1221, 2012.
development “The Journal of Systems and [11]
McHugh, M., Cawley.O., McCaffcry.F.,
Software. 93(1): 84-101, 2014.
Richardsonand I. and WangX. ”An Agile V-model
for medical device Software Development to
overcome the challenges with plan-driven
software development lifecycles”In: Software
Engineering in Health Care, 5th International
Workshop. 1(1):12-19, 2013.
[12]
Melo, C.O., Santos.V., Katayama.E.,
Corbucci.H., Prikladnicki.R., Goldman A. and Kon.
F.”The evolution of agile software development
in Computer” Journal of Systems and Software.
19 (4): 523-552, 2013.
[13]
Deuter, A and Engels. G.”Measuring the
Software Size of Sliced VModel Projects” In:
Software Measurement and the International
Conference on Software Process and Product
Measurement, Joint Conference of the
International Workshop. 2(1): 233242, 2014.
[14]
Papadopoulos, J, ”Moving from traditional to
agile software development methodologies also
on large, distributed
[15]
Silva, F.S., Felipe.S. F. S., Angela.L. P.,
Ivanildo.M. A., Ana.L. F. P., Fernando K. K. and
Silvio. R. L. M.”Using CMMI together with agile
software development”Journal of Information
and Software Technology. 58(1): 20-43, 2015.
[16]
Yetunde, A and KoladeW.”Integrating
usability work into a large inter organizational
agile development project Tactics developed by
usability designers”The Journal of Systems and
Software. 100(1): 54-66, 2015.