Differences

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

--- training:block_diagrams [2016/02/29 03:28]
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 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.
+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
+  * **Look through some of the [[ .:block diagram examples:start]]**
-  * **Include enough text to give your audience context**
+    * Which one is closest to what you're trying to aim for?
-    * Label communication types or voltage/current measurements
+    * Do any of them fit what you're trying to describe?
-  * **Make sure that you're representing things correctly**
+    * Look through the other project's presentations to look at their block diagrams
-    * Is there a chance for misintrepretation?
+  * **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 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 =====
@@ Line 27: / Line 43: @@
   * Powerpoint
   * Google Presentations
-  * Draw.io
+  * [[ https://www.draw.io/ | Draw.io ]]
 ===== Reading =====
-  * https://en.wikipedia.org/wiki/Block_diagram
+  - https://en.wikipedia.org/wiki/Block_diagram
-  * https://www.smartdraw.com/block-diagram/
+  - https://www.smartdraw.com/block-diagram/
-===== Examples =====
-  * [[ .:Block Diagram Examples:start]]
-  * http://cdn.upverter.com/static/blog/blockdiagram.jpg