{'fraction_non_alphanumeric': 0.04248088360237893, 'fraction_numerical': 0.022090059473237042, 'mean_word_length': 5.103626943005182, '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}}
TOWARDS A MULTIVIEWS COMPONENT BASED MODEL DRIVEN APPROACH

A Multiviews Component is an extension of a UML2.0 component [El Asri (2005a)], that offers a richer behavior by adopting the concept of views. The problem of its representation has been tackled by VUML [Nassar (2004)] [El Asri (2005b)], which is a UML extension (UML profile). In this paper, we propose an approach to implement Multiviews Components under the MDA (Model Driven Architecture) initiative [Soley (2000)]. This process follows two sequential steps: The first step is a PIM-to-PIM transformation. It transforms and converts a Multiviews Component (which is a Platform Independent Model) into a conventional UML component by applying a proprietary design pattern [Hain (2006)] [Hain (2007)]. The second step transforms the resulting PIM into a PSM (Platform Specific Model) that targets Java / EJB platform. Our approach offers two major advantages. The first advantage reduces the complexity related to VUML Multiviews Component handling by making it UML based. The second step implements these components into a specific development platform, which can be taken as an example for other target platforms.