├── LICENCE.md ├── README.md ├── images ├── 2021-06-04--reliability-model-icon.png └── Software Reliability Model.png ├── reliability-model.css ├── screenshots ├── 2021-02-28--kuku-software-reliability-model.png └── 2021-05-06--telus-conflux-reliability-model-in-kumu.png ├── telus-conflux-reliability-model - Connections.csv └── telus-conflux-reliability-model - Elements.csv /LICENCE.md: -------------------------------------------------------------------------------- 1 | Attribution-ShareAlike 4.0 International 2 | 3 | ======================================================================= 4 | 5 | Creative Commons Corporation ("Creative Commons") is not a law firm and 6 | does not provide legal services or legal advice. Distribution of 7 | Creative Commons public licenses does not create a lawyer-client or 8 | other relationship. Creative Commons makes its licenses and related 9 | information available on an "as-is" basis. Creative Commons gives no 10 | warranties regarding its licenses, any material licensed under their 11 | terms and conditions, or any related information. Creative Commons 12 | disclaims all liability for damages resulting from their use to the 13 | fullest extent possible. 14 | 15 | Using Creative Commons Public Licenses 16 | 17 | Creative Commons public licenses provide a standard set of terms and 18 | conditions that creators and other rights holders may use to share 19 | original works of authorship and other material subject to copyright 20 | and certain other rights specified in the public license below. The 21 | following considerations are for informational purposes only, are not 22 | exhaustive, and do not form part of our licenses. 23 | 24 | Considerations for licensors: Our public licenses are 25 | intended for use by those authorized to give the public 26 | permission to use material in ways otherwise restricted by 27 | copyright and certain other rights. Our licenses are 28 | irrevocable. Licensors should read and understand the terms 29 | and conditions of the license they choose before applying it. 30 | Licensors should also secure all rights necessary before 31 | applying our licenses so that the public can reuse the 32 | material as expected. Licensors should clearly mark any 33 | material not subject to the license. This includes other CC- 34 | licensed material, or material used under an exception or 35 | limitation to copyright. More considerations for licensors: 36 | wiki.creativecommons.org/Considerations_for_licensors 37 | 38 | Considerations for the public: By using one of our public 39 | licenses, a licensor grants the public permission to use the 40 | licensed material under specified terms and conditions. If 41 | the licensor's permission is not necessary for any reason--for 42 | example, because of any applicable exception or limitation to 43 | copyright--then that use is not regulated by the license. Our 44 | licenses grant only permissions under copyright and certain 45 | other rights that a licensor has authority to grant. Use of 46 | the licensed material may still be restricted for other 47 | reasons, including because others have copyright or other 48 | rights in the material. A licensor may make special requests, 49 | such as asking that all changes be marked or described. 50 | Although not required by our licenses, you are encouraged to 51 | respect those requests where reasonable. More_considerations 52 | for the public: 53 | wiki.creativecommons.org/Considerations_for_licensees 54 | 55 | ======================================================================= 56 | 57 | Creative Commons Attribution-ShareAlike 4.0 International Public 58 | License 59 | 60 | By exercising the Licensed Rights (defined below), You accept and agree 61 | to be bound by the terms and conditions of this Creative Commons 62 | Attribution-ShareAlike 4.0 International Public License ("Public 63 | License"). To the extent this Public License may be interpreted as a 64 | contract, You are granted the Licensed Rights in consideration of Your 65 | acceptance of these terms and conditions, and the Licensor grants You 66 | such rights in consideration of benefits the Licensor receives from 67 | making the Licensed Material available under these terms and 68 | conditions. 69 | 70 | 71 | Section 1 -- Definitions. 72 | 73 | a. Adapted Material means material subject to Copyright and Similar 74 | Rights that is derived from or based upon the Licensed Material 75 | and in which the Licensed Material is translated, altered, 76 | arranged, transformed, or otherwise modified in a manner requiring 77 | permission under the Copyright and Similar Rights held by the 78 | Licensor. For purposes of this Public License, where the Licensed 79 | Material is a musical work, performance, or sound recording, 80 | Adapted Material is always produced where the Licensed Material is 81 | synched in timed relation with a moving image. 82 | 83 | b. Adapter's License means the license You apply to Your Copyright 84 | and Similar Rights in Your contributions to Adapted Material in 85 | accordance with the terms and conditions of this Public License. 86 | 87 | c. BY-SA Compatible License means a license listed at 88 | creativecommons.org/compatiblelicenses, approved by Creative 89 | Commons as essentially the equivalent of this Public License. 90 | 91 | d. Copyright and Similar Rights means copyright and/or similar rights 92 | closely related to copyright including, without limitation, 93 | performance, broadcast, sound recording, and Sui Generis Database 94 | Rights, without regard to how the rights are labeled or 95 | categorized. For purposes of this Public License, the rights 96 | specified in Section 2(b)(1)-(2) are not Copyright and Similar 97 | Rights. 98 | 99 | e. Effective Technological Measures means those measures that, in the 100 | absence of proper authority, may not be circumvented under laws 101 | fulfilling obligations under Article 11 of the WIPO Copyright 102 | Treaty adopted on December 20, 1996, and/or similar international 103 | agreements. 104 | 105 | f. Exceptions and Limitations means fair use, fair dealing, and/or 106 | any other exception or limitation to Copyright and Similar Rights 107 | that applies to Your use of the Licensed Material. 108 | 109 | g. License Elements means the license attributes listed in the name 110 | of a Creative Commons Public License. The License Elements of this 111 | Public License are Attribution and ShareAlike. 112 | 113 | h. Licensed Material means the artistic or literary work, database, 114 | or other material to which the Licensor applied this Public 115 | License. 116 | 117 | i. Licensed Rights means the rights granted to You subject to the 118 | terms and conditions of this Public License, which are limited to 119 | all Copyright and Similar Rights that apply to Your use of the 120 | Licensed Material and that the Licensor has authority to license. 121 | 122 | j. Licensor means the individual(s) or entity(ies) granting rights 123 | under this Public License. 124 | 125 | k. Share means to provide material to the public by any means or 126 | process that requires permission under the Licensed Rights, such 127 | as reproduction, public display, public performance, distribution, 128 | dissemination, communication, or importation, and to make material 129 | available to the public including in ways that members of the 130 | public may access the material from a place and at a time 131 | individually chosen by them. 132 | 133 | l. Sui Generis Database Rights means rights other than copyright 134 | resulting from Directive 96/9/EC of the European Parliament and of 135 | the Council of 11 March 1996 on the legal protection of databases, 136 | as amended and/or succeeded, as well as other essentially 137 | equivalent rights anywhere in the world. 138 | 139 | m. You means the individual or entity exercising the Licensed Rights 140 | under this Public License. Your has a corresponding meaning. 141 | 142 | 143 | Section 2 -- Scope. 144 | 145 | a. License grant. 146 | 147 | 1. Subject to the terms and conditions of this Public License, 148 | the Licensor hereby grants You a worldwide, royalty-free, 149 | non-sublicensable, non-exclusive, irrevocable license to 150 | exercise the Licensed Rights in the Licensed Material to: 151 | 152 | a. reproduce and Share the Licensed Material, in whole or 153 | in part; and 154 | 155 | b. produce, reproduce, and Share Adapted Material. 156 | 157 | 2. Exceptions and Limitations. For the avoidance of doubt, where 158 | Exceptions and Limitations apply to Your use, this Public 159 | License does not apply, and You do not need to comply with 160 | its terms and conditions. 161 | 162 | 3. Term. The term of this Public License is specified in Section 163 | 6(a). 164 | 165 | 4. Media and formats; technical modifications allowed. The 166 | Licensor authorizes You to exercise the Licensed Rights in 167 | all media and formats whether now known or hereafter created, 168 | and to make technical modifications necessary to do so. The 169 | Licensor waives and/or agrees not to assert any right or 170 | authority to forbid You from making technical modifications 171 | necessary to exercise the Licensed Rights, including 172 | technical modifications necessary to circumvent Effective 173 | Technological Measures. For purposes of this Public License, 174 | simply making modifications authorized by this Section 2(a) 175 | (4) never produces Adapted Material. 176 | 177 | 5. Downstream recipients. 178 | 179 | a. Offer from the Licensor -- Licensed Material. Every 180 | recipient of the Licensed Material automatically 181 | receives an offer from the Licensor to exercise the 182 | Licensed Rights under the terms and conditions of this 183 | Public License. 184 | 185 | b. Additional offer from the Licensor -- Adapted Material. 186 | Every recipient of Adapted Material from You 187 | automatically receives an offer from the Licensor to 188 | exercise the Licensed Rights in the Adapted Material 189 | under the conditions of the Adapter's License You apply. 190 | 191 | c. No downstream restrictions. You may not offer or impose 192 | any additional or different terms or conditions on, or 193 | apply any Effective Technological Measures to, the 194 | Licensed Material if doing so restricts exercise of the 195 | Licensed Rights by any recipient of the Licensed 196 | Material. 197 | 198 | 6. No endorsement. Nothing in this Public License constitutes or 199 | may be construed as permission to assert or imply that You 200 | are, or that Your use of the Licensed Material is, connected 201 | with, or sponsored, endorsed, or granted official status by, 202 | the Licensor or others designated to receive attribution as 203 | provided in Section 3(a)(1)(A)(i). 204 | 205 | b. Other rights. 206 | 207 | 1. Moral rights, such as the right of integrity, are not 208 | licensed under this Public License, nor are publicity, 209 | privacy, and/or other similar personality rights; however, to 210 | the extent possible, the Licensor waives and/or agrees not to 211 | assert any such rights held by the Licensor to the limited 212 | extent necessary to allow You to exercise the Licensed 213 | Rights, but not otherwise. 214 | 215 | 2. Patent and trademark rights are not licensed under this 216 | Public License. 217 | 218 | 3. To the extent possible, the Licensor waives any right to 219 | collect royalties from You for the exercise of the Licensed 220 | Rights, whether directly or through a collecting society 221 | under any voluntary or waivable statutory or compulsory 222 | licensing scheme. In all other cases the Licensor expressly 223 | reserves any right to collect such royalties. 224 | 225 | 226 | Section 3 -- License Conditions. 227 | 228 | Your exercise of the Licensed Rights is expressly made subject to the 229 | following conditions. 230 | 231 | a. Attribution. 232 | 233 | 1. If You Share the Licensed Material (including in modified 234 | form), You must: 235 | 236 | a. retain the following if it is supplied by the Licensor 237 | with the Licensed Material: 238 | 239 | i. identification of the creator(s) of the Licensed 240 | Material and any others designated to receive 241 | attribution, in any reasonable manner requested by 242 | the Licensor (including by pseudonym if 243 | designated); 244 | 245 | ii. a copyright notice; 246 | 247 | iii. a notice that refers to this Public License; 248 | 249 | iv. a notice that refers to the disclaimer of 250 | warranties; 251 | 252 | v. a URI or hyperlink to the Licensed Material to the 253 | extent reasonably practicable; 254 | 255 | b. indicate if You modified the Licensed Material and 256 | retain an indication of any previous modifications; and 257 | 258 | c. indicate the Licensed Material is licensed under this 259 | Public License, and include the text of, or the URI or 260 | hyperlink to, this Public License. 261 | 262 | 2. You may satisfy the conditions in Section 3(a)(1) in any 263 | reasonable manner based on the medium, means, and context in 264 | which You Share the Licensed Material. For example, it may be 265 | reasonable to satisfy the conditions by providing a URI or 266 | hyperlink to a resource that includes the required 267 | information. 268 | 269 | 3. If requested by the Licensor, You must remove any of the 270 | information required by Section 3(a)(1)(A) to the extent 271 | reasonably practicable. 272 | 273 | b. ShareAlike. 274 | 275 | In addition to the conditions in Section 3(a), if You Share 276 | Adapted Material You produce, the following conditions also apply. 277 | 278 | 1. The Adapter's License You apply must be a Creative Commons 279 | license with the same License Elements, this version or 280 | later, or a BY-SA Compatible License. 281 | 282 | 2. You must include the text of, or the URI or hyperlink to, the 283 | Adapter's License You apply. You may satisfy this condition 284 | in any reasonable manner based on the medium, means, and 285 | context in which You Share Adapted Material. 286 | 287 | 3. You may not offer or impose any additional or different terms 288 | or conditions on, or apply any Effective Technological 289 | Measures to, Adapted Material that restrict exercise of the 290 | rights granted under the Adapter's License You apply. 291 | 292 | 293 | Section 4 -- Sui Generis Database Rights. 294 | 295 | Where the Licensed Rights include Sui Generis Database Rights that 296 | apply to Your use of the Licensed Material: 297 | 298 | a. for the avoidance of doubt, Section 2(a)(1) grants You the right 299 | to extract, reuse, reproduce, and Share all or a substantial 300 | portion of the contents of the database; 301 | 302 | b. if You include all or a substantial portion of the database 303 | contents in a database in which You have Sui Generis Database 304 | Rights, then the database in which You have Sui Generis Database 305 | Rights (but not its individual contents) is Adapted Material, 306 | 307 | including for purposes of Section 3(b); and 308 | c. You must comply with the conditions in Section 3(a) if You Share 309 | all or a substantial portion of the contents of the database. 310 | 311 | For the avoidance of doubt, this Section 4 supplements and does not 312 | replace Your obligations under this Public License where the Licensed 313 | Rights include other Copyright and Similar Rights. 314 | 315 | 316 | Section 5 -- Disclaimer of Warranties and Limitation of Liability. 317 | 318 | a. UNLESS OTHERWISE SEPARATELY UNDERTAKEN BY THE LICENSOR, TO THE 319 | EXTENT POSSIBLE, THE LICENSOR OFFERS THE LICENSED MATERIAL AS-IS 320 | AND AS-AVAILABLE, AND MAKES NO REPRESENTATIONS OR WARRANTIES OF 321 | ANY KIND CONCERNING THE LICENSED MATERIAL, WHETHER EXPRESS, 322 | IMPLIED, STATUTORY, OR OTHER. THIS INCLUDES, WITHOUT LIMITATION, 323 | WARRANTIES OF TITLE, MERCHANTABILITY, FITNESS FOR A PARTICULAR 324 | PURPOSE, NON-INFRINGEMENT, ABSENCE OF LATENT OR OTHER DEFECTS, 325 | ACCURACY, OR THE PRESENCE OR ABSENCE OF ERRORS, WHETHER OR NOT 326 | KNOWN OR DISCOVERABLE. WHERE DISCLAIMERS OF WARRANTIES ARE NOT 327 | ALLOWED IN FULL OR IN PART, THIS DISCLAIMER MAY NOT APPLY TO YOU. 328 | 329 | b. TO THE EXTENT POSSIBLE, IN NO EVENT WILL THE LICENSOR BE LIABLE 330 | TO YOU ON ANY LEGAL THEORY (INCLUDING, WITHOUT LIMITATION, 331 | NEGLIGENCE) OR OTHERWISE FOR ANY DIRECT, SPECIAL, INDIRECT, 332 | INCIDENTAL, CONSEQUENTIAL, PUNITIVE, EXEMPLARY, OR OTHER LOSSES, 333 | COSTS, EXPENSES, OR DAMAGES ARISING OUT OF THIS PUBLIC LICENSE OR 334 | USE OF THE LICENSED MATERIAL, EVEN IF THE LICENSOR HAS BEEN 335 | ADVISED OF THE POSSIBILITY OF SUCH LOSSES, COSTS, EXPENSES, OR 336 | DAMAGES. WHERE A LIMITATION OF LIABILITY IS NOT ALLOWED IN FULL OR 337 | IN PART, THIS LIMITATION MAY NOT APPLY TO YOU. 338 | 339 | c. The disclaimer of warranties and limitation of liability provided 340 | above shall be interpreted in a manner that, to the extent 341 | possible, most closely approximates an absolute disclaimer and 342 | waiver of all liability. 343 | 344 | 345 | Section 6 -- Term and Termination. 346 | 347 | a. This Public License applies for the term of the Copyright and 348 | Similar Rights licensed here. However, if You fail to comply with 349 | this Public License, then Your rights under this Public License 350 | terminate automatically. 351 | 352 | b. Where Your right to use the Licensed Material has terminated under 353 | Section 6(a), it reinstates: 354 | 355 | 1. automatically as of the date the violation is cured, provided 356 | it is cured within 30 days of Your discovery of the 357 | violation; or 358 | 359 | 2. upon express reinstatement by the Licensor. 360 | 361 | For the avoidance of doubt, this Section 6(b) does not affect any 362 | right the Licensor may have to seek remedies for Your violations 363 | of this Public License. 364 | 365 | c. For the avoidance of doubt, the Licensor may also offer the 366 | Licensed Material under separate terms or conditions or stop 367 | distributing the Licensed Material at any time; however, doing so 368 | will not terminate this Public License. 369 | 370 | d. Sections 1, 5, 6, 7, and 8 survive termination of this Public 371 | License. 372 | 373 | 374 | Section 7 -- Other Terms and Conditions. 375 | 376 | a. The Licensor shall not be bound by any additional or different 377 | terms or conditions communicated by You unless expressly agreed. 378 | 379 | b. Any arrangements, understandings, or agreements regarding the 380 | Licensed Material not stated herein are separate from and 381 | independent of the terms and conditions of this Public License. 382 | 383 | 384 | Section 8 -- Interpretation. 385 | 386 | a. For the avoidance of doubt, this Public License does not, and 387 | shall not be interpreted to, reduce, limit, restrict, or impose 388 | conditions on any use of the Licensed Material that could lawfully 389 | be made without permission under this Public License. 390 | 391 | b. To the extent possible, if any provision of this Public License is 392 | deemed unenforceable, it shall be automatically reformed to the 393 | minimum extent necessary to make it enforceable. If the provision 394 | cannot be reformed, it shall be severed from this Public License 395 | without affecting the enforceability of the remaining terms and 396 | conditions. 397 | 398 | c. No term or condition of this Public License will be waived and no 399 | failure to comply consented to unless expressly agreed to by the 400 | Licensor. 401 | 402 | d. Nothing in this Public License constitutes or may be interpreted 403 | as a limitation upon, or waiver of, any privileges and immunities 404 | that apply to the Licensor or You, including from the legal 405 | processes of any jurisdiction or authority. 406 | 407 | 408 | ======================================================================= 409 | 410 | Creative Commons is not a party to its public 411 | licenses. Notwithstanding, Creative Commons may elect to apply one of 412 | its public licenses to material it publishes and in those instances 413 | will be considered the “Licensor.” The text of the Creative Commons 414 | public licenses is dedicated to the public domain under the CC0 Public 415 | Domain Dedication. Except for the limited purpose of indicating that 416 | material is shared under a Creative Commons public license or as 417 | otherwise permitted by the Creative Commons policies published at 418 | creativecommons.org/policies, Creative Commons does not authorize the 419 | use of the trademark "Creative Commons" or any other trademark or logo 420 | of Creative Commons without its prior written consent including, 421 | without limitation, in connection with any unauthorized modifications 422 | to any of its public licenses or any other arrangements, 423 | understandings, or agreements concerning use of licensed material. For 424 | the avoidance of doubt, this paragraph does not form part of the 425 | public licenses. -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | # Software Reliability Model - reliability-model 2 | 3 | 4 | 5 | This Software Reliability Model (SRM) provides a flexible and explainable model of software reliability in terms of technical foundations, socio-technical constraints, and human factors. It is designed to help explore and explain software reliability to people of various roles who are involved in building and running software systems (especially when on-boarding new team members), and track progress in improving reliability. The SRM is also designed to make it easy to generate and update hierarchical metrics for product health scores across multiple teams. 6 | 7 | The software reliability model is designed to be relevant to several different kinds of software systems: 8 | 9 | * internet and cloud-based software 10 | * desktop software 11 | * IoT and embedded software 12 | * (combinations of the above) 13 | 14 | The different team measures, context, and genres of influences are linked to create a graph that helps to explain the dynamics around software reliability. The graph is then visualised using the visualisation tool [Kumu](https://kumu.io/). 15 | 16 | ![Screenshot of the reliability model visualised in Kumu](screenshots/2021-05-06--telus-conflux-reliability-model-in-kumu.png) 17 | 18 | ## Who created the Software Reliability Model? 19 | 20 | This software reliability model was co-created by people from [TELUS Digital](https://www.telus.com/en/digital) ([@telus](https://github.com/telus)) and [Conflux](http://confluxhq.net/) ([@ConfluxHQ](https://github.com/ConfluxHQ)), with significant contributions from: 21 | 22 | * [Bojan Savic](https://github.com/savicbo) of TELUS Digital 23 | * [Matthew Skelton](https://github.com/matthewskelton) of Conflux 24 | 25 | ## Audience 26 | 27 | The SRM is aimed at these kinds of people: 28 | 29 | * Product Owner / Product Manager 30 | * [SRE](https://sre.google/) Manager / [SRE](https://sre.google/) Lead 31 | * Software Architect / Systems Architect / Test Architect 32 | * Software Developer 33 | * Software Tester 34 | 35 | The SRM helps these people to explore and discuss different aspects of software reliability to help make targeted improvements. 36 | 37 | ## What's in the SRM? 38 | 39 | The SRM is composed of 2 main parts: 40 | 41 | 1. definitions of reliability factors in CSV format suitable for import to [Kumu](https://kumu.io/) 📄 42 | 2. graphs in [Kumu](https://kumu.io/) generated by importing the CSV definitions 📊 43 | 44 | The CSV files (and visualisation settings) are imported into Kumu to generate explorable graphs. 45 | 46 | # How to use the reliability model 47 | 48 | There are several ways to use the SRM. Here are some suggestions: 49 | 50 | 1. **Freeform exploration**: use the Kumu graphs to investigate different aspects of reliability in a free-form way. 51 | 1. **Guided Workshops**: use the _context_ groupings to do a deep dive into specific aspects of reliability. For example, run a 90-minute workshop on _Decoupling and isolation_ or _Speed of remeditation_. Use the workshop to get a sense of awareness within the team of the team-level practices and measures that sit under that _context_ parent node. Then repeat the workshop but with a new _context_. 52 | 1. **Metrics roll-up**: use the SRM to score teams on their current reliability practices and status. The _Metric_ and _Measure_ details for each leaf node provide details of what to measure and the type of measurement. Aggregate the measures into the parent nodes until you have a single score for Reliability for that team. 53 | 1. **All 3 of the above**: use all three above approaches for maximum benefit, helping the team members to understand how they can help to improve reliability on a daily basis. 54 | 55 | # Explore the latest version of the model on Kumu 56 | 57 | Visit the latest stable version of the reliability model on Kumu: [https://kumu.io/reliability-model/latest](https://kumu.io/reliability-model/latest) 58 | 59 | ![Screenshot of SRM graph visualization on Kumu](screenshots/2021-05-06--telus-conflux-reliability-model-in-kumu.png) 60 | 61 | See all versions of the model: [https://kumu.io/reliability-model](https://kumu.io/reliability-model) 62 | 63 | # Types of factors in the model 64 | 65 | There are several types of factors in the SRM - each factor type is shown differently in the Kumu graph: 66 | 67 | * team measure - team-level measures that influence reliability 68 | * context - the context in which measures are taken 69 | * genre - the high-level grouping of measures 70 | * reliability - the ultimate goal of all these factors 71 | 72 | ## Tags to help explore the model 73 | 74 | Tags are used to explore different dimensions of the model: 75 | 76 | * 4 Key Metrics - from the book [_Accelerate_](https://itrevolution.com/book/accelerate/): 77 | - lead time 78 | - deployment frequency 79 | - Mean Time To Restore (MTTR) 80 | - Change failure rate 81 | * CodeScene - measures from the tool CodeScene (see [CodeScene.io](https://codescene.io/)) 82 | * Continuous Delivery - measures from the Continuous Delivery dimension of MSDA 83 | * Deployment - measures from the Deployment dimension of MSDA 84 | * Deployment technique - techniques for reliability focused on deployment aspects 85 | * Flow - measures from the Flow dimension of MSDA 86 | * Human technique - techniques for reliability focused on human aspects 87 | * MSDA - measures from [Multi-team Software Delivery Assessment (MSDA)](http://softwaredeliveryassessment.com/) 88 | * On-call - measures from the On-call dimension of MSDA 89 | * Operability - measures from the OPerability dimension of MSDA 90 | * RTCE - measures from the [Reliability Through Customer Eyes (RTCE)](http://rtce.net/) principles devised by TELUS and Conflux. 91 | * Reliability and SRE - measures from the Reliability dimension of MSDA 92 | * Runtime technique - techniques for reliability focused on runtime aspects 93 | * Team Health - measures from the Team Health dimension of MSDA 94 | * Team Topologies - measures derived from the book [Team Topologies](https://teamtopologies.com/) 95 | * Team API - measures relating to the 'Team API' concept in Team Topologies 96 | * Team Autonomy - measures relating to team autonomy as discussed in Team Topologies 97 | * Team Cognitive Load - measures relating to the 'Team Cognitive Load' concept in Team Topologies 98 | * Testability - measures from the Testability dimension of MSDA 99 | * UX - measures relating to end-user experience 100 | * Version Control Hygiene - measures relating to good version control practices 101 | 102 | # Notes on the model and visualization 103 | 104 | 1. Names of Kumu element types, connection types, and tags are ["selector friendly" for the Kumu advanced editor](https://docs.kumu.io/guides/import.html#try-to-be-selector-friendly) - a single word. 105 | 1. The graph layout visualization is controlled by the settings in the `*.css` view files (imported into the [Advanced Editor](https://docs.kumu.io/overview/view-editors.html#advanced-editor) settings in Kumu). 106 | 1. The CSV data import in Kumu needs some attention to detail. Be sure to follow the [CSV import details](https://docs.kumu.io/guides/import.html). 107 | 108 | # Books that influenced the model 109 | 110 | These books influenced the reliability model significantly: 111 | 112 | * [_Accelerate_](https://wordery.com/accelerate-nicole-forsgren-phd-9781942788331) by Nicole Forsgren, Jez Humble, and Gene Kim 113 | * [_Agile Testing_](https://wordery.com/agile-testing-lisa-crispin-9780321534460) by Lisa Crispin and Janet Gregory 114 | * [_Continuous Delivery_](http://continuousdelivery.com/) by Jez Humble and Dave Farley 115 | * [_Growing Object-Oriented Software_](https://wordery.com/growing-object-oriented-software-guided-by-tests-steve-freeman-9780321503626) by Steve Freeman and Nat Price 116 | * [_Principles of Product Development Flow_](https://wordery.com/the-principles-of-product-development-flow-donald-g-reinertsen-9781935401001) by Don Reinertsen 117 | * [_Seeking SRE_](https://www.oreilly.com/library/view/seeking-sre/9781491978856/) edited by David N. Blank-Edelman 118 | * [_Site Reliability Engineering_](https://sre.google/sre-book/table-of-contents/) by Betsy Beyer, Chris Jones, Jennifer Petoff, & Niall Murphy 119 | * [_Team Guide to Metrics for Business Decisions_](http://bizmetricsbook.com/) by Mattia Battiston and Chris Young 120 | * [_Team Guide to Software Operability_](http://operabilitybook.com/) by Matthew Skelton, Alex Moore, & Rob Thatcher 121 | * [_Team Guide to Software Testability_](http://testabilitybook.com/) by Ash Winter and Rob Meaney and the companion website [TestabilityQuestions.com](http://TestabilityQuestions.com/) 122 | * [_The Site Reliability Workbook_](https://sre.google/workbook/table-of-contents/) edited by Betsy Beyer, Niall Richard Murphy, David K. Rensin, Kent Kawahara, & Stephen Thorne 123 | * [_Working Effectively with Legacy Code_](https://www.amazon.co.uk/Working-Effectively-Legacy-Michael-Feathers/dp/0131177052) by Michael Feathers 124 | 125 | # Possible improvements 126 | 127 | * Use CI to test Pull Requests against Kumu import: 128 | - Duplicate nodes? 129 | - Dangling connectors? 130 | -------------------------------------------------------------------------------- /images/2021-06-04--reliability-model-icon.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/telus/reliability-model/c27a63f996900750755bf3ee6b0ebff63b70a7aa/images/2021-06-04--reliability-model-icon.png -------------------------------------------------------------------------------- /images/Software Reliability Model.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/telus/reliability-model/c27a63f996900750755bf3ee6b0ebff63b70a7aa/images/Software Reliability Model.png -------------------------------------------------------------------------------- /reliability-model.css: -------------------------------------------------------------------------------- 1 | @settings { 2 | template: custom; 3 | element-size: 16; 4 | connection-curvature: 0.15; 5 | } 6 | 7 | /* elements: team-measure */ 8 | team-measure { 9 | icon: users; 10 | icon-color: #000; 11 | color: #4F4; 12 | } 13 | 14 | /* elements: context */ 15 | context { 16 | icon: map-marked; 17 | icon-color: #000; 18 | color: #F44; 19 | } 20 | 21 | /* elements: genre */ 22 | genre { 23 | icon: sitemap; 24 | icon-color: #000; 25 | color: #44F; 26 | } 27 | 28 | /* elements: reliability */ 29 | reliability { 30 | icon: cog; 31 | icon-color: #000; 32 | color: #FC4; 33 | } 34 | -------------------------------------------------------------------------------- /screenshots/2021-02-28--kuku-software-reliability-model.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/telus/reliability-model/c27a63f996900750755bf3ee6b0ebff63b70a7aa/screenshots/2021-02-28--kuku-software-reliability-model.png -------------------------------------------------------------------------------- /screenshots/2021-05-06--telus-conflux-reliability-model-in-kumu.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/telus/reliability-model/c27a63f996900750755bf3ee6b0ebff63b70a7aa/screenshots/2021-05-06--telus-conflux-reliability-model-in-kumu.png -------------------------------------------------------------------------------- /telus-conflux-reliability-model - Connections.csv: -------------------------------------------------------------------------------- 1 | From,To,Label,Type,Tags,Description 2 | Lead Time,Decoupling and Isolation,,Inverse,, 3 | Deployment Frequency,Decoupling and Isolation,,Proportional,, 4 | Mean Time To Recovery,Speed of remediation,,Inverse,, 5 | Change Failure percentage,Understanding of system behaviour,,Inverse,, 6 | Code under version control,Code-level hygiene,,Proportional,, 7 | Config under version control,Code-level hygiene,,Proportional,, 8 | Schemas under version control,Code-level hygiene,,Proportional,, 9 | Test data generated from version control,Code-level hygiene,,Proportional,, 10 | ML models under version control,Code-level hygiene,,Proportional,, 11 | CodeScene Code Health,Code-level hygiene,,Proportional,, 12 | CodeScene temporal coupling,Code-level hygiene,,Inverse,, 13 | CodeScene Complexity,Code-level hygiene,,Inverse,, 14 | CodeScene Team Autonomy,Decoupling and Isolation,,,, 15 | Tech quality,Code-level hygiene,,Proportional,, 16 | Psychological Safety,Incentives for reliability,,Proportional,, 17 | Speed of environment rebuild,Decoupling and Isolation,,Proportional,, 18 | Frequency of environment rebuild,Decoupling and Isolation,,Proportional,, 19 | Typical WIP,Speed of remediation,,Conditional,, 20 | Flow Efficiency,Speed of remediation,,Proportional,, 21 | Onboarding Speed,Decision-making context,,Proportional,, 22 | Branch Age,Code-level hygiene,,Inverse,, 23 | Steps to create a Release Candidate,Code-level hygiene,,Inverse,, 24 | Config Options,Observability,,Proportional,, 25 | Broken Builds,Code-level hygiene,,Inverse,, 26 | Stubs,Decoupling and Isolation,,Proportional,, 27 | Spend on operability,Incentives for reliability,,Proportional,, 28 | Show active feature toggles,Observability,,Proportional,, 29 | System Health,Understanding of system behaviour,,Proportional,, 30 | Testing logging,Understanding of system behaviour,,Proportional,, 31 | Track TLS cert expiry,Understanding of system behaviour,,Proportional,, 32 | Failure Modes,Observability,,Conditional,, 33 | Unit Test coverage,Code-level hygiene,,Proportional,, 34 | Feature Test coverage,Code-level hygiene,,Proportional,, 35 | Test Data,Decoupling and Isolation,,Proportional,, 36 | CDCs/Pact,Decoupling and Isolation,,Proportional,, 37 | Service Availability,Understanding of system behaviour,,Conditional,, 38 | Synthetics,Understanding of system behaviour,,Proportional,, 39 | Service Health,Understanding of system behaviour,,Inverse,, 40 | SLIs,Understanding of system behaviour,,Inverse,, 41 | Error Budget  / Operability,Incentives for reliability,,Proportional,, 42 | Toil,Incentives for reliability,,Conditional,, 43 | Time to Diagnose,Understanding of system behaviour,,Proportional,, 44 | Accessibility of on-call,Understanding of system behaviour,,Proportional,, 45 | Team API,Decision-making context,,Inverse,, 46 | Blocking dependencies,Decoupling and Isolation,,Inverse,, 47 | Team-sized services,Incentives for reliability,,Proportional,, 48 | Canary,Speed of remediation,,Proportional,, 49 | Blue-Green or phased,Speed of remediation,,Proportional,, 50 | Impact Isolation,Decoupling and Isolation,,Proportional,, 51 | Circuit Breaker,Decoupling and Isolation,,Proportional,, 52 | Exponential Back-off,Decoupling and Isolation,,Proportional,, 53 | Chaos Engineering,Decoupling and Isolation,,Proportional,, 54 | Distributed Tracing,Observability,,Proportional,, 55 | Blameless Postmortem,Incentives for reliability,,Inverse,, 56 | Perception of reliability,Reliability Through Customer Eyes,,Proportional,, 57 | Playbooks,Decision-making context,,Proportional,, 58 | UX under error conditions,Reliability Through Customer Eyes,,Proportional,, 59 | Code-level hygiene,Technical foundations,,Proportional,, 60 | Observability,Technical foundations,,Proportional,, 61 | Decoupling and Isolation,Technical foundations,,Proportional,, 62 | Speed of remediation,Socio-technical constraints,,Proportional,, 63 | Understanding of system behaviour,Socio-technical constraints,,Proportional,, 64 | Decision-making context,Human factors,,Proportional,, 65 | Incentives for reliability,Human factors,,Proportional,, 66 | Reliability Through Customer Eyes,Human factors,,Proportional,, 67 | Technical foundations,RELIABILITY,,Proportional,, 68 | Socio-technical constraints,RELIABILITY,,Proportional,, 69 | Human factors,RELIABILITY,,Proportional,, -------------------------------------------------------------------------------- /telus-conflux-reliability-model - Elements.csv: -------------------------------------------------------------------------------- 1 | Label,Type,Tags,Description,URL,Image,Metric,Measure,Source 2 | Lead Time,team measure,4 Key Metrics,The time taken for a change to flow from version control to the live systems.,https://itrevolution.com/measure-software-delivery-performance-four-key-metrics/,,Minutes,Lower is better,"Source: Accelerate, 2018" 3 | Deployment Frequency,team measure,4 Key Metrics,The frequency of deployments to the live systems. ,https://itrevolution.com/measure-software-delivery-performance-four-key-metrics/,,Deployments per day,Higher is better,"Source: Accelerate, 2018" 4 | Mean Time To Recovery,team measure,4 Key Metrics,Often just MTTR. The mean time taken for service to be restored in the live systems fter an incident or outage. ,https://itrevolution.com/measure-software-delivery-performance-four-key-metrics/,,Minutes,Lower is better,"Source: Accelerate, 2018" 5 | Change Failure percentage,team measure,4 Key Metrics,The % of changes to live systems that fail. ,https://itrevolution.com/measure-software-delivery-performance-four-key-metrics/,,%,Lower is better,"Source: Accelerate, 2018" 6 | Code under version control,team measure,Version Control Hygiene|Continuous Delivery,The % of source code that is stored in version control as the source of truth. ,http://cdchecklist.info/,,%,Higher is better,"Source: Continuous Delivery, 2010" 7 | Config under version control,team measure,Version Control Hygiene|Continuous Delivery,"The % of configuration that is stored in version control as the source of truth. Source: Continuous Delivery, 2010",http://cdchecklist.info/,,%,Higher is better,"Source: Continuous Delivery, 2010" 8 | Schemas under version control,team measure,Version Control Hygiene|Continuous Delivery,"The % of schemas (for databases and other data stores) that is stored in version control as the source of truth. Source: Continuous Delivery, 2010",http://cdchecklist.info/,,%,Higher is better,"Source: Continuous Delivery, 2010" 9 | Test data generated from version control,team measure,Version Control Hygiene|Continuous Delivery,"The % of test date that is generated from scripts stored in version control as the source of truth. Source: Continuous Delivery, 2010",http://cdchecklist.info/,,%,Higher is better,"Source: Continuous Delivery, 2010" 10 | ML models under version control,team measure,Version Control Hygiene|Continuous Delivery,"The % of Machine Learning (ML) models that are generated from scripts and code stored in version control as the source of truth. Source: Continuous Delivery, 2010",http://cdchecklist.info/,,%,Higher is better,"Source: Continuous Delivery, 2010" 11 | CodeScene Code Health,team measure,Codebase Health|CodeScene,Aggregate Code Health score from CodeScene. 10 is good and 1 is bad. ,https://codescene.io/docs/guides/technical/biomarkers.html,,1 to 10,Higher is better,See https://codescene.io/ 12 | CodeScene temporal coupling,team measure,Codebase Health|CodeScene,Highest temporal coupling detected - the % of time when two files change together.,https://docs.enterprise.codescene.io/versions/4.4.8/guides/technical/change-coupling.html,,Percentage,Lower is better,See https://codescene.io/ 13 | CodeScene Complexity,team measure,Codebase Health|CodeScene,The ratio of Cyclomatic Complexity to Lines of Code (LoC),https://docs.enterprise.codescene.io/versions/4.4.8/guides/technical/complexity-trends.html,,Complexity/LoC,Lower is better,See https://codescene.io/ 14 | CodeScene Team Autonomy,team measure,Codebase Health|CodeScene,TBC,TBC,,TBC,,See https://codescene.io/ 15 | Tech quality,team measure,Team Health|MSDA,How healthy is the code base? ,TBC,,1 to 10,Higher is better,Source: Multi-team Software Delivery Assessment from Confux http://softwaredeliveryassessment.com/ 16 | Psychological Safety,team measure,Team Health|MSDA,How good is the psychological safety in the team? Use the Psychological Safety Tool Kit to assess. ,https://www.psychsafety.co.uk/asp-products/psychological-safety-action-pack/,,,Higher is better,Source: Multi-team Software Delivery Assessment from Confux http://softwaredeliveryassessment.com/ 17 | Speed of environment rebuild,team measure,Deployment|MSDA,How quickly can you rebuild a typical environment? ,https://notafactoryanymore.com/2018/03/01/mircos-self-assessment-questions-of-devops-maturity/,,Minutes,Lower is better,Source: Multi-team Software Delivery Assessment from Confux http://softwaredeliveryassessment.com/ 18 | Frequency of environment rebuild,team measure,Deployment|MSDA,How often do you rebuild a typical environment? ,https://notafactoryanymore.com/2018/03/01/mircos-self-assessment-questions-of-devops-maturity/,,Rebuilds per month,Higher is better,Source: Multi-team Software Delivery Assessment from Confux http://softwaredeliveryassessment.com/ 19 | Typical WIP,team measure,Flow|MSDA,The typical number of Work in Progress items for the team. Lower is usually better; higher WIP than team members implies blocking. ,,,Integer,"Contextual: typically, any WIP greater than the number of team members is bad. The greater that number, the worse the problem.",Source: Multi-team Software Delivery Assessment from Confux http://softwaredeliveryassessment.com/ 20 | Flow Efficiency,team measure,Flow|MSDA,The Flow Efficiency for your team. ,https://tasktopblog.wpengine.com/flow-efficiency/,,%,Higher is better,Source: Multi-team Software Delivery Assessment from Confux http://softwaredeliveryassessment.com/ 21 | Onboarding Speed,team measure,Flow|MSDA,The time taken for a new team member to deploy to the live systems + the time taken for a new team member to diagnose a typical problem in the live systems. ,,,Minutes,Lower is better,Source: Multi-team Software Delivery Assessment from Confux http://softwaredeliveryassessment.com/ 22 | Branch Age,team measure,Flow|MSDA,The typical age of non-main branches in version control. 2 days or less is healthy. Older than 2 days is increasingly unhealthy. ,,,Days,Lower is better,Source: Multi-team Software Delivery Assessment from Confux http://softwaredeliveryassessment.com/ 23 | Steps to create a Release Candidate,team measure,Continuous Delivery|MSDA,The number of special manual steps or clicks needed to create a Release Candidate in software. Fewer steps is better (ideally 0). ,,,Integer,Lower is better,Source: Multi-team Software Delivery Assessment from Confux http://softwaredeliveryassessment.com/ 24 | Config Options,team measure,Continuous Delivery|MSDA,How quickly can you diff the config for two environments? ,,,Minutes,Lower is better,Source: Multi-team Software Delivery Assessment from Confux http://softwaredeliveryassessment.com/ 25 | Broken Builds,team measure,Continuous Delivery|MSDA,How many time per month do you check in (or merge) on a broken build? ,,,Integer,Lower is better,Source: Multi-team Software Delivery Assessment from Confux http://softwaredeliveryassessment.com/ 26 | Stubs,team measure,Continuous Delivery|MSDA,"What percentage of ""external"" services are  only ever called directly (never stubbed)? ",,,%,Lower is better,Source: Multi-team Software Delivery Assessment from Confux http://softwaredeliveryassessment.com/ 27 | Spend on operability,team measure,Operability|MSDA,"Low: no spend or no tracking Higher score: 20-30% OR Error Budget. Upt around 30%, higher is better.",,,,Higher is better,Source: Multi-team Software Delivery Assessment from Confux http://softwaredeliveryassessment.com/ 28 | Show active feature toggles,team measure,Operability|MSDA,How quickly can you show all active feature toggles? ,,,Minutes,Lower is better,Source: Multi-team Software Delivery Assessment from Confux http://softwaredeliveryassessment.com/ 29 | System Health,team measure,Operability|MSDA,How quickly can you determine the health of the system? ,,,Minutes,Lower is better,Source: Multi-team Software Delivery Assessment from Confux http://softwaredeliveryassessment.com/ 30 | Testing logging,team measure,Operability|MSDA,How many tests do you have in place to test that logging is working in the live systems (that log events are emitted correctly based on system activity)?,https://www.infoq.com/articles/why-test-logging/,,Integer,Higher is better,Source: Multi-team Software Delivery Assessment from Confux http://softwaredeliveryassessment.com/ 31 | Track TLS cert expiry,team measure,Operability|MSDA,How quickly can you discover the expiry dates of all the TLS certs in your production env? Example: `$ echo | openssl s_client -servername {SERVER_NAME} -connect {SERVER_NAME}:{PORT} | openssl x509 -noout -dates`. ,https://www.cyberciti.biz/faq/find-check-tls-ssl-certificate-expiry-date-from-linux-unix/,,Minutes,Lower is better,Source: Multi-team Software Delivery Assessment from Confux http://softwaredeliveryassessment.com/ 32 | Failure Modes,team measure,Operability|MSDA,"For non-trivial systems we expect 30-150 failure modes. Higher is generally better, because a higher number of failure modes identified means that the team has engaged with the realities of distributed computing.",,,Integer,Higher is better,Source: Multi-team Software Delivery Assessment from Confux http://softwaredeliveryassessment.com/ 33 | Unit Test coverage,team measure,Testability|MSDA,Low: 10% Higher: 80%+ coverage. ,,,%,Higher is better,Source: Multi-team Software Delivery Assessment from Confux http://softwaredeliveryassessment.com/ 34 | Feature Test coverage,team measure,Testability|MSDA,Low: 50% Higher: 100% coverage. ,,,%,Higher is better,Source: Multi-team Software Delivery Assessment from Confux http://softwaredeliveryassessment.com/ 35 | Test Data,team measure,Testability|MSDA,Low: 20% or less of test data is generated by scripts Higher: 100%. ,,,%,Higher is better,Source: Multi-team Software Delivery Assessment from Confux http://softwaredeliveryassessment.com/ 36 | CDCs/Pact,team measure,Testability|MSDA,How many dependencies use 'latest'? How out of date are pinned deps? ,,,%,Lower is better,Source: Multi-team Software Delivery Assessment from Confux http://softwaredeliveryassessment.com/ 37 | Service Availability,team measure,Reliability and SRE|MSDA,"Low score for ""100%"" - higher scores for 99.5, etc. at a service level (not blanket)",,,,Contextual,Source: Multi-team Software Delivery Assessment from Confux http://softwaredeliveryassessment.com/ 38 | Synthetics,team measure,Reliability and SRE|MSDA,What % of time do the synthetics detect problems before users? Higher is better.,,,%,Higher is better,Source: Multi-team Software Delivery Assessment from Confux http://softwaredeliveryassessment.com/ 39 | Service Health,team measure,Reliability and SRE|MSDA,"How often is a single, clear metric representing Service Health refreshed from live data?",,,Lower is better,,Source: Multi-team Software Delivery Assessment from Confux http://softwaredeliveryassessment.com/ 40 | SLIs,team measure,Reliability and SRE|MSDA,How often is a combination of metrics representing SLIs refreshed from live data?,,,Lower is better,,Source: Multi-team Software Delivery Assessment from Confux http://softwaredeliveryassessment.com/ 41 | Error Budget  / Operability,team measure,Reliability and SRE|MSDA,How much error budget do you have left each month? ,,,Minutes,Lower is better,Source: Multi-team Software Delivery Assessment from Confux http://softwaredeliveryassessment.com/ 42 | Toil,team measure,Reliability and SRE|MSDA,Low score: toil is > 50% OR we do not deal with live services,,,,Contextual,Source: Multi-team Software Delivery Assessment from Confux http://softwaredeliveryassessment.com/ 43 | Time to Diagnose,team measure,Reliability and SRE|MSDA,How long does it typically take to diagnose problems in the live/production environment? This is the time taken to understand and pinpoint what is wrong (not to fix or remediate the problem). ,,,Minutes,Lower is better,Source: Multi-team Software Delivery Assessment from Confux http://softwaredeliveryassessment.com/ 44 | Accessibility of on-call,team measure,On-call|MSDA,"How accessible is on-call? Specifically, what proportion of your team members are actually on-call regularly?",,,%,Higher is better,Source: Multi-team Software Delivery Assessment from Confux http://softwaredeliveryassessment.com/ 45 | Team API,team measure,Team API|Team Topologies,How up-to-date is your Team API details? How many weeks since the last update? ,,,Weeks,Lower is better,Source: Team Topologies - https://teamtopologies.com/ 46 | Blocking dependencies,team measure,Team Autonomy|Team Topologies,How many blocking dependencies do you suffer in a typical week/period? ,,,Integer,Lower is better,Source: Team Topologies - https://teamtopologies.com/ 47 | Team-sized services,team measure,Team Cognitive Load|Team Topologies,What % of the services/apps your team works on do you understand? ,,,%,Higher is better,Source: Team Topologies - https://teamtopologies.com/ 48 | Canary,team measure,Deployment technique,How many services (%) have a blue-green or phased roll-out capability? ,,,%,Higher is better,"Source: Continuous Delivery, 2010" 49 | Blue-Green or phased,team measure,Deployment technique,How many services (%) have a canary capability? ,,,%,Higher is better,"Source: Continuous Delivery, 2010" 50 | Impact Isolation,team measure,Runtime technique,"When an external service fails, how often does your service fail (% of cases)? ",,,%,Lower is better,Source: TELUS 51 | Circuit Breaker,team measure,Runtime technique,What % of your services use circuit-breaker when connecting to other systems? ,https://microservices.io/patterns/reliability/circuit-breaker.html,,%,Higher is better, 52 | Exponential Back-off,team measure,Runtime technique,What % of your services use exponential back-off when connecting to other systems? ,https://cloud.google.com/iot/docs/how-tos/exponential-backoff,,%,Higher is better, 53 | Chaos Engineering,team measure,Runtime technique,What % of your services are resilient to  random single-node failures? ,,,%,Higher is better, 54 | Distributed Tracing,team measure,Runtime technique,What % of calls have full end-to-end traces? ,,,%,Higher is better, 55 | Blameless Postmortem,team measure,Human technique,In what % of incidents is a single root cause sought? ,https://codeascraft.com/2016/11/17/debriefing-facilitation-guide/,,%,Lower is better, 56 | Perception of reliability,team measure,Human technique,How many (%) of your user journeys explicitly manage the perception of performance or reliability? ,,,%,Higher is better, 57 | Playbooks,team measure,Human technique,How often (%) do your Playbooks help with human-directed triage and remeditation? ,,,%,Higher is better,Source: TELUS 58 | UX under error conditions,team measure,UX|RTCE,How many (%) of your user journeys have a defined UX under error conditions? How many (%) of your user journeys have a workaround under error conditions? Take the average of these two measures. ,,,%,Higher is better,Source: TELUS/Conflux 59 | Code-level hygiene,context,,The quality of the code and practices around code and version control,,,,Higher is better,Source: TELUS/Conflux 60 | Observability,context,,The ability to observe the state and behavior of the system.,,,,Higher is better,Source: TELUS/Conflux 61 | Decoupling and Isolation,context,,The degree to which different parts of the system are decoupled and isolated.,,,,Higher is better,Source: TELUS/Conflux 62 | Speed of remediation,context,,How quickly problems in the live systems can be addressed.,,,,Higher is better,Source: TELUS/Conflux 63 | Understanding of system behaviour,context,,The overall understanding and awareness of the software systems.,,,,Higher is better,Source: TELUS/Conflux 64 | Decision-making context,context,,The quality of the context in teams and individuals for making decisions about the software systems.,,,,Higher is better,Source: TELUS/Conflux 65 | Incentives for reliability,context,,The social drivers for improving reliability.,,,,Higher is better,Source: TELUS/Conflux 66 | Reliability Through Customer Eyes,context,RTCE,The reliability of the systems as seen through the eyes of the customers of the systems.,http://rtce.net/,,,Higher is better,Source: TELUS/Conflux 67 | Technical foundations,genre,,Largely technical or technology-derived measures,,,,Higher is better,Source: TELUS/Conflux 68 | Socio-technical constraints,genre,,Largely socio-technical derived measures,https://github.com/matthewskelton/sociotechnical-architecture,,,Higher is better,Source: TELUS/Conflux 69 | Human factors,genre,,Largely human-derived measures,,,,Higher is better,Source: TELUS/Conflux 70 | RELIABILITY,reliability,,,,,,Higher is better, --------------------------------------------------------------------------------