{'fraction_non_alphanumeric': 0.02142857142857143, 'fraction_numerical': 0.0031746031746031746, 'mean_word_length': 5.602094240837697, '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}}
Process Use Cases: Use Cases Identification

The identification of use cases is one key issue in the development of interactive information systems. User participation in the development life cycle can be seen as critical to achieve usable systems and has proven its efficacy in the improvement of systems appropriateness. Indeed, the involvement of users in the requirements definition can add a significant improvement in both consecutive/interleaved tasks of: (i) understanding and specifying the context of use, and, (ii) specifying the user and organizational requirements, as defined in Human-Centered Design (HCD) (Organizations, 1999). Existing solutions provide a way to identify business processes and/or use cases in order to achieve system definition, but they don’t do it in an agile and structured way that helps to efficiently bridge between Business Process Management and Software Engineering. Process Use Cases is a methodology, defined in the Goals software construction process, for the identification of use cases and information entities during the modeling and reorganization of business processes focusing the results in the identification of the functional requirements for the correct development of an interactive information system.