Verification in SysML v2 Projects

Verification 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, RVTMRequirements Verification Traceability Matrix A table of each requirement with how it is verified, the tests that verify it and their latest result., Test Center, Traceability Matrix and Model Checks, working on the model.

• A test case is a verification usage or a verification def; the requirements it verifies are the verify members of its objective. A package that owns verification cases is a test suite.
• Test Center: suites, test cases, status buttons, steps, test cycles, Run Suite and reports as in LML projects. + New ▾ → Test Case… adds a verification usage; Test Suite… adds a package. Linking a requirement adds a verify to the objective. Status, expected and actual results, steps and cycles are Holarch data stored next to the model.
• RVTM: each requirement with its verification method, verifying test cases and the status rolled up from sub-requirements.
• Traceability Matrix: rows, columns and relationship as in LML projects. Assets are the part usages, the parts in the system, and Actions the action usages; for a class axis, Elements → Definitions lists the definitions instead. Between model elements a cell can hold satisfied by (satisfy), verified by (verify), performed by (allocate or perform), traced to (dependency) and decomposed by (ownership); other relationships show as not allowed. Each click is one undo step and changes the model text.
• Model Checks: the rules that apply to a model: requirement usages without a name, short name, description, satisfy or verify, a leaf requirement without "shall", repeated short names, vague words, broken live values, risks, failed verification cases and TPMsTechnical Performance Measure A key technical parameter, such as mass or power, tracked over time against its target and threshold., and the items next to the model (risks, tasks …) without relationships or with the same name. The checker in the Editor covers names, types and structure; the LML functional-analysis rules do not run. Merge fixes are not offered for model elements.