🌁Software Engineering: DevOps (Definitions)

"An application delivery philosophy that stresses communication, collaboration, and integration between software developers and their information technology (IT) counterparts in operations. DevOps is a response to the interdependence of software development and IT operations. It aims to help an organization rapidly produce software products and services." (Pierre Pureur & Murat Erder, "Continuous Architecture", 2015)

DevOps is an approach based on lean and agile principles in which business owners and the development, operations, and quality assurance departments collaborate to deliver software in a continuous manner that enables the business to more quickly seize market opportunities and reduce the time to include customer feedback. Indeed, enterprise (Sanjeev Sharma & Bernie Coyne, "DevOps For Dummies" 2nd Ed, 2015)

"Is a method for software development and management that integrates the development and deployment cycles to achieve a more agile, continuous evolution of software-based products and services" (Diego R López & Pedro A. Aranda, "Network Functions Virtualization: Going beyond the Carrier Cloud", 2015)

"DevOps is a mindset, a culture, and a set of technical practices. It provides communication, integration, automation, and close cooperation among all the people needed to plan, develop, test, deploy, release, and maintain a Solution." (Dean Leffingwell, "SAFe 4.5 Reference Guide: Scaled Agile Framework for Lean Enterprises" 2nd Ed., 2018)

"Short for development operations, an information technology environment in which development and operations are tightly tied together, yielding small incremental releases to gain user feedback." (O Sami Saydjari, "Engineering Trustworthy Systems: Get Cybersecurity Design Right the First Time", 2018)

"The practice of incorporating developers and members of operations and quality assurance (QA) staff into software development projects to align their incentives and enable frequent, efficient, and reliable releases of software products." (Shon Harris & Fernando Maymi, "CISSP All-in-One Exam Guide" 8th Ed., 2018)

"The tighter integration between the developers of applications and the IT department that tests and deploys them. DevOps is said to be the intersection of software engineering, quality assurance, and operations." (William Stallings, "Effective Cybersecurity: A Guide to Using Best Practices and Standards", 2018)

"A software engineering practice that aims at unifying software development (Dev) and software operation (Ops)." (Jun Bi et al, "Automatic Address Scheduling and Management for Broadband IP Networks", Emerging Automation Techniques for the Future Internet, 2019)

"Develop operations, or DevOps, is an agile methodology that merges the functions of software development and operations in the enterprise software development domain. This approach has been adopted in the networking world to facilitate a programmable approach to network operations. Often when applied to networking the term is changed to NetOps." (Patrick Moore, "Model-Centric Fulfillment Operations and Maintenance Automation", Emerging Automation Techniques for the Future Internet, 2019)

"Practices and technologies that promote tighter coupling of software development (Dev) and operations (Ops) - typically marked by more automation, continuous monitoring, shorter development cycles and higher deployment frequencies. A key driver for security policy automation. DevSecOps is a related term that refers to practices and technologies that aim to embed security in DevOps practices." (Myo Zarny et al, "Network Security Policy Automation: Enterprise Use Cases and Methodologies", 2019)

"Development and operations is an abbreviation for 'development' and 'operations'; is a software engineering methodology for managing software development (Dev) and technology operations (Ops). The main aim of DevOps is to enable automation and tracing for all phases of software implementation, from integration, testing, releasing to deployment and infrastructure management." (Antoine Trad & Damir Kalpić, "Using Applied Mathematical Models for Business Transformation", 2020)

"Development and operations (DevOps) has been adopted by prominent software and service companies (e.g., IBM) to support enhanced collaboration across the company and its value chain partners. In this way, DevOps facilitates uninterrupted delivery and coexistence between development and operation facilities, enhances the quality and performance of software applications, improving end-user experience, and help to simultaneous deployment of software across different platforms." (Kamalendu Pal & Bill Karakostas, "Software Testing Under Agile, Scrum, and DevOps", 2021)

"DevOps is a sprint-based approach that can catch coding flaws during the development of code due to security reviews, rework on previous sprint cycles, and testing." (David A Bird, "Hacker and Non-Attributed State Actors", Real-Time and Retrospective Analyses of Cyber Security, 2021)

