{'fraction_non_alphanumeric': 0.014744145706851692, 'fraction_numerical': 0.0, 'mean_word_length': 5.709302325581396, '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}}
A Requirements Engineering Process Adapted to Global Software Development

Global software development is spreading increasingly within companies. Although it provides some competitive advantages, such as speeding up the software delivery, reducing cost, and taking advantage of more economic resources, this working model is a very complex one. Threats, such as geographic distance and cultural differences, may impact negatively on activities and artifacts of the software process. Untreated threats usually affect the quality of the requirements, propagating defects to subsequent development phases. Global software development threats were studied in a real major project, where no special treatment was put into practice to mitigate them. Analyzing the serious consequences on that project, a proposal was developed using a Lexicon model and Scenarios in order to mitigate threats to requirements in this distributed working mode. The proposal was applied in a new real project of similar characteristics, and the comparison of results from both projects gives promising perspectives in terms of requirements quality and process time improvements.