Differences

This shows you the differences between two versions of the page.

--- training:block_diagrams [2016/02/29 02:51]
kluong
+++ training:block_diagrams [2021/09/19 21:59] (current)
@@ Line 1: / Line 1: @@
 ====== Block Diagrams ======
-Block diagrams are important to display information in a visual way to an audience. Block diagrams have the potential to display more information in a more condensed form that just text alone.
+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.
+Contrast this with the schematic diagrams and layout diagrams used in electrical engineering, which show the implementation details of electrical components and physical construction.
+===== Workflow =====
 Depending on what you're trying to describe the specific elements can be different but here are some points you should follow:
   * **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?
-    * You may need multiple block diagrams in your presentation, or you might need less.
+    * Do you need multiple block diagrams?
-  * **Make sure you outline relationships well**
-    * For hardware - how are the hardware components interconnected?
-    * For software - you might be describing how your program logically flows from one state to another
-  * **Include enough text to give your audience context**
-    * Label communication types or voltage/current measurements
-  * **Make sure that you're representing things correctly**
-    * Is there a chance for misintrepretation?
-  * **Get comments/feedback early and revise**
-Here are a few tools you can use:
+  * **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
-  * Word
+  * **Outline the blocks that you need to describe**
-  * Google Draw
+    * What are your blocks going to be in this case? Hardware components? Libraries? Software States?
-  * Powerpoint
+    * What are the connections between your blocks?
-  * Google Presentations
-  * Draw.io
-===== Guides =====
+  * **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
-  * https://www.smartdraw.com/block-diagram/
+===== Functional Block Diagram =====
+Functional block diagrams describe what your system's functions are and not necessarily how it's implemented. They very concisely describe the behavior of your system and is a good primer to describe your design.
+===== Tools =====
-===== Examples =====
+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.
-  * http://cdn.upverter.com/static/blog/blockdiagram.jpg
+  * 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/