{'fraction_non_alphanumeric': 0.01695906432748538, 'fraction_numerical': 0.0, 'mean_word_length': 5.505703422053232, '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}}
Modeling of User Interfaces for Conceptual Content Management Systems

Conceptual Content Management Systems (CCMSs) were conceived with the intention of superseding some of the limitations of information systems, such as either failing to stay open to constantly changing domain environments or not being able to dynamically integrate evolution steps. In as much as this target has been achieved CCMSs, however, still need to take responsibility to offer at least the same services as conventional information systems. This study examines one of the paramount services, namely to enable interaction with the user. For this, CCMSs need to offer visualization and the visualization has to be flexible to accommodate changes and support on-the-fly evolution by adopting CCM system properties of openness and dynamics. This primarily necessitates the design of flexible and scalable conceptual User Interface (UI) component and technology models that can be mapped onto concrete ones by generative means. This study furthermore argues that understandability and hence usability can be fostered on the UI by simulating ObjectOriented (OO) concepts, such as inheritance, association and composition. This is done by formally binding every application specific information type to be visualized with conceptual UI components. On request for displaying information, valid formal bindings are evaluated, followed by a view update with respective actual bindings for these formal bindings. Together with the above-mentioned advantages, the end result of modeling UIs for CCMSs is that complex UIs are easily created, since an interface designer need not worry about their real implementations on target UI technologies.