Requirements in SysML v2 Projects

Needs & Requirements has the same 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, Requirements and Quality, working on the model's requirements.

• A requirement is a requirement usage or a requirement def: its short name (<'VR-1'>) is the number, its name the name and its doc comment the description. A requirement owned by another requirement is its child (decomposed by).
• Requirements is the Database filtered to the Requirement class: the same filters, views, columns, Tree mode, inline editing, bulk tools and exports (Table and Definitions exports include Kind, Type, Multiplicity and Value). + New adds a requirement usage with the next number in the package Requirements.
• Editing the number, name or description changes the model text, one undo step per change. Status, Verification Method, the other attributes and labels are Holarch data stored next to the model; they are not part of the SysML text.
• Satisfied by and verified by come from satisfy and verify in the model; adding or removing one changes the text.
• Select a requirement to see it in the SysML v2 inspector. Its link opens it in the Browser.
• Quality scores each requirement's description on nine criteria with the same rules as in LML projects. A score marked Stale belongs to an older text; check quality again.
• An element's change history is in the SysML v2 inspector: Details → History….
• Not in SysML v2 projects: Change Class, Duplicate, Lock and Copy with Children, and the JSON and .inno exports of model elements.
• Suspect links, approvals and the 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. register work as in LML projects: see Suspect Links, Approvals and TBD/TBR in SysML v2 Projects.