Breaking Dependencies: The SOLID Principles Klaus Iglberger, CppCon 2020 klaus.iglberger@gmx.de2 Klaus Iglberger C++ Trainer since 2016 Author of the C++ math library (Co-)Organizer The SOLID Principles Single-Responsibility Principle Open-Closed Principle Liskov Substitution Principle Interface Segregation Principle Dependency Inversion Principle9 The SOLID Principles Single-Responsibility Inversion Principle Robert C. Martin Michael Feathers10 The SOLID Principles11 The SOLID Principles I will introduce the SOLID principles … … as guidelines not limited to OO programming … as general

Bottom Up Integration Boundary Value Branch Breadth Code-driven Comparison Compatibility Compliance Component Concurrency Condition Coverage Configuration Conformance Context Driven Conversion familiar with the design principles ‣ Then consider trying TDDwrite a failing test write just the code to make the test pass refactor start end are we done?DesignThe SOLID principles Single Responsibility

the task with other approaches, that will be explained later. This is just an introduction to the principles and concepts. The important idea is that now we got 2 versions of matrix in the lockfile, and following guidelines contain a series of recommendations to ensure repeatability, reliability, compliance and, where applicable, control to enable customization. As a summary, it is highly recommended recommendations also apply when consuming packages from external sources in any package manager. 5.1.3 Compliance and security Some industries such as finance, robotics and embedded, have stronger requirements

executable, test results, coverage data and many other different files needed for traceability, compliance and business purposes. See also: • Metadata files blog post 2.17 Third party backup sources the task with other approaches, that will be explained later. This is just an introduction to the principles and concepts. The important idea is that now we got 2 versions of matrix in the lockfile, and following guidelines contain a series of recommendations to ensure repeatability, reliability, compliance and, where applicable, control to enable customization. As a summary, it is highly recommended

executable, test results, coverage data and many other different files needed for traceability, compliance and business purposes. See also: • Metadata files blog post 2.17 Third party backup sources the task with other approaches, that will be explained later. This is just an introduction to the principles and concepts. The important idea is that now we got 2 versions of matrix in the lockfile, and following guidelines contain a series of recommendations to ensure repeatability, reliability, compliance and, where applicable, control to enable customization. As a summary, it is highly recommended

executable, test results, coverage data and many other different files needed for traceability, compliance and business purposes. See also: • Metadata files blog post 2.17 Third party backup sources the task with other approaches, that will be explained later. This is just an introduction to the principles and concepts. The important idea is that now we got 2 versions of matrix in the lockfile, and following guidelines contain a series of recommendations to ensure repeatability, reliability, compliance and, where applicable, control to enable customization. As a summary, it is highly recommended

executable, test results, coverage data and many other different files needed for traceability, compliance and business purposes. See also: • Metadata files blog post 2.17 Third party backup sources the task with other approaches, that will be explained later. This is just an introduction to the principles and concepts. The important idea is that now we got 2 versions of matrix in the lockfile, and following guidelines contain a series of recommendations to ensure repeatability, reliability, compliance and, where applicable, control to enable customization. As a summary, it is highly recommended

executable, test results, coverage data and many other different files needed for traceability, compliance and business purposes. See also: • Metadata files blog post 2.17 Third party backup sources the task with other approaches, that will be explained later. This is just an introduction to the principles and concepts. The important idea is that now we got 2 versions of matrix in the lockfile, and following guidelines contain a series of recommendations to ensure repeatability, reliability, compliance and, where applicable, control to enable customization. As a summary, it is highly recommended

executable, test results, coverage data and many other different files needed for traceability, compliance and business purposes. See also: • Metadata files blog post 2.17 Third party backup sources the task with other approaches, that will be explained later. This is just an introduction to the principles and concepts. The important idea is that now we got 2 versions of matrix in the lockfile, and following guidelines contain a series of recommendations to ensure repeatability, reliability, compliance and, where applicable, control to enable customization. As a summary, it is highly recommended

executable, test results, coverage data and many other different files needed for traceability, compliance and business purposes. See also: • Metadata files blog post 2.17 Third party backup sources the task with other approaches, that will be explained later. This is just an introduction to the principles and concepts. The important idea is that now we got 2 versions of matrix in the lockfile, and following guidelines contain a series of recommendations to ensure repeatability, reliability, compliance and, where applicable, control to enable customization. As a summary, it is highly recommended