Building blocks¶
Elements¶
Elements are SysML definitions used to create model content.
| Source area | Elements | Reference |
|---|---|---|
| Core | Shared base types, dimensions, terminology, and semantic metadata | Core |
| Operational | Actors, stakeholders, use context, use cases, activities, workflows, and scenarios | Architecture |
| Functional | Functions, actions, flows, behavior, modes, states, and constraints | Architecture |
| Logical | Logical components, interfaces, ports, connectors, exchanges, and decisions | Architecture |
| Implementation | Software, hardware, and user-interface definitions | Architecture |
| Realization | Physical nodes, runtime environments, deployment units, and deployed flows | Architecture |
| Assurance | Requirements, risk, cybersecurity, human factors, verification, validation, and evidence | Assurance |
| Artifacts | Artifact classifications and controlled records | Artifacts |
| Viewpoints | Viewpoint contracts, selection definitions, and views | Viewpoints |
| Methodology | Scope, profiles, patterns, workflow, gates, usage rules, and project bindings | Methodology |
Browse element declarations by namespace.
Relationships¶
MEMO connects elements with native SysML v2 relationships where the language has
one, and with its own typed relationships (connection defs, and allocation
defs for the deployment chain) where the native form would lose meaning.
MEMO in a nutshell explains the
split, and each layer page lists every relationship that touches the layer.
| Purpose | Native SysML | MEMO relationships |
|---|---|---|
| Operational context | actor, subject |
AppliesInContext, SituatedIn, InteractsInContext, Governs |
| Use cases and workflow | include use case, succession |
Motivates, RequiresCapability, EnablesUseCase, RealizesUseCase |
| Function and architecture | allocate, perform, #refinement dependency, flow, bind |
IndependentOf, BindsToInterface, ConnectionBinding |
| Implementation and deployment | dependency |
BuildsInto, DeploysTo, HostedBy, ProvidesEnvironment, MemoryBinding, FlowTraversesBinding, DependsOnSoup |
| Requirements and risk | satisfy |
DerivesFrom, Causes, LeadsToHarm, IdentifiesHazard, Mitigates, ControlImplementedBy |
| Cybersecurity and safety | ThreatenedBy, Exploits, CrossesTrustBoundary, ImpactsSafety, DerivesCyberRequirement |
|
| Verification and evidence | subject, perform |
Validates, ProducesEvidence, PerformsStep, TestedByUsability, EvaluatesTask |
Browse relationship declarations by namespace.
Enumerations¶
Enumerations are SysML enum def declarations that define controlled values.
| Used by | Examples |
|---|---|
| Core identity and classification | ElementStatusKind, LifecycleStateKind, RealizationStageKind, CrossCuttingConcernKind |
| Operational | UseCaseKind, WorkflowStateKind, ScenarioKind, DemandLevelKind |
| Functional and logical | ActionKind, FunctionalFlowKind, TimingConstraintKind, InterfaceKind, DirectionKind, ComponentRoleKind |
| Implementation and realization | ModuleKind, RuntimeKind, SafetyClassKind, UIElementFormKind, DeploymentKind, ProcessingNodeKind |
| Assurance | RequirementTypeKind, SeverityKind, ProbabilityKind, RiskControlKind, ThreatCategoryKind, MemoVerificationMethodKind |
| Viewpoints and methodology | PresentationKind, ViewOutputKind, DiagramViewKind, WorkflowStageKind, RuleStrengthKind |