Difference between revisions of "Blockdiagram"
From EUDP
| 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 meaningfull |
* 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 | ||
Revision as of 11:07, 27 August 2012
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 meaningfull
- 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:
 |
 |
|
|---|