"It is a set of practices emerging to bridge the gaps between operation and developer teams to achieve a better collaboration." (Mirna Muñoz, "Boosting the Competitiveness of Organizations With the Use of Software Engineering", 2021)

"It is a way to work were the software is rapidly developed and immediately deployed for operating in a computational productive environment. It is continuous delivery product development lifecycle. It must automate the development process. DevOps is both a culture and a set of technologies and tools used for automation." Laura C Rodriguez-Martinez et al, "Service-Oriented Computing Applications (SOCA) Development Methodologies: A Review of Agility-Rigor Balance", 2021)

"People from software development and operations work together to enhance the speed of delivery of new software features. It is a concept for bridging the gap between software development and software operations and integrating the logic of common responsibility for the complete software delivery lifecycle into one cross-functional team." (Anna Wiedemann et al, "Transforming Disciplined IT Functions: Guidelines for DevOps Integration", 2021)

"DevOps is a set of tools and processes that help automate IT operations." (Aniruddha Deswandikar,"Engineering Data Mesh in Azure Cloud", 2024)

"DevOps is a catch‑all term for the blending of roles between developers and operations engineers. As the barriers between roles such as database administrator, systems administrator, and software engineer have eroded, the term DevOps has emerged as a way of describing the intersection of responsibilities from all these camps, and their increasing interrelation in the lifecycle of a product. A crucial enabling aspect of this movement is the increased use of automation in building, deploying, and monitoring large applications." (NGINX) [source]

"DevOps is a collection of best practices and working methods for the software development process whose cumulative goal is to shorten the development life cycle and support practice such as continuous integration, continuous delivery and continuous deployment." (Sum Logic) [source]

"DevOps is a set of practices that works to automate and integrate the processes between software development and IT teams, so they can build, test, and release software faster and more reliably." Atlassian [source] 

"DevOps is the combination of cultural philosophies, practices, and tools that increases an organization’s ability to deliver applications and services at high velocity: evolving and improving products at a faster pace than organizations using traditional software development and infrastructure management processes." (Amazon) [source]

"DevOps refers to a broad range of practices related to the development and operation of software code in production in cloud data centers. DevOps is centered in Agile project management techniques and microservice support. DevOps approaches the entire software development lifecycle with automation based around version control standards." (VMWare) [source]

"The cultural movement that stresses communication, collaboration and integration between software developers and IT operations." (Global Knowledge)

🌁Software Engineering: Prototype (Definitions)

"A preliminary type, form, or instance of a product or product component that serves as a model for later stages or for the final, complete version of the product. This model (e.g., physical, electronic, digital, analytical) can be used for the following (and other) purposes: assessing the feasibility of a new or unfamiliar technology; assessing or mitigating technical risk; validating requirements; demonstrating critical features; qualifying a product; qualifying a process; characterizing performance or product features; elucidating physical principles; quality. The ability of a set of inherent characteristics of a product, product component, or process to fulfill requirements of customers." (Sandy Shrum et al, "CMMI®: Guidelines for Process Integration and Product Improvement", 2003)

"Software program, hardware assembly, or mockup built to assess feasibility or risks, validate requirements, demonstrate critical features, quantify (measure) performance, or evaluate alternative designs." (Richard D Stutzke, "Estimating Software-Intensive Systems: Projects, Products, and Processes", 2005)

"A simulation of the product using either software prototyping tools, low-fidelity whiteboards, or paper mock-ups. The prototype is intended to make iteasier for stakeholders to understand and describe their requirements." (Suzanne Robertson & James Robertson, "Mastering the Requirements Process" 2nd Ed., 2006)

"A validated build of a system produced at the end of an iteration microcycle." (Bruce P Douglass, "Real-Time Agility", 2009)

"1.An artifact in iterative development. A prototype may be disposable or the base for further incremental development. 2.Verb. To create a test artifact for the sole purpose of determining whether the design is feasible or will be successful given environmental restraints." (DAMA International, "The DAMA Dictionary of Data Management", 2011)

"An early sample or model built to test a concept or process or to act as a thing to be replicated or learned from. In Requirements Engineering prototypes can be used for requirements elicitation and validation." (IQBBA, "Standard glossary of terms used in Software Engineering", 2011)

