pith. sign in

arxiv: 1906.08520 · v1 · pith:SVJ3FRIJnew · submitted 2019-06-20 · 💻 cs.SE

A System Modeling Approach to Enhance Functional and Software Development

Saurabh Tiwari , Emina Smajlovic , Amina Krekic , Jagadish Suryadevara This is my paper

Pith reviewed 2026-05-25 19:41 UTC · model grok-4.3

classification 💻 cs.SE
keywords SysMLfunctional developmentembedded softwareheavy machinerytransmission systemmodel-based developmenttraceability
0
0 comments X

The pith

A SysML-based modeling approach supports flexible functional development, team communication, and traceability from design concepts to software artifacts in industrial embedded systems.

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

The paper describes an application of SysML modeling to manage rising complexity in embedded software for heavy construction machinery driven by electromobility and automation. It seeks to deliver more flexible functional development, clearer communication across teams, and explicit links from early concepts through to implemented software. The method was applied to the design of a new partially electrified transmission system, yielding some early positive outcomes while also exposing remaining gaps. A reader would care because conventional development practices may become insufficient as system complexity grows, making structured modeling potentially valuable for maintaining control over large projects.

Core claim

The authors establish that a SysML-based approach, when used in an industrial setting for developing a new transmission system, enhances the functional and software development process by addressing needs for flexibility, improved inter-team communication, and traceability between design concepts and software artifacts.

What carries the argument

SysML-based modeling approach, which represents system functions and software elements to support development activities.

If this is right

  • Development teams gain a structured way to link high-level functions to software implementations.
  • Traceability from initial concepts to final artifacts becomes more explicit and maintainable.
  • Communication across functional and software groups improves through shared models.
  • The method demonstrates initial viability in a real industrial transmission system case.

Where Pith is reading between the lines

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

  • The same modeling strategy could be tested on other vehicle subsystems such as power management or safety controls.
  • Integration with existing toolchains might further reduce manual translation steps between models and code.
  • If scaled, the approach could shorten iteration cycles when requirements change late in development.

Load-bearing premise

Rising complexity from electromobility and automation in heavy machinery requires new modeling methodologies to deliver flexible development, better communication, and traceability.

What would settle it

A side-by-side comparison showing that the SysML approach produces no measurable gain in traceability, communication quality, or development flexibility over prior methods in the transmission system project would undermine the central claim.

Figures

Figures reproduced from arXiv: 1906.08520 by Amina Krekic, Emina Smajlovic, Jagadish Suryadevara, Saurabh Tiwari.

