Views in SysML v2 Projects

A view shows part of the model as a diagram. Each view is a view usage in the model, so it also appears in the text.

Create a view

• Open the Diagrams tool and click + New Diagram. The lists by view kind start with their kind: Behavior → Action Flows, State Machines and Sequences, Architecture → General Views and Interconnection Views.
• Choose the view kind, then under Shows the package or definition the view shows, and optionally a name.
• Click Create. The view opens; the text gains a line such as view structure : StandardViewDefinitions::GeneralView { expose Vehicles::**; }.

Work with views

• Views appear in the Diagrams list with a picture, like other diagrams. Open, duplicate and export them (PNG, SVG, HTML, Word) from the card menu or the diagram toolbar.
• Every change made in a view is one undo step and shows in the text at once.
• Views open as tabs under the top bar, as 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. diagrams do. ▲ Parent opens the view of the same kind that shows the owner of what this view shows. The ⚠ button in the top bar lists the problems that Home counts; click one to open its page.
• The Add panel on the left lists what the view can hold. Drag an entry onto the view, or into a shape; type a name to create an element or to find one of the model (each found element shows its owner path, such as Vehicles::Car). Drag from the dot on a shape to another shape to relate them: the menu offers what the model allows between the two.
• A grid view is the Database table: the Views pane has built-in views such as Unsatisfied requirements, Parts without ports, Untyped usages, Unresolved names and Unnamed elements (elements without a name, such as an action in a succession, listed by kind and owner; other lists leave them out), and saved views. The Kind, Type, Multiplicity and Value columns edit in the cell: double-click or press Enter.
• A general view lays itself out in ranks: wholes above their parts, and general definitions above their specializations (a definition that many others specialize goes below them). Lines from one box share a trunk. Above 12 boxes the compartments fold to their headings; turn on Compartments in the toolbar to show them, or click a heading to fold or show one. Boxes you have not moved are laid out again when their size changes.
• An interconnection view adds a Part, a Port (into a part) or an Item from the Add panel. Drag from one part or port to another for a Connection, an Interface (offered when an interface definition fits both ports), a Binding or a Flow (you choose the item). Drag a part into another part to move it there. An interconnection view places the parts in columns along their connections (of a few arrangements it keeps the one whose lines cross least), each port on the side that faces what it connects to, and sizes the parts to their names and ports. Port labels sit inside their part (a part nested deeper shows the port name; point at a port for its type); lines run around the parts in their own lanes, with connection names on a free stretch of the line. Arrange ▾ → Tidy Layout returns every shape to this layout. The frame is the border of the exposed part.
• A state transition view shows the states of a state definition, nested states and parallel regions, with transitions labelled trigger [guard] / effect. The Add panel adds a State, a Parallel State, a Region (into a parallel state), an Initial State or Final State (onto a state) and Entry, Do and Exit Actions (onto a state). Drag from one state to another for a transition; select it to edit its name, trigger, guard and effect.
• An action flow view shows an action's steps, successions, flows and swim lanes (Action Flow View).
• A sequence view has the Add panel: drop Lifeline (part), Lifeline (port) or one of the subject's parts to show its lifeline, and drop Message between two lifelines. Remove hides a lifeline; the part stays in the model.
• Delete Diagram deletes the view usage and its layout; the elements it shows stay. Restore it from the Trash.

Change a relationship

• Select a line and choose Relationship ▾ in the toolbar. It lists the kinds the line can be between the same two elements: on a General View Composition, Reference and Specialization, or Satisfy and Verify; on an Interconnection View Connection, Interface, Flow and Binding; on Requirement and Use Case Views their relationships.
• The change is written into the text as one undo step. A kind the model does not allow between the two elements, or one that would add an error, is refused with the reason (for example, an interface connects two ports).

Requirement, use case, parametric, package and geometry views: Requirement, Use Case, Parametric, Package and Geometry Views. Holarch's analysis diagrams (Spider, Hierarchy, Tree, IDEF0Integration Definition for Function Modeling A function-modeling method: each box is a function, with inputs, controls, outputs and mechanisms on fixed sides., FFBDFunctional Flow Block Diagram A diagram of functions in the order they run, with branches, loops and parallel paths.): Analysis Diagrams and Functional Analysis in SysML v2 Projects.