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

government-contractor teams. Agile cannot solve all of the DoD’s IT acquisition challenges, but offers a set of principles that can help reduce cycle times and risks to deliver IT in a complex environment. “The US joint Agile within the unique and complex DoD acquisition environment. This guide seeks to adapt proven principles of Agile development specifically to the DoD context. More and more federal acquisition programs exploring a more flexible approach than the traditional defense acquisition framework to apply Agile principles effectively. Figure 1 Agile Acquisition Guidebook Venn Diagram Because there is no single

structured as:1. Standardized Model – where routine and systems govern everything; including strict compliance with budget and schedule 2. Experimental Model – every day every exercise and new piece of information forms of standards and processes iii. Justin Arbuckle, Chief Architect at GE Capital, “the actual compliance of an organization is in direct proportion to the degree to which its policies are expressed provides safe, supported passage 2. You can go beyond the buoys, if you follow organizational principles 4. Ch. 21 – Reserve Time to Create Organizational Learning and Improvementa. Toyota Production

Myth—DevOps is incompatible with ITIL d. Myth—DevOps is Incompatible with Information Security and Compliance: e. Myth—DevOps Means Eliminating IT Operations, or “NoOps” f. Myth—DevOps is Just “Infrastructure batch sizes of work b. Agile, Continuous Delivery, and the Three Ways 7 c. The First Way: The Principles of Flow 15 i. MAKE OUR WORK VISIBLE 1. A significant difference between technology and manufacturing f. Motion: g. Defects: h. Nonstandard or manual work:i. Heroics: d. The Second Way: The Principles of Feedback 27 i. KEEP PUSHING QUALITY CLOSER TO THE SOURCE 1. In complex systems, adding more

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

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194 13.1.1 General Security Principles . . . . . . . . . . . . . . . . . . . . . . . . . 194 13.2 Secure Installation and Configuration Overview 13.1.1 General Security Principles The following principles are fundamental to using any application securely. Keep Software Up To Date One of the principles of good security practise is to keep under this License will not have their licenses terminated so long as such parties remain in full compliance. 5. You are not required to accept this License, since you have not signed it. However, nothing

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215 13.1.1 General Security Principles . . . . . . . . . . . . . . . . . . . . . . . . . 215 13.2 Secure Installation and Configuration Overview 13.1.1 General Security Principles The following principles are fundamental to using any application securely. Keep Software Up To Date One of the principles of good security practise is to keep under this License will not have their licenses terminated so long as such parties remain in full compliance. 5. You are not required to accept this License, since you have not signed it. However, nothing

memory errors on Solaris 10 hosts . . . . . . . . 275 13 Security guide 277 13.1 General Security Principles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277 13.2 Secure Installation and Configuration Security guide 13.1 General Security Principles The following principles are fundamental to using any application securely. Keep Software Up To Date One of the principles of good security practise is to keep under this License will not have their licenses terminated so long as such parties remain in full compliance. 5. You are not required to accept this License, since you have not signed it. However, nothing

memory errors on Solaris 10 hosts . . . . . . . . 274 13 Security guide 276 13.1 General Security Principles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 276 13.2 Secure Installation and Configuration Security guide 13.1 General Security Principles The following principles are fundamental to using any application securely. Keep Software Up To Date One of the principles of good security practise is to keep under this License will not have their licenses terminated so long as such parties remain in full compliance. 5. You are not required to accept this License, since you have not signed it. However, nothing

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227 13.1.1 General Security Principles . . . . . . . . . . . . . . . . . . . . . . . . . 227 13.2 Secure Installation and Configuration Overview 13.1.1 General Security Principles The following principles are fundamental to using any application securely. Keep Software Up To Date One of the principles of good security practise is to keep under this License will not have their licenses terminated so long as such parties remain in full compliance. 5. You are not required to accept this License, since you have not signed it. However, nothing