{'fraction_non_alphanumeric': 0.020942408376963352, 'fraction_numerical': 0.013961605584642234, 'mean_word_length': 4.857142857142857, '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}}
5.4.1 Would the real systems engineer please stand up?

The conventional systems engineering process (as defined in ISO 15288 or the INCOSE SE handbook) assumes that projects start with a defined requirement or problem statement and end with contract acceptance or in‐service validation. This has led to a belief by some in industry that the role of systems engineers within client organisations is kicking‐off and accepting well formed programmes for industry to deliver. Whilst this is an important role, it is not the only part of the client side systems engineer's job.