Standard SysML diagram samples

The standard SysML diagram sample project ships with the ontology package. It declares one MemoDiagramView per standard SysML v2 view kind under model/samples/, and nothing else — the views describe no product and no reference architecture.

Read it when you want to see how a MemoDiagramView is declared for each DiagramViewKind value, and what diagramType pairs with each.

Rendering these views

This page covers what the sample model declares. Opening the views in a graphical workbench is MEMO Architect's job, and is documented there.

View	Diagram type	View kind	Demonstrates
tree_view.sysml	bdd	general	Block Definition Diagram — a decomposition hierarchy.
interconnection_view.sysml	ibd	interconnection	Internal Block Diagram — nested parts, boundary ports, typed connectors.
action_flow_view.sysml	afd	actionflow	Activity / action flow — actions, item flows, successions.
functional_flow_view.sysml	ffd	actionflow	Functional flow — swimlanes per realising component, typed data/energy flows.
context_view.sysml	context	general	System context — the system as one block among the external actors, systems, and use context it interacts with.
requirements_view.sysml	req	general	Requirements — stakeholder needs deriving into system requirements.
state_transition_view.sysml	stm	statetransition	State machine — pump operating modes and their triggered transitions.

Read an IBD as a connected structure

An internal block diagram has an unambiguous direction of flow: an upstream port produces an item and a downstream port consumes it. The connectors should point from producer to consumer; a renderer must not reverse them to fit a preferred layout.

What these samples are not

They are not a device reference model and they do not teach the MEMO ontology. For a connected medical-device argument — context through evidence — use the GPCA pump walkthrough, whose own model/samples/ folder backs the same Samples experience.

Where this sits in MEMO

Every tutorial is one slice of the same structure. This example populates these layers:

Layer	Element types it uses	Reference
Operational	OperationalEntity, UseCase, UseContext, User	Operational
Functional	ModeState, StateMachine, Transition	Functional
Logical	DataPort, LogicalComponent	Logical
Implementation and realization	HardwareAssembly	Implementation and realization
Assurance	Need, Requirement	Assurance
Views and methodology	MemoDiagramView	Views and methodology

Typed links it uses: AppliesInContext, Composes, DerivesFrom, ExchangesWith, Extends, Includes, Initiates, InteractsWith, MemoLink, ParticipatesIn — see Relationships for what each one claims and which ends are legal.

Narrative treatment: Context and Use · Functional Analysis · Requirements and Architecture · Risk, Cybersecurity, and Assurance.

Source model: examples/sysml-diagram-samples