"A method of obtaining early feedback on requirements by providing a working model of the expected product before actually building it. " (For Dummies, "PMP Certification All-in-One For Dummies" 2nd Ed., 2013)

"A simulation, usually automated, of the computer system to be implemented." (James Robertson et al, "Complete Systems Analysis: The Workbook, the Textbook, the Answers", 2013)

"A mockup of some or all of the application to let the developers and customers study an aspect of the system. Typically a software prototype is a program that mimics part of the application you want to build." (Rod Stephens, "Beginning Software Engineering", 2015)

"The first model of a product. In software, it’s the incomplete product used for testing and validation before final development." (Pamela Schure & Brian Lawley, "Product Management For Dummies", 2017)

Software Enfineering: Model-Driven Development (Defintions)

[Model Driven Software Development:] "The process of developing software using different models on different levels of abstraction with (automated) transformations between these models." (Anneke Kleppe et al, "MDA Explained: The Model Driven Architecture™: Practice and Promise", 2003)

[Agile Model-Driven Development (AMDD):] "A highly iterative approach to development in which you create agile models before you write source code." (Pramod J Sadalage & Scott W Ambler, "Refactoring Databases: Evolutionary Database Design", 2006)

[Model-driven software development (MDSD):] "An approach where a significant amount of schematic code, which has the same structure but varies depending on the concrete situation, is generated out of an abstract model." (Nicolai M Josuttis, "SOA in Practice", 2007)

[Model-Driven Engineering:] "Paradigm of software engineering where the development of software is directed using models and transformations." (M J Escalona & G Aragón, "The Use of Metamodels in Web Requirements to Assure the Consistence", 2008)

[Model-Driven Engineering:] "This software development methodology is centered around the notion of modeling (as opposed to coding) to be the primary activity in the software development process. Model refinement, transformation and code generation techniques are then applied to produce executable software artifacts in a semi-automatic way." (Cesare Pautasso, "Compiling Business Process Models into Executable Code", Handbook of Research on Business Process Modeling, 2009)

[Model-Driven Development (MDD):] "A software development process that creates models or abstractions of a system or data in order to increase basic compatibility between systems." (DAMA International, "The DAMA Dictionary of Data Management", 2011)

"Is a software design and implementation approach that encourages efficient use of models in the software development process, and supports reuse of best practices when creating families of systems. In general, it provides a way to organize and manage software architectures supported by automated tools and services for both defining the models and facilitating transformations between different models, including the automated transformation of the software system specification into automated code generation." (Christian Scholz et al, "From the Lab to the Factory Floor: Engineering Software for Wireless Sensor Networks", 2012)

[Model-Based Systems Engineering (MBSE):] "Model-Based Systems Engineering is the practice of developing a set of related system models that help define, design, and document a system under development. These models provide an efficient way to explore, update, and communicate system aspects to stakeholders, while significantly reducing or eliminating dependence on traditional documents." (Dean Leffingwell, "SAFe 4.5 Reference Guide: Scaled Agile Framework for Lean Enterprises" 2nd Ed., 2018)

🌁Software Engineering: Exception (Definitions)

"An error condition that will divert a program's flow of control to an exception handler or to the calling program. PL/SQL supports both built-in system exceptions and programmer-defined exceptions. Exceptions may be named or unnamed." (Bill Pribyl & Steven Feuerstein, "Learning Oracle PL/SQL", 2001)

"An object that is passed from the area of code where a problem occurs to the part of the code that is going to handle the problem." (Jesse Liberty, "Sams Teach Yourself C++ in 24 Hours" 3rd Ed., 2001)

"A runtime error-reporting mechanism that requires programs to handle raised exceptions or have their stack unwound until each exception is handled (caught) or the thread terminates." (Damien Watkins et al, "Programming in the .NET Environment", 2002)

"Allows you to catch and manage runtime and other errors while programming. Managed with rescue, ensure, and raise. Compare with error." (Michael Fitzgerald, "Learning Ruby", 2007)

"a condition that violates one or more preconditional invariants; a kind of event sent to indicate such a violation." (Bruce P Douglass, "Real-Time Agility: The Harmony/ESW Method for Real-Time and Embedded Systems Development", 2009)

