Difference between revisions of "System Overview Diagram"
From EUDP
Line 1: | Line 1: | ||
== What == | == What == | ||
+ | A overview in blocks of the system-to-be. | ||
== How == | == How == | ||
Line 6: | Line 7: | ||
'''The dish''' | '''The dish''' | ||
− | A | + | A diagram showing the system at-a-glance. |
'''Ingredients''' | '''Ingredients''' | ||
− | * | + | * [[Rich Picture]] |
+ | * [[System Definition]] | ||
'''Process''' | '''Process''' | ||
+ | |||
+ | The Rich Picture shows basically the environment that system-to-be should operate within and the system-to-be is '''not''' a part of the Rich Picture. | ||
+ | |||
+ | In order to make the first overview of the system-to-be the interfaces that the system needs can be found in the Rich Picture. | ||
+ | |||
+ | From the System Definition the functionality can be determined. | ||
+ | |||
+ | Compose a diagram using squares to indicate a block that isolates related functionality. Do '''not''' at all think how the functionality can be implemented. | ||
+ | |||
== Why == | == Why == |
Revision as of 10:34, 11 August 2010
What
A overview in blocks of the system-to-be.
How
The dish
A diagram showing the system at-a-glance.
Ingredients
Process
The Rich Picture shows basically the environment that system-to-be should operate within and the system-to-be is not a part of the Rich Picture.
In order to make the first overview of the system-to-be the interfaces that the system needs can be found in the Rich Picture.
From the System Definition the functionality can be determined.
Compose a diagram using squares to indicate a block that isolates related functionality. Do not at all think how the functionality can be implemented.
Why
Example
An example will be presented later. Please return to this page later.