Rapid Release Model for Software Development

The assignment discusses the software company TSU, which is implementing rapid release model to shorten their project delivery duration. The model involves dividing projects into parts and delivering them in a 90-day cycle. This approach has several advantages, including quick delivery, good quality, and encouraging collaboration between developers and clients. However, it also has some disadvantages, such as being less suitable for smaller or complex projects.

Running head: PROGRAM AND PROGRAM MANAGEMENT 1
Portfolio Entry 2 – Rapid Release
Student Name
Institution

PROGRAM AND PROGRAM MANAGEMENT 2
Introduction
In this portfolio, we will discuss the software company TSU, which is based in Perth. It
has 21 employees and currently making software for an Australian Company Oz Chips. Although
the company manages to deliver the projects, currently they are facing an issue of a long time.
So, shorten their duration, the company is now focusing on implementing rapid release model,
which will help in dividing their PLC into parts and this will shorten the duration of the
competition of projects. In this report, we will discuss how rapid release will help TSU in
fastening their delivery of projects (Mäntylä, Adams, Khomh, Engström, & Petersen, 2015).
RAD which is also known as Rapid Application Development, describes a strategy for
the development of software that underlines repeater distribution and rapid model. In this
manner, the RAD model is a rapid decision of ordinary waterfall development model which is
often focused on sequential design practices and planning. For the first time in the book of James
Martin in 1991, it was introduced with the same name, the Rapid release has turned out to be an
important strategy amongst the most famous and powerful advancement strategies, which goes
under the development strategy of agile.
Advantages and Disadvantages of TSU’s approach
Transferring software development schedule in a cycle of 90 days give the product
enough advantages to both the software developers and consumer. For the buyers of software or
client like TSU have, this is the way for quicker access to new functionality and features and
better programming quality. For software developers, this implies better project management,
less risk and market agility (Silva, Carneiro, Abreu, & Monteiro, 2017).
Rapid releases of significant versions are just for psychological impact and there is no
impact on the speed of delivery of new features. "This is both valid and false. In a case that

PROGRAM AND PROGRAM MANAGEMENT 3
development is incremental and completely worked by a fixed roadmap, there is no strong
difference among" fast "and normal release cycle. It is trusted that for this situation, the
significant version bumps are for the most part psychological. Even so, in the event that you
adopt an iterative strategy for development and make a external learning from end client within
your procedure, at that point a quick release cycle gives you the chance to change the course
dependent on feedback from outside (Khomh, Adams, Dhaliwal, & Zou, 2015).
Advantages:
The first advantage is Quick Delivery, quicker turnaround time is the most fundamental
aspects indisputably that used to make the rapid release a correct choice for an engineer. Rapid
release model development incorporates quick prototyping with software development tools
which enable engineers to reuse the codes that were generated previously, hence saving critical
time for manual coding.
The second advantage is good quality: As a totally iterative methodology, Rapid Release
enables engineers to execute consistent iterations inside the prototype by figuring in end-client
feedback, reviews, and recommendations. This basically does not influence in general
application design and its functionality. Note that Rapid Release empowers the division of a
specific advancement project in numerous modules where every module is considered as the
main model. Designers can incorporate stringent test cycles in every prototype to guarantee that
the last item is total without bug and the quality is consistent (Costa, McIntosh, Treude, Kulesza,
& Hassan, 2018).
Third is that rapid release encourages upgraded collaboration between end-clients,
developers and customers in each progression of the process of design, deployment and
development. Joining every stakeholder is especially useful in situations where the client's

PROGRAM AND PROGRAM MANAGEMENT 4
necessities are uncertain or not fixed. The expanded partnership between both the developer and
the user eliminates interval communication and guarantees that the development team has the
chance to work at the feedback of the client.
Statistic demonstrates that around 65% of the whole IT budget plan is spent on existing
framework support. Routinely updating these legacy systems turns into a difficult and time-
consuming assignment. Rapid Release promotes the development of sophisticated programming
applications, which are not hard to maintain and upgrade.
Disadvantage:
Rapid releases can't be utilized for nearly smaller projects, which are extremely complex
or exceptionally identified with being viably isolated, and it is something that goes about as its
significant drawback. Indeed, this isn't reasonable for projects with a low margin of resources
since the cost of code generation and modelling is very high. The rapid release incorporates
complex levels of testing and prototyping, in this manner, it requires the intervention of
exceptionally talented engineers, who can participate nearly on various grounds including
development, design, and innovation (Souza, Chavez, & Bittencourt, 2015).
Extension to other organization
From what I have learnt, I think that rapid release as an iterative programming design
approach which has developed over a long time and currently advancing more. A designer will
appreciate the level of comfort given in the whole lifecycle of development. The opportunity to
prototype the basic idea demonstrates the end client for the capacity to respond, and after that
taking out the final has helped in making bug free services.

PROGRAM AND PROGRAM MANAGEMENT 5
Bibliography
Costa, D. A., McIntosh, S., Treude, C., Kulesza, U., & Hassan, A. E. (2018). The impact of rapid
release cycles on the integration delay of fixed issues. Empirical Software Engineering,
23(2), 835-904. Retrieved 10 27, 2018, from
http://dblp.uni-trier.de/db/journals/ese/ese23.html
Khomh, F., Adams, B., Dhaliwal, T., & Zou, Y. (2015). Understanding the impact of rapid
releases on software quality. Empirical Software Engineering, 20(2), 336-373. Retrieved
10 27, 2018, from http://dblp.uni-trier.de/db/journals/ese/ese20.html
Mäntylä, M. V., Adams, B., Khomh, F., Engström, E., & Petersen, K. (2015). On rapid releases
and software testing: a case study and a semi-systematic literature review. Empirical
Software Engineering, 20(5), 1384-1425. Retrieved 10 27, 2018, from
https://link.springer.com/article/10.1007/s10664-014-9338-4
Silva, A. C., Carneiro, G. d., Abreu, F. B., & Monteiro, M. P. (2017). Frequent Releases in Open
Source Software: A Systematic Review. Information-an International Interdisciplinary
Journal, 8(3), 109. Retrieved 10 27, 2018, from http://mdpi.com/2078-2489/8/3/109/htm
Souza, R. F., Chavez, C., & Bittencourt, R. A. (2015). Rapid Releases and Patch Backouts: A
Software Analytics Approach. IEEE Software, 32(2), 89-96. Retrieved 10 27, 2018, from
http://dblp.uni-trier.de/db/journals/software/software32.html