Figure 1
Figure 1. Figure 1: Overview of the SysML-based modeling approach The overall system modeling approach is divided into three stages. 7 https://www.ibm.com/se-en/marketplace/rational-rhapsody [PITH_FULL_IMAGE:figures/full_fig_p003_1.png] view at source ↗
Figure 2
Figure 2. Figure 2: BDD for Powertrain subsystem: description of the Brake function 4.1 Functional Modeling (Structure) The first phase of the modeling activity (refer to [PITH_FULL_IMAGE:figures/full_fig_p004_2.png] view at source ↗
Figure 3
Figure 3. Figure 3: BrakeDrivetrain IBD representing Operations and Signals requirement and system engineers, and enhance communications within devel￾opment teams. The results of this phase are also reviewed with the stakeholders. 4.2 System Modeling (Behavior) It is the next level of modeling activity using SysML Statemachine diagrams to capture the functional behavior of the structural “parts” (w.r.to the system-of￾interest… view at source ↗
Figure 4
Figure 4. Figure 4: State Machine of BrakeHubUnit subsystem and “hardware” parts are identified during behavior modeling phase, as part of the system specification. This phase further requires extensive domain exper￾tise (both system and software level), for the technical trade-offs to be made regarding whether a certain SysML Operation is to be implemented in software or hardware (e.g. sensor). For instance, as shown in [PI… view at source ↗
read the original abstract

This paper presents a SysML-based approach to enhance functional and software development process within an industrial context. The recent changes in technology such as electromobility and increased automation in heavy construction machinery lead to increased complexity for embedded software. Hence there emerges a need for new development methodologies to address flexible functional development, enhance communication among development teams, and maintain traceability from design concepts to software artefacts. The discussed approach has experimented in the context of developing a new transmission system (partially electrified) and its functionality. While the modeling approach is a work-in-progress, some initial success, as well as existing gaps pointing to future works are highlighted.

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

1 major / 2 minor

Summary. The paper presents a SysML-based approach intended to enhance functional and software development processes in an industrial setting for heavy construction machinery. It argues that electromobility and automation increase complexity, creating needs for flexible development, better team communication, and traceability from concepts to artifacts. The approach was applied experimentally to the development of a new partially electrified transmission system; the manuscript describes initial successes while noting that the modeling approach remains a work-in-progress with gaps for future work.

Significance. If supported by concrete evidence of improvement, the work could address a genuine industrial need for better handling of embedded software complexity. However, the manuscript offers only a high-level description of application and 'initial success' without metrics, baselines, or comparative data, so its significance remains prospective rather than demonstrated.

major comments (1)
  1. Abstract: The central claim that the SysML approach 'enhance[s] functional and software development process' rests solely on an unquantified reference to 'initial success' in one transmission-system case. No traceability-coverage figures, defect-rate comparisons, coordination metrics, or baseline non-SysML process data are supplied, leaving the enhancement assertion unsupported.
minor comments (2)
  1. The manuscript should clarify in the introduction or a dedicated section what specific SysML diagrams or extensions were used and how they map to the claimed benefits of flexibility and traceability.
  2. The work-in-progress status and listed gaps should be summarized more explicitly so readers can assess the maturity of the reported results.

Simulated Author's Rebuttal

1 responses · 0 unresolved

We thank the referee for the detailed review and constructive feedback on our manuscript describing an experimental SysML-based approach in an industrial setting. We address the major comment point by point below.

read point-by-point responses

  1. Referee: Abstract: The central claim that the SysML approach 'enhance[s] functional and software development process' rests solely on an unquantified reference to 'initial success' in one transmission-system case. No traceability-coverage figures, defect-rate comparisons, coordination metrics, or baseline non-SysML process data are supplied, leaving the enhancement assertion unsupported.

    Authors: We agree that the abstract's phrasing could be read as asserting a stronger, quantified enhancement than the evidence in the manuscript supports. The paper is explicitly framed as a report on an ongoing, work-in-progress application of SysML modeling to a new partially electrified transmission system, where benefits such as improved team communication and traceability were observed qualitatively by the development team. No comparative baselines, defect metrics, or coverage statistics were collected or reported. We will revise the abstract (and any corresponding claims in the introduction) to describe the work as an initial experimental application that yielded observable benefits alongside identified gaps, without claiming demonstrated process enhancement. revision: yes

Circularity Check

0 steps flagged

No circularity: descriptive case study with no derivations or self-referential reductions

full rationale

The paper describes a SysML modeling approach applied to a transmission system development case study. No equations, parameters, predictions, uniqueness theorems, or ansatzes appear in the provided text. The central claim of enhancement rests on narrative description of 'initial success' rather than any derivation chain that reduces to fitted inputs or self-citations by construction. This matches the default expectation of no significant circularity.

Axiom & Free-Parameter Ledger

0 free parameters · 0 axioms · 0 invented entities

No mathematical content or derivations; the approach rests on the unexamined premise that SysML can address the stated complexity issues without further specification.

pith-pipeline@v0.9.0 · 5640 in / 962 out tokens · 17788 ms · 2026-05-25T19:41:06.520804+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

4 extracted references · 4 canonical work pages

  1. [1]

    In: INCOSE 2007 Symposium (2007)

    Friedenthal, S., Griego, R., Sampson, M.: INCOSE model based systems engineering (MBSE) initiative. In: INCOSE 2007 Symposium (2007)

    work page 2007

  2. [2]

    Morgan Kaufmann (2014)

    Friedenthal, S., Moore, A., Steiner, R.: A practical guide to SysML: the systems modeling language. Morgan Kaufmann (2014)

    work page 2014

  3. [3]

    , " * write output.state after.block = add.period write

    ENTRY address author booktitle chapter doi edition editor eid howpublished institution journal key month note number organization pages publisher school series title type url volume year label INTEGERS output.state before.all mid.sentence after.sentence after.block FUNCTION init.state.consts #0 'before.all := #1 'mid.sentence := #2 'after.sentence := #3 '...

    work page

  4. [4]

    write newline

    " write newline "" before.all 'output.state := FUNCTION n.dashify 't := "" t empty not t #1 #1 substring "-" = t #1 #2 substring "--" = not "--" * t #2 global.max substring 't := t #1 #1 substring "-" = "-" * t #2 global.max substring 't := while if t #1 #1 substring * t #2 global.max substring 't := if while FUNCTION word.in bbl.in capitalize ":" * " " *...

    work page