Analysis Diagrams and Functional Analysis in SysML v2 Projects

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., ICOMInputs, Controls, Outputs, Mechanisms The four kinds of arrows on an IDEF0 box, each entering or leaving on its own side. and FFBDFunctional Flow Block Diagram A diagram of functions in the order they run, with branches, loops and parallel paths.) and the Functional Analysis page work on the model of a SysML v2 project, with the same engines and look 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.

They are Holarch diagrams, not SysML standard views: they are kept with the project under the element they start from (their root), not as view usages in the model, and they do not appear in the text. Their layout is yours to arrange; what they show always comes from the model.

Open one

• Click + New Diagram in the Diagrams list, choose the diagram type and the element it starts from.
• Or select an element in a view, the Browser or a list and choose Open in ▾ → Spider Diagram (also Hierarchy, Tree, FFBD or IDEF0 Diagram where the element has members or steps). The Browser row menu has Show in Spider Diagram.
• Behavior → FFBD and Architecture → Hierarchy list those diagrams. The Diagrams list also offers a derived Hierarchy Diagram of every definition with members.
• ▲ Parent opens the same diagram of the owner. Double-click an element, or choose Open Entity View in its menu, to open its Entity View.
• On an IDEF0 Diagram, Generate ▾ → Generate Parts View… previews the parts that perform the action and its steps, then creates an Interconnection View of the part that contains them (else a General View) and opens it.
• On the IDEF0 Diagram of a step, Generate ▾ → Generate Requirements… creates a requirement per input, control, output and step for the part that performs it, in the package of the document <part> Requirements.

What each shows

• Spider Diagram: the element in the centre and everything related to it, out to the Level: owns, typed by, specializes, subsets, redefines, connected to, satisfied by, verified by, performs, allocated to, flows to and depends on. Relationships… chooses the kinds it follows; + on a node shows that node's neighbours. Drag from a node's dot to another node, or use + Add Related…, to add a relationship the model can hold (typed by, specializes, satisfy, verify, allocate, dependency, connection, ownership); it is written into the text.
• Hierarchy and Tree Diagrams: the decomposition: a part's parts, an action's actions, a requirement's requirements, a package's packages, definitions and top-level usages. A usage with no members of its own shows its definition's (part powertrain : Powertrain shows the parts of Powertrain). + Add Child adds a usage; dragging a node onto another moves the element there.
• IDEF0 and ICOM Diagrams: an action's steps as boxes A1, A2, …. in item parameters are Inputs (left), in attribute parameters Controls (top), out parameters Outputs (right); a flow between two steps is an arrow from one box to the other; the part that performs a step is its Mechanism (bottom). + Action adds a step.
• FFBD: the action's steps in their order: successions as arrows, forks and joins as AND, decisions as OR (with their guards), loops with LP. It is edited as in LML projects (Add panel, drop points, lines, Delete); the changes are written into the model as steps, successions, fork and join, decision and merge nodes and loops. Edit Flow… opens the Action Flow View that shows the action.

Add panel

• The Add panel on the left works as in LML projects, with SysML kinds: type a name and choose Create "name" as …, or find a model element (its kind is shown next to it, its owner path such as Vehicles::Car under it; type part of the path to narrow the list). Drag the row onto the diagram, or press Enter to add it to the selected node. Each addition is one undo step and is written into the text.
• Hierarchy and Tree: the kinds of the decomposition (a part: Part; an action: Action; a package: Package, definitions and usages). A new element becomes a member of the node it is dropped on; an existing element moves there. On a Tree, drop it on a node.
• Spider: every kind. The new or existing element is related to the selected node (or the centre): choose the relationship (owns, typed by, specializes, subsets, satisfied by, verified by, allocated to, depends on).
• IDEF0 and ICOM: Action (Step) adds a step; an action definition from the search becomes a step typed by it. Parameter dropped on a step's top side is a Control (in attribute), on its left side an Input (in item), on its right side an Output (out item); an item or attribute definition from the search types it. Part (Mechanism) adds a part that performs the step; drop an existing part to have it perform the step.
• FFBD: Action, AND, OR and LP, the steps of the action and its definitions (an action definition becomes a step typed by it; an action usage elsewhere moves into the action), and Not in the flow: steps taken out with Delete (they stay in the model, without successions). AND adds a fork and a join, OR a decision and a merge (probabilities split evenly), LP a while loop; a line back to an earlier step is a succession back to it (a loop). Delete from Model… in the inspector deletes a step (Trash).

Functional Analysis

• Open Behavior → Functional Analysis. The top-level function is an action definition or usage (Choose…); its functions are its action usages, numbered by their short names.
• The Functions tab edits IDs, names and the requirements each function satisfies (a satisfy in the model). Tick Subsystem to see the parts that perform each function (perform or allocate).
• The Flow & FFBD tab shows the flow as an FFBD. Edit as Text… edits it in the flow notation of LML projects (->, AND( a | b ), OR( a | b ), LOOP( … )); Apply writes successions, fork / join and decision / merge nodes and loops into the model as one undo step. A new name becomes a new action usage; a step left out leaves the flow and stays in the model. ✦ AI ▾ → Suggest Flow with AI… opens the same dialog. You can also change the flow on the Action Flow View.
• Tables, Coverage and the Word report work as in LML projects.

Selecting an element shows the SysML v2 inspector. Every change is one undo step; deleted elements go to the project's Trash.