Requirements drift from analysis
Requirements live in one tool, physics in another. Traceability is rebuilt by hand before every review.
Connect SysML v2 architectures and ReqIF requirements to JSBSim flight models, NASA ROCETS propulsion decks, and CCSDS telemetry, then simulate, verify, and export FMUs without leaving one toolchain.
$ msx rocets simulate engine.roc
$ msx render SpacecraftPower spacecraft.sysml --view IBD -o ibd.svg
$ msx verify BrakingController brake.mo --format sarif
Requirements live in one tool, physics in another. Traceability is rebuilt by hand before every review.
Decades of validated propulsion and flight code are locked in card decks and Fortran routines nobody wants to touch.
Verification artifacts are assembled from screenshots and spreadsheets instead of generated from the models.
SysML v2 architecture + ReqIF requirements
JSBSim airframe, ROCETS engine, Modelica subsystems
Stiff DAE solvers, Monte Carlo, surrogates
Requirement entailment & SARIF evidence
Parse JSBSim aircraft definitions and lower them to DAEs for simulation and linearization.
Ingest ROCETS engine decks and turbomachinery maps, with a bridge for embedded Fortran user routines.
Read CCSDS orbit and XTCE telemetry definitions and align them with simulated trajectories.
Check SysML v2 constraints and requirement contracts with k-induction and SMT-backed proofs.
Browser, CLI, VS Code, CI pipelines, or air-gapped Enterprise Appliances (AGPL-3.0 Core & Commercial Editions).