Next: , Up: The Dezyne Modeling Language   [Contents][Index]


3.1 System Decomposition

As an illustration, below a picture of a system with four parts where the loader loads raw input into a machine, the processor transforms the raw input into the final product and the output part moves the product out of the machine and the complete process is controlled by the controller.

                         [Controller]
                              |
         ---------------------------------------------
         |                    |                      |
     [Loader]            [Processor]             [Output]

Software development using Dezyne is component based, meaning that the system parts are components

To illustrate this, in the interaction diagram below the component called "Application" requests the component "ProtocolStack" to activate itself, by sending the enable event to the "ProtocolStack" component. The ProtocolStack responds synchronously with a "reply", either a void reply or a value returned as result of the enable.

 [Application]    [ProtocolStack]
      |                     |
      |       enable        |
      |-------------------->|
      |      "reply"        |
      |<- - - - - - - - - - |

Events have a direction. The direction is determined as seen from the component providing the service. For the Server component in this example the enable event is an in event.


Next: , Up: The Dezyne Modeling Language   [Contents][Index]