{'fraction_non_alphanumeric': 0.021437578814627996, 'fraction_numerical': 0.0, 'mean_word_length': 4.838235294117647, '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}}
Transformation of Use Cases to EPC Models

Within the requirements phase of many projects, functional requirements are often documented as Use Cases. Within SOA projects, however, these Use Cases are not sufficient since they do not represent a global control flow resembling the one of a business process an integral aspect of a SOA. Instead they are written from the point of view of a single actor. This makes an additional step necessary: Converting the Use Cases to business processes, which is – if done manually – a tremendous task. To reduce this effort wasted on conversion, this paper proposes a method for generating business processes – expressed as EPC – as from Use Cases. Thereby, the need for extensive business process modelling after gathering the requirements is eliminated.