Appendix I. Influence Diagrams

This book contains many examples of influence diagrams. The idea of influence diagrams is taken from Gerald Weinberg's excellent Quality Software Management series, particularly Book 1: Systems Thinking.[1] The purpose of an influence diagram is to see how the elements of a system affect one another.

[1] Weinberg, Gerald. 1992. Systems Thinking. Quality Software Management. New York: Dorset House. ISBN: 0932633226.

Influence diagrams have three elements:

  • Activities, notated as a word or short phrase

  • Positive connections, notated as a directed arrow between two activities; meaning that more of the source activity tends to create more of the destination activity, or less of the source activity tends to create less of ...

Get Test Driven Development: By Example now with the O’Reilly learning platform.

O’Reilly members experience live online training, plus books, videos, and digital content from nearly 200 publishers.