{'fraction_non_alphanumeric': 0.013820335636722606, 'fraction_numerical': 0.005923000987166831, 'mean_word_length': 5.627450980392157, '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}}
Representing ODP enterprise language deontic tokens in UML

The ODP Enterprise Language is used to describe the organizational objectives and policies that apply to some system to be specified. It also captures constraints associated with the environment in which the system is to be used. Because the enterprise specification is concerned more with organizational issues than technical details of the system, there is considerable emphasis on obligations and norms, rather than on the declaration of some single rigidly required behaviour. The recently revised Enterprise Language is already able to express directly obligations and other deontic concepts, such as permissions and prohibitions. However, mapping such concepts into UML offers interesting challenges. This paper describes work currently in progress within the International Organization for Standardization (ISO) to extend the UML4ODP standard ISO/IEC 19793 for dealing with deontic concepts, and illustrates the approach with a simple case study.