{'fraction_non_alphanumeric': 0.025157232704402517, 'fraction_numerical': 0.03270440251572327, 'mean_word_length': 5.170542635658915, '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 difficulty in distinguishing product from process

When engineers design a system, they must design both the product and the process that will create it. Accordingly, systems engineers must write requirements for the product and the process. Stating these requirements in separate documents might make it easier to get the requirements right and manage the requirements when either the product or the process requirements change. But, of course, these two sets of documents must be intricately interrelated, integrated, and produced with extensive feedback loops. This paper shows the results of an experiment that was designed to investigate the difficulty in distinguishing between the product and the process. © 2003 Wiley Periodicals, Inc. Syst Eng 6: 106–115, 2003 DOI 10.1002/sys.10035