All were focused on a central issue that was ending up more pervasive over a developing number and assortment of IT associations: How would we conquer any hindrance amongimprovement and activities for the advancement of the business? Let me put in a simpler way. Have you seen Google or Amazon or Facebook or any of these kinds of giants go down for their work/ enhancements? Downtime (Time in which Application is inaccessible) of such giants can cause them in millions. Hence to sort with this a culture of continuous integration and Development was alluded as Development plus Operation (DevOps). let’s emphasize on the expression “DevOps” which regularly alludes to the rising proficient development that backers a community-oriented working connection among improvement and IT activities, bringing about the quick stream of arranged work (i.e., high convey rates) while at the same time expanding the dependability, steadiness, flexibility, and security of the creative environment.
How to cite this article:
Khator M. DevOps. J Engr Desg Anal 2020; 3(2): 104-105.
Henderson-Sellers B. Process metamodelling and process construction: examples using the OPEN Process Framework (OPF). Ann Softw Eng 2002; 14(1&4): 341-362.
Henderson-Sellers B, Serour M, McBride T et al. Process construction and customization. Journal of Universal Computer Science 2004; 10(3). online journal accessible at http://www.jucs.org
Kumar K, Welke RJ. Methodology engineering: a proposal for situation-specific methodology construction. In Challenges and Strategies for Research in Systems Development (eds. W.W. Cotterman and J.A. Senn), J. Wiley, Chichester 1992; 257-269.
Method fragment definition. FIPA Document, http://www.fipa.org/activities/methodology.html, (Nov 2003).
OMG. Software Process Engineering Metamodel Specification, Version 1.0, Object Management Group, formal. 2002.
Ralyté J. Towards situational methods for information systems development: engineering reusable method chunks, Procs. 13th Int. Conf. on Information Systems Development.
Advances in Theory, Practice and Education Vilnius Gediminas Technical University, Vilnius, Lithuania 2004; 271-282.
Ralyté J, Rolland C. An assembly process model for method engineering, Advanced Information Systems Engineering), LNCS2068, Springer 2001: 267-283.
Ralyté J. Reusing scenario-based approaches in requirement engineering methods: CREWS method base. Proc. of the 10th Int. Workshop on Database and Expert Systems Applications.
Copyright (c) 2021 Journal of Engineering Design and Analysis
This work is licensed under a Creative Commons Attribution-NonCommercial 4.0 International License.
We, the undersigned, give an undertaking to the following effect with regard to our article entitled
________________________________________________________________________________” submitted for publication in (Journal title)________________________________________________ _______________________________________________________Vol.________, Year _________:-
1. The article mentioned above has not been published or submitted to or accepted for publication in any form, in any other journal.
2. We also vouchsafe that the authorship of this article will not be contested by anyone whose name(s) is/are not listed by us here.
3. I/We declare that I/We contributed significantly towards the research study i.e., (a) conception, design and/or analysis and interpretation of data and to (b) drafting the article or revising it critically for important intellectual content and on (c) final approval of the version to be published.
4. I/We hereby acknowledge ADRs conflict of interest policy requirement to scrupulously avoid direct and indirect conflicts of interest and, accordingly, hereby agree to promptly inform the editor or editor's designee of any business, commercial, or other proprietary support, relationships, or interests that I/We may have which relate directly or indirectly to the subject of the work.
5. I/We also agree to the authorship of the article in the following sequence:-
Authors' Names (in sequence) Signature of Authors
1. _____________________________________ _____________________________________
2. _____________________________________ _____________________________________
3. _____________________________________ _____________________________________
4. _____________________________________ _____________________________________
5. _____________________________________ _____________________________________
6. _____________________________________ _____________________________________
7. _____________________________________ _____________________________________
8. _____________________________________ _____________________________________
(I). All the authors are required to sign independently in this form in the sequence given above. In case an author has left the institution/ country and whose whereabouts are not known, the senior author may sign on his/ her behalf taking the responsibility.
(ii). No addition/ deletion/ or any change in the sequence of the authorship will be permissible at a later stage, without valid reasons and permission of the Editor.
(iii). If the authorship is contested at any stage, the article will be either returned or will not be
processed for publication till the issue is solved.