{'fraction_non_alphanumeric': 0.01717967072297781, 'fraction_numerical': 0.0021474588403722263, 'mean_word_length': 6.096446700507614, '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}}
Directives of Communicability for Software Artifacts

Software artifacts created in the early stages of the development process describe the proposed solutions for the system, such as UML and prototypes. For this reason, these artifacts are important for team communication. Miscommunication via artifacts occurs because practitioners typically focus on modeling, without reflecting on how other software development team members interpret them. Incorrect information during the development process can be introduced in the system due to miscommunication, impacting its quality. In this context, this work aimed to answer the following research question: How to support effective communication between producers and consumers of artifacts developed in the early stages of software development? To answer this question, we proposed the Directives of Communicability (DCs), based on theories that investigate different communication perspectives and exploratory studies. We designed the DCs to support practitioners to analyze characteristics that affect the artifact's content on communication. We conducted different empirical studies with our proposal, with 105 participants from industry and academia. From the empirical studies results, we noticed the DCs supported the reflection of producers’ artifacts, contributing to effective communication and reducing defects caused by miscommunication.