{'fraction_non_alphanumeric': 0.025711662075298437, 'fraction_numerical': 0.0, 'mean_word_length': 5.411764705882353, '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}}
Improving the Quality and the Comprehension of Requirements: Disciplined Use Cases and Mockups

In this paper we sketch a novel method for writing requirements specifications that enriches disciplined use cases with screen mock-ups. Disciplined use cases are characterized by a quite stringent template, strongly structuring also the form of the scenarios' steps (e.g., The subject of each step must be explicit). That structuring allows to impose further constraints helping to prevent common mistakes and to increase the quality of the specifications (e.g., Defining a detailed glossary helps to avoid confusion and ambiguities). Disciplined use case are still expressed using natural language, but the strong structuring allows to reach a good level of precision without having to introduce new notations. Screen mock-ups associated with the scenarios' steps, present the corresponding GUIs as seen by the human actors before/after the step executions, improving the comprehension of the requirements, and allowing also to precisely present user interface's non-functional requirements.