lect23_S07 - Robust, Yet Lecture 23 Preview This...

Info iconThis preview shows pages 1–4. Sign up to view the full content.

View Full Document Right Arrow Icon
R obust, Yet Fragile: Gotcha! Engineering 100 J. Daida Based on a seminar entitled “Robust, Yet Fragile,” by J. Doyle, U-M / SFI Fall Workshops, Fall 1999 Lecture 23 Standard Disclaimer: These lecture notes are provided as a SERVICE to you to help you study for this class. At no time are we obligated to provide notes for every lecture. Understand that these notes are NOT a replacement for either coming to lecture or for the class readings. Indeed, these notes represent only a PARTIAL SET, which means it's up to you to attend class (or to find someone else's notes) to fill in the SUBSTANTIAL fraction of the lecture that has been left out of these notes. Indeed, these notes may represent only a draft and may be based on last term's lectures (which may or may not be repeated in their entirety for this term.) If it turns out that attendance to the class drops below 80%, we reserve the right to reduce the amount of content in these notes. If it turns out that attendance to the class drops below 80%, we also reserve the right to discontinue the distribution of these notes either before or after lecture. Copyright: © 2007, Jason M Daida. All Rights Reserved. Preview Background Robustness and Design Robust, Yet Fragile Managing and Structuring Complexity for Robustness Review and Conclusions This lecture—Gotcha!—describes how we design artificial systems to face adversity. Network Dynamic Interconnection Feedback Yes (Positive / Negative) Organization Hierarchical Scale Multiscale Optimal Constituency Heterogeneous Strength/Mode Nonlinear Six Characteristics of Robust Systems & Robust Teams Robust Teams v. Robust Designs Just as a team has robust attributes and structures… …so do the designs themselves…
Background image of page 1

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Complexity Robustness Courtesy of J. Doyle Robust Systems To become more robust, systems need more structures All of these additional structures leads to system COMPLEXITY Courtesy of J. Doyle Complexity Robustness Courtesy of J. Doyle Adversity Adversity An unfortunate event or circumstance ± aradoxica ² y, ³ ot avoiding, ´ u µ mbracin · ¸ dversi ¹ ¸² ows us º ¸ vert eve » ¼ rea ½¾ ¿ raged À Moreover, Adversity can Afford us an Opportunity for Success Courtesy of J. Doyle Adversity Embracing means: Anticipate the Future Model It Accurately Follow Through ± aradoxica ² y, ³ ot avoiding, ´ u µ mbracin · ¸ dversi ¹ ¸² ows us º ¸ vert eve » ¼ rea ½¾ ¿ raged À About “Embracing” Systemic Structure (generative) Patterns of Behavior (responsive) Events (reactive) Leverage Often Comes from New Ways of Thinking
Background image of page 2
Resulting Strategies Reactive System Time scales for cause and effect Generally short time frames Model of future events Generally none Planning No strategy, no plan Consequence for Design Strength Needed for rapid, reflexive response (e.g., reactive systems are helpful in avoiding sudden danger) Weakness Robust design is very difficult, especially if adversity is distributed over
Background image of page 3

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Image of page 4
This is the end of the preview. Sign up to access the rest of the document.

This note was uploaded on 11/07/2010 for the course ME 100 taught by Professor Jasondaida during the Fall '07 term at University of Michigan.

Page1 / 13

lect23_S07 - Robust, Yet Lecture 23 Preview This...

This preview shows document pages 1 - 4. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online