pith. sign in

arxiv: 2606.29006 · v1 · pith:TYFIF74Bnew · submitted 2026-06-27 · 💻 cs.SE

Automated SysML-Based Verification of Discipline-Specific Models

Daniel Marley , Siyuan Ji This is my paper

Pith reviewed 2026-06-30 08:24 UTC · model grok-4.3

classification 💻 cs.SE
keywords SysML verificationmodel-based systems engineeringUML Testing Profileautomated model verificationbehavioral propertiesdiscipline-specific modelstool-agnostictraceability
0
0 comments X

The pith

A SysML verification process automates checks on behavioral and interface properties of discipline-specific models and traces results back to the model.

A machine-rendered reading of the paper's core claim, the machinery that carries it, and where it could break.

This paper establishes a verification process for discipline-specific models that starts from SysML test cases. The process is designed to be tool-agnostic by relying on common SysML capabilities and the UML Testing Profile rather than proprietary APIs. It enables verification of behavioral properties such as ordering, timing, and state responses, which parametric diagrams alone cannot handle. Results are returned to the SysML model to support traceability. The authors demonstrate the full process in two separate SysML tool-chains.

Core claim

The central discovery is a model-based verification process that converts SysML test cases into automated verifications of discipline-specific models, covering behavioral and interface requirements, and feeds the outcomes back into the SysML model, with the entire workflow shown to operate independently in two different tool environments.

What carries the argument

The verification process derived from validated stakeholder needs and implemented using SysML behavioral diagram constructs and UML Testing Profile elements to bridge SysML test cases with discipline-specific model checks.

If this is right

  • Automated verification becomes possible for properties beyond performance, including behavior and interfaces.
  • Traceability is maintained by returning verification results directly to the SysML model.
  • Portability is achieved without dependence on proprietary tool APIs.
  • The approach supports verification of ordering, timing, and state-based responses.

Where Pith is reading between the lines

These are editorial extensions of the paper, not claims the author makes directly.

  • The process could be extended to additional SysML tool environments beyond the two tested.
  • It might enable more comprehensive verification in multi-disciplinary engineering projects.
  • Integration with other modeling standards could broaden its applicability.

Load-bearing premise

Stakeholder needs from literature research and interviews provide a complete and general set of requirements for the verification process.

What would settle it

Failure to successfully implement the process or verify the targeted properties in an additional SysML tool-chain not used in the demonstrations.

Figures

Figures reproduced from arXiv: 2606.29006 by Daniel Marley, Siyuan Ji.

Figure 1
Figure 1. Figure 1: UC model showing the system of interest boundary and the actor blocks that interact with [PITH_FULL_IMAGE:figures/full_fig_p008_1.png] view at source ↗
Figure 2
Figure 2. Figure 2: Context architecture BDD showing the system of interest boundary, human actor roles, and peer context systems used to model the MBV process teractions with systems modelling tools are well understood and would not add value to the stake￾holders of this work. The logical test architecture, shown in [PITH_FULL_IMAGE:figures/full_fig_p008_2.png] view at source ↗
Figure 5
Figure 5. Figure 5: Test planning information is captured in [PITH_FULL_IMAGE:figures/full_fig_p009_5.png] view at source ↗
Figure 4
Figure 4. Figure 4: MBV profile stereotype diagram as im￾plemented in Magic SoS, showing custom stereo￾type icons integrated into the tool browser and menu system but does not affect portability. The profile shares significant commonality with UTP, with two de￾liberate differences: test logs are implemented as instance specifications to record execution results directly at runtime, and test sets absorb the test component conc… view at source ↗
Figure 5
Figure 5. Figure 5: Test plan artefact in Magic SoS, showing tagged value fields for test planning information, [PITH_FULL_IMAGE:figures/full_fig_p010_5.png] view at source ↗
Figure 8
Figure 8. Figure 8: Signal gain test case AD verifying two re [PITH_FULL_IMAGE:figures/full_fig_p011_8.png] view at source ↗
Figure 6
Figure 6. Figure 6: Test context structure: the BDD estab￾lishes the block hierarchy and the IBD defines the data flow interface between the test sets and the SUT [PITH_FULL_IMAGE:figures/full_fig_p011_6.png] view at source ↗
Figure 7
Figure 7. Figure 7: Test schedule AD using call behaviour actions and control flows to sequence test cases and collect verdicts into the test context COSE SEH, provided a suitable framework for the demonstration reported in Section 4. The process [PITH_FULL_IMAGE:figures/full_fig_p011_7.png] view at source ↗
read the original abstract

Current examples of SysML-based verification of discipline-specific models in the literature typically have two flaws. Firstly, they are developed in a tool-specific manner using proprietary APIs, limiting portability. Secondly, they focus on performance properties modelled via parametric diagrams, overlooking behavioural and interface properties that also require verification. This project addresses the problem with a verification process tailored to model-based verification, informed by common SysML tool capabilities and the UML Testing Profile, that enables automated verification of discipline\-/specific models from SysML test cases and returns the results to the SysML model for traceability. A mixed-method approach combining literature research and stakeholder interviews was used to derive validated stakeholder needs, which drove the specification and design of the process. The process was demonstrated end-to-end in two independent SysML tool-chains to evidence tool-agnosticism, and was shown to verify behavioural and interface requirements, including ordering, timing, and state-based responses, using SysML behavioural diagram constructs that parametric approaches alone cannot address.

Editorial analysis

A structured set of objections, weighed in public.

Desk editor's note, referee report, simulated authors' rebuttal, and a circularity audit. Tearing a paper down is the easy half of reading it; the pith above is the substance, this is the friction.

Referee Report

2 major / 1 minor

Summary. The paper claims that existing SysML-based verification approaches are limited by tool-specific proprietary APIs and a focus on parametric diagrams for performance properties. It addresses this by deriving stakeholder needs via literature review and interviews, then specifying a verification process informed by common SysML tool capabilities and the UML Testing Profile. This process enables automated verification of behavioral and interface properties (ordering, timing, state-based responses) from SysML test cases, with results returned to the SysML model for traceability. The process is demonstrated end-to-end in two independent SysML tool-chains to support tool-agnosticism.

Significance. If the process holds as described, it would provide a portable alternative to tool-specific methods and extend verification coverage beyond parametric diagrams to behavioral properties using standard SysML constructs. The mixed-method derivation of needs and explicit use of documented common capabilities are strengths; the two end-to-end demonstrations with traceability add concrete evidence of feasibility.

major comments (2)
  1. [Abstract] Abstract and demonstration description: the tool-agnosticism claim rests on end-to-end execution in two tool-chains, but supplies no quantitative validation metrics, error rates, or analysis of failure modes when common capabilities are absent; this is load-bearing for the generalizability asserted.
  2. [Process specification] Stakeholder needs derivation: the process is driven by needs from literature and interviews, yet the manuscript provides no explicit mapping or validation showing these needs suffice for a general process beyond the two demonstrated chains (weakest assumption in the approach).
minor comments (1)
  1. [Abstract] The abstract mentions 'detailed implementation steps' are absent; adding pseudocode or explicit activity diagrams for the verification workflow would improve reproducibility without altering the central claim.

Simulated Author's Rebuttal

2 responses · 0 unresolved

Thank you for the opportunity to respond to the referee's report. We address each major comment point-by-point below. We propose targeted revisions to strengthen the presentation of generalizability and the traceability of the needs derivation.

read point-by-point responses

  1. Referee: [Abstract] Abstract and demonstration description: the tool-agnosticism claim rests on end-to-end execution in two tool-chains, but supplies no quantitative validation metrics, error rates, or analysis of failure modes when common capabilities are absent; this is load-bearing for the generalizability asserted.

    Authors: We agree that the manuscript does not supply quantitative metrics, error rates, or an explicit failure-mode analysis. The tool-agnosticism claim is grounded in the process being restricted to documented common SysML capabilities and in the two independent end-to-end demonstrations; however, these demonstrations alone do not constitute statistical validation. We will add a dedicated limitations subsection that (a) enumerates plausible failure modes when a tool lacks support for required UML Testing Profile elements and (b) explicitly states the absence of large-scale empirical testing as a boundary on the current generalizability claim. revision: yes

  2. Referee: [Process specification] Stakeholder needs derivation: the process is driven by needs from literature and interviews, yet the manuscript provides no explicit mapping or validation showing these needs suffice for a general process beyond the two demonstrated chains (weakest assumption in the approach).

    Authors: The needs were obtained through a mixed-method sequence (literature review followed by stakeholder interviews) and the process was subsequently specified to satisfy them. We concur that an explicit mapping from each need to the corresponding process elements, together with an argument for sufficiency beyond the two demonstrated tool-chains, is not present. We will insert a traceability table (or appendix) that links each validated need to the process steps and will add a short paragraph arguing why the needs set, being derived from common tool capabilities and the UML Testing Profile, supports broader applicability. revision: yes

Circularity Check

0 steps flagged

No significant circularity

full rationale

The paper's derivation begins with a mixed-method approach of literature research and stakeholder interviews to derive validated needs, which then drive the specification of a verification process informed by common SysML capabilities and the UML Testing Profile. This process is demonstrated end-to-end in two independent tool-chains for tool-agnosticism. No equations, fitted parameters, self-citations, or uniqueness theorems are invoked in a load-bearing way that reduces the result to its inputs by construction. The central claim rests on external inputs and explicit demonstrations rather than self-referential definitions.

Axiom & Free-Parameter Ledger

0 free parameters · 2 axioms · 0 invented entities

The central claim rests on standard domain assumptions about SysML and the UML Testing Profile with no free parameters or invented entities stated in the abstract.

axioms (2)
  • domain assumption SysML supports definition of test cases and automated verification of discipline-specific models via its behavioral diagram constructs
    The process is built on common SysML tool capabilities as stated in the abstract.
  • domain assumption The UML Testing Profile provides a suitable foundation for the verification process
    The process is explicitly informed by the UML Testing Profile.

pith-pipeline@v0.9.1-grok · 5691 in / 1295 out tokens · 44434 ms · 2026-06-30T08:24:44.876392+00:00 · methodology

discussion (0)

Sign in with ORCID, Apple, or X to comment. Anyone can read and Pith papers without signing in.

Reference graph

Works this paper leans on

