Skip to main content
If you previously published to beta.sysand.org, follow the migration guide to move your packages to sysand.com.

sysmlv2-sandbox

published by hugoormo
45 released
Latest Validated
sysand add hugoormo/sysmlv2-sandbox
README Source Changelog Licenses 0 usages 3 versions Validation

Changelog

All notable changes to this project will be documented in this file.

The format is based on Keep a Changelog, and this project adheres to Semantic Versioning.

[Unreleased]

[3.0.0] - 2026-11-01

Added

  • Celestials (Framework/Celestials.sysml): the natural elements of space the operations work with, starting with ore and its volume, in m³. The COTS ore (miningLaserCOTSOre) and the ore parameters of the frigate's and the laser's Needs subset Celestials::ores, so the volume of the ore a product extracts is the volume the architecture speaks of, without naming the product.

Changed

  • The Framework and Ontology follow RAWP's development version of 2026-11-01: useCaseIntentTraceabilityRule states the provenance chain through the interface flow and when a flow belongs in a connector definition; whiteboxMountingTunnelingRule that only the whitebox tunnels and why ports belong to the interface; COTSConnectorBoundaryRule that a COTS product is chosen in design (a product-neutral graybox leaf, the product and its imposed interface at the whitebox); analysisValuePlacementRule that an architecture analysis has the graybox as subject and a design analysis the whitebox, a configuration or a candidate, and that a given external system's committed values are exogenous inputs; standardComplianceOverlayRule and verificationSubjectAndObjectiveRule the given-participant case; concernFramingRule the root of the chain, which in the sandbox is the L0 operational requirement.
  • The mining laser's Needs ('Extract ore - Needs') takes the cycle settings and the capacitor charge and returns the capacitor draw, which the Imperial standard's module control and capacitor channels demand of every fitted module; 'Mine ore - Design' has their six Design flows, so every graybox flow of the frigate subsets a Design flow. The laser's blackbox binds its operating states' inputs to the two new parameters.
  • Verification cases that read values of a COTS product take the released configuration's whitebox as subject in each case usage, since the product is chosen in design (analysisValuePlacementRule): the frigate's capacitor sustain cases (VC-0013, VC-0014) observe the fitted lasers' capacitor usage and cycle time there, and now evaluate them. The L0 configuration income analyses read the lasers' optimal range in each usage, whose deployed configuration subsets the released configuration.
  • The frigate's mining-rate allocation, an architecture analysis of the graybox, takes its off-the-shelf ceilings (laser mining rate, yield bonus) as exogenous market values instead of reading the Particle Bore Compact and Mining Yield Enhancer I products; the values are unchanged.
  • Breaking: a COTS product is chosen in design, not in the architecture (RAWP's COTSConnectorBoundaryRule): a COTS leaf's blackbox is a product-neutral contract, an abstract collection holding the Needs behavior and the satisfaction claims of the requirements that select the product, and each candidate product subsets the library product and it and performs the fit-for-purpose mapping of the product's behavior. The contract subsets the standard's module category (a selection criterion every candidate meets) and its action's items the standard's resources, so the standard's product-neutral properties, such as powerGridUsage, are read on the contract. The integrating graybox subsets the contract, its whitebox the selected candidate. Done for the mining yield enhancer: miningYieldEnhancer_bb is the contract (was the product's usage), miningYieldEnhancerI_bb the Mining Yield Enhancer I candidate, MiningYieldEnhancerBehavior::enhanceYield_bb subsets the Needs action only and the new enhanceYieldMiningYieldEnhancerI_bb maps the product's behavior; the frigate's whitebox subsets the candidate. Done for the mining laser: miningLaser_bb is the contract (subsets ImperialStandard::miningModules), with the Particle Bore Compact (particleBoreCompactMiningLaser_bb) and EP-S Gaussian Scoped (epsGaussianScopedMiningLaser_bb) candidates; MiningLaserBehavior::extractOre_bb subsets the Needs action only (its cycle report subsets ImperialStandard::miningModuleCycleReports) and the new extractOreMiningLaserFamily_bb maps the family's behavior once for both candidates, as miningLaserStates_bb does the family's operating states. The released frigate configurations' lasers subset their candidate.
  • Breaking: the mining laser's verification cases are per candidate: VC-0011 (particleBoreCompactCommandedMiningVerification, was commandedMiningMiningLaserVerification) and VC-0012 (particleBoreCompactSupplierEvidenceInspection, was miningLaserSupplierEvidenceInspection) for the Particle Bore Compact, new VC-0015 and VC-0016 for the EP-S Gaussian Scoped. Each inspection verifies its candidate's supplier yield specification claim.
  • The README's "Standards and COTS" conventions describe Celestials, the COTS contract and its candidates, where product values may be read, and per-candidate verification; "Checking" names the two Syside constraints that fix the order of subsets and the product in the model.
  • Breaking: MySystemOntology::SystemConnector::systemFlow is removed; connector definitions own only the flows that carry something the use-case flow does not.
  • Breaking: each whitebox exchange is one interface flow, which subsets the graybox connector flow, so the interface control view's rows trace to the use case messages: message -> Design flow -> graybox connector flow -> interface flow -> port item bound to a leaf action parameter (RAWP's useCaseIntentTraceabilityRule). The whitebox tunnel flows are removed, and the taxonomy connector flows, which carried nothing the Design flows do not, are removed with them; graybox connector flows subset only the Design flows. Done for the mining operation (MiningOperationConnection's miningCommandFlow/miningReportFlow, pilotFrigateConnection_wb's miningCommandTunnel/miningReportTunnel) and the mining frigate (MiningFrigateConnection's seven flows, the seven whitebox tunnel flows; its thirteen interface flows subset the graybox flows) and the power subsystem (PowerSubsystemConnection's three flows; its three interface flows subset the graybox flows).
  • The student guide depends on ^3.0.0 (was ^2.0.0).

