{'fraction_non_alphanumeric': 0.02422145328719723, 'fraction_numerical': 0.0, 'mean_word_length': 5.820754716981132, '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}}
Object-Orientation in Graph-Based Design Grammars

The ongoing digital transformation in industry applies to all product life cycle's stages. The design decisions and dimensioning carried out in the early conceptual design stages determine a huge part of the product's life cycle costs (LCC). The automation of the conceptual design phase promises therefore huge gains in terms of LCC. Design grammars encode design processes in production systems made up of rule sequences which automatically create an abstract central product model (central data model) from given requirements. Graph-based design languages use the Unified-Modeling-Language (UML) to define the product entities (classes) supporting object-oriented inheritance. Graphical rules instantiate the classes and iteratively assemble the central model. This paper proposes to extend the design languages by introducing methods (operations). This allows the use of object-oriented design patterns and interface mechanisms as object-oriented principles are then fully implemented. A graphical mechanism to model the method calls is presented which integrates seamlessly into the graph-based design language's graphical rule specification. The object oriented design grammar enables modularization and reusability of engineering knowledge. The integration of engineering domains is enhanced and multistakeholder collaboration with access control (information security) becomes feasible.