Date: Thu, 28 Mar 2024 21:02:25 +0100 (CET) Message-ID: <326480719.1083.1711656145614@nm-docs> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_1082_726371349.1711656145613" ------=_Part_1082_726371349.1711656145613 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
Working on a server project requires an up-to-date knowledge of all rele= vant project changes. For this, we introduce a new set of validation rules = for suspect link analysis. These rules help you track changes in requiremen= ts that are linked to design elements (such as SysML Blocks, Test Cases, Us= e Cases, etc.) by Satisfy, Derive, Refine or Verify relationships, and stay= informed about unlinked and deprecated requirements in the model.
Before you start tracking changes using the Suspect Link analysis, make = sure your model (or its particular elements) are locked.
To learn about the requirements tracking, r= ead the following topics:
You can also create your own suspect links customization to keep track o= f the changes in the elements of the specified type. To learn more, read th= e following topic: