Under CopyrightKnethen, A. vonA. vonKnethenGrund, M.M.Grund2022-03-0714.10.20032003https://publica.fraunhofer.de/handle/publica/29184910.24406/publica-fhg-291849Goal of this report is to define different types of relationships between documentation entities of the QUASAR requirements documents. The described types of relationships are the foundation for development, traceability, and impact analysis guidance. In this report, types of relationships between documentation entities are identified and defined based on two conceptual models: a conceptual system and a conceptual documentation model. The conceptual system model defines the domain dependent and abstract content of the QUASAR requirements documents independent of its representation (e.g., system or software functions). The conceptual documentation model describes how this domain dependent content is represented by documentation entity types (e.g., actor, use-case, mode, or statechart) in the QUASAR requirements documents. Using two conceptual models to identify and document types of relationships has various benefits: (1) the conceptual system model help domain-dependent types of relationships to be defined, and (2) relationships between the conceptual system and the conceptual documentation model show (2a) what types of documentation entities have to be related to reflect the domain-dependent relationships and (2b) what types of documentation entities are related because they represent the same content. The conceptual models described are based on the QUASAR requirements documentation structure [KvKP02], a case study from the automotive industry [HP01], and the conceptual models defined by [vKn01]. This report is targeted to requirements engineers and researchers, in particular at DaimlerChrysler AG. Previous versions of this report were written also as a basis for discussion within the QUASAR project to promote the concepts for structuring requirements developed.Table of Contents S.vii-viii 1 Motivation S.1-3 2 Conceptual system model S.4-31 - 2.1 Problem (P)-Level S.6-14 - 2.1.1 Items S.7-8 - 2.1.2 Functions S.9-11 - 2.1.3 Constraints S.11-13 - 2.1.4 Relationships S.13-14 - 2.2 Technology (T)-Level S.14-21 - 2.2.1 Items S.14-16 - 2.2.2 Functions S.16-18 - 2.2.3 Constraints S.18-19 - 2.2.4 Relationships S.19-21 - 2.3 Software (S)-Level S.21-31 - 2.3.1 Items S.21-24 - 2.3.2 Functions S.24-28 - 2.3.3 Constraints S.28-30 - 2.3.4 Relationships S.30-31 3 Conceptual documentation model S.32-120 - 3.1 System Requirements Document S.33-52 - 3.1.1 Overview S.34-39 - 3.1.2 Context Description S.40-41 - 3.1.3 Variables S.42-44 - 3.1.4 Functional Requirements S.44-46 - 3.1.5 Non-functional Requirements S.47-50 - 3.1.6 Project Issues S.50-52 - 3.2 System Specification Document S.53-75 - 3.2.1 Overview S.54-60 - 3.2.2 Context Description S.60-63 - 3.2.3 Variables and mapping S.63-64 - 3.2.4 Functional Requirements S.65-69 - 3.2.5 Non-functional Requirements S.69-72 - 3.2.6 Project Issues S.73-75 - 3.3 Software Requirements Document S.76-98 - 3.3.1 Overview S.77-83 - 3.3.2 Context Description S.84-86 - 3.3.3 Variables and mapping S.86-88 - 3.3.4 Functional Requirements S.88-92 - 3.3.5 Non-functional Requirements S.92-95 - 3.3.6 Project Issues S.96-98 - 3.4 Software Specification Document S.99-120 - 3.4.1 Overview S.100-106 - 3.4.2 Context Description S.106-108 - 3.4.3 Variables and mapping S.108-110 - 3.4.4 Functional Requirements S.110-114 - 3.4.5 Non-functional Requirements S.114-117 - 3.4.6 Project Issues S.118-120 4 Summary and Conclusion S.121-122 References S.123-125enQUASARconceptual modelMeta-modelconceptual system modelconceptual documentation model004005006report