startthat.work home

DM-18 Design structure matrix (dependency structure matrix)

Records which element depends on or supplies which in a square matrix, reorders it to reveal clusters or sequence, and produces a reordered matrix.

Decompose and mapEvidence: DocumentedPrimary technique, runs in step 5.3Strongest statement: describe

What it does

Records which element depends on or supplies which in a square matrix, then reorders it to reveal clusters or sequence. Artefact: a reordered matrix; read clusters, coupled blocks and the elements affected by a change.

When to use it

Use when a system has many interdependent parts and you need to see clusters, coupled blocks or the parts affected by a change.

When it does not fit

Reordering never produces clusters or a stable order, which suggests the elements are defined at the wrong granularity.

Result format

The result is a square matrix of the elements recording which depends on or supplies which, reordered so that clusters or sequence show. It names the clusters, the coupled blocks, and the elements affected by a change.

Requirements on the material

PropertyRequirement typeRequirement
Content typeAlways appliesrequires=tabular; requires=network
Unit of analysisAlways appliesrequires=topic
Level of detail availableAlways appliesrequires=aggregate tables
Appraises source credibilityApplies in some casesno

Not restricted on: Structure, Variable types, Time structure, How the sample was chosen, Number of sources, Whether sources can be joined, Amount of material, Known data problems, Producer interest, Source dependence, Origin, Document genre, Language, Personal information, Security classification, Licence.

Minimum materialAt least 8 elements and the directed links between them.
Additional sources needednone
Not for (rules)none
Not for (text)Reordering never produces clusters or a stable order, which suggests the elements are defined at the wrong granularity.

Choosing and ordering

Kind of techniquePrimary technique, runs in step 5.3
Phase taganalyse
Other phase tagsframe
Kind of findingpattern; risk
Question answeredwhat
Strongest statement it supportsdescribe
Needs as input
Makes as output
Must exist firstNone
Loop targetreturn to analyse

Library checks by stakes

Each stakes level includes the checks of the level below it. Checks that need a person apply at high stakes only, so the process leaves them out at lower stakes (decision 38). Repeatability: repeatable with fixed settings.

StakesCheckPerson involvedCounts as a different method
exploratoryinput validationnoneno
decision-informinginput validationnoneno
decision-informingspot checkoptionalno
decision-informingsensitivity analysisnoneno
high-stakesinput validationnoneno
high-stakesspot checkoptionalno
high-stakessensitivity analysisnoneno
high-stakesindependent reviewneededno
high-stakessecond technique with different assumptionsnoneconditional

Failure modes and limits

Model suitabilitymodel plus code
Typical model failureReorders the matrix by hand or by reading and mislabels dependencies, instead of running a reordering algorithm in code.
Error sourcesinput data; data transformation; statistical assumptions
Certainty limitsMinimising feedback works for binary matrices but not always for numeric ones; the result depends on how elements are defined and on the reordering method.

Evidence and tag basis

Documented. Origin traced to Steward in the 1960s; minimising feedback works for binary matrices but not always for numeric ones. (Wikipedia, Design structure matrix)

Tag basis: input profile inference; selection inference; sequencing inference; robustness inference. All tag values are inference unless a source is named.