Design structure matrix: Difference between revisions

Revision as of 00:14, 3 April 2015

Revision as of 08:06, 9 April 2015

Line 14:

* 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."] 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"/>