39 extracted references · 21 canonical work pages

  1. [1]

    ERTS 2010 proceedings , year =

    Feiler, P and Wrage, L and Hansson, J , title =. ERTS 2010 proceedings , year =

    2010

  2. [2]

    and Purohit, Shatad , title =

    Madni, Azad M. and Purohit, Shatad , title =. Systems 2019, Vol. 7, Page 12 , year =. doi:10.3390/SYSTEMS7010012 , issn =

    work page doi:10.3390/systems7010012 2019

  3. [3]

    1st IEEE International Symposium on Systems Engineering, ISSE 2015 - Proceedings , year =

    Morkevicius, Aurelijus and Jankevicius, Nerijus , title =. 1st IEEE International Symposium on Systems Engineering, ISSE 2015 - Proceedings , year =. doi:10.1109/SYSENG.2015.7302739 , isbn =

    work page doi:10.1109/syseng.2015.7302739 2015

  4. [4]

    INCOSE International Symposium , year =

    Wang, Gan and Pavalkis, Saulius , title =. INCOSE International Symposium , year =. doi:https://doi.org/10.1002/j.2334-5837.2019.00634.x , issn =

    work page doi:10.1002/j.2334-5837.2019.00634.x 2019

  5. [5]

    Wind , VOLUME =

    Zhang, Yizhe and Roeder, Julian and Jacobs, Georg and Berroth, Joerg and Hoepfner, Gregor , TITLE =. Wind , VOLUME =. 2022 , NUMBER =

    2022

  6. [6]

    INSIGHT , year =

    Bajaj, Manas and Friedenthal, Sanford and Seidewitz, Ed , title =. INSIGHT , year =. doi:10.1002/INST.12367 , issn =

    work page doi:10.1002/inst.12367

  7. [7]

    2023 , publisher =

    INCOSE , title =. 2023 , publisher =

    2023

  8. [8]

    ISO/IEC/IEEE 15288:2023 , year =

    ISO/IEC/IEEE , title =. ISO/IEC/IEEE 15288:2023 , year =. doi:10.1109/IEEESTD.2023.10123367 , isbn =

    work page doi:10.1109/ieeestd.2023.10123367 2023

  9. [9]

    2018 , number =

    ISO/IEC/IEEE , title =. 2018 , number =

    2018

  10. [10]

    ISO/IEC/IEEE 15288:2023 , year =

    ISO/IEC/IEEE , title =. 2023 , publisher =. doi:10.1109/IEEESTD.2023.10123376 , isbn =

    work page doi:10.1109/ieeestd.2023.10123376 2023

  11. [11]

    2017 , publisher =

    Dick, Jeremy and Hull, Elizabeth and Jackson, Ken , title =. 2017 , publisher =

    2017

  12. [12]

    Requirements Engineering , year =

    Yue, Tao and Briand, Lionel C and Labiche, Yvan , title =. Requirements Engineering , year =

  13. [13]

    2009 17th IEEE International Requirements Engineering Conference , year =

    Mavin, Alistair and Wilkinson, Philip and Harwood, Adrian and Novak, Mark , title =. 2009 17th IEEE International Requirements Engineering Conference , year =. doi:10.1109/RE.2009.9 , isbn =

    work page doi:10.1109/re.2009.9 2009

  14. [14]

    Systems Modeling Language™ (SysML® ) Version 1.7 , year =

  15. [15]

    2014 , publisher =

    Friedenthal, Sanford and Moore, Alan and Steiner, Rick , title =. 2014 , publisher =

    2014

  16. [16]

    Systems 2019 , year =

    Salado, Alejandro and Wach, Paul , title =. Systems 2019 , year =. doi:10.3390/SYSTEMS7020019 , issn =

    work page doi:10.3390/systems7020019 2019

  17. [17]

    2020 , url =

    Omg , title =. 2020 , url =

    2020

  18. [18]

    and Zorzo, Avelino F

    Bernardino, Maicon and Rodrigues, Elder M. and Zorzo, Avelino F. and Marchezan, Luciano , title =. IET Software , year =. doi:10.1049/iet-sen.2015.0154 , issn =

    work page doi:10.1049/iet-sen.2015.0154 2015

  19. [19]

    ACM Transactions on Software Engineering and Methodology , year =

    Cederbladh, Johan and Cicchetti, Antonio and Suryadevara, Jagadish , title =. ACM Transactions on Software Engineering and Methodology , year =. doi:10.1145/3631976 , issn =

    work page doi:10.1145/3631976

  20. [20]

    Testing: Academic and Industrial Conference Practice and Research Techniques - MUTATION (TAICPART-MUTATION 2007) , year =

    Baker, Paul and Jervis, Clive , title =. Testing: Academic and Industrial Conference Practice and Research Techniques - MUTATION (TAICPART-MUTATION 2007) , year =. doi:10.1109/TAIC.PART.2007.33 , isbn =

    work page doi:10.1109/taic.part.2007.33 2007

  21. [21]

    2010 36th EUROMICRO Conference on Software Engineering and Advanced Applications , year =

    Stefanescu, Alin and Wendland, Marc-Florian and Wieczorek, Sebastian , title =. 2010 36th EUROMICRO Conference on Software Engineering and Advanced Applications , year =. doi:10.1109/SEAA.2010.44 , isbn =

    work page doi:10.1109/seaa.2010.44 2010

  22. [22]

    2006 IEEE International Conference on Global Software Engineering (ICGSE'06) , year =

    Andaloussi, Brahim and Braun, Andreas , title =. 2006 IEEE International Conference on Global Software Engineering (ICGSE'06) , year =. doi:10.1109/ICGSE.2006.261230 , isbn =

    work page doi:10.1109/icgse.2006.261230 2006

  23. [23]

    IBM Engineering Systems Design Rhapsody ‐ TestConductor Add On | TestConductor User Guide | Release 2.9.2 , year =

  24. [24]

    Innovations in Systems and Software Engineering , year =

    Lasalle, Jonathan and Peureux, Fabien and Fondement, Frédéric , title =. Innovations in Systems and Software Engineering , year =. doi:10.1007/s11334-011-0164-1 , issn =

    work page doi:10.1007/s11334-011-0164-1

  25. [25]

    Systems , year =

    Hossain, Niamat Ullah Ibne and Lutfi, Mostafa and Ahmed, Ifaz and Akundi, Aditya and Cobb, Daniel , title =. Systems , year =. doi:10.3390/SYSTEMS10060264 , issn =

    work page doi:10.3390/systems10060264

  26. [26]

    and Varmazyar, Mojtaba and Nejati, Shiva and Briand, Lionel C

    González, Carlos A. and Varmazyar, Mojtaba and Nejati, Shiva and Briand, Lionel C. and Isasi, Yago , title =. Proceedings of the 21th ACM/IEEE International Conference on Model Driven Engineering Languages and Systems , year =. doi:10.1145/3239372.3239409 , isbn =

    work page doi:10.1145/3239372.3239409

  27. [27]

    Applied Sciences , year =

    Habermehl, Christian and Höpfner, Gregor and Berroth, Jörg and Neumann, Stephan and Jacobs, Georg , title =. Applied Sciences , year =. doi:10.3390/app12115316 , issn =

    work page doi:10.3390/app12115316

  28. [28]

    , title =

    Stenzel, June and Masterson, Rebecca and Simcoe, Robert A. , title =. 2024 IEEE Aerospace Conference , year =. doi:10.1109/AERO58975.2024.10521313 , isbn =

    work page doi:10.1109/aero58975.2024.10521313 2024

  29. [29]

    Procedia CIRP , year =

    Nigischer, Christian and Bougain, Sébastien and Riegler, Rainer and Stanek, Heinz Peter and Grafinger, Manfred , title =. Procedia CIRP , year =. doi:10.1016/J.PROCIR.2021.05.073 , issn =

    work page doi:10.1016/j.procir.2021.05.073 2021

  30. [30]

    Developer Guide - MagicDraw 19.0 LTR , howpublished =

  31. [31]

    MDG Technology for DDS , howpublished =

  32. [32]

    Enterprise Architect User Guide (Version 17.1) , howpublished =

  33. [33]

    Overview of custom tables (Utilities profile) , howpublished =

  34. [34]

    INCOSE International Symposium , year =

    Cederbladh, Johan and Krems, Daniel , title =. INCOSE International Symposium , year =. doi:10.1002/iis2.13135 , issn =

    work page doi:10.1002/iis2.13135

  35. [35]

    and March, Salvatore T

    Hevner, Alan R. and March, Salvatore T. and Park, Jinsoo and Ram, Sudha , title =. MIS Quarterly , year =

  36. [36]

    and Chatterjee, Samir , title =

    Peffers, Ken and Tuunanen, Tuure and Rothenberger, Marcus A. and Chatterjee, Samir , title =. Journal of Management Information Systems , year =

  37. [37]

    2022 , edition =

    Leavy, Patricia , title =. 2022 , edition =

    2022

  38. [38]

    Systems Engineering , year =

    Salado, Alejandro and Kannan, Hanumanthrao , title =. Systems Engineering , year =

  39. [39]

    Systems Engineering , volume =

    Kannan, Hanumanthrao and Salado, Alejandro , title =. Systems Engineering , volume =. doi:https://doi.org/10.1002/sys.70034 , year =

    work page doi:10.1002/sys.70034