{'fraction_non_alphanumeric': 0.017241379310344827, 'fraction_numerical': 0.0, 'mean_word_length': 5.760273972602739, '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}}
A case-based assessment of the FLUIDE framework for specifying emergency response user interfaces

In this paper, we report the results from assessing the FLUIDE Framework for model-based specification of user interfaces supporting emergency responders. First, we outline the special challenges faced when developing such user interfaces, and the approach used in the FLUIDE Framework to meet these challenges. Then we introduce the framework, including its two specification languages. Thereafter, we present the case addressing the specification of user interfaces for three existing emergency response applications. Based on these specifications, we discuss how well we succeeded, concluding that we were able to describe the applications in a comprehensive and understandable way taking similarities and difference between the applications into account. The language constructs function as intended, having two languages has proven valuable, and the specifications scale quite well.