Difference between revisions of "Blockdiagram"
From EUDP
(Created page with "A blockdiagram, as the name implies, contains blocks. Before drawing a blockdiagram, one needs an overview of the required functionality in the collection of blocks (that wou...") |
|||
(2 intermediate revisions by one other user not shown) | |||
Line 1: | Line 1: | ||
A blockdiagram, as the name implies, contains blocks. | A blockdiagram, as the name implies, contains blocks. | ||
− | Before drawing a blockdiagram, one needs an overview of the required functionality in the collection of blocks | + | Before drawing a blockdiagram, one needs an overview of the required functionality in the collection of blocks that would be the system-to-be. |
The principal parts or functions, in the system-to-be, are represented by blocks connected by lines, that show the relationships of the blocks. | The principal parts or functions, in the system-to-be, are represented by blocks connected by lines, that show the relationships of the blocks. | ||
Line 8: | Line 8: | ||
In order to draw a block diagram, follow these simple rules : | In order to draw a block diagram, follow these simple rules : | ||
− | * Name | + | * Name blocks meaningful |
* Inputs are on the left, outputs are on the right | * Inputs are on the left, outputs are on the right | ||
− | * Higher abstraction are on top, lower in the bottom, | + | * Higher abstraction are on top, lower in the bottom, if this is possible to distinguish |
** For example physical hardware blocks will be drawn in the bottom, and the user application will drawn on the top | ** For example physical hardware blocks will be drawn in the bottom, and the user application will drawn on the top | ||
Line 19: | Line 19: | ||
{| class="wikitable" | {| class="wikitable" | ||
|- | |- | ||
− | ! [[File:bd1.png|300px] !! [[File:bd2.png|300px]] !! [[File:bd3.png|300px]] | + | ! [[File:bd1.png|300px]] !! [[File:bd2.png|300px]] !! [[File:bd3.png|300px]] |
|} | |} |
Latest revision as of 09:00, 15 July 2015
A blockdiagram, as the name implies, contains blocks.
Before drawing a blockdiagram, one needs an overview of the required functionality in the collection of blocks that would be the system-to-be.
The principal parts or functions, in the system-to-be, are represented by blocks connected by lines, that show the relationships of the blocks.
Block diagrams can represent both Hardware, Software or Mechanical engineering.
In order to draw a block diagram, follow these simple rules :
- Name blocks meaningful
- Inputs are on the left, outputs are on the right
- Higher abstraction are on top, lower in the bottom, if this is possible to distinguish
- For example physical hardware blocks will be drawn in the bottom, and the user application will drawn on the top
A few examples: