{'fraction_non_alphanumeric': 0.007497656982193065, 'fraction_numerical': 0.0, 'mean_word_length': 5.433734939759036, '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}}
Generic analysis metamodel based on service oriented software design

Analyzing software in order to evaluate its quality attributes is not a foreign concept in software lifecycle. There are many methods that can be implemented to analyze software with some focusing on source code analysis and others concentrating on analyzing software artifacts from various phases such as design artifacts. Service oriented software is not excluded from this. As software that uses services as part of its functionalities, service oriented software designs represent more completed view of the software compared to other artifacts. This work focus on identifying elements from design artifacts that represent service oriented software structure and behavior based on standard modeling language for service oriented architecture. The elements are then represented in a generic metamodel that can be used to analyze the software. A case study will be used to show how design artifacts from selected standard modeling language, SoaML being mapped to model based on proposed metamodel