[2.0.0] - 2026-10-27

Changed

  • The Framework and Ontology follow RAWP's development version of 2026-10-27: exhibitedStateRule and the state paragraphs of the rules it touches, the relay of commanded values, configurations that differ by scenario and claimed requirement, and operating practice set by the configuration. The requirement kinds are restated, and they, SystemRequirement and System are mapped to the INCOSE Needs and Requirements Manual.

  • Every verification case, definition or usage, states its VerificationMethod in its own body, not in its objective (RAWP's verificationMethodRule): the Framework's three case definitions, the seven case definitions and the fourteen cases of the model. A tool that read the method from the objective reads it from the case.

  • MyFrameworkSystemArchitecture states that the box-kind tags apply at every level, L0 included, and its metadata defs spell out specializes, subsets and redefines.

  • Breaking: each element's verification cases are owned by its verification context (MiningOperationsVerificationContext, MiningFrigateVerificationContext, MiningPilotVerificationContext, ShipControllerVerificationContext, MiningLaserVerificationContext) instead of the package, as RAWP's verificationSubjectAndObjectiveRule states; their qualified names change. The case definitions stay package members, as verificationSubjectAndObjectiveRule now states: a rig owns case usages only.

  • Breaking: the interconnection view draws the graybox, not the whitebox: the constituents of the level's graybox and the connections it owns; each element's interconnection usage exposes <Element>Context::<element>_gb::*, and a leaf's exposes nothing. Its new selection view ReusableViews::ConstituentConnectionView (part usages, connections included) replaces WhiteBoxView as its general. Interfaces and flows stay in the interface control view, and a whitebox tunnel shows at the level below. The Interconnection viewpoint states its precondition and what the view must show as an assume and a require constraint, which genericViewpointRule now defines.

  • Breaking: the decomposition tree is a tree of element contexts, selected by the new semantic metadata ElementContext (with ElementContextKind and elementContextParts). Its new selection view ReusableViews::ElementContextView replaces GrayBoxView as its general. Each level's tree shows the contexts its context mounts and the contexts those mount; the DecompositionTree viewpoint states this as an assume and a require constraint. The twelve element-context usages carry #ElementContext, the package-level miningOperationsContext included, which roots the mining operation's tree (its usage exposes miningOperationsContext::**); the other elements' usages expose <Element>Context::**. A student's mounted context carries the tag too (the guide's snippet does).

  • genericViewpointRule states that a recursive expose descends only into owned namespaces (KerML 7.4.12), and that a generic view shows only what its expose and filter can select, adding semantic metadata where a view would otherwise need tool navigation.

  • Breaking: the interface control document has one row per flow an interface carries (was one row per interface), so each row has a sender and a receiver. ReusableViews::InterfaceFlowView (was InterfaceView) selects the flow usages owned by interface usages; InterfaceControlView's columns are sender part, sender port, interface, flow, exchanged item, receiver port and receiver part (were supplier part and port, interface, flows, consumer port and part). OwningInterfaceColumn and ExchangedItemColumn are new; FlowColumn is removed.

  • richConnectorOwnershipRule (new) states that the whitebox connection owns, or redefines, the interface it carries and the interface owns its flows; that ports belong to the interface, COTS product ports excepted; and that an interface and its connection declare the supplier end first.

  • Whitebox connections own their interfaces, as richConnectorOwnershipRule states: the mining operation's pilotFrigateConnection_wb redefines the capsule standard's capsuleInterface, which owns the mining command and the mining report flows, their payloads narrowed to the standard's miningShipCommands and miningShipReports; the mining frigate's seven whitebox connections redefine the Imperial standard's low slot, high slot, module control and capacitor interfaces, which own their thirteen flows, the mining effect, yield modifier and cycle report payloads narrowed to the standard's mining groups; the power subsystem's rechargeConnection_wb and capacitorGridConnection_wb declare their recharge and capacitor supply interfaces, which own their three flows. The interface control documents list them.

  • Breaking: PowerSubsystem_Taxonomy::RechargeConnector and CapacitorSupplyConnector own no interface (were rechargeInterface and capacitorSupplyInterface): only a standard's or a COTS product's connector definition imposes one, and an element's whitebox connections declare their own.

  • The student guide depends on ^2.0.0 (was ^1.0.0).

  • The README notes a known limit of Syside 1.0.1: with the sandbox installed as a sysand dependency, syside viz draws no flows for the interface control views; rendering a copy of the package outside .sysand/lib works.

Removed

  • MyFramework::MyFrameworkIllustrativeAnalysisVocabulary (ContributionAllocationScenario, TradeAlternativeProfile, WeightedTradeEvaluation): the vocabulary of RAWP's payload example, which no sandbox element uses.

Fixed

  • The docs of three requirement packages name parentGrayboxToChildBlackboxRule in MyFrameworkConfigurationBehaviorSemantics, where it is declared.
  • The four inspection cases (VC-0006, VC-0007, VC-0008, VC-0012) state their inspect method; they stated none.

[1.0.0] - 2026-10-25

Added

  • The mining operation baseline, structured by the Recursive Architecture Wave Pattern (RAWP): Level 0 mining operations, Level 1 mining frigate, Level 2 subsystems and Level 3 components, with taxonomies, requirements and configurations at every level, plus use cases, behavior, verification cases and analysis cases where the level needs them.
  • A tailored copy of the RAWP Framework in Framework/ (no UAF at Level 0), with the capsule and imperial standards and a COTS library.
  • Low-sec and high-sec nominal scenarios in MiningOperations_AnalysisCases::MiningOperationsAnalysisContext. Their operating conditions are default values a consumer may redefine in its own context; all other values are bound commitments of the baseline.
  • Viewpoints and views for each developed element: the Framework's generic purpose views applied to the element, and a concern-driven view for each stakeholder concern (competitive pilot income, capsule standard compliance, off-the-shelf mining rate).
  • The student guide in README.md: the model, the transport-ship task (an own project depending on this package, specializing MiningOperations_Configuration::MiningOperationsContext), the modeling conventions, and the known tool limits.
  • License files LICENSES/MIT.txt and LICENSES/CC-BY-4.0.txt.