Design structure matrix: Difference between revisions

Revision as of 15:37, 13 January 2020

Latest revision as of 09:43, 17 June 2025

(14 intermediate revisions by 12 users not shown)

Line 1:

{{Short description|Decision tracking and managing method}}

[[File:A sample Design Structure Matrix (DSM).png|273x193px|framed|right|A sample DSM with 7 elements and 11 dependency marks.]]

The '''design structure matrix''' ('''DSM'''; also referred to as '''dependency structure matrix''', '''dependency structure method''', '''dependency source matrix''', '''problem solving matrix (PSM)''', '''incidence matrix''', '''''N²'' matrix''', '''interaction matrix''', '''dependency map''' or '''design precedence matrix''') is a simple, compact and visual representation of a system or project in the form of a square [[matrix (mathematics)|matrix]].<ref name="DSMbook">S.D. Eppinger and T.R. Browning, [http://mitpress.mit.edu/books/design-structure-matrix-methods-and-applications Design Structure Matrix Methods and Applications], MIT Press, Cambridge, 2012.</ref>

It is the equivalent of an [[adjacency matrix]] in [[graph theory]], and is used in [[systems engineering]] and [[project management]] to model the structure of complex systems or processes, in order to perform system analysis, project planning and organization design. [[Don Steward]] coined the term "design structure matrix" in the 1960s,<ref>D. V. Steward: ''The Design Structure System: A Method for Managing the Design of Complex Systems.'' In: ''IEEE Transactions on Engineering Management.'' 28(3), 1981, S. 71-74.</ref> using the matrices to solve mathematical systems of equations.

== Overview ==

Line 13 ⟶ 14:

* The presentation is amenable to matrix-based analysis techniques, which can be used to improve the structure of the system.

* In modeling activities precedence it allows representing feedback linkages that cannot be modeled by [[Gantt chart]]/[[Program evaluation and review technique|PERT]] modeling techniques <ref>Browning TR, Fricke E, Negele H (2006) [http://sbuweb.tcu.edu/tbrowning/Publications/Browning%20Fricke%20Negele%20(2006)--Process%20Modeling%20Concepts.pdf "Key Concepts in Modeling Product Development Processes"], Systems Engineering, 9(2):104-128</ref>

DSM analysis provides insights into how to manage complex systems or projects, highlighting [[information flow]]s, task/activities sequences and [[iteration]].<ref name="DSMbook"/><ref name="complex">Yassine A, Braha D (2003),[http://necsi.edu/affiliates/braha/CERA.pdf "Complex Concurrent Engineering and the Design Structure Matrix Approach."] {{Webarchive|url=https://web.archive.org/web/20170829135538/http://necsi.edu/affiliates/braha/CERA.pdf |date=2017-08-29 }} Concurrent Engineering: Research and Applications, 11(3):165-177</ref> It can help teams to streamline their processes based on the optimal flow of information between different interdependent activities.

DSM analysis can also be used to manage the effects of a change. For example, if the specification for a component had to be changed, it would be possible to quickly identify all processes or activities which had been dependent on that specification, reducing the [[Risk management|risk]] that work continues based on out-of-date information.<ref name="DSMbook"/>

Line 21 ⟶ 20:

A DSM is a [[square matrix]], representing linkages between the system elements. The system elements are often labeled in the rows to the left of the matrix and/or in the columns above the matrix. These elements can represent for example product components, organization teams, or project activities.

The off-diagonal cells are used to indicate relationships between the elements. A marking of the cell indicates a directed link between two elements and can represent design relations or constraints between product components, communication between teams, information flow or precedence relations between activities. In one convention, reading across a row reveals the outputs that the element in that row provides to other elements, and scanning a column reveals the inputs that the element in that column receives from other elements. For example, in the DSM, the marking in rowcolumn A and columnrow C indicated a link from A to C (output from A, input to C). Alternatively, the rows and columns may be switched (without a change of meaning). Both conventions may be found in the literature.<ref name="DSMbook"/>

The cells along the diagonal are typically used to represent the system elements. However, the diagonal cells can be used for representing self-iterations (e.g., rework of a code that did not pass its unit testing). Self-iterations are required when a matrix element represents a block of activities/subsystems that may be further detailed, allowing hierarchical DSM structure.<ref>A. Karniel and Y. Reich, [https://www.researchgate.net/publication/4255493_Simulating_Design_Processes_with_self-iteration_activities_based_on_DSM_planning “Simulating Design Processes with self-iteration activities based on DSM planning,”] in Proceedings of the International Conference on Systems Engineering and Modeling - ICSEM'07, Haifa, 2007. </ref>

Line 33 ⟶ 32:

===DSM marking===

Initially, the off-diagonal cell markings indicated only the existence/non-existence of an interaction (link) between elements, using a symbol (or the figure '1'). Such marking is defined as '''Binary DSM'''. The marking then has developed to indicate quantitative relation '''Numeric DSM''' indicating the "strength" of the linkage, or statistical relations '''Probability DSM''' indicating for example the probability of applying new information (that require reactivation of the linked activity).<ref name{{CN|date="complex"/>October 2021}}

==DSM algorithms==

The DSM algorithms are used for reordering the matrix elements subject to some criteria. Static DSMs are usually analyzed with [[Cluster analysis|clustering algorithms]] (i.e., reordering the matrix elements in order to group together related elements). Clustering results would typically show groups (clusters) of tightly related elements, and elements that are either not connected or are connected to many other elements and therefore are not part of a group.<ref name="DSMbook"/>

Time-based DSMs are typically analyzed using partitioning, tearing and sequencing algorithms.<ref name="DSMbook"/><ref name="complex"/><ref>A. Karniel and Y. Reich, [https://link.springer.com/chapter/10.1007%2F978-0-85729-570-5_3 "Design process planning using DSM"], in Managing the Dynamics of New Product Development Processes: A New Product Lifecycle Management Paradigm, Springer, 2011 </ref>

'''Sequencing''' methods try to order the matrix elements such that no feedback marks remain.<ref name="DSMbook"/><ref name="complex"/> In case of coupled activities (activities that have cyclic links, e.g., activity A is linked to B, which is linked to C, which is linked to A) the results is a block diagonal DSM (i.e., blocks or groups of coupled activities along the diagonal). Partitioning methods include: Pathpath Searchingsearching; Reachability[[reachability Matrixmatrix]]; Triangulation[[triangulation]] algorithm; and the powers of the Adjacency Matrix.

'''Tearing''' is the removal of feedback marks (in Binary DSM) or assignment of lower priority (numeric DSM). Tearing of a Component-based DSM may imply modularization (the component design is not influencing other components) or standardization (the component design is not influencing and not influenced by other components).<ref name="DSMbook"/><ref name="complex"/><ref>Sered Y, Reich Y (2006)," Standardization and modularization driven by minimizing overall process effort." Computer-Aided Design, 38(5):405-416</ref> After tearing a partitioning algorithm is (re)appliedreapplied.

Minimizing feedback loops gets the best results for Binary DSM, but not always for Numeric DSM or Probability DSM. '''Sequencing''' algorithms (using [[optimization]], [[genetic algorithms]]) are typically trying to minimize the number of [[feedback loopsloop]]s and also to reorder coupled activities (having cyclic loop) trying to have the feedback marks close to the diagonal. Yet, sometimes the algorithm just tries to minimize a criterion (where minimum iterations is not the optimal results).<ref name="DSMsim">T. Browning: [https://dx.doi.org/10.1109/TEM.2002.806709 "Modeling Impacts of Process Architecture on Cost and Schedule Risk in Product Development"], In: ''IEEE Transactions on Engineering Management.'' 49(4):428-442, 2002.</ref>

==Use and extensions==

Interactions between various aspects (people, activities, and components) is done using additional (non-square) linkage matrices. The Multiple Domain Matrix (MDM) is an extension of the basic DSM structure.<ref>Maurer M (2007) Structural Awareness in complex product design. Dissertation, Technischen Universität München, Germany</ref> A MDM includes several DSMs (ordered as block diagonal matrices) that represent the relations between elements of the same ___domain; and corresponding Domain Mapping Matrices (DMM) <ref>M. Danilovic; T. R. Browning: "[https[doi:10.1016//dxj.doiijproman.org/102006.1007/s10951-009-0131-y "11.003|Managing Complex Product Development Projects with Design Structure Matrices and Domain Mapping Matrices"]]". In: ''International Journal of Project Management.'' 25(3), 2007, S. 300-314.</ref> that represent relations between elements of different domains.

The use of DSM has been extended to visualize and optimize the otherwise invisible information flow and interactions associated with office work. This visualization via DSM allows the Lean Body of Knowledge to be applied to office and information intensive flows.<ref>{{cite book|title=Far From the Factory: Lean for the Information Age|year=2010|publisher=Productivity Press|___location=New York|isbn=978-1420094565|pages=159–180}}</ref>

A customisation of MDM has been illustrated in <ref>{{cite journal |last1=Cardenas |first1=IC |last2=Kozine |first2=I |title=Customizing an Approach to Analyze an Underspecified Socio-Technical System |journal=Engineering Management Journal |date=2025 |volume= |issue= |pages=1–20 |doi=10.1080/10429247.2025.2502690|doi-access=free }}{{Creative Commons text attribution notice|cc=by4|from this source=yes}}</ref> for the analysis of underspecified systems.

The DSM method was applied as a framework for analyzing the propagation of rework in product development processes, and the related problem of convergence (or divergence) using the theory of linear dynamical systems.<ref name="complex"/><ref>Smith R, Eppinger S (1997) “Identifying controlling features of engineering design iteration.” Management Science 43(3):276–293. </ref><ref> Yassine A, Joglekar N, Braha D, Eppinger S, and Whitney D (2003),"Information hiding in product development: the design churn effect." Research in Engineering Design, 14(3): 131-144.</ref>

See (Browning 2016)<ref>Browning, Tyson R. (2016) “Design Structure Matrix Extensions and Innovations: A Survey and New Opportunities,” IEEE Transactions on Engineering Management, 63(1): 27-52.[https://dx.doi.org/10.1109/TEM.2015.2491283]</ref> for a comprehensive, updated survey of DSM extensions and innovations.

==References==

Line 65 ⟶ 62:

*DSM book: http://mitpress.mit.edu/books/design-structure-matrix-methods-and-applications

*{{cite book

| lastlast1 = Karniel

| firstfirst1 = Arie

| last2 = Reich

| first2 = Yoram