Suspect Links, Approvals and TBD/TBR in SysML v2 Projects

Needs & Requirements has the same change-control pages as in LMLLifecycle Modeling Language An open modeling language with a small set of classes and relationships that covers a system's whole lifecycle. Holarch models are LML models. projects: TBDTo Be Determined A requirement value or detail that is not known yet. Holarch tracks TBDs with an owner and a due date./TBRTo Be Reviewed A requirement value that is filled in but still needs to be confirmed., Suspect Links and Approvals, working on the model's requirements.

• Suspect links. When a requirement changes, the links that depend on it become suspect in the same undo step: its satisfied by (satisfy), verified by (verify), decomposed by (owned requirements) and traced to (dependency) links. A change is an edit of its name or doc, of a key attribute (Priority, Criticality, Verification Method, Verification Level), of the value of an attribute it owns (attribute :>> limit = maxCurbMass;) or of one of its constraints, and of a target attribute those values or constraints name (attribute maxCurbMass : MassValue = 1650 [kg];). It counts wherever you make it: the Editor, a view, the inspector or a table. A changed Verification Method or Level makes only the verified by links suspect; setting the first one makes none suspect.
• Suspect Links lists each suspect link with what changed, when and by whom. Diff shows the old and new name and doc; Show in Text opens the requirement in the Editor. Clear… records that you checked the linked element, with an optional comment on it. A suspect element shows a banner with Review… in the inspector and a Suspect badge in tables; the Database view Suspect links lists them.
• Approvals. A requirement's Status runs Draft → In Review → Approved or Rejected. The inspector shows the status with Approve, Reject… and Reopen, and who set it and when. People with the Reviewer role can approve and reject. Editing the text of an Approved requirement moves it back to In Review. Approvals lists the requirements In Review; My Work lists them under Awaiting review, and on a hosted project the reviewers get a notification. The status is Holarch data next to the model; it is not part of the SysML text.
• TBD/TBR. A requirement is open when its TBD/TBR attribute is TBD or TBR, when TBD, TBR or TBSTo Be Supplied A value that another party will provide later. Holarch treats it as an open item, like a TBD. appears in its name or doc, or when one of its attribute values carries TBD or TBR metadata. The register lists each with its owner, due date and age, a burn-down of open items and Export XLSX. Close sets the attribute back to None and removes the values' TBD/TBR metadata; marks in the doc close when you edit it.
• TBD/TBR on a value. Writing TBD in place of a value is not valid SysML. Mark the attribute with metadata from the package HolarchMetadata instead: import it (private import HolarchMetadata::*;), then write #TBD attribute chargerPower : PowerValue; for a value still to be determined (leave the value out, or give an estimate) and #TBR attribute limit : TimeValue = 0.5 [h]; for a value to be reviewed. To record who owns it and why, use the long form in the attribute's body: @TBD { owner = "Powertrain lead"; rationale = "The charging standard is not chosen yet."; due = "2026-12-01"; }. TBD and TBR specialize ModelingMetadata::StatusInfo, so other SysML v2 tools read them as status annotations, and @StatusInfo { status = StatusKind::tbd; } counts too. Insert ▾ → TBD Value and TBR Value in the Editor write these for you. The package is listed under Holarch in the Standard Library.