Report: Comparing DevOps and RAD Methodologies for System Development

This report provides a comparative analysis of two system development methodologies: DevOps and Rapid Application Development (RAD). The study begins with an investigation into the core principles and practices of each methodology, highlighting their unique approaches to software development and deployment. A critical analysis of both DevOps and RAD is then presented, evaluating their respective strengths and weaknesses in the context of enterprise-wide information system updates. The report considers factors such as collaboration, risk management, security, and scalability. A comparative section directly contrasts the two methodologies, emphasizing their key differences and similarities. Finally, the report concludes with a recommendation for the most appropriate methodology for the given project scenario, considering the specific requirements of updating an enterprise-wide information system with a web-enabled front-end and SQL Server database. The report also includes a summary of findings, references, and an appendix.

Running head: SYSTEM DEVELOPMENT METHODOLOGY COMPARISON REPORT
System Development Methodology Comparison Report
Name of the Student
Name of the University
Author Note

1SYSTEM DEVELOPMENT METHODOLOGY COMPARISON REPORT
Table of Contents
Introduction................................................................................................................................2
Investigation for the DevOps as a system development methodology..................................2
Investigation for the RAD or Rapid Application Development as a system development
methodology...........................................................................................................................4
Critical analysis of DevOps as a system development methodology....................................4
Critical analysis of RAD or Rapid Application Development as a system development
methodology...........................................................................................................................6
Comparison of both the methodologies.................................................................................6
Summary of the findings........................................................................................................7
Recommendation of the appropriate methodology to be used...............................................8
References..................................................................................................................................9
Appendix..................................................................................................................................11

2SYSTEM DEVELOPMENT METHODOLOGY COMPARISON REPORT
Introduction
Development of software, even when it is associated with the updating procedure of
an existing website is associated with the accepting of a proper methodology for which the
system would have a standardized procedure to follow. The organization has been thinking
about implementing the same for the updating procedure for the information system. The
implementation would be done throughout the entire enterprise. This is why, the system has
also been thinking about the proper inclusion of the accession ability for the intranet of the
organization with a web-enabled front end and at the same time develop a Microsoft SQL
Database for the storage and the manipulation of the organizational data regarding the policy
document and reports (Soni & Kohli, 2017). The development procedure would begin within
the organization with in-house resources. At the same time, the system development
methodologies would also be kept into consideration to find out which of them would be the
most appropriate of all of them for the project. The considerations, in this case, are about the
two methodologies that are being thought about, the DevOps methodology and the RAD or
Rapid Application Development methodology. The following would be a comparison report
based on the consideration of both these with a proper investigation and critical analysis for
both of them. In the end, there would be a proper representation of both the methodologies
where the recommendation of the most appropriate amongst the two would be identified and
the reasons for the same would be shared.
Investigation for the DevOps as a system development methodology
DevOps is regarded as one of the most popular integrated systems methodologies as
per the recent practices. The set of practices that help in the systems development is built
with the development of the software and the information technology operations. The name
of the systems development methodology has also been derived from the combination of the
set of practices (Francis, Nunez Lloyd & Torres, 2019). The procedure has the ability to
shortening the life cycle for the systems development where the continuous delivery of the
development procedure as well as increasing the quality of the software.
This methodology allows both the personnel or engineers for the operations and
development for the system to participate in the service lifecycle together. The involvement
of both kinds of engineers are involved throughout the development procedure and the
support after the production even. The methodology has been identified as a mindset that an
organization can develop during the system development methods and procedures. The

3SYSTEM DEVELOPMENT METHODOLOGY COMPARISON REPORT
amalgamation of both aspects of operations and development are seen to be present in the
DevOps development methodology. When an organization is looking forward to
implementing the DevOps technique of methodology for the development of a system,
therefore, it can be regarded as the specific mindset of an organization to reach several
identified goals. These can be listed as follows:
 The planning of the system is being looked forward to through the
implementation of DevOps only for the inclusion of the value stream and the
development of the automated and continuous pipeline for development.
 The organization must be looking forward to increasing its frequency and the
deployment quality from the existing ways in which it was carried out
previously through the DevOps development methodology.
 The way by which the organizations are trying out to implement the DevOps
development methodology might mean that the organization is looking
forward towards the application of innovations towards the approaches of the
safer environment for performing any experiment (Erich, Amrit & Daneva,
2017).
 The organization might implement the DevOps development methodology as
it has understood the importance of the utilization of a faster market approach
and how to make a better move at being in synchronization with the same.
 The organization must be looking forward to having a better implementation
of the quality of time to be invested in the solution of any problem arising at
the juncture throughout the development procedure, which is why the
organization has been looking forward to implementing the DevOps
development methodology.
 The urge of an organization to have a better aim at reducing the severity and
the failure issues might be another goal for which the organization have been
looking forward to the implementation of DevOps development methodology
for the development of the organizational systems.
 The organization might be reached at the goal to improve the Mean Time to
Recovery or the MTTR for which they have been looking forward to the
DevOps development methodology for the development of their systems.
These reasons, as well as the urge of a business to share a business environment of an
associated culture involving people from a different department to have a collaborative work

4SYSTEM DEVELOPMENT METHODOLOGY COMPARISON REPORT
environment can also be developed with the implementation of the DevOps development
methodology. DevOps development methodology can understand the manual procedures that
are involved with the procedures required for the delivery. The methodology understands the
automation procedure that the organization has been utilizing and has a faster learning
module between the understanding of the customer demand and the market demand as well.
Investigation for the RAD or Rapid Application Development as a system
development methodology
One of the typically used sources or suites for the system and software development
used in the organizations are RAD or Rapid Application Development. This is a methodology
that defines a prototyping technique that is defined previously. There are several ways by
which the prototyping technique and tools can be implemented for the development of
applications, which is why the RAD technique uses the GUI or Graphical User Interphase for
the development of the software (Soni & Kohli, 2017). Simply putting it, the RAD or Rapid
Application Development is a methodology where the development process follows the
utilization of GUI interphase with predefined tools and techniques. Therefore, any person
who is trying to develop the system or software for the organization can have a controlled
atmosphere where the software can be developed just by dragging and dropping techniques as
per the requirements for the development for the software application components.
The ease of use for the RAD or Rapid Application Development methodology has
made it even mode accepted amongst the people as it needs minimum incorporation of
development codes or syntax. The methodology is easy to pick up.
Critical analysis of DevOps as a system development methodology
The analysis of the DevOps development methodology in a critical manner may not
only find out the advantages of the system as a service for any organization but might also
result into the disadvantages of the business through the systems. Where on the other hand,
there might be incidences that might result into several aspects of the difficulties in the
development procedure that might not involve the likes of the advantageous positions during
the development of a system (Olagunju, 2018). As per the identification of the advantages of
the system, it can be seen that the DevOps development methodology enables the
organization to collaborate amongst its existing organizational employees and at the same
time can tolerate and handle the risks occurrences with the easiest and the most feasible

5SYSTEM DEVELOPMENT METHODOLOGY COMPARISON REPORT
solutions. There are situations where the infrastructure has self-servicing empowerment and
has a mindset that can provide the ability to automate everything possible.
However, there might be occurrences where the aspects of the development
methodology for DevOps development methodology can even cause problems to the
organization when it comes to the implementation for information system development
followed by the implementation of the web enables front-end for the intranet being used in an
organization and the SQL server database. DevOps development methodology also has
several drawbacks, for which the advantages may sometimes be not considered as an
appropriate system for the development. The critical analysis of the DevOps development
methodology as a service has figured out the following probability for which the DevOps
development methodology might be disadvantageous to the development of the system:
 The organization, in this case, is not looking forward to the implementation of
DevOps development methodology through outsourcing facilities, and this is
why it would not face this identified issue. However, there are incidences
where outsourcing the DevOps development methodology has resulted into a
disadvantageous move for an organization as an in-depth understanding of the
integration procedure is not at all realized (Gill, Loumish, Riyat & Han,
2018). Furthermore, the DevOps development methodology can be
misleading for the organization due to outsourcing as the organization, and its
workflow orchestration or infrastructure might not be clear to the outsources.
Since this organization is thinking of orchestrating the ingenious employees
within the organization for the development procedure, this would not be
posing as a problem.
 The DevOps development methodology sometimes requires the cloning of the
enterprise infrastructure, which might even lead to issues related to the
compatibility of the productive environment and the environment that has
been thought about. It is difficult to implement or clone an environment in the
cloud which particularly has no existence.
 The major concern about the DevOps development methodology is the
security issues that are not at all a part of the system. Thus, it would be even
riskier a situation for the organization to clone the system in the cloud. There
might be chances of severing exposure, and also, the insecure transport layer

