{'fraction_non_alphanumeric': 0.008733624454148471, 'fraction_numerical': 0.0, 'mean_word_length': 5.811881188118812, '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': 1, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
Specification Modules for Methodical System Development

We show how an alternative approach to document-oriented specification can ease the system design process. By identifying the modeling concepts needed for a complete system specification in an underlying conceptual model a specification can be interpreted as one single well-formed information complex avoiding inconsistencies as found in document oriented approaches. Besides a more intuitive development and treatment of specifications, an immediate benefit of a design process based on a conceptual model is the possibility to define specification modules that can be used as building blocks to assemble complex specifications.