{'fraction_non_alphanumeric': 0.017661900756938603, 'fraction_numerical': 0.0, 'mean_word_length': 5.4324324324324325, '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': 1, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
The Requirements Dissection Model: A Model for Aiding Users/Customers in the Development of Software Requirements

This paper briefly looks at the various methodologies that are used to represent software requirements. One of the deficiencies of the various software methodologies available is that they do not use terminology that the user/customer can understand. One of the ways to help in developing stable software requirements is to make the user/customer as actively involved as possible during the software development process. Unfortunately, not many software requirements notation models incorporate the user’s/customer’s viewpoint or, if they do, not in a way that can be easily understood by the user/customer. The Requirements Dissection Model is designed in simple language that an untrained user/customer can comprehend, yet sophisticated enough to capture the salient features of software systems for implementation in the design of these systems. Six representative systems were chosen to show how this Requirements Dissection Model can be implemented. After analyzing these systems, the paper concludes with ideas for future research on the Requirements Dissection Model.