{'fraction_non_alphanumeric': 0.023255813953488372, 'fraction_numerical': 0.0073439412484700125, 'mean_word_length': 5.244274809160306, '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}}
Enhancing ArgoUML by the Context-Based Component Constraint Language CCL

Software evolution is a major challenge to software development. When adapting a system model to new, altered or deleted requirements, existing requirements should not unintentionally be violated. Therefore, the context-based component constraint language CCL specifies which requirement applies to which parts of a system. It is based on UML and uses a new technique: one context-based constraint (CoCon) specifies a requirement for a group of components, interfaces or business objects that share a context. Thus, compliance with requirements can be verified automatically when modells are modified. We plan to implement a CCL plugin for ArgoUML in winter 2001/02. This Plugin will add new diagrams and enhance the design critique mechanism.