{'fraction_non_alphanumeric': 0.023575638506876228, 'fraction_numerical': 0.003929273084479371, 'mean_word_length': 5.490445859872612, '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}}
Towards traceability from project management to system models

Traceability is commonly known as the ability to describe and follow links between artifacts, e.g. between requirements and their corresponding part of the system design. These links are typically inside of the system specification. Very few approaches consider traceability between the system specification and project management artifacts. By introducing links between these two models, a task can be traced to the system model elements it is related to. This paper proposes a unified model, which explicitly combines project management models and system specification models to enable traceability. We introduce and discuss the following key concepts, which are currently evaluated in a case study: (1) Ability to navigate between tasks and the according part of the specification, (2) Project management status aggregation by system specification artifacts, (3) Use of entities from the system model for project planning, (4) Unified model validation.