{'fraction_non_alphanumeric': 0.02034587995930824, 'fraction_numerical': 0.003051881993896236, 'mean_word_length': 5.111801242236025, '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}}
8.1.3 Ten Questions to Ask Before Opening the Requirements Document

In projects where Systems Engineering is applied, the basis for contract is usually a set of Requirements, captured in one or more requirements documents. The Supplier must understand the requirement set, and evaluate his potential to supply the required functionality and performance at acceptable cost, timescale and risk. There is a risk that he may commit himself to a solution and a cost, thinking that the requirement set is understood, when in fact there are hidden omissions, contradictions and risks which expose the Supplier to potential project failures. This paper presents a simple checklist of ten questions, based on practical experience, that the Supplier's Requirements Analyst or Chief Engineer should ask himself, and ideally to ask his customer, before such a commitment. These questions do not depend on the detailed content of the requirements – instead they are properties of the set itself.