pith. sign in

arxiv: 1907.00344 · v1 · pith:JQHBANUOnew · submitted 2019-06-30 · 📡 eess.SY · cs.SY

Development of a novel matrix-based methodology for system engineering: A case study

Pith reviewed 2026-05-25 12:43 UTC · model grok-4.3

classification 📡 eess.SY cs.SY
keywords Mixed Matrix ModelDesign Structure MatrixInterface Structure Matrixsystem engineeringbusiness process modelingactivity levelssub-processescase study
0
0 comments X

The pith

A Mixed Matrix Model fuses DSM and ISM outputs to frame real-world system engineering.

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

The paper develops a method that takes a real business project, models it as processes, and converts those into Design Structure Matrix and Interface Structure Matrix forms. Algorithms then pull out activity levels and sub-processes from each matrix. These extracted elements are assembled into a Mixed Matrix Model presented as a usable framework for engineering actual systems. A reader would care because the approach aims to turn matrix analysis into a practical tool for handling complex, real projects rather than abstract theory.

Core claim

By modeling a real work project as processes, representing it in DSM and ISM, and running algorithms to extract activity levels and sub-processes, the authors construct a Mixed Matrix Model that can serve as a framework for the engineering of real-world systems.

What carries the argument

The Mixed Matrix Model (MMM), assembled from activity levels and sub-processes extracted by algorithms applied to DSM and ISM representations of a process model.

If this is right

  • The MMM organizes engineering tasks according to the identified activity levels.
  • Sub-process extraction supports breaking large systems into manageable modules for separate analysis.
  • Structural information from DSM and interface data from ISM become integrated within a single model.
  • The framework can be applied to additional real projects to guide their engineering process.

Where Pith is reading between the lines

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

  • If the MMM proves effective, it could reduce coordination failures in multi-team projects by making activity dependencies explicit.
  • The method might extend to domains like software architecture or supply-chain design where matrix representations already exist.
  • Repeated application on varied case studies would test whether the extraction algorithms remain stable across different project types.

Load-bearing premise

That the activity levels and sub-processes extracted by the two algorithms, when combined into the MMM, produce outputs that meaningfully improve system engineering.

What would settle it

A controlled comparison in which systems engineered with the MMM show no measurable improvement in outcomes such as completion time, cost, or error rates compared with systems engineered using DSM or ISM alone.

read the original abstract

Developing a structured method for analyzing various aspects of a system requires a novel methodology. This study is aimed at developing such as methodology through combining two major matrix methods, namely, Design Structure Matrix (DSM) and Interface Structure Matrix (ISM). Through this paper, a business process modeling method is applied to turn a real work project to a process model. Then that process model is written in two various matrix forms of DSM and ISM. These two matrices are analyzed by two types of algorithm for extracting activity levels and sub-processes. In the end, a Mixed Matrix Model (MMM) is built upon these activity levels and sub-processes, which can be used as a framework for the engineering of real-world systems.

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 / 2 minor

Summary. The paper proposes combining the Design Structure Matrix (DSM) and Interface Structure Matrix (ISM) via two algorithms that extract activity levels and sub-processes from a business-process model of a real project; the resulting Mixed Matrix Model (MMM) is presented as a novel framework for engineering real-world systems, with the construction illustrated in a case study.

Significance. If the MMM were shown to improve engineering outcomes over DSM or ISM alone, it could supply an integrated matrix-based view that links activity sequencing with interface dependencies. The manuscript supplies no such demonstration, so the practical significance remains unestablished.

major comments (2)
  1. [Abstract and case study] Abstract (final paragraph) and case-study description: the central claim that the MMM 'can be used as a framework for the engineering of real-world systems' rests on the assumption that the extracted activity levels and sub-processes meaningfully improve outcomes, yet the manuscript reports only the structural matrices and MMM construction with no metrics, before/after comparisons, decision-quality assessment, or risk-reduction evidence relative to the input DSM/ISM.
  2. [Case study / MMM construction] The two algorithms for activity-level and sub-process extraction are applied to the DSM and ISM, but no analysis is given of how their outputs alter engineering practice or reduce identified risks; the case study therefore functions only as an illustration of matrix construction rather than a test of the framework's utility.
minor comments (2)
  1. [Abstract] Abstract: 'such as methodology' should read 'such a methodology'.
  2. [Abstract] Abstract: 'two various matrix forms' is awkward; 'two different matrix forms' would be clearer.

Simulated Author's Rebuttal

2 responses · 0 unresolved

We thank the referee for the detailed report and the opportunity to respond. The comments correctly identify that the manuscript presents the MMM construction as an illustration rather than an empirical validation of improved outcomes. We address each major comment below and will revise the manuscript to align claims with the scope of the work performed.

read point-by-point responses
  1. Referee: [Abstract and case study] Abstract (final paragraph) and case-study description: the central claim that the MMM 'can be used as a framework for the engineering of real-world systems' rests on the assumption that the extracted activity levels and sub-processes meaningfully improve outcomes, yet the manuscript reports only the structural matrices and MMM construction with no metrics, before/after comparisons, decision-quality assessment, or risk-reduction evidence relative to the input DSM/ISM.

    Authors: We agree that the manuscript contains no quantitative metrics, comparisons, or evidence of improved engineering outcomes. The work develops and illustrates the MMM via algorithms applied to a real-project process model; the claim in the abstract is prospective. We will revise the abstract and conclusion to state that the MMM offers an integrated matrix-based representation demonstrated through the case study, while noting that assessment of practical benefits requires future empirical studies. revision: yes

  2. Referee: [Case study / MMM construction] The two algorithms for activity-level and sub-process extraction are applied to the DSM and ISM, but no analysis is given of how their outputs alter engineering practice or reduce identified risks; the case study therefore functions only as an illustration of matrix construction rather than a test of the framework's utility.

    Authors: We concur that the case study illustrates the extraction algorithms and MMM assembly without analyzing effects on engineering practice or risk reduction. The manuscript's purpose is methodological development shown through application. We will revise the case-study and discussion sections to explicitly characterize the work as illustrative and to identify empirical evaluation of practice changes as an avenue for future research. revision: yes

Circularity Check

0 steps flagged

No circularity; derivation is a forward constructive combination of DSM and ISM

full rationale

The paper applies standard DSM and ISM representations to a process model obtained from a real project, runs two extraction algorithms to obtain activity levels and sub-processes, and assembles an MMM from those outputs. No equation or definition makes the MMM equivalent to its inputs by construction, no parameters are fitted and then relabeled as predictions, and no load-bearing premise rests on self-citation. The chain is self-contained as a methodological recipe whose outputs are distinct from the input matrices.

Axiom & Free-Parameter Ledger

0 free parameters · 2 axioms · 1 invented entities

The central claim depends on standard assumptions in systems engineering about the validity of matrix representations and process modeling, plus the ad-hoc construction of MMM from algorithm outputs.

axioms (2)
  • domain assumption Business process modeling accurately converts a real work project into a usable process model.
    Invoked at the start of the method to create the input for DSM and ISM.
  • domain assumption Algorithms exist that correctly extract activity levels and sub-processes from DSM and ISM representations.
    Used to generate the inputs for building the MMM.
invented entities (1)
  • Mixed Matrix Model (MMM) no independent evidence
    purpose: Framework for engineering real-world systems
    Constructed by combining outputs of the two matrix analyses; no independent evidence provided outside the case study.

pith-pipeline@v0.9.0 · 5657 in / 1258 out tokens · 41551 ms · 2026-05-25T12:43:05.997238+00:00 · methodology

discussion (0)

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