Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision |
| ece4011:main [2017/12/02 23:21] – [Plan Visuals] pvela | ece4011:main [2023/03/06 10:31] (current) – external edit 127.0.0.1 |
|---|
| ------------------------ | ------------------------ |
| |
| While Gantt charts are nice, they can be far too detailed while at the same time missing important aspects of the best way to execute the construction process. Additionally, Pert charts are easy to make without thinking too deeply about what is an effective execution strategy for the team. Both of these charts are easy to draft up in a very generic form that hide all of the important parts of the design process/timeline. That makes the documents pretty useless as guides to follow. | While Gantt charts are nice, they can be far too detailed while at the same time missing important aspects of the best way to execute the construction process. Additionally, Pert charts are easy to make without thinking too deeply about what is an effective execution strategy for the team. Both of these charts are easy to draft up in a very generic form that hide all of the important parts of the design process/timeline. That makes the documents pretty useless as guides to follow. The typical charts remind me of the PhD Comics strip on drafting a [[http://phdcomics.com/comics/archive.php?comicid=715|thesis outline]]. The outline is so generic as to be uninformative. A good outline gives a strong sense for what will be done. The design chart documents need to do the same. |
| | |
| I advocate creating a few additional planning documents that precede the Gantt and Pert charts. These documents are visual and textual summaries of the proposed design solution. There are two basic additional charts that I always recommend since they really expose what the design process will require. | |
| |
| | The best way to proceed is to actually have multiple documents that go from the high level and descend to the low level. The high level would be the //manager// equivalent and promote rapid identification of the overall design and its components. The low level is the //engineer// equivalent and gets closer to the day-to-day or week-to-week details. I advocate creating a few additional planning documents that operate at the higher level and precede the Gantt and Pert charts. These documents are visual and textual summaries of the proposed design solution. There are two basic additional charts that I always recommend since they really expose what the design process will require. |
| ==== Device Block Diagram ==== | ==== Device Block Diagram ==== |
| |
