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
91 released
Validated
Older version: You are viewing 2.0.0. The latest stable version is 3.0.0.
sysand add hugoormo/sysmlv2-sandbox 2.0.0
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]

[2.0.0] - 2026-10-27

Changed

  • The Framework and Ontology follow RAWP commit dcfcb72: 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.