{'fraction_non_alphanumeric': 0.013003901170351105, 'fraction_numerical': 0.0, 'mean_word_length': 5.754385964912281, '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}}
From Groupware Requirements to Services Design: Supporting the Development Process of a Pre-meeting Application

In the groupware development process the generated code usually does not reflect adequately the functional requirements initially specified. This is related to the complexity of collaborative system domain, and the ever changing requirements according to the evolution of the involved activities. This paper describes an MDA process which was deployed in a SOA infrastructure (WGWSOA) in order to support the development of a pre-meeting application. Through this development process we aimed to enhance the linkage permanence between different models which are generated during the design of specific collaborative services in a middleware infrastructure.