Date: Thu, 28 Mar 2024 14:08:45 +0100 (CET) Message-ID: <388138643.390.1711631325557@nm-docs> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_389_1651896671.1711631325557" ------=_Part_389_1651896671.1711631325557 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
Requirement Diagram is particularly valuable when you want to demonstrat= e the traceability from the requirements to the elements in your system mod= el that are dependent on them. This diagram provides modeling constructs to= represent text-based requirements and relate them to other modeling elemen= ts. These requirement modeling constructs are intended to provide a bridge = between traditional requirement management tools and other SysML models.
Requirements diagrams display requirements, packages, other classifiers,= test cases, rationales, and relationships. Possible relationships availabl= e for Requirements diagrams are containments, deriveReqt and requirement de= pendencies (=E2=80=98Copy=E2=80=99, =E2=80=98Refine=E2=80=99, =E2=80=98Sati= sfy=E2=80=99, =E2=80=98Trace=E2=80=99, and =E2=80=98Verify=E2=80=99). The c= allout notation can also be used to reflect the relationships of other mode= ls.
Requirements can also be shown on other diagrams to illustrate their rel= ationships to other modeling elements.