{'fraction_non_alphanumeric': 0.025227750525578137, 'fraction_numerical': 0.0, 'mean_word_length': 5.641860465116279, '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}}
Integrating DSLs into a Software Engineering Process: Application to Collaborative Construction of Telecom Services

The development of large and complex systems involves many people, stakeholders. Engineeringly speaking, one way to control this complexity is by designing and analyzing the system from different perspectives. For each perspective, stakeholders benefit from means, tools, languages, specific to their activity domain. A Domain Specific Language (DSL) per perspective is such a dedicated means. While DSLs are used for modeling, other means, tools, languages, are needed for other connected activities, like testing or collaborating. However, using together such different types of tools, integrating DSLs into stakeholders' software process, is not straightforward. In this chapter we advance an integration process of DSLs with other tools. To each stakeholder, we propose they have their own DSL with associated graphical editor, operational semantics and generation of scripts for off the shelf simulators for e.g. testing. Additionally to the integrated stakeholders' software process, we introduce a model driven process dedicated to the tool vendor which creates the DSLs and its associated tools. Due to the integration of DSLs into this process, we contend that stakeholders will significantly reduce system construction time. We illustrate the two processes on Telecommunications service construction.