Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
training:block_diagrams [2016/02/29 01:55] kluong |
training:block_diagrams [2016/11/16 20:05] kluong |
||
---|---|---|---|
Line 1: | Line 1: | ||
====== Block Diagrams ====== | ====== Block Diagrams ====== | ||
+ | Block diagrams are important to display information in a visual way to an audience. Block diagrams are typically used for higher level, less detailed descriptions that are intended to clarify overall concepts without concern for the details of implementation. | ||
- | Block diagram guidelines. | + | Contrast this with the schematic diagrams and layout diagrams used in electrical engineering, which show the implementation details of electrical components and physical construction. |
- | Tools: | + | ===== Workflow ===== |
- | * Word | + | Depending on what you're trying to describe the specific elements can be different but here are some points you should follow: |
- | * Google Draw | + | |
- | * Powerpoint | + | |
- | * Google Presentations | + | |
- | * Draw.io | + | |
- | ===== Guides ===== | ||
- | * https://www.smartdraw.com/block-diagram/ | + | * **Figure out what information you want to convey to the audience** |
+ | * Do you even need a block diagram? Why? | ||
+ | * Are you describing the overall system? | ||
+ | * Are you describing an algorithm? | ||
+ | * Are you describing a workflow? | ||
+ | * Do you need multiple block diagrams? | ||
- | ===== Examples ===== | + | * **Look through some of the [[ .:block diagram examples:start]]** |
+ | * Which one is closest to what you're trying to aim for? | ||
+ | * Do any of them fit what you're trying to describe? | ||
+ | * Look through the other project's presentations to look at their block diagrams | ||
- | * http://cdn.upverter.com/static/blog/blockdiagram.jpg | + | * **Outline the blocks that you need to describe** |
+ | * What are your blocks going to be in this case? Hardware components? Libraries? Software States? | ||
+ | * What are the connections between your blocks? | ||
+ | |||
+ | * **Get comments/feedback early and revise** | ||
+ | * Do not work on this the night before | ||
+ | * It's important to get some feedback from either the leadership team or another team | ||
+ | * Look at something else and come back to the block diagram after a while | ||
+ | |||
+ | ===== Functional Block Digram ===== | ||
+ | |||
+ | Functional block diagrams describe what your system is doing. | ||
+ | |||
+ | ===== Tools ===== | ||
+ | |||
+ | Listed below are some tools that you can use to design your block diagram. Regardless of the tool you use, the content should be first on your priority list - try and few tools and see if they can help you achieve the objective that you want. | ||
+ | |||
+ | * Word | ||
+ | * Google Draw | ||
+ | * Powerpoint | ||
+ | * Google Presentations | ||
+ | * [[ https://www.draw.io/ | Draw.io ]] | ||
+ | ===== Reading ===== | ||
+ | - https://en.wikipedia.org/wiki/Block_diagram | ||
+ | - https://www.smartdraw.com/block-diagram/ | ||
- training/block_diagrams.txt
- Last modified: 2021/09/19 21:59
- (external edit)