6SYSTEM DEVELOPMENT METHODOLOGY COMPARISON REPORT
might cause a favourable situation for the cybercriminals to barge into the
system.
Critical analysis of RAD or Rapid Application Development as a system
development methodology
As per the critical analysis was done for the RAD or Rapid Application Development
as a system development methodology, there are several aspects in the development strategy
that might prove that it is not the most appropriate system development methodology that
needs to be used (Armstrong, Rosario Rivera, & Wagner, 2019). Of course, it is needless to
mention that the application of the methodology would be easier to implement and there
would be no requirement of core website development personnel as the system development
would be easier with the tools and techniques that are predefined.
The most difficult situation that a developer or any person using the RAD or Rapid
Application Development might face is the lack of the full-scale functionality of the system.
This is why, it would be easier to say that for a full-scale functioning website, RAD or Rapid
Application Development might not be appropriate as it would be best suited for the
demonstration and requirement gathering functionalities. Besides, the customization of the
system is difficult to attain for the system being predefined and non-customizable.
Comparison of both the methodologies
Following would be a comparison of both the technologies so that the advantages and
the disadvantages of both the methodologies can be identified:
DevOps Development Methodology RAD or Rapid Application Development
1. It is a system development methodology
that allows the amalgamation of the
operations and the development department.
Both the department and their personnel can
work side by side for the development of
the system according to the requirements
(Jabbari, Ali, Petersen & Tanveer, 2016).
2. It has issues regarding the development
procedure as the cloud cloning during the
development planning would be
problematic, and also might be issues
1. The RAD methodology defines a
prototyping technique that is defined
previously (Poulovassilis, Larsson, Candlin
Larkin & Ballatore, 2019). There are several
ways by which the prototyping technique
and tools can be implemented for the
development of applications, which is why
the RAD technique uses the GUI or
Graphical User Interphase for the
development of the software.

7SYSTEM DEVELOPMENT METHODOLOGY COMPARISON REPORT
regarding the security of the system. 2. Full-scale functionality and the
customization would be difficult to attain
with the predefined tools and techniques.
Summary of the findings
The findings lead the report in finding out a website for Duta Tani, which was
developed through the RAD methodology. The website is poorly constructed and appears as a
prototype, which functions poorly.
Figure 1: Cuts and Bruises Website
(Source: cutsandbruisesbarbershop.com, 2019)

8SYSTEM DEVELOPMENT METHODOLOGY COMPARISON REPORT
The following is the development of a software or website for Netflix as done with
DevOps. This defines the clarity in the development procedure.
Figure 2: Netflix Website
(Source: Netflix.com, 2019)
Recommendation of the appropriate methodology to be used
Therefore, according to the findings as above, it would be easier to recommend that
the appropriate methodology for this purpose would be the RAD development methodology
and it can use the software Wix for the development of the software. It has been
recommended as it would be easier to implement considering the organization is looking
forward to implement the people within the organization. The predefined tools would not
require intense knowledge for coding and would be easier to implement.

9SYSTEM DEVELOPMENT METHODOLOGY COMPARISON REPORT
References
Armstrong, B., Rosario, A., Rivera, M., & Wagner, T. (2019). Prototyping Rapid Application
Development with Rut. Software engineering and CS Journal, 9(1).
Cuts and Bruises. (2019). Retrieved 14 October 2019, from
https://www.cutsandbruisesbarbershop.com/
Day, D., Boyd, J., Holden, C., & Ramirez, J. (2019). Deployment of Rapid Application
Development. Recent advances in software engineering and computer science, 8(1).
Erich, F. M. A., Amrit, C., & Daneva, M. (2017). A qualitative study of DevOps usage in
practice. Journal of Software: Evolution and Process, 29(6), e1885.
Francis, K., Nunez, J., Lloyd, C., & Torres, C. (2019). Exploration of Rapid Application
Development. Systems and Software Engineering Publication, 3(1).
Gill, A. Q., Loumish, A., Riyat, I., & Han, S. (2018). DevOps for information management
systems. VINE Journal of Information and Knowledge Management Systems.
Jabbari, R., bin Ali, N., Petersen, K., & Tanveer, B. (2016, May). What is devops?: A
systematic mapping study on definitions and practices. In Proceedings of the
Scientific Workshop Proceedings of XP2016 (p. 12). ACM.
Netflix United Kingdom – Watch TV Programmes Online, Watch Films Online. (2019).
Retrieved 14 October 2019, from https://www.netflix.com/
Olagunju, A. O. (2018, September). Revamping the IT Curriculum with Agile and DevOps
Methodology. In Proceedings of the 19th Annual SIG Conference on Information
Technology Education (pp. 86-86). International World Wide Web Conferences
Steering Committee.
Poulovassilis, A., Larsson, N., Candlin, F., Larkin, J., & Ballatore, A. (2019). Creating a
Knowledge Base to research the history of UK Museums through Rapid Application
Development. ACM Journal of Computing and Cultural Heritage.
Soni, D., & Kohli, P. J. (2017). Cost estimation model for web applications using agile
software development methodology. Pertanika Journal Of Science &
Technology, 25(3), 931-938.

10SYSTEM DEVELOPMENT METHODOLOGY COMPARISON REPORT
Soni, D., & Kohli, P. J. (2017). Cost estimation model for web applications using agile
software development methodology. Pertanika Journal Of Science &
Technology, 25(3), 931-938.

11SYSTEM DEVELOPMENT METHODOLOGY COMPARISON REPORT
Appendix
Figure 3: Developed Website by Wix
(Source: Created by Author)

12SYSTEM DEVELOPMENT METHODOLOGY COMPARISON REPORT
(The website is available at https://jack143jones.wixsite.com/developmentmethodos)