![]() ![]() ![]() Readers - Represent ways a project can be read. ![]() Note: The arrow diagram looks simpler also due to the fact that I transitively reduced it. In small graphs like the above the difference is really subtle, but the more complex the project gets the easier it is to read its arrow diagram compared with its node diagram. Using a node diagram we could represent it like this:Īnd with an arrow diagram it would look like this: For more information and a quick overview of the tools and approaches I use you can read my post about working with graph data structures in. In this project I rely heavily on the great library QuickGraph. After a couple of hours wasted, I decided spending that time on writing a tool to generate such diagrams would be a more reasonable investment. I came across a project I wanted to draw a diagram for, it had 76 activities, and I failed to complete the diagram regardless of how hard I tried. The problem is that for small projects (with a few dozen activities) it is a time consuming effort, while for big projects (> 80 activities) it becomes a real challenge. With arrow diagrams, the activity is the edge and nodes represent events (like the start/end events of the activities).įollowing the guidance of IDesign's project design methods, I have come to appreciate the arrow diagram as a tool to visualize and understand the forces that operate within a project and its activity dependencies. The difference is that in a node diagram every node is an activity and an edge is a dependency. Representing the dependency tree of activities within a project is better done with arrow diagrams compared to node diagrams (Which is how MS-Project draws them). ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |