This paper deals with the task of working out artifacts in software and system development, their representation, and the analysis and documentation of the relationships between their logical contents - often referred to as tracing and traceability. Among others, key tasks in system development are as follows: capturing, analyzing, and documenting system level requirements, the step to functional system specifications, the step to architectures given by the decomposition of systems into sub-systems with their connections and behavioral interactions. Each of these steps produces artifacts for documenting the development, as a basis for a specification and design rationale, for documentation, for verification, and impact analysis of change requests. Crucial questions are how to represent and formalize the content of these artifacts and how to relate their content. When designing multi-functional systems key artifacts are system level requirements, functional specifications, and architectures in terms of their sub-system specifications. Links and traces between these artifacts are introduced to relate their contents. Traceability has the goal to relate artifacts. Traceability is required for instance in standards for functional system safety such as the ISO 26262. We introduce a rigorous semantic approach to capturing artifacts by logics and to deal with traceability completely based on logical representations of system models.