{'fraction_non_alphanumeric': 0.03118712273641851, 'fraction_numerical': 0.01609657947686117, 'mean_word_length': 5.180124223602484, 'pattern_counts': {'":': 0, '<': 0, '<?xml version=': 0, '>': 0, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
The Crisis in Software: The Wrong Process Produces the Wrong Results

YOUR ORGANIZATION—WHETHER business, governmental, or nonprofit—likely needs to be able to create value by building, customizing, and using software. Without software, your ability to achieve your goals as a business leader is inherently limited, if not impossible. But despite this need, software development has historically been an unreliable, costly, error-prone endeavor. This leaves you in a pickle: You need software, but you can’t get what you need, when you need it, at a cost that is acceptable, at a level of quality the makes it usable. Indeed, the Standish Group’s 2011 CHAOS Report found that more than half of software projects conducted between 2002 and 2010 were either described as challenged or complete failures; just 37 percent were classified as successful (Figure 1.1) The Standish Group modestly defined a successful project as delivering all the requested functionality, on the expected date, for the