{'fraction_non_alphanumeric': 0.017011834319526627, 'fraction_numerical': 0.0, 'mean_word_length': 5.382075471698113, '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}}
Juggling Concern for Completeness and Consistency with Concerns for Flexibility and Adaptability Using Most

The Multi-Oriented Structured Task analysis (MOST) methodology attempts to be most things to most of its users most of the time by balancing the needs of both system users and system designers for flexibility and adaptivity. The MOST methodology structures a task analysis and integrates it with other more formal specification methodologies including software engineering methodologies, human-computer interaction methodologies, and explicit user models. MOST stores these specifications in a knowledge base of four major interlinked foci for the information (users, tasks, data, and tools) and an optional foci (constraints) that can be linked to any of the major foci. The linkages in a MOST knowledge base facilitate the flexible structuring and restructuring of records. These linkages can model alternative designs and/or paths by which a system can adapt its interface while maintaining functional consistency. Various design heuristics (both software engineering and human factors) can be applied to an analysis recorded in a MOST knowledge base to assist in its transformation into a suitable design. The MOST methodology is designed to cooperate with and to assist the designer rather than to force the user to serve the methodology.