{'fraction_non_alphanumeric': 0.012205754141238012, 'fraction_numerical': 0.0, 'mean_word_length': 6.220125786163522, '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}}
Documenting Regulatory Requirements Decision-Making as a Compliance Concern

Software practitioners must implement a growing list of regulatory and security mandates, but have no established tool or mechanism for demonstrating their due diligence or compliance efforts exists. Providing an approach does more than help software practitioners. External agencies and auditors also need tools or mechanisms to enforce compliance requirements. Consumers also benefit. Standardized approaches a mechanism for accountability regarding compliance without software organizations compromising its proprietary or sensitive information. Currently, perceptions, practices, or decision making on regulatory or security standard compliance is not a well researched area in academia. Our research aims to understand the practices and decision making software organizations apply toward regulatory compliance requirements during the software development process. Then, we take this improved understanding and apply it to building an approach that auditors or regulators can use to validate regulatory compliance throughout the entire software development process.