Sneed, HarryBecker, SteffenBogicevic, IvanHerzwurm, GeorgWagner, Stefan2019-03-142019-03-142019978-3-88579-686-2https://dl.gi.de/handle/20.500.12116/20899The following paper presents the current state of the author’s research on the subject of static software tracing, a research which dates back to the year 2000 when the author was requested to predict the costs of software maintenance projects. The goal of static tracing is to link the software artifacts produced in software development with the original requirements. These artifacts are linked by comparing the data names they use, i.e. their operands, with the nouns in the requirement text. Artifacts that have data names similar to those used in the requirement texts are considered to be implementations of those requirements.enRequirement modelsDesign modelsCode modelsTest modelsModel comparisontracing requirementslinking software artifactsconsistencycompletenessChecking Consistency and Completeness of Software SystemsText/Conference Paper10.18420/se2019-391617-5468