{'fraction_non_alphanumeric': 0.02132701421800948, 'fraction_numerical': 0.0, 'mean_word_length': 5.869918699186992, '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}}
A systematic software development process for non-functional requirements

As the importance of non-functional requirements has increased, many researchers have become interested in software development process for non-functional requirements including the notation, modeling, and assessment of non-functional requirements. However, the characteristics of non-functional requirements are so sophisticated that there have been many topics that should be defined more clearly. In order to address one of the challenging topics, we propose a systematic software development process to support the management of nonfunctional requirements. The process consists of six steps, each of which is composed of detailed activities. Using the proposed process, the non-functional requirements can be more effectively and systematically managed and modeled.