Modern DevOps: Optimizing software development through effective system interactions
Authors:
- 1 October 2014
- conference paper
- Published by Institute of Electrical and Electronics Engineers (IEEE)
- No. 2158091X,p. 1-7
Abstract
Software development processes are fundamentally based on efficient and effective communication. Communication between engineers, between engineers and managers, and between teams and clients are all essential components of a successful project. Requirements must be effectively transferred from client to engineer, specifications must be transitioned from architect to engineer, and constant communication between project team members, managers, and clients throughout the project life cycle is critical to the success of projects of any complexity. To succeed in a world where technologies, requirements, ideas, tools, and timelines are constantly changing, information must be accurate, readily available, easily found, and ideally delivered constantly, in real-time, to all team members. To meet these challenges, modern software development has evolved to encompass key concepts of adaptability to change and data-driven project management. A recent movement dubbed DevOps has attempted to use automated systems to bridge the information gap between project team entities and to enforce rigorous processes to ensure real-time communications. In this paper, the authors frame this challenge as a communications problem that can be addressed by the introduction of specifically designed autonomous system actors and processes. Successful implementation of such a methodology will enable efficient, effective, and immediate data collection, synthesis, and transfer of information between all requisite entities within the software project. A generalized model of DevOps will be presented and analyzed, offering a formalization of the communications and actors requisite to any effective software development process. These concepts will be further developed to illustrate the information flow between human and system actors, and explore how this model can be used to optimize the processes of a software development team to maximize productivity and quality of work products.Keywords
This publication has 13 references indexed in Scilit:
- Software Analytics in PracticeIEEE Software, 2013
- The wisdom hierarchy: representations of the DIKW hierarchyJournal of Information Science, 2007
- A diary study of task switching and interruptions2004
- Metric-driven analysis and feedback systems for enabling empirically guided software development2002
- An Investigation of Memory for Daily Computing Events2002
- Agile software development: the business of innovationComputer, 2001
- What Brings Intentions to Mind? An In Situ Study of Prospective MemoryMemory, 1997
- Using a defined and measured Personal Software ProcessIEEE Software, 1996
- A spiral model of software development and enhancementComputer, 1988
- Evolutionary Delivery versus the "waterfall model"ACM SIGSOFT Software Engineering Notes, 1985