Abstract:
In the past decade, there has been an increased emphasis on software development processes that attempt to link engineers with their deployments in a single system. This trend has given rise to two camps: continuous integration CI and continuous delivery CD, the proponents of "DevOps". The rise of DevOps began with the realization that many separate teams are involved with development, operations and security. DevOps is organizational culture and practice that emphasizes communication, collaboration, and integration between the development teams and information technology operations teams. The goal of DevOps is to tie these teams together in order to reduce the risks associated with each group working in isolation.
DevOps promotes continuous integration and continuous delivery. Due to its benefits, we have decided to use DevOps for critical software development. Critical systems demand high-level of quality and reliability. In this research, we will discuss how we can use DevOps for Critical Software Development to improve quality. We have analysed existing software development methodologies for critical software development and finds gaps and limitations in it. To overcome these gaps, we have proposed a new DevOps-based process model called "DevCritOps". To support this process model, we have provided the supporting guidelines for the better utilization of "DevCritOps" for Critical Systems.
