Plan & Deliver in SysML v2 Projects

Plan & Deliver 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: My Work, SE Process, Project Management, Charts, Change Requests, Baselines & Versions, Review Packages and Presentations.

• Tasks (Project Management, Charts, My Work) are Holarch items. Link a task to model elements in its Trace section with Link existing….
• Change Requests: add affected items from the model or from Holarch items. Add Change ▾ → Change an Item… on a SysML v2 element proposes a new short name, name or documentation; Edit SysML Text… proposes new text for a package. The proposed changes show the text difference. Apply Changes changes the model as one undo step.
• Baselines & Versions: a project baseline holds the SysML v2 model as well. Compare lists the elements added, removed, changed, moved and renamed, and the text changes per package. Restore brings the model and the Holarch items back to the baseline; undo is available. Restore a Previous Version… lists the model's element and text changes before you restore. A document baseline holds the model inside the document's package too: Compare and Compare Versions… list its element and text changes.
• SE Process: the guides (Kossiakoff, ISO/IEC/IEEE 15288, NASA, DoDDepartment of Defense The US Department of Defense. and others) read requirements, satisfy and verify relationships, parts, actions and connections from the model. Checks that have no SysML v2 meaning, such as stakeholder needs as statements or suspect links, are not shown.
• Documents hold the requirements of the model. A document holds the requirement usages of one package (Write ▾ → Requirements Package…; a new document gets a package named after it with its first requirement). The outline, numbers, nesting, inspector, quick add, indent, outdent and move work as in LML projects: a requirement under a section belongs to the package, one under a requirement is nested in it, and the number is its short name. Requirements written in the Editor in that package appear in the document. Remove deletes a requirement of the package after a confirmation; to take it out without deleting it, move it to another package in the Editor.
• Document blocks: RTMRequirements Traceability Matrix A report of requirements and the items they trace to., RVTMRequirements Verification Traceability Matrix A table of each requirement with how it is verified, the tests that verify it and their latest result., VCRMVerification Cross-Reference Matrix A table that maps requirements to verification methods (test, analysis, inspection, demonstration) and events., flow-down and allocation matrix blocks list the requirements of the model. Live values and live tables read model elements: Kind, Type, Multiplicity and Value (with its units, for example 1650 [kg]) are attributes and columns. Figures of views show the view. Word, Markdown and CSV exports contain them.
• SysML text and element links: in a text editor, + → SysML Text… inserts the textual notation of an element, printed from the model and updated when the model changes (or a copy you can edit), with the Editor's colors; + → Model Element Link… links to an element. Both name the element by its qualified name (Vehicles::Battery); live values, view figures and links may name elements that way too. Word exports show the text as code.
• Templates from the model: + New Document and Write ▾ → Templates ▸ Apply Template… offer System Specification, Interface Description, Verification Plan and Architecture Description (SysML v2). They are written from the open model: live tables of requirements, interfaces, ports, verification cases, parts and actions, the matrices, a figure per view and the text of the packages.
• Whiteboards: Convert to Model… makes requirements, verification cases, parts and actions in the model (other classes stay Holarch items); lines between them become satisfy, verify, allocate or dependency relationships. Harvest Requirements… adds requirement usages to a document (in its package) or to a package of the model. Generate Diagram… moves the linked actions or parts into a new action or part, adds successions (or a connection per line) and opens an Action Flow or Interconnection View of it. Each is one undo step, and the notes link to the new elements.