"Object that represents some kind of error such as an attempt to divide by zero or an attempt to parse a string that has an invalid format." (Rod Stephens, "Stephens' Visual Basic® Programming 24-Hour Trainer", 2011)

"A fancy term for an error." (Jon Orwant et al, "Programming Perl" 4th Ed., 2012)

"A condition or event that cannot be handled by a normal process." (IBM, "Informix Servers 12.1", 2014)

"An error that prevents the program from continuing unless handled by the software." (Matt Telles, "Beginning Programming", 2014)

"An unexpected condition in a program such as a divide by zero or trying to access a missing file. If the code doesn’t catch and handle the exception, the program crashes." (Rod Stephens, "Beginning Software Engineering", 2015)

"Associated with an unusual, sometimes unpredictable event, detectable by software or hardware, which requires special processing; the event may or may not be erroneous" (Nell Dale et al, "Object-Oriented Data Structures Using Java" 4th Ed., 2016)

"A signal that some unexpected condition has occurred in the program. In Java, exceptions are objects that are subclasses of Exception or Error (which themselves are subclasses of Throwable). Exceptions in Java are “raised” with the throw keyword and handled with the catch keyword. See also catch, throw, and throws." (Daniel Leuck et al, "Learning Java" 5th Ed., 2020)

🌁Software Engineering: Use Case (Definitions)

"A description of how the system will be used." (Jesse Liberty, "Sams Teach Yourself C++ in 24 Hours" 3rd Ed., 2001)

"The definition of a behavior of the software product based on gradually described interactions between user and system." (Johannes Link & Peter Fröhlich, "Unit Testing in Java", 2003)

"A set of possible sequences of interactions (scenarios) between systems and users (actors) in a particular environment and related to a particular goal. The use case and goal are sometimes considered to be synonymous. Use cases capture the intended behavior of the system, without specifying how that behavior is implemented. Use cases can be employed to identify, clarify, and organize system requirements, and, during later stages of software development, to validate design, create test cases, and create online help and user manuals." (Richard D Stutzke, "Estimating Software-Intensive Systems: Projects, Products, and Processes", 2005)

"A sequence of actions a system performs that yields an observable result of value to a particular actor. A use-case class contains all main, alternate, and exception flows of events related to producing the 'observable result of value'." (Bruce MacIsaac & Per Kroll, "Agility and Discipline Made Easy: Practices from OpenUP and RUP", 2006)

"A concrete usage of a system, characterized by a set of scenarios, a set of requirements to which it traces, and a specification state machine." (Bruce P Douglass, "Real-Time Agility", 2009)

"A description of how end users will use a software code. It describes a task or a series of tasks that users will accomplish using the software and includes the responses of the software to user actions. Use cases may be included in the Software Requirements Document (SRD) as a way of specifying the end users’ expected use of the software." (Mark S Merkow & Lakshmikanth Raghavan, "Secure and Resilient Software Development", 2010)

"A model of human/machine interaction similar to data flow diagrams, in that it represents communications between external entities (here called 'Actors') and processes, but the assumption is that the processes involved represent systems (typically shown only as a single process representing the entire system). The content of data flows are not documented and, rather than being decomposed into lower-level detail, these details are simply described in text as 'steps'. There is no notion of storing data in intermediate 'data stores'." (David C Hay, "Data Model Patterns: A Metadata Map", 2010)

"A sequence of transactions in a dialogue between an actor and a component or system with a tangible result, where an actor can be a user or anything that can exchange information with the system." (IQBBA, "Standard glossary of terms used in Software Engineering", 2011)

"A sequence of transactions in a dialogue between an actor and a component or system with a tangible result. An actor can be a user or anything that can exchange information with the system." (Tilo Linz et al, "Software Testing Foundations" 4th Ed, 2014)

"A description of a series of interactions between actors. The actors can be users or parts of the application. A simple template might include a title, main success scenario, and extensions (other variations on the scenario)." (Rod Stephens, "Beginning Software Engineering", 2015)

"It is a list of events and actions among systems and users in a specific environment and for a specific goal." (Yassine Maleh et al, 'Strategic IT Governance and Performance Frameworks in Large Organizations", 2019)

"Technique used to define required functionality and objectives, and to design tests." (ITIL)